RFI and submittal tracking
No RFI sits unanswered for weeks. Every RFI and submittal gets an owner and a due date, and is chased until it's answered.
Hours back
4
hours a week back, typically
How it runs
What we build, step by step.
This is the usual shape. Yours gets built around how your team actually does the job.
- 01
RFIs drafted from site questions
A question from the site manager becomes a draft RFI with the drawing reference, photos and a response-by date.
- 02
Submittals checked against the register
Packages from subs are checked against the submittal register for missing items and the right revision.
- 03
Overdue items chased
Reviewers who've passed the due date get a polite reminder naming the item and what's waiting on it.
- 04
Answers routed back
When the architect or engineer responds, the answer is logged and the site manager and affected subs are told.
- 05
A weekly open-items list
Every open RFI and submittal, who has it, how long it's been, and what work it's holding up.
Shown with software we see a lot. If your team uses something else, we build it into that instead.
Built for your business
Same job, different business. We build yours.
Two firms in the same trade rarely run a job the same way. Different software, different steps, different people signing off. We build it for your business, around how your team actually does the job.
Your steps
Built around the order your team already works in, odd exceptions included.
Your software
Runs inside the tools you already pay for, set up the way you use them.
Your rules
Your wording, your limits, your sign-offs. Nothing generic goes out in your name.
You sign off
Your team keeps the final say.
The project manager approves every RFI before it's issued. Technical answers only ever come from the architect or engineer.
What it's worth
What those hours add up to.
4 hours a week, over 46 working weeks, is 184 hours a year. At $50 an hour, that’s
$9,200
back in the business, every year.
Typical, not promised.
Before and after
The job, before and after.
How it runs today
Questions from site go to the architect by email. The project manager keeps a log when they have time. Submittals bounce between subs, the head contractor and the design team, and nobody knows which revision is current.
What we build
- RFIs drafted from site questions
- Submittals checked against the register
- Overdue items chased
- Answers routed back
- A weekly open-items list
A month in
Overdue RFIs get chased the day they're late, crews stop standing around waiting on answers, and the weekly meeting starts with a list everyone agrees on.
FAQ
Can AI read construction drawings for RFIs?
Partly. It can find the drawing reference for an RFI and quote what conflicts. Working out what the design means stays with the architect or engineer.
Does RFI tracking work without Procore?
Yes. The RFI and submittal log can live in a shared spreadsheet and folder. Procore is where it goes if you already use it.
More for construction
See them all →Next step
Bring this one to a free live build.
Thirty minutes on rfi and submittal tracking. We build its elf with you, live, and you keep it.