Studio Contour's Sumana Kumar on the NKDA Query That Costs Owners the Most Time

Studio Contour has sat across the table from enough New Town plot owners by now to know that almost every sanction delay traces back to one question, and it is rarely the question the owner thinks it is. People come in worried about floor area ratio, or whether their setback is a few feet short, or whether the front elevation will get flagged on aesthetic grounds. Those things matter, but they are rarely what stalls a file for six or eight weeks at NKDA. The query that actually eats the calendar is a quieter one, and it sits buried inside the paperwork stage rather than the design stage, which is exactly why most owners do not see it coming until it has already cost them a month.

This piece is written for the person who has already submitted a plan, or is about to, and wants to understand why NKDA files that look clean on paper still sit for weeks without movement. We are Sumana Kumar's studio, Studio Contour, practising out of New Town since 2014 with 330+ buildings behind us across New Town, Salt Lake, Rajarhat and greater Kolkata, and this is the pattern we see on repeat, told the way we would tell it to a client sitting across our desk.

The Query That Actually Costs the Most Time

Here is the honest version of it, and it is going to sound almost too simple to be the thing that costs owners the most time. The query is title and ownership document consistency, specifically whether the name on the land deed, the name on the mutation certificate, the name on the property tax receipt and the name on the sanction application are all the same person, spelled the same way, in the same order, with the same father's name or spouse's name attached where the record calls for it. It sounds like a formality. In practice it is the single most common reason a file gets parked rather than processed, because the moment there is a mismatch, even a small one, the file does not get rejected outright, it just stops moving while the desk waits for a clarification that the applicant does not know has been raised.

The reason this particular query costs more time than a design objection is structural, not procedural. A design objection, say a setback shortfall or an FAR overshoot, comes back to the applicant as a specific, actionable note, and a competent architect can usually resolve it in one redrawn sheet and one resubmission. A document mismatch does not generate that kind of clean feedback loop. It sits in a queue, it may or may not get flagged verbally at a counter visit, and if the owner is running the file themselves without someone tracking it daily, weeks pass before anyone realises the plan is not stuck on design at all, it is stuck on a spelling variation between two decades-old property documents.

Why Owners Rarely Catch It Themselves

Most first-time owners assume the hard part of getting a plan through NKDA is the architecture, and to be fair, that assumption is not unreasonable, because the architecture is the part they can see and evaluate. But the sanction file is really two parcels bundled together, a technical drawing parcel and a legal documentation parcel, and NKDA processes both before it issues anything. Our guide to documents required for NKDA building sanction walks through the full list, but the list itself is not the hard part. The hard part is that these documents were often generated years apart, by different clerks, under different naming conventions, sometimes before the plot even had its current mutation status, and nobody cross-checked them against each other until the sanction application forced the comparison.

For instance, a plot bought in 2011 might carry a deed with the owner's full legal name including a middle initial, while the mutation certificate issued in 2016 dropped the initial because the Bidhannagar Municipal Corporation clerk who processed it typed it the way it appeared on a different supporting document. Individually, both papers are valid. Side by side inside a sanction file, they read as two different people, and that discrepancy is exactly the kind of thing that triggers a hold rather than an approval or a rejection.

The Mechanism, Explained Properly

It helps to understand what is actually happening inside NKDA once a file lands, because the mechanism explains why this specific query behaves so differently from every other kind of objection. A sanction file moves through a sequence of internal checks, typically starting with a completeness check, then a technical scrutiny against the NKDA building rules covering height, coverage and setback compliance, and running in parallel with a title and ownership verification against municipal records. The technical scrutiny is a known, bounded process, and any architect who works this circuit regularly can predict roughly how a plan will be read against the rulebook before it is even submitted. Our NKDA building plan sanction process guide for New Town covers that sequence step by step for anyone who wants the fuller picture.

The ownership verification is a different animal, because it depends on records that sit outside the architect's drawing set entirely, records that were generated by revenue offices, sub-registrars and municipal assessment departments over years, sometimes decades. When those records disagree with each other, the file does not fail the technical scrutiny, it simply cannot clear the ownership check, and NKDA will not issue a sanction on a file where ownership is not cleanly established, for the fairly obvious reason that sanctioning a plan on disputed or ambiguous ownership creates a liability nobody at the desk wants to carry. So the file waits, the technical drawings sit fully compliant and untouched, and the owner is left wondering why nothing is happening when, on paper, everything looks approvable.

A Worked Example

Take a fairly typical case we have handled more than once, a G+2 residential plot in one of the newer New Town action areas, purchased by a joint family where the original deed was in the grandfather's name, the mutation had since moved to the father as legal heir, and the sanction application was being filed in the son's name as the intending builder with a power of attorney from the father. On the drawing side, none of this mattered, the design was compliant, the setbacks were correct, the coverage was within limit, and a first-pass reviewer would have expected a straightforward sanction. On the documentation side, the file needed a clean chain, deed to mutation to heir succession to power of attorney, each link matching the next in name and spelling, before NKDA would treat the son's application as valid.

