> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gloo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Requests

> Track change requests as they move through the Forge dogfood delivery lifecycle.

Use **Production → Requests** (`/production/requests`) to follow change requests through the Forge Dogfood Factory's delivery lifecycle. The request is the change being delivered; the associated implementation plans and workflow runs provide the execution context.

![Change requests (light)](https://mintcdn.com/gloo-b243725a/Ndtg9NEpwGc2OULA/forge/images/console/production/requests-light.png?fit=max\&auto=format\&n=Ndtg9NEpwGc2OULA\&q=85\&s=77e4e14b7e00e063a50cf040f584307e)

Change requests — Forge Console at `/production/requests`

## What you can do

* Filter change requests by lifecycle stage. See [Find the request](#find-the-request).
* Inspect a request's description, acceptance criteria, properties and triage notes. See [Inspect a request before acting](#inspect-a-request-before-acting).
* Follow its implementation plan and runs to check progress. See [Verify progress](#verify-progress).

## Find the request

The page opens on **Active**. Choose a filter before interpreting an empty queue:

| Filter | Included statuses |
| - | - |
| **Active** | `pending`, `planned`, `in_progress`, `verification`, `verification_rejected`. |
| **Needs Approval** | `awaiting_approval`. |
| **Completed** | `verified`, `completed`, `won't_do`. |
| **All** | Every returned request. |

A request awaiting approval is intentionally absent from **Active**. A request marked `verified` can appear under **Completed** even before its stored status becomes `completed`.

Each row shows its title and status, with risk, priority, source deployment, external references, and updated time when those values exist. Open the row to inspect the full request.

## Inspect a request before acting

1. Read **Description** and **Acceptance criteria** to establish the requested result.
2. Check **Properties** for risk, priority, and severity.
3. If **Source deployment** is present, confirm the environment and PR context. A preview reference and a production reference describe different evidence.
4. Review **Triage notes** for the reasoning, recorded approver, or rejection reason.
5. Open the associated implementation plan to follow the delivery work. Use external references when you need the linked issue or PR.

The detail is an inspection surface: the presence of an approver's name is a recorded fact, not an instruction to approve the request again. Use the relevant [Approvals](https://docs.gloo.com/forge/console/production/approvals.md) or [My Work](https://docs.gloo.com/forge/console/my-work.md) task when a human decision is waiting on you.

## Verify progress

Return to the list and compare the current status and updated time. To investigate execution, follow the associated plan and inspect [Runs](https://docs.gloo.com/forge/console/production/runs.md); a request's delivery status is not a substitute for the status of an individual workflow run.

| Symptom | Next check |
| - | - |
| **No requests found for this filter** | Switch to **All**, then check whether the request moved to approval or completion. |
| Request detail is unavailable | Reopen it from the current list; the record may no longer be available to your session. |
| A section fails to load | Retry the contained request or implementation-plan region. Other Console navigation remains available. |
| No implementation plan is shown | Check the request's stage and external references before assuming execution has started. |
| A request is waiting for a person | Inspect the relevant approval or assigned task rather than repeatedly launching a run. |

## Key state to watch

* **`awaiting_approval`** — shown under **Needs Approval**, not **Active**.
* **`verification_rejected`** — verification of the change was rejected; the request stays under **Active**.
* **Source deployment** — a preview reference and a production reference are different evidence.

See [Factories](https://docs.gloo.com/forge/console/production/factories) for the production team and [Events](https://docs.gloo.com/forge/console/observe/events) for execution evidence.

## Related surfaces

* [Approvals](https://docs.gloo.com/forge/console/production/approvals.md): requests waiting on a decision.
* [Runs](https://docs.gloo.com/forge/console/production/runs.md): the run a request started.
* [Factories](https://docs.gloo.com/forge/console/production/factories): the production team that delivers requests.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.