# Sample acceptance checklist — Request review workflow

ILLUSTRATIVE ONLY. Proposed checks, not results from a delivered client system. Every check below is NOT RUN.

| ID | Scenario | Expected behavior | Evidence needed | Status |
| --- | --- | --- | --- | --- |
| AC-01 | Submit without a required field | Keep the draft and identify the missing field | Recorded validation result | Not run |
| AC-02 | Submit a valid draft | Show In review and the next responsible role | State transition and activity record | Not run |
| AC-03 | Return without a decision note | Ask for the required note without changing state | Validation and unchanged-state evidence | Not run |
| AC-04 | Revise a returned request | Preserve prior context and show the revised item for review | Revision and activity evidence | Not run |
| AC-05 | Attempt an unauthorized approval | Reject the action at the authorization boundary | Server-side authorization check | Not run |
| AC-06 | Review on supported phone and keyboard | Keep information and permitted actions usable | Device and keyboard review notes | Not run |

## Acceptance decision
Customer acceptance, test execution, unresolved issues and release approval must be recorded separately for a real project.