🏗️ Cornerstone AI module · RFIs

Construction RFI Software

Every project runs on questions. A dimension does not match, a drawing is unclear, the site condition differs from the plan. Handle those questions over phone calls and WhatsApp and they get lost, the work stalls, and sometimes the wrong thing gets built. Cornerstone AI’s construction RFI software turns each question into a tracked request with a number, an owner, a due date and an answer on the record. Nothing sits unanswered, and every decision is logged. When you want to know which RFIs are still open, ask the GenAI chat.

Part of Cornerstone AI · 500+ features · raise, route, answer, close · full RFI log

Cornerstone RFI log · Marina Residency 2 open + Raise RFI RFIQUESTIONOWNERSTATUS 014Beam depth clash at C3StructuralClosed 1d 015Terrace slope directionArchitectClosed 2d 016Rock at footing F4StructuralDue today 017Tile substitutionArchitect1d left 018Waterproofing detailArchitectOverdue 4d Avg response this month1.6 days RFI-014 Beam depth 600mm clashes with 2.9m ceiling at C3 ↳ Structural consultant · answered in 1 day Reduce beam to 450mm, add 2-T16 bars. Sketch attached.
Numbered
RFI log per project
Owner
and due date on each
Response
time tracked
Mobile
raise from site with a photo
17+ yrs
iStudio, Chennai
01 How it works

The RFI flow, from a site question to a logged answer

A request for information construction teams raise should never get lost. Cornerstone AI’s construction RFI software moves every question through the same clear path, so it is asked properly, answered by the right person, and closed on the record.

1

Raise

Site raises an RFI with the question, a photo and the drawing reference.

2

Route

It goes to the person who must answer, with a due date.

3

Respond

They answer with a clarification and any attachment.

4

Close

The requestor closes the RFI once the answer is enough.

5

Log

The whole thread stays on the project, numbered and time-stamped.

No technical experience needed

Raising an RFI is typing a question and attaching a photo. Answering one is a reply. Your site engineer does not learn a system, they just ask the question in the app instead of on a call that nobody remembers. And when you want to know what is still open or overdue, you do not scroll a chat history. You ask the GenAI chat and it lists them.

02 A real walkthrough

See the construction RFI flow, step by step

Here is a real question. A beam-depth clash on the “Marina Residency” villa in Chennai, from the site to a logged answer.

Step 1 & 2 · Raise and route

A site question becomes a tracked RFI

The site engineer finds that the beam depth on the structural drawing clashes with the false-ceiling height on the interior drawing. Instead of a phone call, he raises an RFI from the site: a short question, a photo of the spot, and a reference to both drawings. It is routed straight to the structural consultant with a two-day due date.

Example: RFI-014 raised by Suresh. “Beam depth 600mm clashes with 2.9m false ceiling at grid C3.” Routed to structural consultant, due in 2 days.
Cornerstone RFI log · Marina Residency 2 open + Raise RFI RFIQUESTIONOWNERSTATUS 014Beam depth clash at C3StructuralClosed 1d 015Terrace slope directionArchitectClosed 2d 016Rock at footing F4StructuralDue today 017Tile substitutionArchitect1d left 018Waterproofing detailArchitectOverdue 4d Avg response this month1.6 days RFI-014 Beam depth 600mm clashes with 2.9m ceiling at C3 ↳ Structural consultant · answered in 1 day Reduce beam to 450mm, add 2-T16 bars. Sketch attached.
Step 3 · Respond on the record

The answer comes back to the same thread

The consultant replies on the RFI itself: reduce the beam to 450mm with extra reinforcement, and attaches a marked-up sketch. The answer is on the record, not buried in an email. The site engineer and the office both see it at once, and there is no ambiguity about what was decided or who decided it.

