Studio Contour: Why We Keep an NKDA Submission Log for Every Client

Studio Contour keeps a submission log for every single client who comes to us for an NKDA building plan sanction, and we did not start doing this because a manual told us to, we started doing it because we watched enough files get stuck in queue for reasons nobody could quite reconstruct later, and we decided that was never going to happen to one of our own clients again.

If you are a plot owner in New Town right now, staring down the sanction process for the first time, or you are the person who got a plan rejected once already and is trying to figure out what actually went wrong, this is written for you specifically. Not for other architects, not for a general audience, for the person who owns a plot in Action Area I, II or III, or in Salt Lake or Rajarhat, and needs the paperwork to move without three months of silence in between.

We are Studio Contour, an architecture and interior design studio based in New Town, Kolkata, founded in 2014, and across a little over a decade we have delivered 330+ buildings across New Town, Salt Lake, Rajarhat and the wider Kolkata belt. Our principal architect, Sumana Kumar, has spent that decade working residential and commercial projects through the NKDA, KMC and Bidhannagar Municipal Corporation sanction processes directly, which is a different kind of familiarity than reading the building code once and hoping it holds. This article is about one specific habit that habit produced, the submission log, and why it matters more than most homeowners realise until they are the one chasing a file that has gone quiet somewhere in the system.

What Actually Goes Wrong Without a Submission Log

Here is the pattern we see most often when a homeowner comes to us after a rejected or stalled application elsewhere. Nobody can tell them, with dates and specifics, what was submitted, when it was submitted, what version of the drawing it was, who at the office received it, and what query came back and when. The file becomes a kind of fog. The owner remembers dropping off a set of drawings sometime in a given month, remembers a phone call about a query, but cannot reconstruct the sequence well enough to know whether the resubmission actually addressed the query or just repeated the same drawing with a cover letter attached.

The catch here is that NKDA sanction files move through several rounds of scrutiny, and each round can generate its own set of remarks on setback compliance, floor area ratio, parking provision, or structural drawings, and if you do not have a clean record of exactly which remark was answered by exactly which revised sheet, you end up re-answering the same query twice, or worse, missing one entirely because it got buried under a newer round of comments. A missed query does not just cost you a delay, it can send the whole file back to the bottom of a queue, and for a plot owner who is paying EMI on a loan while a house sits unbuilt, that kind of delay is not abstract, it is money leaving the account every month for nothing.

So the submission log exists to remove the fog. It is not a fancy piece of software, it is a disciplined record, but the discipline is the entire point.

What Our NKDA Submission Log Actually Tracks

For every client file, we log the same fields every single time, and we do it the same way whether the project is a small G+1 residence or a larger commercial building. The habit only works if it is consistent, so we never skip a field because a submission feels routine.

That last item matters more than it sounds. A large share of the delay we see in NKDA files traces back to something sitting on the client's side, a mutation document not yet collected, a no-objection certificate from a neighbour not yet signed, a soil test report not yet in hand. When that is logged with a date and a follow-up reminder attached to it, it stops being an abstract thing someone meant to get around to, and it becomes a tracked item with an owner. Our guide on the documents required for NKDA building sanction walks through that full list if you want to see what tends to sit pending longest.

A Worked Example, Stage By Stage

Take a fairly typical G+2 residential file on a New Town plot, the kind we handle constantly. Here is roughly how the submission log fills in across the life of that file, and why each entry earns its place.

At the revision stage is where most files without a log start to break down, because a typical scrutiny round does not come back as one tidy list, it comes back scattered, sometimes a setback observation, sometimes a query on the floor area ratio calculation, sometimes a structural note that has nothing to do with the architectural drawings at all. Our practice cross-references every single remark against the specific revised sheet that answers it, in the log itself, so if a query resurfaces three weeks later asking whether it was addressed, we are not scrambling to reconstruct an answer from memory, we are pulling up a dated entry that already has it.

This is also why, when we take on a project that another architect started and stalled, the first thing we ask for is whatever paper trail exists. If there is one, rebuilding the file is fast. If there is not, we have to reconstruct the history from whatever the client remembers and whatever copies survive, which is slower and occasionally means resubmitting things that may already have been submitted once, just to be safe. Our guide to why building plans get rejected under NKDA covers the specific failure patterns we see most, and a broken paper trail sits near the top of that list even though it is rarely the stated reason for rejection.

Corner Plots, Different Action Areas, and Why the Log Gets Heavier

