Workflows
Every item on the work list earns its place.
Scope grows because nobody has the evidence to challenge it, and schedules break on the work found late. An Intuigent tests each work-list item against equipment history and as-built topology, attaches the evidence, and builds the execution detail early: isolation points, blind lists, long-lead flags.
Why turnaround scope grows
A work list is a list of claims. Each item claims the work is needed now. Challenging a claim takes evidence: the inspection history, the prior findings, the as-built configuration. Assembling that per item takes days nobody has, so items pass unchallenged and the scope swells.
- Requests outrun evidence. Items arrive from tribal knowledge, an old report, or “while we are in there.” In the scope review, an unchallenged claim survives by default.
- Late discovery destroys the plan. Work discovered after the freeze, or worse, mid-execution, is bought at the cost of schedule and budget. Much of it was knowable: it sat in inspection records and history nobody had time to read.
- The freeze only holds with evidence behind it. A freeze is a promise to the schedule. Items with evidence can be defended when the pressure to add work arrives. Items without it reopen the argument every week.
- Execution detail comes too late. Isolation points and blind lists get enumerated per work item deep into planning, and long-lead materials get identified after they have already become schedule drivers.
None of this is a planning discipline problem. It is an evidence problem: the history exists, but not at the speed the scope process needs it.
The workflow
Every item tested against the record.
The Intuigent works each work-list item against the compiled graph of your plant: the equipment's history, its as-built configuration, and the execution detail the planners will need.
Build the evidence file
For each item, pulls the inspection history, work orders, prior turnaround findings, and operating events on the asset. What supports the item and what undercuts it, side by side.
Test the claim
Checks the item against the as-built topology: the actual service, the actual configuration, sibling equipment in the same duty and its history. Items that survive carry their proof into the scope review.
Enumerate isolation and blinds
For each surviving item, lists the isolation points and blind locations from the as-built graph, cited to the sheets. The execution detail exists when the item enters the scope, not months later.
Flag the long leads
Identifies materials and equipment with long procurement times while the scope is still forming, so the order date is a decision instead of a discovery.
Hold the freeze
After the freeze, every late request faces the same evidence test as the original list, with the file attached for the team that has to say no.
Division of labor
IntuigentDoes the legwork
- Evidence files per work-list item: history, inspections, prior findings
- As-built topology checks on each claim
- Isolation point and blind list enumeration per item, cited to sheets
- Long-lead flags while the scope is forming
- The same evidence test applied to every post-freeze request
Your teamOwns the judgment
- Runs the scope challenge and decides what is in and what is out
- Owns the freeze and defends it
- Plans and sequences the execution
- Approves or rejects late additions with the evidence in hand