What it produces
A live RFI log and submittal register with due dates, follow-ups, cost flags and purchasing hand-offs.
Workflows
RFI & Submittal Logs
the running record of questions sent to the design team and product packages sent for approval, with who owes the next response
The job in one minute
Who owns it
The project engineer, with the PM, superintendent, the architect or engineer, and purchasing at the far end.
How often
Daily, plus a weekly review before the owner-architect-contractor meeting.
Why it hurts
Questions start in text threads and never become RFIs. Two superintendents ask the same thing a week apart. An RFI goes out without a sheet number. Answers come back and nobody reads them for cost. A resubmittal gets a new number and the history splits. Purchasing hears about an approval two weeks late, and the lead time eats the float. And if the owner runs its own system, every record exists twice.
Systems it touches
Procore or Autodesk Construction Cloud, the owner's Primavera Unifier, Bluebeam, Teams, Outlook, Excel registers, SharePoint spec books and the ERP.
If the whole team works in one platform, its reminders already cover much of the follow-up. The agent works across the seams: chats, emailed answers, two logs and the purchase order.
- Procore or Autodesk Construction Cloud
- Owner's Primavera Unifier
- Bluebeam
- Teams
- Outlook
- Excel registers
- SharePoint spec books and the ERP
12 steps · 5 actions · 5 decisions · 2 human reviews
The workflow, step by step
Action Decision Human review Select a step in the flowchart to jump to it.
1RFIs steps 1–6
-
Action · Teams
Capture a field question from email, a markup, a Teams chat or the daily report into a draft RFI with spec section, sheet, location and photos.
-
Decision · Agent
An existing RFI on the same spec section and sheet flags a possible duplicate.
-
Human review · The project
The project engineer edits and approves the wording. Nothing leaves without it.
-
Action · Agent
Create the RFI in each required log, with a due date in working days from the contract.
-
Decision · Agent
Past due sends a follow-up; past the escalation point it joins the next OAC agenda.
-
Decision · Agent
An answer that may change cost or time opens a draft change order and starts the notice clock.
2Submittals steps 7–11
-
Action · Agent
Build the submittal register from the specs, one row per required item.
-
Action · Agent
Work back each row's submit-by date from the on-site date, lead time and review times.
-
Decision · Agent
A submit-by date inside 14 days with nothing received triggers a request to the sub.
-
Action · Agent
Log the returned stamp. Revise and resubmit keeps the number and adds a revision.
-
Decision · Agent
An approval goes to purchasing with confirmed lead time. Approved with corrections waits for the sub's written acknowledgment.
3Together steps 12–12
-
Human review · The project
The project engineer works the weekly exception list before the OAC meeting.
✓ Done
See it done in the Gallery
Rules vs judgment
When it stops
Steps
- 01
Flagged; the owner's system is never overwritten.
- 02
Held; no status is guessed.
- 03
New rows proposed for review, history kept.
- 04
Returned to the drafter.
- 05
Dates recomputed and the PM sees the float change.
What you end up with
One RFI log and one submittal register that always say whose turn it is, a weekly list sorted by who holds the ball, cost-bearing answers already on the change order track, and approvals in purchasing's hands the same day. Product →
Questions
Can the agent write the RFI question?
It drafts it. The project engineer approves the wording, because an RFI can become page one of a claim.
How does it keep two logs in step?
A mapping table ties each GC number to the owner's record. The agent enters in both, reads both back and flags any difference.
Does the agent decide whether a submittal is approved?
No. The design team's stamp decides. The agent reads it and acts on it. Change Orders →
No prompts. No babysitting. No Integrations.