STO·SDC · Scope Development & Challenge
Is every discretionary hour earning its place in the window?
Most STO work lists carry hundreds of discretionary items that were never tested with data. STO·SDC runs a two-stage, risk-based challenge on every one, live with your team and a reliability expert panel in the room, so the scope that survives is the scope that belongs.
Challenge the list. Keep what earns it.
The problem
Work lists grow by accretion, not by decision.
Scope lands on the list by habit, by memory of the last event, and by the quiet fear of leaving something off. Very little of it is ever challenged with a documented basis, and the review that should catch it usually happens in a room that keeps no record. Three failures hide there.
Work is carried because it was carried last time, not because a risk or a return was ever stated. The padding inflates cost, duration, and the manpower curve.
Generic failure curves overstate risk on equipment that is nowhere near its wear-out life. More scope is not less risk: unnecessary work introduces its own early-life failures.
Decisions get made in the room and lost the moment it clears. There is no record of what was challenged, what was decided, or why, so nothing is auditable and nothing carries to the next event.
The reliability case
More scope is not safer scope.
Scope challenge gets resisted because it sounds like cutting corners. It is the opposite, and the failure-rate curve is the reason.
Equipment failures cluster at the beginning of a life and again at the end: an early-life region where assembly errors, seal and gasket failures, and contamination shake out, then a long stable middle, then a rising wear-out slope. Opening healthy mid-life equipment does not move it along that curve. It puts it back at the start of it, with fresh early-life risk carried straight into startup.
The goal is optimal scope, not maximum scope. Work belongs in the event where there is evidence of an active mechanism, not where the equipment is simply accessible.
That reframes the whole exercise. This is not cost-cutting, which operations resists. It is reliability discipline, which operations owns.
Every added intrusion carries its own early-life failure risk into startup. That is a cost of scope, and it belongs in the decision beside the hours and the window.
What makes it different
A two-stage, risk-based challenge, with data in the loop.
Every discretionary item runs the same disciplined gate. Required work is logged and exempted; discretionary work has to earn its place twice.
Before and after, not just before
Score the risk if the work is skipped, and the risk if it is done. A severe risk only forces an item in when the work actually reduces it. Work that does not move the risk is sent to Stage 2, because doing it is not justified by the risk.
The value of the risk removed, over the cost
Priced with your real unit economics: daily margin, and the margin lost to a partial rate cut, not just a full shutdown. Above the minimum ratio it belongs in the window; below it, it comes out or moves out.
A bar that rises after the freeze
Once scope is frozen, additions face an escalating hurdle that climbs as the event nears and the growth allowance is spent, so late adds are held to the standard the early list already met.
The difference · 01
A reliability panel in the room, on every item.
A multi-discipline expert panel, fixed equipment, rotating, electrical, instrumentation and SIS, heat transfer, and operations, reads every item against your event premise and sharpens the challenge. It coaches and questions; it never certifies. It issues no SIL determination, no RBI certification, and no fitness-for-service verdict, and never stands in for your integrity program.
Grounded, not generative
The panel reasons only over a retrieved reference pack and your premise, never free-associates a failure mode, and cites a standard only when the pack supports it.
Every gap or opportunity it raises must survive an adversarial review that tries to knock it down. Only findings it cannot refute reach your team.
What it does to a weak item
It separates captured fact from inference, names the failure mechanism the justification is really leaning on, and flags where the basis is too thin to close.
It tests each item against the premise: does this work serve a stated driver, and does it clear your own scope rules.
The difference · 02
The whole team challenges, without corrupting the record.
Scope challenge is a room, not a spreadsheet owner. Everyone joins on a personal code, follows the facilitator’s item live on their own screen, and proposes changes and evidence into a contribution queue. The facilitator accepts, so the register stays clean while the room fills its own fields, planner, operations, process, inspection, and equipment engineers all in at once.
What you get
A frozen, defensible challenge register.
Every discretionary item leaves the session with a recorded disposition, include, defer, eliminate, offload, or reduce, its quantified basis, and the hours and cost it added or removed. The baseline is snapshotted at freeze, and every post-freeze change is governed on the escalating hurdle.
work list
+ panel + room
+ change control
The register is the decision document: each item, its disposition, and the risk-and-cost basis behind it, in priority order. An endorsement package captures the room’s sign-off.
Intake the list by spreadsheet, or pull the scope items straight from a linked schedule via STO·SAR. STO·SDC runs standalone or as the scope engine feeding a STOAR readiness gate.
What changes
The difference before the list locks.
Without STO·SDC
- ×A work list padded with discretionary items no one challenged
- ×Risk argued from opinion and generic curves, in a room that keeps no record
- ×Late additions that never faced the bar the early list did
With STO·SDC
- ✓Every discretionary item challenged on risk and cost, with data
- ✓Scope that survives because it earns its place in the window
- ✓A frozen register that defends every decision and governs every change
Your guide
We have sat in the seat, on both sides of the table.
STO Intelligence is an independent assurance partner, founder-led by 25 years across refining, petrochemicals, and LNG, as the owner accountable for the outcome and as the consultant brought in to protect it.
Our methods stay at public-framework level, API 580/581 risk-based methods, AACE, and PMI, so every finding is defensible and nothing is a black box. You own the standard, not a proprietary score you cannot see inside.
Why STO Intelligence
Empathy for the seat you are in, defending a work list where every item has an owner who wants it in. Authority to challenge it, reliability methods at public-framework level and a founder who has owned the scope call.
Where this goes
One review fixes one event. The system is the prize.
The frozen register carries this event. After the freeze the same discipline continues in STO·PATH, where late additions face a rising bar and every change is a recorded decision, and the STOAR gate reviews assure the whole event on the same record.
Challenge your next work list before it locks.
Send us the discretionary work list for the event you are planning now. We will show you which items earn their place, which come out, and what it takes off the cost and the critical window.