How it works
Every important decision has a visible state.
Move from captured field information to a saved restoration budget without treating proposed work, approved measurements, or pending prices as the same thing.
A person reviews this decision before the workflow advances.
- 1
Create the job
Start a company-owned claim record with the people and property context the team needs.
- 2
Capture or import the scope
Type, dictate with supported capture, or import available scope records while preserving the source.
- 3
Review structured work
Accept, correct, defer, or reject proposed rooms, areas, surfaces, actions, components, materials, quantities, and units.
- 4
Resolve project questions
Set the budgeting basis, relevant package choices, specifications, and other job-specific decisions.
- 5
Enter or approve measurements
Record calculation evidence and approve only the quantity assigned to the correct area or surface.
- 6
Generate the draft budget
Apply the active company catalog, mapping rules, packages, approved quantities, and valid job-specific prices.
- 7
Resolve the open work
Keep missing prices, mappings, bids, specifications, and stale decisions visible until somebody resolves them.
- 8
Review PM-entered prices
Managers approve or return the exact proposed revision; project managers cannot approve their own entries.
- 9
Approve the budget
Final status is available only when required reviews and blockers are resolved.
- 10
Export the saved revision
Download PDF and spreadsheet outputs tied to the saved scope, budget, and approval record.
A state model people can read
Project manager decisions
Capture and review scope, answer project questions, enter measurement evidence, generate drafts, and propose job-specific prices with reasons.
Management decisions
Approve or return PM-entered price revisions, protect company rules, and approve a budget only after required work is resolved.
Implementation
Early access starts with one real company workflow, roles, pricing sources, packages, review points, and output needs.
Security and data
Company workspaces are separated, access is role-based, and saved revisions retain decision history. Detailed security questions can be reviewed before testing.
Early access
A request begins a fit review; it does not promise immediate acceptance or production readiness for every workflow.