> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/transformations/requirements-view.md).

# Requirements View

### Overview

Requirements View is the primary list view for reviewing scope. A stable view reduces review churn and improves reporting consistency.

### Key Concepts

* **Save View**: stored configuration for repeatable review lists
* **Columns**: fields used for triage and reporting
* **Filters and grouping**: focus reviews by status, owner, process, or segment

### How It’s Used

Use a default Requirements View for weekly scope reviews. Use dedicated Save Views for approval, change control, and delivery readiness.

### Benefits

* Faster triage during scope reviews
* More consistent reporting across Projects
* Reduced rework from inconsistent filtering

### Setup Steps

{% stepper %}
{% step %}

### Open Requirements

Navigate to a Project. Open **Requirements**.
{% endstep %}

{% step %}

### Configure columns

Show fields used for scope reviews. Typical fields include Status, Owner, Process, Priority, and Due date.
{% endstep %}

{% step %}

### Create Save Views

Create Save Views for repeatable reviews, such as `Requirements — In review` and `Requirements — Approved`.
{% endstep %}
{% endstepper %}

### Best Practices

* Keep shared Save Views stable.
* Duplicate shared views before major changes.
* Use consistent naming patterns across Projects.

### Summary

Requirements View standardizes how scope is reviewed. Save Views provide repeatable review lists.

Related:

* [Filtering and Sorting Data](/getting-started/filtering-and-sorting-data.md)
* [Save Views and Templates](/getting-started/save-views-and-templates.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.transform.ai/transformations/requirements-view.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.