> 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-rejection.md).

# Requirements Rejection

### Overview

Not all requirements should be delivered. A clear rejection workflow prevents work on out-of-scope items.

### Key Concepts

* **Rejection reason**: why the requirement is not being delivered
* **Status semantics**: difference between rejected, deferred, and obsolete
* **Downstream impact**: tasks and tests that must be closed or updated

### How It’s Used

Use rejection when scope is explicitly removed. Use deferral when scope remains valid but not in the current phase.

### Benefits

* Reduced wasted effort
* Clearer audit trail for scope decisions
* Cleaner reporting by excluding non-deliverable scope

### Setup Steps

{% stepper %}
{% step %}

### Confirm decision

Record decision rationale in comments. Link supporting artifacts when available.
{% endstep %}

{% step %}

### Set requirement status

Set status to a rejected or out-of-scope state. Use standardized status meanings across Projects.
{% endstep %}

{% step %}

### Close downstream work

Close or re-scope linked tasks and tests. Remove assignments that would continue delivery work.
{% endstep %}
{% endstepper %}

### Best Practices

* Avoid deleting rejected requirements.
* Prefer clear status states for reporting.
* Use a consistent set of rejection reasons in an internal SOP.

### Summary

Requirements Rejection prevents delivery work on removed scope. Status and downstream cleanup keep reporting accurate.

Related:

* [Requirements](/transformations/requirements.md)
* [Status Types and Meanings](/transformations/status-types-and-meanings.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-rejection.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.