RAJUK approval is a sequence, not a single event, and each stage depends on a document set assembled earlier. Developers who treat it as a queue to be waited in lose months. Developers who treat it as a document pipeline — knowing which paper is needed at which stage, and starting each one early — move through it materially faster on the same plot with the same architect.
The sequence
| Stage | What it establishes | Depends on |
|---|---|---|
| Land ownership and record clean-up | That the applicant holds clear title | Deeds, mutation, land tax receipts |
| Land use clearance | That the plot may be used as intended | Ownership records, location, applicable plan |
| Design within the applicable rules | Buildable envelope, ratio and coverage | Plot size, road width, use category |
| Building plan approval | Permission to construct the approved design | Drawings, structural design, professional certifications |
| NOCs and clearances | Fire, aviation height, environment and utilities, as applicable | Building height, use, location |
| Construction | — | Approved drawings |
| Occupancy | That the completed building may be occupied | As-built compliance with the approved plan |
Where projects actually lose time
Incomplete land records. The single most common delay is a mutation not completed or a khatian that still names a previous owner. It is discovered at clearance stage, and by then it takes as long as it takes. This is why land records belong in a system from the day of purchase — see land acquisition records.
Designing before clearance. A detailed design produced before land use clearance and the applicable ratio are confirmed frequently has to be redrawn, and the redraw costs weeks and consultant fees.
Discovering NOCs late. The list depends on height, use and location. Establishing it during feasibility costs a phone call. Establishing it at submission costs a resubmission.
Documents scattered across people. The deed is with the legal adviser, the mutation with an agent, the survey with the architect, the tax receipt in an accounts file. Every submission then becomes a collection exercise, and every query restarts it.
What to track, and why it belongs in a system
For each project, one screen should answer: which stage are we at, what was submitted and when, what was queried, what is outstanding, and who owns each open item. That is a workflow, not a folder. Two benefits follow immediately. Management can see where a project actually is rather than being told "it is with RAJUK". And when a query comes back, the response can be assembled from the same records that produced the submission.
Approval status changes commercial decisions
The approval stage determines what you may legitimately do commercially — what may be marketed, at what stage of certainty, and what a buyer may reasonably be told. Selling ahead of certainty is a familiar shortcut and a reliable source of later disputes, because a buyer who was shown a layout that then changes has a grievance, whatever the paperwork says. Feasibility numbers should also be re-run when the approved envelope differs from the assumed one — the unit count in a feasibility is an assumption until the plan is approved. See project-wise profitability.
Cost, and where it belongs
Approval costs — fees, consultants, professional certifications, utility connection charges — belong against the project, not in head office administration. They are a meaningful line on a mid-size residential building and they are almost always understated in the original budget, because the NOC list was not complete when the budget was written.
What to do next
For your current project, write down each approval stage, its status, the documents held for it, and who owns the next action. If assembling that takes more than an hour, the approval timeline is being managed by memory — see how land records and approval stages sit against the project.