Example: Response in 1 day: “Reduce beam to 450mm, add 2-T16 bars.” Marked-up sketch attached. Visible to site and office together.
Cornerstone RFI log · Marina Residency 2 open + Raise RFI RFIQUESTIONOWNERSTATUS 014Beam depth clash at C3StructuralClosed 1d 015Terrace slope directionArchitectClosed 2d 016Rock at footing F4StructuralDue today 017Tile substitutionArchitect1d left 018Waterproofing detailArchitectOverdue 4d Avg response this month1.6 days RFI-014 Beam depth 600mm clashes with 2.9m ceiling at C3 ↳ Structural consultant · answered in 1 day Reduce beam to 450mm, add 2-T16 bars. Sketch attached.
Step 4 & 5 · Close and log

Close it, and keep it on the record forever

Suresh confirms the answer is clear and closes RFI-014. It stays in the project’s RFI log with its question, the response, the sketch and the full timeline. Months later, if anyone asks why the beam was changed, the answer is one click away, with the date and the name of who approved it. No rework, no dispute.

Example: RFI-014 closed, response time 1 day. Logged on Marina Residency. Beam change traceable with date, sketch and approver.
Cornerstone RFI log · Marina Residency 2 open + Raise RFI RFIQUESTIONOWNERSTATUS 014Beam depth clash at C3StructuralClosed 1d 015Terrace slope directionArchitectClosed 2d 016Rock at footing F4StructuralDue today 017Tile substitutionArchitect1d left 018Waterproofing detailArchitectOverdue 4d Avg response this month1.6 days RFI-014 Beam depth 600mm clashes with 2.9m ceiling at C3 ↳ Structural consultant · answered in 1 day Reduce beam to 450mm, add 2-T16 bars. Sketch attached.
03 GenAI chat

Just ask, and the GenAI chat reads your RFI log

Alongside the normal RFI screens, the built-in GenAI assistant lets anyone ask about open and overdue RFIs in plain English. No log to scroll, no report to build.

Cornerstone AI · Assistant
Ask anything about your RFIs
Which RFIs are open and overdue?
✦ Cornerstone AI2 RFIs are overdue:
RFI-018 · Skylinewaterproofing detail · 4 days
RFI-021 · Lotusdoor schedule clash · 2 days
What is our average RFI response time this month?
✦ Cornerstone AI1.8 days across 12 RFIs. The architect answers in about a day, the structural consultant takes closer to 3. 2 are still open.
Ask about open RFIs, overdue, response time…↑
✦ GenAI built into every module

No log to scroll. Just type the question.

Every Cornerstone AI module can be run the normal way, with forms, lists and a log. On top of that, the GenAI chat lets you ask about your RFIs in plain language. Ask “which RFIs are overdue?”, “who owes us an answer?”, or “what is our average response time” and the assistant reads your live RFI log and answers in seconds, with a table when that helps.

That means a project manager can chase the right people from a phone, without opening the log at all. They just ask. It is what makes Cornerstone AI usable by a whole team, not only the office coordinator.

The GenAI chat is a core Cornerstone AI capability, implemented within the application. Examples shown are illustrative of how it answers.

04 What you get

Modern construction RFI software features

Everything a builder needs from construction RFI management software: ask the right question, get it answered, track it as RFI tracking software should, and keep the decision on the record.

Raise from site

A site engineer raises an RFI from the phone with a question and a photo.

Route to an owner

Send the RFI to the person who must answer, with a clear due date.

Answer on the record

Responses with attachments stay on the RFI, not in an email chain.

Response time

Every RFI tracks how long it took, so slow answers become visible.

Overdue flags

RFIs past their due date are flagged, with the blocked task made clear.

Numbered RFI log

Every RFI sits in a numbered, searchable log per project.

Drawing reference

Link an RFI to the drawing or document it is about, so context is never lost.

Audit trail

The full, time-stamped history of every RFI, kept for the life of the project.

Linked to schedule

See which scheduled task is waiting on an RFI answer, so delays are clear.

05 Types of RFI

The kinds of question an RFI handles on a real site

