Submittals
Own the register and the compliance screen; the design team keeps approval.
Walter extracts the submittal register straight from the spec book, ties every item to the activity it gates, screens incoming packages against spec requirements line by line, and tracks the review clock. It informs — it never approves.
The problem
What this costs you today — and what Walter does instead.
The pain
The submittal register is built by hand from a thousand-page spec book — if at all.
With Walter
Walter extracts every SUBMITTALS article into a register with item, spec section, type, responsible sub, and review cycle. You verify it once; it becomes the system of record.
The pain
An unapproved submittal blows a lead-time window and stalls installation.
With Walter
Each item is back-scheduled from install date minus review cycles minus fabrication and shipping, so required-submit-by dates surface before they're a problem.
The pain
Deviations from spec slip through review unnoticed.
With Walter
On intake, Walter checks documents, model numbers, and performance values against the spec and flags every deviation with its citation.
The workflow
How Walter runs it.
- 01
Register
Extract every submittal requirement from the spec book into a register; you verify once, then it's the source of truth.
- 02
Schedule-link
Connect each item to the activity it gates and compute required-submit-by dates backward from install.
- 03
Intake & screen
Check completeness, model numbers, and performance values against spec; flag deviations line by line with citations.
- 04
Substitutions
Detect or-equal and substitution requests and route them through the contract's stricter substitution procedure.
- 05
Route & track
Transmit to the reviewer, track the contractual review clock, and remind at 50%, 80%, and overdue.
- 06
Returns
Log the action, restart Revise-Resubmit cycles with a recomputed risk date, and release the procurement hold on approval.
Human in the loop
What stays your call.
- Walter never marks a submittal approved — it only records the design professional's action.
- Compliance flags cite the spec section and the exact submitted value; no uncited rejections.
- Approved-as-Noted markups that change scope or cost open a ChangeEvent.
What you get
Outputs.
- Submittal register
- Compliance screen reports
- Transmittals
- Ball-in-court log
- Lead-time risk 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.