Managing RFIs on Architecture Projects

If you run an architecture practice in India, you already know that a drawing is never really finished, because the moment it reaches site the contractor, the MEP consultant and the structural engineer all start asking questions, and every one of those questions is technically an RFI, a request for information, that you have to answer, log and sometimes bill for. This post is for the principal or project lead who is tired of RFIs scattered across WhatsApp, email and three versions of the same PDF, and who wants a calmer way to keep drawings, consultants, BOQs and billing in one place. Let me walk through what an RFI actually is, why they pile up, and how to run them so they stop eating your week.

What an RFI really is, and why yours are a mess

An RFI is a formal request during construction to clarify or fill a gap in the design information, and on a well-run project it is a healthy thing, because it means the people building the work are reading your drawings carefully. The problem is not the questions, it is where they live. On most Indian sites the contractor sends a photo on WhatsApp with a voice note, the client forwards an email at midnight, and the structural consultant marks up a print and couriers it back, so the same query exists in four places and none of them is the record. When the query is finally answered, that answer also lives in a chat thread, and six weeks later, when there is a dispute about who approved the beam drop, nobody can find it.

That is the real cost of loose RFIs, and it is worth being honest that this is where practices in architecture-heavy markets like Mumbai quietly lose both time and goodwill. The fix is a single log where the question, the drawing it relates to, the consultant who owns the answer, and the response all sit together with a date on them.

The RFI lifecycle, laid out so it can be tracked

Every RFI moves through the same stages, and once you can see the stages you can see where yours get stuck. Here is the shape of it.

The two stages that hurt most are "assigned" and "closed", because an RFI that sits unassigned for a week holds up site, and an RFI that is answered verbally but never closed properly is the one that comes back as a claim. If you keep the whole chain in one place, the person waiting on site can see exactly whose desk the question is on, which alone removes half the follow-up calls.

Tie every RFI to the drawing, the consultant and the BOQ

Here is the part that separates a tidy practice from a stressed one. An RFI is almost never just a question, it usually points at three other things, the drawing that needs revising, the consultant who owns the technical answer, and the bill of quantities line that changes because of it. When a contractor asks whether a wall moves 150mm, that is a drawing revision, a possible structural check, and a change in blockwork quantity all at once.

If those three live in separate tools, someone has to remember to update all three, and someone always forgets, so the drawing gets revised but the BOQ does not, and the quantity surveyor bills the old number. When your drawings with pinned markups, your consultant coordination and your quantities sit in one connected workspace, answering the RFI updates the record in one motion. This is the same argument I make about coordinating MEP and structural consultants generally, because RFIs are where that coordination is tested in public, on site, under time pressure.

The billing side nobody logs until it is too late

Let me be honest about the money, because this is where RFIs go from an admin nuisance to a margin leak. A good share of RFIs reveal a change that is genuinely outside the original scope, a client-driven variation, a site condition nobody could have foreseen, a specification upgrade. Each of those is billable, and yet most practices never bill for them, because the RFI was answered informally and never captured as a variation with a cost attached. Across a project that is real fee left on the table, and it compounds if you run several projects at once.

The discipline is simple to state and hard to do by memory: at the moment you close an RFI, decide whether it changed scope, and if it did, raise it as a variation tied to your milestone billing. This is exactly why I treat RFIs as part of billing and fee collection for architecture practices rather than as a purely technical process, and it is why your fee structure for the project should already spell out how variations are charged, so the conversation with the client is a reference, not a fight.

That last bar is the one that should worry you, because the billable variation is the highest-value part of the whole process and it usually gets the least attention.

Run RFIs inside one connected workspace

Here is how I think it should work, and it is how we built it into Designa. Every project carries construction drawings you can pin comments onto, so an RFI is raised right on the detail it refers to, not in a separate email. You assign it to the architect or the relevant consultant, it shows up on their task list, and the principal reviews the answer before it is issued. When the answer changes a quantity, the room-by-room specs and the BOQ update in the same place, and when it changes scope, you raise the variation against the project's milestone billing without leaving the workspace. Because the whole studio runs in one connected system rather than five disconnected tools, the drawing, the consultant, the quantity and the fee stay in step by default.

There is also a client-facing benefit that matters more than it sounds. When a client can see, in a branded portal, that a change they asked for has been logged, priced and approved, the month-end billing conversation stops being a surprise. Unlimited free client logins mean you never ration that visibility, and the record is timestamped, so "I never approved that" simply does not happen.

The wider point about tool sprawl

RFIs are a good stress test for how your practice runs, because they touch design, coordination, drawings, quantities and money all at once, so if your RFIs are chaotic it usually means those five things live in five tools. Whether you call the discipline interior design or architecture, the standards bodies expect a clear paper trail, and both the Council of Architecture and the Institute of Indian Interior Designers frame professional practice around documented, accountable process. A single workspace is simply the practical way to keep that trail without hiring someone whose whole job is chasing threads. If you are weighing tools, my guide to the best software for design studios in India and the note on how flat rupee pricing works for the whole studio are the two I would read next.

The calm version of RFI management is not more discipline from you at eleven at night, it is a system where the question, the drawing, the consultant and the fee already sit together. See that working on a real project setup at demo.designa.work, and if it fits how your practice runs, the founding offer with done-for-you onboarding and a 7-day money-back guarantee is at go.designa.work.