Not every RFI is the same. These are the common types an Indian builder raises, and all of them are logged the same way, so your RFI log stays one consistent record.

Design clarification

The drawing is not clear on an intent. A junction detail, a finish, a slope direction. The field asks the architect what was meant before building it.

Example: “Is the terrace slope toward the east or west drain?”

Drawing or spec conflict

Two documents disagree. The structural drawing says one thing, the interior drawing another, as in the beam-depth clash above. The RFI forces a single answer.

Example: “Beam depth clashes with the false-ceiling height at grid C3.”

Dimension mismatch

A measured dimension on site does not match the drawing. Rather than guess and cut, the field raises an RFI so the correction is on the record.

Example: “Column spacing measures 3.9m on site, drawing shows 4.0m.”

Field condition

The ground reveals something the drawing did not, a rock seam, an old foundation, a service line. The RFI captures how the team should proceed.

Example: “Rock encountered at 1.2m in footing F4, drawing assumed soil.”

Substitution request

A specified material is unavailable or costly, and the team proposes an equal. The RFI gets the designer’s sign-off before the swap is made.

Example: “Specified tile out of stock, propose equivalent from same vendor.”

Owner-requested change

The client asks for something different in the field. The RFI records the request so it can flow into a change order rather than a quiet, unpriced extra.

Example: “Owner wants an extra power point in each bedroom.”
06 Response time & ageing

Why unanswered RFIs cost money, and how the software stops that

RFIs are normal on every project. They only become expensive when they sit. Tracking response time and ageing turns a hidden cost into something you can see and chase.

The real cost of a slow RFI

When an RFI goes unanswered, the work that depends on the answer stalls. The crew moves to something else, momentum is lost, and sometimes the team guesses to keep going, which is how a wrong beam or a wrong slope becomes rework. Industry writing on RFIs is consistent that unanswered requests are one of the largest sources of avoidable delay on a job. The cost is rarely on one invoice, so it hides, which is exactly why it needs to be measured.

Cornerstone AI puts a due date on every RFI and tracks how long each one actually took to answer. Slow responders become visible, not by blame but by fact, and the project manager can chase the two that matter instead of worrying about all of them.

RFI ageing · all projects Open: 5
Age bucketOpen RFIsAction
0 to 2 days2on track
3 to 5 days1chase today
Over 5 days2escalate
Avg response1.8 daysthis month

Sample data shown for illustration. Ageing buckets and due dates are configurable.

Escalation, without the drama

When an RFI crosses its due date, it is flagged and can be escalated to the next person automatically, so a question does not die because one inbox was busy. The owner sees the ageing at a glance, and the GenAI chat answers “what is overdue?” in one line. The point is not to police people. It is to make sure a two-day question never quietly becomes a two-week delay.

07 The problem & the fix

What’s broken in handling site questions by phone, and how Cornerstone AI fixes it

These are the real problems builders hit running questions through calls and WhatsApp. Cornerstone AI’s construction RFI software was built against each one.

⚠️ With phone calls & WhatsApp

  • Questions lost in a chat scroll or a forgotten call
  • No record of who was asked or what was decided
  • Work stalls while an answer is chased by phone
  • The team guesses, builds it wrong, and reworks it
  • No idea how long answers actually take
  • Disputes later with no paper trail to settle them

✓ With Cornerstone AI RFIs

  • Every question a numbered RFI with an owner and due date
  • Answer and attachments kept on the record
  • Overdue RFIs flagged, with the blocked task shown
  • The right thing gets built, because the answer is clear
  • Response time tracked, so slow answers are visible
  • A full audit trail that settles any later question

These pain points reflect widely reported problems with informal RFI handling in construction. See PMI on project communication and the Construction Industry Development Council (India) on project processes. Content was rephrased for clarity.

08 A real sample

Sample: an RFI log, as the office sees it

A clean, numbered log showing each question, its owner, how old it is, and where it stands.