Left to the family alone, this would likely have meant a trip to the desk, a verbal note about the gap, a return visit two weeks later to ask what exactly was needed, another round to the sub-registrar's office for a certified copy, and a resubmission that then re-enters the queue rather than continuing from where it stopped. We built the succession chain into the file before submission, flagged the power of attorney's wording against what NKDA typically wants to see, and the file cleared technical and ownership scrutiny in the same pass. That single piece of preparation, done before the file ever reached the counter, is the difference between a six-week wait and a straightforward approval. You can see the kind of residential work this comes out of in our G4 residence project in Action Area 2.

Sub-Cases That Change the Timeline

The grandfather-to-father-to-son chain above is the most common version, but it is far from the only one, and each variant has its own wrinkle worth knowing about before you submit.

A corner plot case is worth a special mention because it compounds two separate review tracks at once, the ownership check and the dual-frontage technical review, and we cover the technical side of that specifically in a separate piece for anyone dealing with a two-road-frontage plot. Similarly, once a file does clear and construction is underway, the same discipline around document consistency carries forward into the occupancy certificate stage, because NKDA cross-checks the same ownership chain again before issuing completion sign-off, and a gap papered over at the sanction stage has a habit of resurfacing there if it was not properly closed the first time.

What Sumana Kumar and Studio Contour Actually Do Differently

None of this is exotic knowledge, and we are not going to pretend it is some closely guarded trick. What it actually takes is deep working familiarity with how NKDA, KMC and Bidhannagar Municipal Corporation files move in practice, built up over years of taking projects through those exact processes and paying attention to where they stall. Sumana Kumar, our principal architect, has run enough sanction files through New Town, Salt Lake and Rajarhat to know which document combinations tend to raise a flag before the file is even submitted, and the studio's habit is to build the ownership chain alongside the drawing set from day one rather than treating paperwork as an afterthought once the design is locked. That is really the whole difference, catching the query before the desk does, instead of finding out about it three weeks into a silent hold.

This is also why, when people search for a top NKDA architect or the best architect for NKDA sanction, they tend to land on studios that can talk about this kind of process detail rather than just show a portfolio, because a good portfolio tells you what a firm can design, and a good sanction record tells you what a firm can actually get through the desk. We would rather be judged on the second one. Our own residential process, from first sketch through residential architecture drawings to sanction-ready documentation, is built around exactly this kind of front-loaded diligence, and it extends into how we handle Vastu-compliant design requests too, since plot orientation questions and ownership documentation questions often surface at the same client meeting.

Beyond the Ownership Query: Other Reasons Files Stall

It would be misleading to suggest the ownership and title query is the only thing that slows a file down, so it is worth being upfront about the rest of the field. Setback and coverage miscalculations remain a real cause of rejection, particularly on plots where the owner has an old survey that does not match current FAR and ground coverage rules or has not accounted for the current setback requirements for the action area their plot sits in. Incomplete structural stability certificates, missing soil test reports on taller structures, and NOCs that were applied for late in the process all show up regularly too. We go through the fuller list of common rejection triggers in our piece on why building plans get rejected at NKDA, and honestly, most of them are avoidable with the same discipline that resolves the ownership query, which is doing the unglamorous verification work before submission rather than after a hold.

The other thing worth naming plainly is that NKDA's process exists within a broader building code and zoning framework that most owners never have reason to study closely, and that is fine, that is not the owner's job. It is the architect's job to sit inside that framework daily and know where the friction points actually are, which is a fairly different skill from being good at design. Both matter. A beautiful plan that cannot clear ownership scrutiny is not a finished plan, it is a stalled one, and a technically flawless sanction file attached to a design nobody wants to live in is not much of a win either.

Frequently Asked Questions

How long does a clean NKDA file typically take once documentation is sorted? Once the ownership chain is fully resolved and the technical drawings are compliant, most residential files in New Town move through in a matter of weeks rather than months, though the exact window depends on the action area and the current desk load. Can I fix a document mismatch myself without an architect involved? Yes, in principle, but it usually means multiple trips to the sub-registrar or municipal office and a resubmission cycle that restarts the queue, whereas building the chain correctly before the first submission avoids that restart entirely. Does this apply to Salt Lake and Rajarhat too, or only New Town? The same principle holds anywhere sanction is routed through NKDA, KMC or Bidhannagar Municipal Corporation, since all three verify ownership against municipal and revenue records the same way. What if my plot has more than one of these issues at once, say an inherited title and a corner-plot dual frontage? That is exactly the kind of file where having someone map every review track in advance saves the most time, because the tracks run in parallel at the desk and a gap in one can hold up an otherwise-clear result on the other.

Where This Leaves You

If you are sitting on a New Town or Salt Lake plot and you are not sure whether your title documents will hold up cleanly against a mutation record from years ago, that uncertainty is worth resolving before you file, not after. It is the single highest-leverage thing you can check, and it is the thing most owners genuinely do not think to check until it has already cost them a month sitting in a silent queue. At the end of the day, the design work, the 3D visualization that helps you see the house before it is built, all of that is the part clients enjoy, and it should be. But the sanction file is the gate everything else has to pass through, and the query that costs the most time is rarely the one anyone expects. If you want a second set of eyes on where your file actually stands, get in touch with us and we will walk through it with you.