Compares the construction-set notes against field-marked as-built notes and produces a structured redline log. Each delta carries a type (dimension / equipment / route / elevation / quantity / material), a severity, side-by-side spec ↔ as-built values, location, and a rationale. Persists every delta into asbuilt_redlines so the closeout package has the diff already done.
The construction set leaves the field with red pencil markups on every other sheet: a duct rerouted around steel, an outlet relocated 18", a chiller upsized from 250 ton to 300 ton via change order. By closeout, the redlines need to be reconciled back into the as-built set the owner gets. Most projects do this in a 4-week mad scramble by a junior engineer who didn't see the install.
As-built Reconciler ingests the construction-set notes and the field-marked notes as text and produces a structured redline log: every delta typed (dimension/equipment/route/elevation/quantity/material/other), classified by severity (low/medium/high/critical), with side-by-side spec value vs as-built value, a location reference, and a rationale string. Each row persists to asbuilt_redlines so the closeout package can render the diff without a second pass.
Best practice: reconcile per trade as installation completes. Don't wait for closeout — field memory degrades fast and the foreman who knew why the duct moved is on the next job.
v1 ships with text-based reconciliation. v2 will add drawing-image diff via a CV pipeline so you can upload PDF redlines and get pixel-anchored deltas. For now, the engine works on text the field already records.
Specified values for dimensions, equipment models, routing, materials. Pasted from the spec or extracted from the issued-for-construction sheet notes. One sheet's worth of text per run.
What was actually installed. From the foreman's redline log, the daily log entries describing changes, or the trade's typed as-built narrative.
The engine matches each delta to the sheet it lives on so the redline log carries a sheet reference (M-201, E-401, P-103) for closeout deliverable indexing.
Sample reconciliation output for a mechanical roughed-in floor, comparing construction-set values to field as-built notes:
Structured redline log keyed by sheet, severity-classified, with side-by-side spec/as-built values, location reference, and the rationale (RFI, CO, substitution, field directive) per delta. Closeout Builder consumes these directly for the as-built section of the owner package.
The engine classifies severity using construction-domain rules — not just by magnitude. A 2" dimension shift on a mechanical room is medium; the same 2" on an ADA-clearance corridor is critical.
AHU upsized affects roof loading. Beam moved affects shear path. Anything that triggers a code review or a structural engineer call. Owner sign-off required.
Major duct or pipe reroutes that affect future maintenance access or ceiling-cavity clearance. The facilities team needs to know.
Approved substitutions or dimensional shifts that don't affect access or code. Reported but routine.
Outlet count adjustments, height tweaks for furniture clearance, minor relocations. Documented but no escalation needed.
Each redline links back to the authorizing document — RFI number, CO number, substitution log, field directive, or owner change request.
Critical and high-severity redlines render in the owner's package with full rationale. Medium and low render as summary entries. The owner gets the signal, not the noise.
As-built Reconciler is a tracking-phase engine whose output is consumed at closeout. The data flow is linear: field markup → reconciled log → closeout package.
v2 will add a CV-based pipeline that ingests PDF redlines (the actual marked-up sheet) and detects deltas pixel-by-pixel between the construction set and the field markup. v1 is text-only because text is what the field reliably produces in real-time (daily logs, RFI responses, foreman's redline notes). Most reconciliation value lands without the CV step.
Construction-domain rules library. Equipment upsizing on rooftop = critical (structural). Duct reroute > 5' = high. Substitution = medium if approved, high if unapproved. Outlet count change = low. Override is one tap per redline if the engine misjudged context.
Yes — same engine, different consumer. Owner-rep PMs use it to validate that the GC's delivered as-builts match what the field actually did. Mismatches surface as redlines in the owner's review log.
Voice Synthesis from a walkthrough produces transcript text that feeds As-built Reconciler as the "field notes" input. The chain captures verbal field communication into structured redlines. Common pattern: walk the floor with the foreman, record the walk, run Voice Synthesis, feed the meeting transcript into Reconciler.
v1 is text-only. The reconciled redline log can be exported as a structured table for the CAD tech to consume during the DWG-level merge — we don't auto-merge into DWG. v2 will add a CAD-aware export. Most owners accept PDF as-builts (with the reconciled redline log) for non-government work.
Bring the construction-set notes and the field as-built notes for one trade on one floor to a 15-minute call. We'll run it on screen and walk through the severity classifications. You keep the reconciled log.
Start free — 14 days, no card →