As-builts reconciled to the construction set.
The As-Built Reconciler is the Trueleveler engine that 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.
Try it now
As-built Reconciler runs on your construction-set and field as-built notes and needs a free account (no card). It has no sample data yet, and the no-signup demo only levels bids.
The field marked the drawings. Now someone has to read them.
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 (info/minor/major/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.
Rolling. Not closeout-day.
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.
- At trade rough-in completion — reconcile MEP roughs once concealed. The field markup that recorded a 6" pipe rerouted around the column is fresh; the trade's foreman can answer the rationale question.
- At area substantial completion — phased projects (residential mid-rise, hospitals) reconcile per floor or per area.
- 30 days pre-closeout — full project reconcile across all sheets. Surfaces any redline that wasn't logged in real-time.
- Owner walkthrough prep — severity-classified redlines surface to the PM for owner discussion. Major-severity deltas (equipment upsizing, route changes affecting access) get explicit owner sign-off.
Two text inputs. v1 is text-only.
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.
Construction-set notes
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.
Field as-built notes
What was actually installed. From the foreman's redline log, the daily log entries describing changes, or the trade's typed as-built narrative.
Project sheet index
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.
Structured redlines. One row per delta.
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.
Not all redlines need owner sign-off.
The engine classifies severity using construction-domain rules — not just by magnitude. A 2" dimension shift on a mechanical room is minor; the same 2" on an ADA-clearance corridor is critical.
Equipment upsizing / structural / code
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.
Route changes / maintenance access
Major duct or pipe reroutes that affect future maintenance access or ceiling-cavity clearance. The facilities team needs to know.
Material substitutions / dimensional shifts
Approved substitutions or dimensional shifts that don't affect access or code. Reported but routine.
Field-directed adjustments
Outlet count adjustments, height tweaks for furniture clearance, minor relocations. Documented but no escalation needed.
Source-tagged
Each redline links back to the authorizing document — RFI number, CO number, substitution log, field directive, or owner change request.
Severity drives package format
Critical and major-severity redlines render in the owner's package with full rationale. Minor and info render as summary entries. The owner gets the signal, not the noise.
Field notes in. Closeout deliverable out.
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.
- Closeout Builder — consumes the reconciled redlines as a required deliverable section. Carries-data badge fires on this chain.
- Closeout package — the package's as-built drawings section renders the reconciled set with severity-tagged redlines highlighted.
- CO Review — approved COs are the authorizing document for many redlines. The CO number is the rationale tag.
- RFI Tracker — resolved RFIs that drove a field change (route, material) are linked from the redline so the audit trail spans from question to as-built.
Things everyone asks first.
What about v2 with drawing-image diff?
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.
How does it know which severity level to assign?
Construction-domain rules library. Equipment upsizing on rooftop = critical (structural). Duct reroute > 5' = major. Substitution = minor if approved, major if unapproved. Outlet count change = info. Override is one tap per redline if the engine misjudged context.
Can it handle owner-side as-built reviews?
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.
What if no formal as-built notes exist (just verbal at walks)?
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.
What about CAD layers preserved (DWG files)?
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.
Reconcile a real sheet. See the redlines in 30 seconds.
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.
Try Free for 14 Days →