Scheduling
The time half of the money graph — every delay it quantifies is a potential cost.
Walter ingests P6/MSP schedules, diffs each version into plain language, binds activities to the records that gate them, runs a daily forward-risk scan, and produces time-impact analyses for change orders. The schedule of record is always published by a human.
The problem
What this costs you today — and what Walter does instead.
The pain
A new schedule lands and nobody can tell what actually changed or why it matters.
With Walter
Walter diffs each upload — logic, durations, sequence, float, milestones — into a plain-language narrative naming the driver.
The pain
"What's delaying Tower A next week?" takes a day of digging across systems.
With Walter
A daily forward-risk traversal links submittals, deliveries, RFIs, and change events to activities, answering the question instantly.
The pain
Delay records built after the fact lose the claim.
With Walter
When actual diverges from planned, Walter opens a contemporaneous delay node with evidence, ready for a time-impact analysis.
The workflow
How Walter runs it.
- 01
Ingest & diff
Parse each schedule upload and diff it against the prior version, publishing what changed and why it matters.
- 02
Bind to reality
Link activities to the submittals, deliveries, RFIs, and change events that gate them, plus field percent-complete.
- 03
Forward risk scan
Run the forward-risk traversal over the next 14–30 days to power 'everything delaying X' queries.
- 04
Lookaheads
Draft 2–3 week lookaheads from the master schedule, field reality, and open blockers for the superintendent to publish.
- 05
Delay capture
Open delay nodes contemporaneously with evidence; responsibility classification is drafted and human-confirmed.
- 06
Time impact analysis
Insert a fragnet, compute critical-path impact, and produce the TIA exhibit for the CO package.
Human in the loop
What stays your call.
- The schedule of record is published by a human; Walter analyzes, drafts, and flags but never silently changes logic or the data date.
- Delay-responsibility findings are claims-sensitive drafts, finalized by the PM.
- Every impact number is reproducible — fragnet and logic shown, no estimated durations presented as CPM output.
What you get
Outputs.
- Schedule-update narrative
- Daily forward-risk report
- Lookahead drafts
- Delay log with evidence
- TIA exhibits for COs
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.
Change Orders
Detect scope changes, price them, start the contractual notice clock.
Procurement
Buyout, POs, long-lead tracking, and delivery expediting.
Superintendent
Daily logs, manpower, percent complete — captured in the field.
Contract Compliance
Notice windows, COI tracking, certified payroll, claims clocks.