By Nilesh Gadekar, Founder · Last reviewed .
Read the state together with the next action
A useful handoff lets your team answer four questions: which version is this, what was reviewed, what remains open, and who acts next? A record should make those answers visible without turning every production task into the same “done” label.
The three entries below illustrate different stages in a document workflow. In a real engagement, the record identifies the actual tools and versions, reviewers, technical criteria, task coverage, dates, and supporting logs agreed for that scope.
SAMPLE-001 · Enrollment instructions
| Evidence field | Illustrative entry |
|---|---|
| Document version | enrollment-v2.pdf |
| Review date | 2026-11-02 |
| Review state | Automated checks passed |
| Method and coverage | Automated PDF checks; tool and version belong in the production log |
| Open stage | Human review pending |
| Scope limit or open item | Image descriptions and reading order need human review |
| District owner | District content owner |
| Publication | Not posted |
| Next action | Complete human review before acceptance |
SAMPLE-002 · Board meeting agenda
| Evidence field | Illustrative entry |
|---|---|
| Document version | agenda-v3.pdf |
| Review date | 2026-11-02 |
| Review state | Human review complete |
| Method and coverage | Manual heading, navigation, reading-order and link review; agreed tool checks |
| Open stage | District approval and posting pending |
| Scope limit or open item | Publication has not been verified |
| District owner | Board office |
| Publication | Not posted |
| Next action | District approves and posts the accepted version |
SAMPLE-003 · Nutrition menu
| Evidence field | Illustrative entry |
|---|---|
| Document version | menu-v2.pdf |
| Review date | 2026-11-03 |
| Review state | Published version verified |
| Method and coverage | Reviewed file matched to the published version; agreed manual and tool checks |
| Open stage | Closed for the illustrated version and scope |
| Scope limit or open item | Later content changes require a new version and appropriate recheck |
| District owner | Nutrition office |
| Publication | Illustrative publication field; no live customer URL |
| Next action | Keep the accepted source and record later revisions |
What an acceptance review should check
Match each returned file to the agreed input and version. Confirm that required content questions have been resolved and that the review coverage meets the statement of work. Keep district content approval separate from the technical review. A file awaiting posting should still show that action as open.
When publication verification is included, the record should identify the actual public URL, the version served, the date checked, and the method used to match it to the accepted deliverable. A later re-export, supplement, or replacement does not automatically inherit the earlier result.
Download and discuss the format
Download the fictional sample evidence log (CSV). Each row retains its sample notice when opened separately. For an accessible reading version, use the tables on this page.
Use the project scoping worksheet (plain text) to identify your district’s expected outputs and acceptance questions. The quality guide explains the review stages; Procurement explains how they belong in a purchased scope.