Construction RFI Software for Irish Projects

The question, the answer and the proof, on one record.

Raise, track and answer RFIs on the project record, with an owner and a deadline on every question. Irish main contractors and their supply chains keep site and design team on one record, so what was asked and answered is never argued from memory at the final account.

Get Started

Trusted by construction companies of every size, worldwide

Queries answered on the record, not argued at the final account

RFI software for Irish contractors keeps technical queries where they can be found: on the record of the project they concern. Each question carries a named owner, a response deadline, a priority and a discipline, so the open list always shows what is waiting on whom. Subcontractors, consultants and clients take part through branded external forms at no cost, and every action from raised to closed is logged with the person and the timestamp. When agreement of the final account turns on what the design team confirmed months earlier, the answer is read from the project record, not hunted through inboxes.

Project manager reviewing an RFI on a tablet on site

Answers that stand at the final account

Each action is logged with the person and the timestamp, so what was asked and what was answered is settled by the record, not by recollection.

An owner on every question

Every RFI carries a named owner and a response deadline, and the open list shows which answers the site is waiting on before work is held up.

Raised where the work is

Questions are raised on the project they concern, so the query and its answer stay on the record of the job instead of scattering across inboxes.

The supply chain included

Subcontractors, consultants and clients raise and answer questions through branded external forms at no cost, with no licences to buy for the supply chain.

One record, from site query to final account

RFIs live on the same project record as the documents, site forms and costs of the job, so the question raised on site and the answer given by the design team stay in the system that runs the work, ready when the final account is agreed.

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

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

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

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

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

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

How to judge RFI software

Every serious RFI tool makes the same promises, so the differences show up in the details. These are the criteria worth testing before you choose, and how Archdesk answers each one.

Status you can see at a glance

The open-RFI list should show what is waiting on whom before it holds up the site. In Archdesk every question carries an owner, a deadline, a priority and a discipline, so the list reads as a work queue, not an archive.

Accountability that survives a dispute

When a claim turns on what was asked and answered, the audit trail is the evidence. Archdesk logs every action with the person and the timestamp on the project record.

The whole supply chain, without licenses

RFIs fail when half the parties answer by email because seats cost money. Subcontractors, consultants and clients take part in Archdesk through free external forms.

Questions that live with the project

An RFI raised in a standalone tool still has to find its way back to the job. Archdesk raises RFIs on the project record itself, alongside the documents, site forms and costs of the same job: one place, one record.

New to the process? Read the complete guide to RFIs in construction or start from the free RFI log template.

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 variations, 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.

How do RFIs help at the final account?

Because every question keeps its answer and its full history, logged with the person and the timestamp, the final account is agreed from the record rather than argued from memory. What the design team confirmed, when it was confirmed and who was told are read straight off the project.

Do consultants and design teams need licences?

No. External collaborators, including consultants, design teams, subcontractors and clients, work through branded external forms shared by a link at no cost. Their questions and answers land on the right project record automatically, so the whole team works one record without extra seats.

Can open RFIs be seen across the whole order book?

Yes. RFIs live on their project records in one platform, so open questions, owners and deadlines report at project and portfolio level. A contracts manager reads which jobs are waiting on which answers from one screen rather than ringing each site.

How are questions routed to the right person?

Workflows route each RFI by type or discipline: a design query notifies the design lead, a commercial question goes to its owner rather than a shared inbox, and the requester is notified the moment the answer is recorded against the originating RFI.