Not every plot generates the same volume of correspondence. A straightforward mid-block plot in a settled part of Action Area I tends to move through scrutiny with fewer rounds than, say, a corner plot with two road frontages, where setback calculations have to satisfy both frontages simultaneously and parking access has to be justified against two possible entry points. The heavier the technical case, the more the submission log earns its keep, because there are simply more moving parts that could get answered out of order otherwise.

The same logic extends across the different bodies we work through. NKDA governs most of New Town proper, but depending on where exactly a plot sits, a file might instead route through the Bidhannagar Municipal Corporation, or in parts of the older city fabric, through the Kolkata Municipal Corporation system entirely, and each body has its own submission rhythm, its own preferred documentation order, its own typical turnaround. Sumana Kumar's decade of working across all three is exactly what lets our team log the right things for the right authority rather than applying a generic checklist that happens to work for one body and quietly misses something specific to another. Whether an architect or an empanelled engineer is the right fit for a given file's scale is a separate question worth reading on its own, but the paperwork discipline underneath either choice should look the same.

Beyond the Sanction Itself: Occupancy and Mutation

The submission log does not close the day the plan gets sanctioned, because sanction is the middle of the process, not the end of it. Completion and occupancy documentation, and eventually mutation of the property record, all generate their own paper trail, and a client who kept a clean log through the sanction stage is in a much stronger position when it comes time to apply for the occupancy certificate, because the inspection dates, the as-built deviations if any, and the original sanctioned drawings are all sitting in one place rather than scattered across two years of folders and forwarded emails.

We have seen homeowners come back to us years after their house was built, needing to produce sanction paperwork for a bank loan or a resale transaction, and the ones whose original file was logged properly find that document in minutes. The ones whose file was not logged sometimes spend weeks trying to track down a copy from the authority's own records, which is not a fast process on a good day.

Why This Sits Inside Our Design Process, Not Alongside It

We do not treat the submission log as an administrative add-on that a junior staffer manages separately from the design work. It sits inside the same workflow as the drawings themselves, because the two are not actually separate things, a revised drawing sheet only means something in context of which remark it is answering, so tracking one without the other is half a record. When we take a client through residential architecture from concept to sanctioned drawing, or through a Vastu-compliant design brief where room orientation has to satisfy both the client's beliefs and the setback envelope simultaneously, the log grows alongside the drawing set, stage by stage, not as an afterthought bolted on once a query arrives.

It is also, frankly, part of why people search for phrases like the best architect for NKDA sanction and end up at our door. New Town has enough of its own residents who have been through a stalled or rejected file once already that word travels fast about which studio actually keeps its paperwork straight. We would rather earn that reputation the boring way, one logged entry at a time, than promise speed we cannot back with a record.

A Few Questions Owners Actually Ask Us

Does a submission log guarantee a faster sanction? No, and we would never claim that, because the timeline ultimately sits with the authority's own scrutiny schedule, not with us. What the log guarantees is that nothing on our side of the file causes an avoidable delay, and that if a query comes back, we answer it correctly the first time instead of guessing.

What happens if I switch architects mid-process? This is exactly the situation where a missing log costs the most. If your previous architect did not keep one, expect the new team, us or anyone else, to spend real time reconstructing the file before fresh submissions can go in with confidence.

Do you keep this record after the project is sanctioned? Yes, we hold it as part of the client's project file, which is precisely what makes later occupancy, mutation, or resale paperwork faster to assemble.

Is this specific to residential plots? No, we run the same discipline on commercial files, though commercial buildings in New Town, Kolkata tend to carry additional fire and structural clearances layered on top, which just means the log carries more rows, not a different structure.

Bringing This Back to Your Own Plot

If you are early in the process and just trying to understand the sequence of steps, our NKDA building plan sanction process guide for New Town is the right starting point before you commit to any architect. If you are already deep into a file that has gone quiet and you are not sure what was actually submitted last, that is a conversation worth having directly rather than guessing at over email, because reconstructing a stalled file properly usually needs someone looking at the actual drawing sheets and query letters side by side.

You can see the kind of residential work this discipline sits underneath in a project like our DE Block residence in New Town, and if you want to know more about the person behind the studio's approach to sanction work, our piece on who Sumana Kumar is and how Studio Contour was built covers that in full. At the end of the day, a submission log is a small, unglamorous habit, but it is the difference between a file that moves in a predictable rhythm and one that disappears into a drawer for three months. If you own a plot anywhere in New Town and want a straight answer on where your file stands, or where it should start, get in touch with us and we will walk you through exactly what we would log from day one.