RFI log · Marina Residency Open: 2 Avg response: 1.6 days
RFIQuestionOwnerStatus
014Beam depth clash at C3StructuralClosed, 1 day
015Terrace slope directionArchitectClosed, 2 days
016Rock at footing F4StructuralOpen, due today
017Tile substitutionArchitectOpen, 1 day left

Sample data shown for illustration. RFI numbers, owners and due dates are configurable.

09 Examples

Construction RFI examples: everyday tasks

Common things site and office teams do with RFIs every day.

Raise

Flag a drawing clash from site

Snap a photo, type the question, attach the drawing reference, and route it.

Route

Send it to the right consultant

Assign the RFI to the architect or structural consultant with a due date.

Answer

Reply with a marked-up sketch

The consultant answers on the RFI and attaches a sketch, all on the record.

Chase

Find what is overdue

Ask the GenAI chat which RFIs are past due and who owes an answer.

Close

Close a resolved RFI

The requestor confirms the answer is enough and closes it on the log.

Trace

Prove a past decision

Open the RFI log months later to show what was asked and who approved it.

See it live on your own project

Book a free, no-obligation demo. We will raise a sample RFI on data shaped like yours, route it, answer it with an attachment, and show the ageing and the log, so you can see how a site question stays on track.

Book a live demo
10 In depth

Construction RFI software, explained for Indian builders

An RFI is not a complaint, it is a safeguard

A request for information in construction is not a sign of trouble, even though some builders treat it that way and ask the question quietly on a call that never gets written down. That is the dangerous version. A good RFI is the opposite: it is the team saying “we will not build on a guess.” On an Indian site where the architect, the structural consultant and the contractor are often three different firms, construction RFI software gives every written question a clear owner, which is how you avoid building the wrong thing and arguing about it later.

The record is the whole value

A verbal answer on a phone call is gone the moment the call ends. When the beam gets questioned six months later, nobody can prove what was agreed. Construction RFI software keeps the question, the answer, the sketch and the date in one place, so the decision is permanent. That record protects the builder in a dispute, and it protects the client because the work matches a documented instruction, not a memory.

Linked to the schedule, so delay is visible

An RFI on its own is just a question. The value appears when it is tied to the work it blocks. Because RFIs live on the project schedule, you can see that RFI-016 is holding up the footing task, and that the footing is on the critical path. So the question is not just open, it is urgent for a reason you can point to, and the right people treat it that way.

From field question to priced change

Many RFIs are harmless clarifications. Some are not. When an owner-requested change or a field condition means extra work, the RFI is where that first surfaces. Capturing it as an RFI means it can flow into a change order and a priced revision instead of becoming an unpaid extra the builder absorbs. The RFI log becomes an early-warning list for scope creep.

Everyone sees the same thread

The quiet failure of phone-and-WhatsApp is that three people end up with three versions of the answer. With a single RFI thread, the site engineer, the project manager, the architect and the owner all read the same question and the same response. There is no “but you told me” because the record is shared. On a multi-firm Indian project, that shared truth is worth more than any single feature.

RFIs inside the ERP, not a tool on the side

A standalone RFI app can track questions, but it cannot connect them to anything. It does not know which task the RFI blocks, which drawing it references, or whether the answer should become a priced change. So the RFI gets answered and the knock-on effects are handled somewhere else, by hand, if at all.

In Cornerstone AI the RFI lives on the project, next to the schedule, the drawings and the money. A beam-clash RFI references the structural drawing, flags the footing task it holds up, and if the fix adds reinforcement, that extra can be carried into costing. The question, the answer, the schedule impact and the cost impact all sit together, which is what lets the GenAI chat answer “what is overdue and what is it blocking” with a real answer instead of a list of open items with no context.

What builders need and rarely get: every site question asked properly, routed to a clear owner with a due date, answered on the record with attachments, tracked for response time, linked to the task it blocks and the cost it may add, and kept forever as proof. Getting that loop inside the ERP is the point, instead of a RFI tool that only makes a list.

