From Capture to Change
Illustrative workflow concept — not a customer deployment.
Capture is not the same as acceptance
A field observation must pass through five stages before it becomes an actionable project record: observe what happened, structure the key facts, confirm with the recorder, review by the accountable role, and incorporate into the controlled workflow.
Why the gap matters
An unexpected condition is discovered. A service is rerouted. A material is substituted. The immediate site problem gets solved—but the reason, exact location, evidence, and review status may remain split across tools. The friction between a field observation and controlled project information is the core problem.
AI proposes structure. People retain authority.
High-confidence fields are prefilled. Medium-confidence fields are highlighted for confirmation. Low-confidence or missing fields remain unresolved. No model output silently becomes an approved record. The atomic unit is not the recording or the BIM model — it is the verified field-change packet.