Construction RFI software with ball-in-court ownership, aging alerts, and drawing context
Keep every request visible - ball-in-court, aging, cost impact, and drawing links - so projects move instead of waiting on email threads.
Construction Software
Construction RFI management
This is a Request for Information (RFI) tool that tracks ball-in-court ownership, aging, cost impact, and drawing context. It keeps questions, routing, answers, and audit trails in one register - replacing email threads and spreadsheets with a structured path from submission to closure that prevents delays and supports claims.
WorkHub
Part of WorkHub
- Ball-in-court ownership showing who owes the next answer (GC, architect, engineer, trade)
- Aging and overdue alerts with days-open and escalation heat
- Cost impact capture and drawing pins for revision context
- Full lifecycle from draft to closed with audit trail and task spawning
The problem
RFIs do not fail because teams forget how to ask - they fail when ownership disappears
When requests live in inboxes, shared drives, and side chats, nobody can answer three simple questions: who has it, how old is it, and what will it cost if it slips? Delayed answers become idle crews, rework, and margin bleed. Put the RFI register back at the center of delivery - with the signals project teams actually chase.
From question to closed - without losing the thread
A clear path every stakeholder can follow, whether they live on site or in the design office.
- 01
Capture the question
Create an RFI with number, trade, location, due date, and attachments - structured enough for the field, clear enough for design.
- 02
Assign ball-in-court
Route to the right reviewer. Everyone sees who owns the next answer and when it is due.
- 03
Answer with context
Respond against drawings, specs, and prior discussion. Cost impact stays attached to the record.
- 04
Close and carry forward
Close with a durable answer. Spawn tasks, keep links to sheets, and keep the trail for closeout.
Everything a modern RFI register needs
Ball-in-court ownership
See whether the GC, architect, engineer, or trade owes the next move - without a status meeting to find out.
Aging & overdue heat
Days-open, due dates, and overdue highlighting so silent RFIs surface before they become schedule claims.
Cost impact capture
Flag potential cost exposure when the question is asked, not after the change order arrives.
Drawing & sheet context
Pin RFIs to sheets and details so reviewers answer against the right revision, not a vague email subject.
Trade routing & priority
Urgent vs standard paths, trade tags, and filters that match how coordinators actually work the log.
Full lifecycle & audit trail
Draft to open to under review to answered to closed, with a history that survives handover and disputes.
Deep dive
A register your PM can trust at 7 a.m.
Sortable, filterable RFI log with status, assignee, trade, aging, and search across number and title - the morning view that replaces three spreadsheets.
- Official numbering (RFI-014) for field reference
- Submitted-by and assigned-to without guessing
- Days-open and overdue rows that demand attention
RFIs · Register
- RFI-014Slab edge detailArchitect5d
- RFI-015AHU clearancesMEP2d
- RFI-016Storefront glassGC1d
Deep dive
Answers that stick past the weekly meeting
Detail drawers keep question, discussion, attachments, and official answer together - so supers do not re-ask what design already clarified.
- Complete comment and status history
- Attachments and related files in one place
- Export-ready trail for handover and claims
RFI-014 · Detail
Question
Confirm waterproofing membrane at Level 4 slab edge per Detail 3/A-501.
Official answer
ClosedProceed with Detail 3/A-501. Use membrane system B as noted.
Deep dive
Aging signals before idle time hits the site
Proactive visibility into overdue and aging RFIs helps coordinators chase the right items - not every item - before crews wait.
- Portfolio and project overdue rollups
- Priority lanes for urgent questions
- Escalation cues that match your delivery rhythm
RFIs · Aging
4 RFIs open longer than 15 days
Deep dive
Connect the question to the work that follows
Link RFIs to drawings and spawn tasks when an answer creates field work - so the register is not a dead log at the end of the job.
- Sheet and pin context on the RFI
- Create follow-up tasks from the answer
- Keep commercial impact visible downstream
Connected records
RFI-014Waterproofing detail
T-067Level 4 waterproofing
A-501Detail 3 · Rev C
“RFI response time dropped from twelve days average to four. Ball-in-court visibility made the difference - we stopped guessing who owed the next move.”
Built for everyone who touches an RFI
General contractors
Own the log, chase aging, and keep design and trades aligned without Friday status archaeology.
Design & consultants
Answer against the right sheet and revision with a clear due date and full question context.
Trade partners
Submit structured questions, see status without email ping-pong, and get answers that stick.
FAQ
RFI software FAQ
Straight answers for teams evaluating construction RFI management.
A Request for Information (RFI) is a formal question raised during a project when drawings, specs, or site conditions are unclear - or when a team proposes an alternate material or method. RFIs create a documented path from question to official answer so work can proceed without guesswork.
Trade partners and site teams often raise RFIs. The general contractor or construction manager usually owns the register and routes questions to architects, engineers, or other consultants. Depending on contract structure, some fabricators may engage design directly - but accountability still needs a single visible owner.
Email buries ownership, aging, and attachments across personal inboxes. Dedicated RFI software like WorkHub keeps numbering, ball-in-court, due dates, cost impact, and history in one project record - so delays and disputes are easier to prevent and prove.
The register surfaces who owes the next answer, how long the item has been open, and whether cost impact is flagged. Linked drawings and follow-up tasks keep context attached, so reviewers spend time deciding - not hunting for the last attachment.
Yes. WorkHub links RFIs to sheets and can spawn tasks from answers. Cost impact fields help commercial conversations start early, and the audit trail stays available for closeout and claims support.
Owners and developers benefit from portfolio visibility into aging RFIs and risk signals - without waiting for a weekly status deck. The same register the delivery team uses becomes the source of truth for oversight.
Related
Explore connected modules
Build on the Construction OS
Join the waitlist for Aroclad - field and office collaboration inside a platform built for the full construction lifecycle.