How to choose construction RFI software

Look for a numbered RFI log per project, mobile raising from site with a photo, routing to a clear owner with a due date, answers kept on the record with attachments, response-time tracking with overdue flags, and a link from the RFI to the drawing and the scheduled task it affects. Most of all, look for RFIs that sit inside the project, not in a separate app, so a question connects to the schedule and the cost. Cornerstone AI does all of this inside a full construction ERP. Explore the scheduling module RFIs connect to, the quality module that shares the same site-record discipline, the proposal module a change flows into, or the Cornerstone AI overview.

iS

Built by iStudio Technologies · Chennai

Written from hands-on experience building RFI, site-query and project-communication workflows for Indian builders at iStudio Technologies, a Chennai software company with 17+ years delivering web, mobile and ERP products. About iStudio Technologies.

Updated: October 2026. Serving builders and contractors across Chennai, Tamil Nadu and India. Figures are illustrative.

11 Questions

Construction RFI software FAQ

What is an RFI in construction?
An RFI, or Request for Information, is a formal written question raised from the site to the office or the architect when a drawing, specification or site condition is unclear, missing or contradictory. It records the question, who must answer, and by when, so the right thing gets built instead of a guess. Cornerstone AI runs RFIs on the project record itself.
What is construction RFI software?
Construction RFI software is the tool that raises, routes, tracks and closes RFIs. Instead of questions lost in WhatsApp and email, every RFI has a number, an owner, a due date, the answer with attachments, and a status. Cornerstone AI keeps that log on the project, so nothing sits unanswered and every decision is on the record.
How does the RFI workflow work?
Someone on site raises an RFI with the question, a photo and the drawing reference. It is routed to the person who must answer, with a due date. They respond with a clarification and any attachment, and the requestor closes the RFI once the answer is enough. Every step is time-stamped on the log.
Why do unanswered RFIs cost money?
An RFI that sits unanswered stalls the work that depends on the answer, and if the team guesses wrong, it becomes rework. Because RFIs are a leading source of delay on projects, tracking response time and ageing turns a hidden cost into something you can see and chase before it hits the schedule.
What types of RFI does it handle?
It handles the common types: a design clarification, a drawing or specification conflict, a dimension mismatch, a field condition that differs from the drawing, a material substitution request, and an owner-requested change. Each is logged the same way, so your RFI log is one consistent record.
Can the site raise an RFI from mobile?
Yes. A site engineer raises an RFI from the phone with a photo and a short question, and it reaches the right person immediately. The answer comes back to the same thread, so the field is never waiting on an email chain.
Does it keep an RFI log and audit trail?
Yes. Every RFI sits in a numbered log with its question, owner, due date, response, attachments and status. The full history is time-stamped, so months later you can show exactly what was asked, who answered, and what was decided.
Does the RFI connect to the schedule?
Yes. Because the RFI lives on the project, you can see which task is waiting on an answer, and an overdue RFI that blocks a scheduled task is flagged. The GenAI chat will also list open and overdue RFIs when you ask.
How much does it cost in India?
Cornerstone AI is priced for the Indian market and sized to your projects and users. RFI management is a built-in part of the platform rather than a separate add-on. A free demo is available and pricing is shared on request.
Who builds and supports it?
It is built and supported by iStudio Technologies, a Chennai-based software company with 17+ years of experience delivering web, mobile and ERP software for Indian businesses.

Book a free construction RFI demo

See Cornerstone AI raise an RFI from site, route it to a consultant, capture the answer on the record, and track the response time. Then ask the GenAI chat what is overdue. No technical experience needed.

iStudio Technologies · No. 5, 1st Floor, Arcot Road, Valsaravakkam, Chennai – 600087 · +91-8807003902 · info@istudiotech.in

Enquiry Now
close slider
[]
1 Step 1
keyboard_arrow_leftPrevious
Nextkeyboard_arrow_right
FormCraft - WordPress form builder