Static worksheet, supplied for review. Original MDP design. No app, automated transfer or live integration. All completed entries below are fictional.
For a planner preparing a maintenance review, with an analyst checking calculations and a supervisor accepting follow-up within their authority.
Inputs: agreed review question, versioned evidence pack, source/order IDs, draft statement, supporting or conflicting observations, checked calculation, action-owner agreement and authorisation boundaries.
Output: a record of an accepted, corrected or unaccepted draft; an owned preparation action; and evidence needed for human acceptance at the next review.
Assumptions: records may be used in the organisation's accepted environment; reviewers can reach the original evidence; status labels and date rules have been agreed; this worksheet grants no operational authority. Keep the worksheet with the organisation's accepted records, using its access and retention arrangements.
Completed fictional example
| Field | Entry |
|---|---|
| Review and decision question | 9 Nov 2026: what preparation check does WO-1601 need before the schedule discussion? |
| Preparation owner | Priya, planner; Alex checks the calculation |
| Pack position | A: 6 Nov 2026, 16:00; B1: Dan's check, 6 Nov at 15:00 |
| Draft claim | Both seal jobs are delayed by late suppliers |
| Supplied evidence | A says Waiting materials and kit not confirmed; B1 says specified kit received 4 Nov, in stores, no reservation recorded |
| Review finding | Late delivery unsupported; WO-1601 and WO-1602 require separate questions |
| Accepted wording | Kit in stores per B1, no reservation recorded; Priya and Dan to check reservation and current preparation position |
| Still unknown | Why reservation missing; remaining readiness, crew, access and work authorisations |
| Interpretation checked by | Priya checked the draft against A and Dan's B1; further kit/reservation verification remains follow-up |
| Accepted preparation action | Dan verifies specified kit and supplies receipt/reservation evidence; Priya then checks preparation record |
| Authorisation and acceptance | Helen accepts preparation follow-up only; other decisions retain site authorities |
| Action owner / due | Dan / 10 Nov 2026, 12:00; Dan accepts the task/deadline and Priya accepts her review step in the fictional meeting |
| Completion evidence expected | Traceable receipt and reservation position for the specified kit; Priya's check |
| Next review / acceptance owner | 16 Nov 2026 / Helen checks references and remaining position |
| Invented follow-up C1 | Dan supplied receipt/reservation reference on 10 Nov; Priya's check recorded; no crew/access/execution evidence supplied |
| Acceptance status | Prepared for Helen's evidence check; overall readiness and schedule approval remain unestablished |
Blank sheet
| Field | Your entry |
|---|---|
| Review / decision question | |
| Preparation owner / calculation checker | |
| Pack version / snapshot / review time | |
| Order / source references | |
| Draft claim or proposed group | |
| Supporting observations | |
| Conflicting / missing observations | |
| Review finding and correction | |
| Accepted wording / unaccepted wording | |
| Still unknown | |
| Interpretation checked by | |
| Accepted preparation action | |
| Decision owner and scope of authority | |
| Action owner acceptance / due time | |
| Evidence needed to close action | |
| Follow-up received / reference / date | |
| Human acceptance of evidence / remaining work | |
| Next review owner / date |
Human acceptance: the relevant specialist checks meaning, the named decision owner accepts the action within their authority, the action owner accepts the work, and the closure owner checks evidence before closing it. A filled cell doesn't establish that those conversations happened.
Proposed future companion: an electronic form could retain pack IDs, corrections and action ownership. Audience, inputs, outputs and acceptance remain as above. Assumptions needing a separate implementation scope include identity, permissions, duplicate actions, version history, failed transfers and access to source evidence. No such form or connection is built here.