How it works
The request lifecycle
A request has twelve statuses. The arrows are the only moves the code allows; anything else is refused. The colour of an arrow says who usually makes the move.
Diagram 2. Every status and every allowed move. Delivered and Cancelled are final. Proposed goes to Intake or Cancelled. Intake to Queued or Cancelled. Queued to In production or Cancelled. In production to QA failed, Internal review or back to Queued. QA failed to Queued or Cancelled. Internal review to Client review, Revision, Queued, or Cancelled for a free sample only. Client review to Approved, Revision or Cancelled. Revision to Queued. Approved to Published or Delivered. Published to Delivered. Delivered and Cancelled are final.
| Move | Who | When |
|---|---|---|
| Proposed → Intake / Cancelled | Client approver | Accepts or declines a request the weekly results job proposed. The job also expires it after 14 days, and the team may withdraw it. |
| Intake → Queued | Pipeline | A client's brief is taken on at once; a sweep picks up any still in Intake after 5 minutes. A request the team creates starts in Queued. |
| Queued → In production | Pipeline or team | The pipeline starts it when every check passes; a strategist can press Produce. |
| In production → Queued | Pipeline | The run failed. It is retried once automatically. |
| In production → Internal review / QA failed | Pipeline | The QA gate settled the version: something passed or was held (Internal review), or nothing passed (QA failed). |
| QA failed → Queued / Cancelled | Team | Re-queue with a reason, or cancel. |
| Internal review → Client review | Team (reviewer) | A reviewer approves. The pipeline sends the version to the approvers the moment every piece of it is decided. |
| Internal review → Revision / Queued | Team | Send back for changes, or re-queue with a reason. |
| Client review → Approved / Revision / Cancelled | Client approver | Approve, request changes, or decline every piece. |
| Revision → Queued | Pipeline | The re-run with the steer starts, after a reviewer's re-run or the client's request for changes. |
| Approved → Published | Team (admin) | Published to Google Ads. |
| Approved → Delivered | Pipeline | Closed once the client approved every approved piece and nothing is waiting to publish. |
| Published → Delivered | Team (strategist) | Closed from the request page once published work is done; the pipeline does not close published requests by itself. |
A free sample makes one extra move: from Internal review it closes as Cancelled once the prospect has decided each piece. Work never makes that move.