Use this with the planner and process owner to choose one repeatable task in a maintenance review. A system owner and data owner join before a connected implementation is accepted. This is a static planning sheet, with an invented example. It stores and sends nothing.
Completed fictional example: WO-2004 information check
| Field | Example |
|---|---|
| Review and decision | Fenbrook weekly planning-information review, 9 November 2026. Agree information checks before the scheduling discussion. |
| Process acceptance owner | Helen, within her fictional delegated authority for preparation actions. Operational work, risk acceptance and scheduling use local arrangements. |
| People checking the pack | Priya prepares and checks source/counts; Dan checks materials meaning. |
| Original inputs | 2 and 9 November exports, both 08:00; agreed “Planning information needed = Yes” filter; accepted-action log. WO-2004 note: “Parts availability not confirmed.” |
| Input identity and version | Pack FEN-2026-11-09-v2; raw v1 retained and superseded after repeated WO-2005. Source system and extraction records must accompany a real pack. |
| Repeatable rule | Compare unique ID sets only after checks pass; retain source references and cut-offs. Previous 3, corrected current 4; 2 remain, 2 enter, 1 leaves. |
| Proposed AI task | Draft counts, referenced observations and questions from the checked pack. Keep unknowns. No cause, urgency, due date or authority inferred. |
| Proposed output | Draft brief with order references and uncertainty; candidate information check; carried-forward actions. |
| Inputs needing a person | What material/part is specified, receipt and reservation evidence, local meaning, owner capacity, authority and due time. |
| Hold conditions and owner | Repeated/missing ID, changed columns, unknown field value, stale/missing export: Priya holds the pack and obtains source-owner correction. Unsupported draft claim: Priya corrects/rejects it. |
| Human acceptance before transfer | Helen accepts exact action wording; Dan agrees to own it; record both with accepted time and evidence version. |
| Accepted fictional wording | Dan to check the specified material and its receipt and reservation position for WO-2004, and return the evidence by 12:00 on Tuesday 10 November. |
| Stable accepted-action reference | A-0201. Keep the same reference for a retry; work-order number alone doesn't identify an action. |
| Receipt / uncertain transfer | Record receiving-register reference and response. If unconfirmed, Priya reconciles in the receiving register before resending. |
| Correction and affected actions | Mark wrong pack superseded; retain old/new versions and reason; alert recipients through agreed process. Helen reviews affected accepted actions with owners before change/cancellation; preserve history. |
| Follow-up and closure | Bring returned evidence beside A-0201 next week. Helen checks it answers the agreed question before closure; a status label alone isn't evidence. |
| Manual fallback | Priya prepares a labelled manual pack with the same definition and checks if a run fails. |
| Proposed trial checks | Compare against manually checked pack; unchanged week, repeated ID, missing export, uncertain transfer/retry, corrected input after acceptance. Measure preparation plus checking/rework effort. |
| Build acceptance | Process owner accepts trial results; system/data owners agree access, retention, permitted AI handling, transfer rules and manual recovery. No connection exists in this example. |
Blank scope
Complete one copy for each task. Keep operational details in your organisation's approved storage and use only the data permitted for the proposed tool.
| Question | Your answer |
|---|---|
| Which review decision will this task support? | |
| Who owns the process and accepts the trial? | |
| What is the exact population, definition and cut-off? | |
| Which original sources, versions and fields are required? | |
| What fixed rule can a person verify? | |
| What may an assistant draft, using which supplied observations? | |
| What output will the checker receive, with which record references? | |
| What remains unknown or needs local context? | |
| Which conditions stop the run, and who resolves each exception? | |
| Who checks the draft, who accepts an action and who agrees to own it? | |
| What exact acceptance record is required before transfer? | |
| What stable action reference and receiving-system receipt prevent duplicate retries? | |
| How will an uncertain transfer be reconciled before resending? | |
| How will corrected evidence reach recipients and affected action owners? | |
| Who may change/cancel an accepted action, and how is history retained? | |
| What evidence and human acceptance close the action? | |
| What happens if the automation isn't available? | |
| Which test cases, effort measures and results will establish acceptance? | |
| Which access/data-handling arrangements must system/data owners accept? | |
| What is explicitly outside this proposed task's authority? |
Acceptance record
- Scope version and review date:
- Process acceptance owner and decision:
- System/data-owner acceptance or open conditions:
- Trial pack versions and results:
- Manual preparation effort, automated preparation plus human checking effort, rework:
- Open issues and named owner:
- Scope accepted / revise / hold, by whom and when:
- Next review:
This worksheet doesn't authorise maintenance, accept risk, commit a schedule or establish that any integration works. Record actual human decisions and verified trial results when they exist.