Document Control
Why the system knows Rev 17 exists — and that nobody is still building from Rev 16.
Every other skill's 'current set only' rule depends on this one being right. Walter ingests and indexes drawings and specs, manages revision supersession with content hashing, produces plain-language change summaries, and tracks distribution acknowledgments.
The problem
What this costs you today — and what Walter does instead.
The pain
Crews build from superseded sheets because supersession was never tracked cleanly.
With Walter
Each new revision writes a supersession edge with exactly one current sheet; field crews in a changed area get a targeted alert.
The pain
A sheet is silently reissued under the same revision label and no one notices.
With Walter
Every issuance gets a content hash — same label, different hash creates a new revision node and an incident flag, never an overwrite.
The pain
A revision changes scope and the downstream RFIs, submittals, and COs go stale.
With Walter
Supersession triggers a stale-citation sweep, flagging every downstream artifact citing the old revision for re-validation.
The workflow
How Walter runs it.
- 01
Ingest & index
Extract sheet numbers, titles, revision marks, and dates from every incoming set; verify against the transmittal's sheet list.
- 02
Supersede
Write the supersession edge, retain the old revision, and content-hash every issuance to catch silent reissues.
- 03
Diff & notify
Compare revisions, produce a plain-language change summary per sheet, and hand the change list to change orders and coordination.
- 04
Distribute & acknowledge
Transmit to the distribution matrix, track acknowledgments, and chase unacknowledged critical revisions.
- 05
Conflict registry
Log plan-vs-plan and plan-vs-spec conflicts with both citations and route them as RFIs until resolved.
- 06
As-builts
Collect field markups continuously against current revisions and track completeness for closeout.
Human in the loop
What stays your call.
- Superseded documents are never deleted and never cited as current; historical queries get them explicitly labeled.
- A document is current only when received through an authorized channel — a sub's emailed sheet is recorded but not promoted.
- Walter summarizes drawing changes; it never interprets design intent.
What you get
Outputs.
- Current set index
- Revision change summaries
- Transmittals with acknowledgment tracking
- Conflict registry
- As-built completeness report
Hands off to
It doesn't work alone.
Walter's workflows share one construction brain, so a signal in one becomes action in the next — automatically.