RFIs
Replace the forward–wait–follow-up–distribute loop.
Walter runs the RFI pipe end to end: it normalizes the question, pins it to the right drawing revision, routes it to the responsible design party, and chases the answer on the contract clock. You own the question's substance — the design professional owns the answer.
The problem
What this costs you today — and what Walter does instead.
The pain
RFIs sit in someone's inbox until they're suddenly blocking next week's pour.
With Walter
Every RFI gets a deadline from the contract response time and is tied to the schedule activity it blocks, so a critical-path question outranks a finish detail.
The pain
Field crews build from the wrong revision because the RFI cited last month's sheet.
With Walter
References resolve to the revision current at the question's date — revision-pinned citations, never a superseded sheet.
The pain
An answer quietly changes scope and nobody opens a change order in time.
With Walter
Every answer runs a consequence scan; if scope, cost, or time moves, Walter opens a ChangeEvent and hands it to change orders — the link where contractors lose money.
The workflow
How Walter runs it.
- 01
Intake
Normalize the question, attach revision-pinned sheets and spec sections, and check prior RFIs — if it's already answered, you get the citation instead of a duplicate.
- 02
Categorize & route
Determine discipline, priority, and responsible party from the project directory and communication protocol, then draft the transmittal.
- 03
Clock
Set the response deadline from the contract and tie priority to the schedule activity it gates.
- 04
Chase
Reminders at 50%, 80%, and overdue with escalating tone; overdue and critical-path drafts a formal delay letter for the PM.
- 05
Distribute
On response, push the answer to the original asker plus every affected trade by graph traversal, update the log, and close the deadline.
- 06
Consequence scan
If the answer changes scope, open a ChangeEvent and hand it to change orders to start the notice clock.
Human in the loop
What stays your call.
- Walter never answers design questions — it may attach relevant excerpts, but the response of record comes from the design professional.
- Routing to external parties and formal delay letters are never autonomous.
- Distribution may never narrow: everyone on the original RFI sees the answer.
What you get
Outputs.
- Routed RFI transmittals
- Live RFI log with ball-in-court and age
- Reminder and escalation drafts
- Answer distributions
- ChangeEvent handoffs
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.