Original practice scenario: A hypothetical energy-site planning application routes a work package for review. The equipment scope changes after approval. Design version and authorization checks.
Read model answer +
Bind an approval to a specific plan version and scope. A historical signature must not silently authorize later changes to the equipment, time window or work description.
Work through it
Model the work package as versioned data with identified reviewers, approved scope and decision timestamps; preserve superseded versions for audit.
Classify which edits invalidate which approvals, rechecking authorization and required reviews before the updated package may be released.
Use optimistic concurrency or another explicit conflict mechanism, with idempotent decision records and tests for simultaneous edits, revocation and expired time windows.
Tradeoffs to discuss
Fine-grained approval reuse avoids repeated review but requires a defensible dependency model; invalidating every edit is simpler while creating more workload.
Common pitfalls
The application should support an approved operational process rather than claim to establish site safety by itself.
Never authorize execution merely because a user opened an approved version earlier.
Original practice scenario: A hypothetical operations dashboard reports that nearly all scheduled inspections passed. Some assets were removed from the schedule after problems were found. How would you redesign the metric?
Read model answer +
Freeze the eligible inspection population and distinguish completion from outcome. A high pass rate among surviving scheduled records can conceal missed or removed work.
Work through it
Create an as-of schedule snapshot with asset identity, due date and explicit cancellation or scope-change reasons, retaining changes rather than deleting rows.
Report completed, passed, failed, overdue and legitimately withdrawn populations separately, reconciling every original scheduled item to one current disposition.
Compare periods using consistent eligibility and maturity rules, reviewing whether withdrawals concentrate in particular asset groups or occur after adverse information arrives.
Tradeoffs to discuss
A fixed population supports accountability but may include genuinely obsolete work; documented scope changes keep that distinction visible.
Common pitfalls
Do not count a cancelled inspection as either a pass or a completed inspection.
An aggregate percentage should not replace the individual overdue or failed cases that require authorized follow-up.
