Archdesk

Construction RFI Software

Every RFI answered on the record. Not in an inbox.

Raise, track and answer requests for information on the project record, with an owner and a deadline on every question. The question, the answer and the audit trail stay in one place, from the first query to closeout.

Get Started
Solution screenshot

Trusted by construction companies of every size, worldwide

Higgins Partnerships logo
QBRE logo
Mitie logo
Daikin logo
VINCI Construction logo
Ballast Nedam logo
Madinet Masr logo
QGMI logo
CDC City Diamond Contracting logo
CSI Energy logo
Polenergia logo
ib vogt logo
TeraWulf logo
Utilligence logo
TaskSpace logo
Echospace logo
EEE Elevator Enterprise logo
Eomac logo
QTS logo
MacLennan logo
Conditioned Environment logo
DVM logo
ADP logo
DMDC logo
Inuti logo
Oakwrights logo
JH logo
K4 logo

Questions become records, not email threads

Construction RFI software manages requests for information: the formal questions that clarify drawings, specifications and scope before the wrong thing gets built. Archdesk runs RFIs on the project record itself. Each question carries an owner, a response deadline, a priority and a discipline, subcontractors take part through free external forms, and every answer is logged on the project record with a full audit trail.

Project manager reviewing an RFI on a tablet on site

Raised where the work is

RFIs are created on the project they concern, so the question and the answer live on the project record instead of scattering across inboxes.

An owner on every question

Each RFI carries a named owner and a response deadline, and the open list shows what is waiting on whom before it holds up the site.

The supply chain included

Subcontractors, consultants and clients raise and answer RFIs through branded external forms at no cost, with no licenses needed.

Answers that hold up

Every action is logged with the person and the timestamp, so when a dispute turns on what was asked and answered, the record already exists.

One place, one record

RFIs sit on the same project record as the drawings, site forms and costs of the job, so questions and answers live in the system that runs the work instead of scattering across inboxes and separate tools.

Site team raising a question from a tablet at the building site

RFI Creation and Tracking

Every request for information is raised on the project it concerns, with an owner, a response deadline, a priority and the discipline it belongs to. The open list shows what is waiting on whom, filterable by date and discipline, so questions stop living in inboxes and start living on the record.

RFIs raised on the project record

An owner and a response deadline per RFI

Status, priority and discipline on every question

Time and cost impact recorded with the answer

RFI Creation and Tracking screenshot

Subcontractor RFI Handling

Subcontractors raise questions and submit responses through branded external forms, without needing an Archdesk license. Their question lands on the right project the moment they send it, and the answer goes back through the same record.

External collaborators submit RFIs at no cost

Branded forms shared by a simple link

Questions land on the right project automatically

Responses recorded against the originating RFI

Subcontractor RFI Handling screenshot

Response Workflows

Workflows route each RFI to the person who owns the answer. A submitted question can notify the design lead, a commercial query can go to the quantity surveyor, and the requester hears back the moment the response is in.

Notifications sent when an RFI is submitted

Conditions route questions by type or discipline

The right owner alerted, not a shared inbox

Requesters notified when the answer lands

Response Workflows screenshot

Full Audit Trail

Every action on an RFI is logged with who did it and when: raised, reassigned, answered, closed. When a claim or dispute turns on what was asked and what was answered, the record is already there.

Every action logged with person and timestamp

The question and the answer kept together

History preserved through reassignments

The record that settles who-said-what

Full Audit Trail screenshot

RFIs on the Project Record

RFIs live on the same project record as the documents, drawings and site forms of the job. Whoever answers a question has the controlled documents at hand in the same system: one place, one record, nothing re-keyed between separate tools.

RFIs and documents on one project record

Version control on the project documents

One project record across office and site

No re-keying between separate RFI tools

RFIs on the Project Record screenshot

Frequently Asked Questions: Construction RFIs

What is an RFI in construction?

An RFI (request for information) is the formal question one project party asks another when drawings, specifications or scope are unclear: a subcontractor asking the design team to clarify a detail, or a main contractor querying a specification conflict. The answer often changes the work, so mature teams treat RFIs as project records with owners, deadlines and a full history, not as email threads.

How does Archdesk track construction RFIs?

Each RFI is raised on the project it concerns with a reference number, an owner and a response deadline. Status is tracked from raised to closed, the open list shows what is waiting on whom, and every action is logged with the person and timestamp. The question, the answer and the documents they relate to stay together on one project record.

Can subcontractors raise and answer RFIs without an Archdesk license?

Yes. External collaborators such as subcontractors, clients and consultants work through branded external forms shared by a link, at no cost. Their questions and responses land on the right project record automatically, so the whole supply chain takes part in the RFI process without buying seats.

How do RFIs connect to project documents and drawings?

RFIs and project documents live on the same project record, so a question about a drawing or specification is raised, answered and stored in the same system that holds the controlled documents, not in a separate email thread. Documents on the record carry version control, and each RFI keeps its own full history from raised to closed.

How do response deadlines and reminders work?

Every RFI carries an owner and a response deadline, and workflows notify the right person when a question is submitted or answered. Because open RFIs are visible per project with their deadlines, overdue questions surface on the record rather than hiding in an inbox.

Why manage RFIs in the same system as cost and site records?

Because RFI answers change scope, and scope changes cost. When RFIs live with the change orders, budgets and site forms of the same project, the commercial consequence of an answer is priced in the same system that recorded the question, with an audit trail across the whole chain.

See your next project on Archdesk

Book a demo and walk through a fully worked example project: one platform running everything from winning the work to closing it out.

Get Started
Archdesk rating on Software AdviceArchdesk rating on CapterraArchdesk rating on GetApp