ARTICLE COMPANION

Opportunity and assumptions worksheet

Use this static sheet to prepare a team conversation. It does not score, authorise or implement a change. Record evidence and estimates separately. Keep required safety work and urgent concerns within the site's authorised arrangements.

Worked example: a fictional 4-week allocation

All people, records, figures and decisions are invented. No achieved benefit is supplied. Article 026 explains the discussion.

Capacity, person-hours Ben, planner Asha, engineer Erin, supervisor Team
Available beyond normal duties 10 8 6 24
Held for interruptions 2 2 2 6
Available to plan 8 6 4 18

One hour with all 3 people consumes 3 person-hours. Calendar duration is separate from person-hours. No overtime, extra staff, purchase or system configuration change assumed. All trial participants are within these roles/allowances.

Candidate and scope Fictional baseline evidence Future estimate and calculation Implementation effort, person-hours Key unknowns and dependencies
A. One job family's materials-status handover, including preparation, user trial, review and instructions 24 eligible handovers in that job family over the preceding 4 weeks generated 12 clarification requests, 8 concerning missing materials status. All 8 sought information available at handover. Each request used 20 combined person-minutes. Other 4 excluded. Assume another 24 comparable handovers with similar job mix in 4 weeks and 6–8 materials questions avoided. 6×20 to 8×20 = 120–160 minutes = 2h–2h40. Gross question time avoided before new handover effort; new recording/review time must be deducted in actual evaluation. Ben 5–7, Asha 4–5, Erin 3–4. Sum 12–16. Upper estimate fits each allowance. Comparable workload/job mix; users understand/use the handover; Ben has time to record status; no change to purchasing, stock or release controls. No failure or schedule improvement assumed.
B. Wider equipment-reference reconciliation for a repeat-repair review 5 repair records cannot confidently be linked to equipment entries in another report. Operational value not yet estimated. Links could confirm different equipment; no failure/production benefit established. Ben 6–8, Asha 14–20, Erin 4–8. Sum 24–36. Exceeds total and Asha's allowance even at lower end. Identity checks and report ownership; follow-on investigation scope/effect unknown.
B alternative. Evidence check of those 5 records only, separate scope Same unresolved records. Output: confirmed links, unresolved cases, follow-on scope. No value figure assigned. Ben 2, Asha 3, Erin 1. Sum 6. Fits alone. Not added to A: 16+6=22 >18; Ben 7+2=9 >8, Asha 5+3=8 >6, Erin 4+1=5 >4. Access to source records and knowledgeable staff within the allowance; unresolved cases remain unresolved. No wider fix included.
C. Review-pack copying reduced with existing export; retain source-total/population checks, trial and instructions 60 person-minutes each week in Ben's diary, copying/checking only. Excludes A's clarification minutes. Assume 30–45 minutes/week removed; 15–30 retained. For 4 weeks: 120–180 minutes = 2h–3h. Gross recurring capacity estimate. Ben 8–10, Asha 1–2, Erin 1–2. Sum 10–14. Total fits, Ben's upper estimate 10 >8. Export population/totals must be verified; no accepted scope transfer or narrower version yet.

Ranges are stated planning estimates, not confidence intervals or assigned probabilities. Endpoints are added by role for conservative capacity checks, with no assumed statistical independence. Value ranges overlap; hours are unmonetised staff capacity, salaries unchanged. No score or weighting is used. No benefits may be added without checking overlap and later workload.

Decision in the fictional discussion: Erin and the team accept A's trial because the immediate aim is fewer materials questions during job preparation, its relevant information exists and its upper role estimates fit. Reserve up to 16 hours for A, leaving 2 planned hours unallocated (Ben 1, Asha 1, Erin 0 at the upper estimate), plus the separate 6-hour reserve. The 16-hour allowance already includes review and instructions; don't add the review again.

Ben prepares the example; Asha checks the records and comparison; Erin makes sure Ben has time to record materials status and accepts trial conditions. All check their own estimates. Review in 4 weeks: actual eligible handovers against the baseline 24, questions, response effort, new recording/review effort, job mix and receiving person's judgement. No mechanical pass/fail threshold. Erin and the team accept whether to continue, change or stop. If actual effort threatens capacity, return to Erin before expanding scope or consuming reserve. No trial has occurred in this article.

Deferred C may release more time but has no agreed solution for Ben's upper effort. Deferred B leaves the repeat-repair review limited by unresolved equipment links. Revisit both in 4 weeks; urgent evidence escalates sooner through existing arrangements. Technical and operating decisions stay with authorised owners.

Blank conversation sheet

Audience: planner or reliability engineer preparing with the affected users and accountable decision owner. Output: an accepted next step with honest limits and a review commitment.

  1. Question and window. Which decision is needed? What outcome matters now? What dates/workload does the comparison cover? Which duties or requirements follow a separate authorised route?
  2. Capacity by person. Named role/person; available hours beyond normal duties; interruption allowance; hours available to plan; who accepts that allowance. Count all participants, meetings, acceptance, training and review. Check calendar availability as well as total effort.
  3. Observed evidence for each idea. Dated record pointers, population, sample selection, counts and actual effort. Who checked them? What is missing? Keep sensitive records in approved storage; use pointers here under the organisation's rules.
  4. Proposed scope. What will be delivered? What is excluded? Who must contribute? Existing access, technical approvals, tools, dependencies and unfulfilled conditions.
  5. Effort estimate by role. Low/high person-hours for preparation, implementation/trial, user checking, instructions and review. State who supplied each range and why; expose tasks shared with another proposal. Don't add overlapping effort twice.
  6. Value estimate. Type of benefit, unit and period; formula; baseline; assumed effectiveness; new recurring work to subtract; overlap with another idea. Keep unknowns visible. Separate released capacity, avoided payments, total expenditure and modelled operational value. No automatic conversion of hours to cash.
  7. Sensitivity and consequences. What happens at the upper effort or lower benefit? Which person becomes unavailable? What must be learned before a larger commitment? What happens if the idea waits?
  8. Team decision. Chosen next step, accepted assumptions, named accountable owner and authority, contributors' agreement, reasons for choosing and deferring. If a score is used, document criteria, weights, meaning and override reasons. It is a discussion aid.
  9. Acceptance and return. Who prepares, checks, authorises and reviews? Date or trigger for returning. Evidence needed to continue/change/stop; actual effort and net effect; unresolved questions. New technical/operating authorisations remain separate.

Optional AI preparation is a proposal: supply only the permitted evidence, assumptions and time allowances; ask for a comparison or sensitivity calculation with unknowns preserved. A person checks record links and arithmetic, contributors accept estimates and the authorised team makes the decision. This sheet has no live assistant or integration.