Static discussion aid, draft for Jason's review. No live connection, automatic validation or database certification. All completed entries below are fictional.
Worked example
Decision: choose an initial investigation into recurring seal problems on cooling-water pumps A/B, considering disruption where evidence allows. Decision owner: reliability engineer for investigation selection. Maintenance strategy owner accepts any later task change through the site's normal review. Scope: 4 distinct corrective orders reported April–June 2026, confirmed in the fictional checked history to concern separate events. This is an illustrative selection, not a demonstrated complete failure population. Evidence: WO-7101–7104 and an unallocated 11-hour loss entry. No operating exposure supplied.
On smaller screens, scroll the table sideways to read all columns.
| Evidence needed | Usable means | Checked result | Limit on answer | Follow-up owner and proposed review |
|---|---|---|---|---|
| Individual equipment | Reference resolves to A or B at event time | 3 of 4 orders do; CW-SYSTEM doesn't | Can't assign WO-7104 | Equipment-record owner, next joint review |
| Seal-event evidence | Observed symptom/component, traceable to order; separate event checked | A has 2 leakage observations and seal replacements; B's note unspecified; system order says motor replaced | Can't conclude B had no seal events; no established cause | Reliability engineer with completion-note author, next joint review |
| Disruption link | Confirmed equipment and event relationship to source loss record, checked timing and scope | “CW pump”, 11 hours; no verified order links | Can't rank A/B by disruption or allocate 11 hours | Operations record owner, next joint review |
| Rate comparison | Complete event population plus comparable exposure and agreed rules | Not supplied | Can't compare failure rates | Reliability engineer, scope evidence before rate analysis |
| Capture conditions | Person can show task, options, access, time and feedback | Not observed in this example | No explanation for generic codes established | Supervisor and collector, arrange a walkthrough |
Bounded answer: A's 2 documented seal-leakage events warrant an investigation conversation. B's history, one equipment allocation and the loss relationship remain unresolved. No task change or disruption ranking follows from the supplied selection.
Next review: agree an actual date and attendees before using this sheet operationally. “Next joint review” is a proposal, not an assigned live commitment. Retain original records beside any corrections; record who checked them and when. Unknowns remain visible until resolved.
Blank sheet
- Question and decision to be made:
- Decision owner and authority:
- Equipment/location/installed asset scope:
- Population, dates, extract cut-off and what one row represents:
- Source references and access/handling limits:
- Evidence required and usable definition for each field/link:
- Sample inspected, selection method and checks performed:
- What the records establish:
- What remains unknown, including unallocated/excluded records:
- Consequence of each gap for the decision:
- Follow-up task, person, due date and evidence required:
- Capture walkthrough: purpose understood, team expectations, confidence, access/tools, time, feedback that can be acted on:
- Decision accepted by, date and conditions:
- Next review date and what to bring:
Use an approved location for operational records. This sheet requires human checks of identity, event meaning and evidence. A small sample can reveal an obstacle; it doesn't measure the quality of the whole database. Interactive software remains a separate proposal.