Before / manual handling
6h- 01Read scopeLocate measurable items in drawings and schedules.
- 02Build linesCreate estimate rows and map rates.
- 03Check gapsReview assumptions and omissions.
Illustrative workflow / one possible configuration
Prepare traceable quantity and scope candidates while reserving rates, adjustments and estimate approval for the Lead Estimator.
01 / Estimate preparation path
Scope and quantity candidates are prepared separately from unit verification and rate retrieval. Every ambiguity returns to the estimator exception desk, and only the Lead Estimator can set price-bearing fields.
Select a synthetic scenario
Resolve scope, unit or rate gaps
SCOPE_BOUNDARY_AMBIGUOUSA controlled exception is waiting for the named owner. No output has been issued.Primary route first · expand controls only when needed
02 / Value hypothesis
This planning model separates machine preparation from remaining human review. It is not a measured result.
Before / manual handling
6hAfter / controlled preparation
Your volume / adjustable
Illustrative estimate4h 10m × 4 cases × 4.33 weeks, rounded to the nearest hour.
03 / Live estimating run
Run synthetic scope and quantity evidence through boundary, unit and rate controls to generate an estimator review line without silently pricing uncertainty.
P-12ARiser enclosure north wall12.4–15.8 m²
P-12BRiser enclosure east wall18.6 m²
P-12CRiser enclosure south wall17.0 m²
Synthetic drawing note and room schedule
The result will be generated from the visible synthetic rows.
All rows, checks and outputs in this run are synthetic. They demonstrate executable workflow behavior and authority boundaries, not analysis of client documents or measured production performance.
04 / Explicit authority
| Authority | Permission | Operating scope | Status |
|---|---|---|---|
| Model | Draft scope and quantity candidates | Prepare a bounded proposal and cite available evidence. | ✓ May |
| Software | Enforce units, rate versions, duplicates and source links | Enforce deterministic rules, state transitions and action limits. | ✓ May |
| Model | Resolve conflicting source evidence | Conflicts must stop or route to the named human owner. | × May not |
| Human | Set pricing judgments and approve the estimate | Only an authorized Lead Estimator can approve the final artifact. | ✓ May |
The Lead Estimator verifies quantities, chooses or edits rates and approves the estimate artifact.
Unclear scope, unavailable rate versions or unsupported quantities remain unpriced and route to manual measurement.
05 / Decision ledger
This synthetic ledger changes with the scenario. Its final decision event records the same state and reason shown in the workflow canvas.
SCOPE_BOUNDARY_AMBIGUOUS| Event | Actor | Result | Evidence | Time |
|---|---|---|---|---|
| case.received | Intake service | Input hash recorded | SM-EST-008/C-12 | |
| validation.completed | Rules engine | Required fields checked | SM-EST-008/C-12 | |
| exception.detected | Rules engine | SCOPE_BOUNDARY_AMBIGUOUS | SM-EST-008/C-12 | |
| review.requested | Workflow service | Lead Estimator assigned | — | |
| case.review_required | State reducer | SCOPE_BOUNDARY_AMBIGUOUS | — |
06 / Related workflows
01 / Preconstruction
Structure tender requirements, surface submission risks and prepare a controlled qualification record.
Tender invitation, schedules, specifications and amendments → Approved tender review and qualification register
02 / Design coordination
Check drawing packages, surface revision conflicts and issue only a human-approved review record.
Drawing package, schedules and revision register → Approved, evidence-linked review record
03 / Design coordination
Compare bounded requirements with submitted evidence and route every mismatch to a Technical Manager.
Approved specification sections and product evidence → Approved compliance matrix with exceptions
Example set / not a fixed catalogue
The eight detailed examples demonstrate reusable patterns, not the limits of the service. State Method maps the real process around your documents, recurring decisions, system touchpoints and named approval boundaries.
01 / Other processes we can map
02 / Other processes we can map
03 / Other processes we can map
Start with a repetitive process, its evidence and the person who must retain authority. It does not need to match one of these examples.
Assessment / human-reviewed intake
Bound the trade, approved source data, estimator authority and measurable preparation baseline.
Share business context only. Do not submit documents, credentials, confidential architecture, sensitive personal data or client information.