Ask ten Indian architects to name the stages of a project and you will get ten slightly different lists, which is fine, because the labels matter less than the discipline of actually moving through them in order rather than collapsing everything into "design" and "site". This post is for the principal or project architect who wants a clean, India-usable breakdown of the stages, what each one has to produce, and how to keep drawings, consultants, quantities and billing lined up as the project moves, so that nothing quietly falls between two stages and comes back as a problem. Let me lay out the stages the way they play out on real projects here.
The stages, from first sketch to handover
The internationally recognised sequence, which the Council of Architecture broadly mirrors in its guidance, runs from concept through to closeout, and it holds up whether you are doing a bungalow in Pune or a small office fit-out. What changes in India is the weight of certain stages, approvals and site supervision usually carry more effort than the neat diagrams suggest, so build your plan around that reality.
| Stage | What it produces | Where it lives in a workspace |
|---|---|---|
| Brief and concept | The client's needs, site study, first design direction | Leads and project brief |
| Schematic design | Layouts, massing, early mood boards for approval | Room-by-room specs and client portal |
| Design development | Resolved plans, materials, coordination with consultants | Specs, drawings and consultant tasks |
| Working drawings | Construction-ready details and the BOQ | Drawings with pins and quantities |
| Tendering | Vendor selection, comparison, purchase orders | Procurement |
| Construction stage | Site supervision, RFIs, snags, quality checks | Site updates and snags |
| Handover | Final checks, documentation, closeout | Project handover |
The value of naming the stages is not bureaucracy, it is that each stage has a clear "done", so you and the client both know when one phase has closed and the next has begun, which is exactly what makes stage-wise billing possible and fair.
The early stages set up everything downstream
Concept and schematic design feel like the fun part, and they are, but they are also where the project's discipline is either established or lost. A concept that captured the client's brief properly, with the site study and the constraints written down, means design development has a firm base, whereas a concept that skipped straight to pretty pictures means you will be reworking layouts for months. This is why I push studios to treat schematic approval as a real gate, present the layouts and early mood boards, get the client to approve them online, and only then move on.
That online approval matters more than it sounds, because a verbal "looks good" in a meeting is not the same as a recorded sign-off, and the difference shows up three months later when someone changes their mind. Setting this up well is its own small craft, which is why I wrote a full piece on how to set up a branded client portal for your studio, so the client approves the schematic in a portal that carries your name, and the approval is timestamped and kept.
Key takeaways
- Each stage needs a clear "done" so billing and handoffs are unambiguous
- Treat schematic approval as a real gate, recorded online, not a verbal nod in a meeting
- The stages only stay in step if drawings, consultants, quantities and billing live together
Design development and working drawings: where coordination is won
Design development is where your project meets the other consultants, and it is genuinely the make-or-break stretch, because this is when the structural engineer, the MEP consultant and your own drawings either come into alignment or start to drift apart. A slab thickness the structural engineer needs, a duct route the MEP consultant requires, a beam that clashes with your ceiling design, all of it gets resolved here or it gets discovered on site at ten times the cost. I go deep on this in coordinating MEP and structural consultants, because it is the stage where tool sprawl does the most quiet damage.
Working drawings then turn the resolved design into something a contractor can build, and they produce the bill of quantities that drives your tender and your budget. The discipline here is that the drawings and the quantities have to agree, so when a detail changes, the quantity changes with it, and if those two live in separate places the mismatch is where your budget starts lying to you.
Tendering and construction: the stages that touch money most
Tendering is where the design becomes a set of purchase decisions, and it is where a lot of practices lose the thread, because the vendor comparison, the rate negotiation and the eventual purchase order can end up in emails and WhatsApp instead of a tracked process. When tendering runs cleanly, you compare vendors on the same BOQ, you raise purchase orders against the approved quantities, and every rate traces back to what was budgeted, which is the whole point of keeping procurement disciplined rather than ad hoc.
The construction stage is the longest and the messiest, full of site updates, RFIs, snags and quality checks, and it is where an Indian project genuinely lives or dies. Site photos, pinned markups on drawings, a running snag list that the client can see, and milestone billing tied to actual progress, these are what keep the construction stage honest. Then handover closes the loop with final checks and documentation, and a project that was run in stages hands over cleanly because there is a record of every decision along the way.
Keep the stages connected, not scattered
Here is the honest problem. Most practices run the design in one set of tools, the consultants over email, the drawings in a folder, the BOQ in Excel, and the billing in the accountant's software, so the stages exist in the architect's head but not in any single system, and that gap is exactly where things fall through. The calmer way is to run the whole sequence in one connected system rather than five disconnected ones, so that moving from schematic to design development, or from working drawings to tendering, is a visible transition and not a leap of faith.
That is how Designa is built, the brief starts as a lead, the specs are built room by room, the client approves the schematic in a branded portal, drawings carry pinned RFIs and snags, the BOQ feeds procurement, and each completed stage becomes a compliant GST invoice through milestone billing, all syncing to Tally or Zoho Books. If you are trying to work out which tools you actually need for this and which you can drop, my piece on every tool a design studio needs and which you can skip is the practical companion to this one, and for a market like Mumbai where projects move fast that consolidation matters even more. Professional bodies like the Institute of Indian Interior Designers frame good practice around exactly this kind of documented, stage-by-stage process, and it applies whether your work is architecture or interior design.
Running a project in clear stages is not about paperwork, it is about never being surprised, and the surprises get expensive precisely at the joins between stages. See the full sequence working on a real project at demo.designa.work, and when it fits, the founding offer with done-for-you onboarding and a 7-day money-back guarantee is at go.designa.work.
Frequently asked questions
What are the main stages of an architecture project?
Broadly brief and concept, schematic design, design development, working drawings, tendering, the construction stage, and handover, each with its own clear deliverable and sign-off.
Why should I treat schematic approval as a formal gate?
Because a recorded online sign-off protects you when someone changes their mind later, whereas a verbal nod in a meeting leaves you reworking layouts with no evidence of what was agreed.
How do project stages relate to billing?
Each stage has a clear completion point, which lets you release fees stage by stage through milestone billing, so you are paid as you deliver rather than carrying months of unbilled work.
Where does coordination with other consultants happen?
Mainly in design development and working drawings, where the structural and MEP inputs must align with your drawings before the design reaches site, ideally coordinated in one shared workspace.