The Master Plan tells Singapore what a site may broadly become. Development control decides whether one actual proposal can fit inside that planning framework.
A site may be zoned Residential, Commercial, Business, Hotel or another use and still not have permission for a particular building. The design has to fit the allowed use, development intensity, setbacks, height, access, urban-design requirements and the technical requirements of other public agencies.
URA calls this project-level process development control. The central legal output is planning permission under the Planning Act framework.
The public-safe chain is: check statutory plan → identify approved or proposed use → determine whether planning permission is required → prepare the appropriate application or lodgment → assess zoning and development-control rules → consult relevant agencies → issue planning decision → obtain separate building, fire-safety, licensing and operational approvals → build and use according to the approved plans.
Quick answer: what does URA planning permission decide?
Planning permission answers whether the proposed development and use of land are acceptable from the planning perspective.
URA’s current planning-permission page states that planning permission is required for development and building works, including changes of use, unless the proposal falls within an applicable exemption or lodgment route.
The decision is therefore different from approving structural engineering, fire systems, food-shop operations or childcare licensing. Those sit in other regulatory systems.
1. Development control begins with the prevailing Master Plan
The first planning question is what the statutory Master Plan allows on the site.
The zoning sets the broad use framework. The Gross Plot Ratio controls intensity where specified. The Written Statement, Special and Detailed Control Plans and other planning provisions add context.
A project that conflicts fundamentally with the statutory plan may require a different planning route or a Master Plan amendment rather than an ordinary application pretending the conflict does not exist.
2. Existing approved use matters as much as the property’s appearance
A unit that looks like a shop may have an approved use different from the business a new tenant wants to operate.
URA therefore maintains an Enquiry on Approved Use of Premises service. Owners and operators can check the approved use before committing to a new activity.
The visual appearance of the space is not legal evidence that every similar business use is already approved.
3. Changing use can create planning impacts even when no walls move
Development control regulates more than physical construction.
Changing a shop into a school, a warehouse unit into another activity or a commercial premise into a higher-impact use can change traffic, noise, parking, fire-safety, servicing and neighbour impacts without adding a single square metre.
URA’s current change-of-use guidance therefore states that planning permission may be required and that applications are assessed against Master Plan zoning, prevailing guidelines and compatibility with surrounding development.
4. The ordinary Development Application is the project-level planning route
For a building project requiring planning permission, the applicant can submit a Development Application to URA.
The submission describes the proposed development, its land use, GFA, design, access and other planning information needed for assessment.
Planning applications are generally prepared by professional consultants for larger projects because the proposal must demonstrate compliance across many interlocking controls rather than simply complete a consumer form.
5. An Outline Application lets a developer test principle before full design
A developer may need to know whether the planning concept is acceptable before paying for full architectural and engineering detail.
URA’s Outline Application route allows planning issues to be tested at an earlier, less detailed stage.
The value is risk reduction: settle major questions of use, intensity or planning principle before investing in a complete design that may later prove unacceptable.
6. Planning permission can expire if the project is not implemented
A planning approval is not necessarily an indefinite right that can be stored forever while planning rules change around it.
URA provides an application route for extension of written permission where the applicant cannot implement the approved project within the relevant validity period.
The extension process asks for reasons and progress information, reinforcing that planning permission belongs to a live development process rather than a perpetual abstract entitlement.
7. Some low-risk proposals can use Plan Lodgment
Not every compliant proposal needs the same intensity of case-by-case assessment.
URA’s Plan Lodgment Scheme allows specified proposals that meet all stated conditions to be registered and obtain an immediate planning approval through lodgment.
The model shifts more compliance responsibility to the applicant and Qualified Person: instant processing is possible because the proposal already fits a clearly defined low-discretion rule set.
8. Change of Use Lodgment creates a similar fast lane
URA also allows specified changes of use in selected premises to proceed through Change of Use Lodgment where every scheme condition is met.
Current 2026 guidance states that successful lodgment receives an acknowledgement approval on the same day.
If the proposed use does not fit the lodgment scheme, the operator must use the ordinary Change of Use application instead.
Fast approval therefore comes from greater standardisation, not from the planning system abandoning control.
9. Some development and building works are exempt from planning permission
URA maintains an exemption list for specified works that do not require planning permission.
This prevents the planning system from spending professional and regulatory effort on minor works whose planning impacts are sufficiently controlled through exemption conditions.
Exemption is conditional. A proposal outside the stated conditions does not become exempt merely because it appears small to the owner.
10. GPR tests total intensity
Development control checks whether the project remains within the permissible Gross Plot Ratio and GFA framework.
That calculation is not only arithmetic. GFA classification, site area, bonus schemes and other provisions can affect the final permitted floor area.
The Master Plan GPR is also an upper bound. A development that cannot physically satisfy setbacks, height or other requirements may not be able to use the full theoretical GFA.
11. Setbacks protect streets, neighbours and future infrastructure
Buildings cannot usually occupy every centimetre of land up to every boundary.
Setbacks and buffers can preserve road space, greenery, fire access, privacy, environmental separation and a workable relationship between neighbouring developments.
The exact requirement depends on development type and site context, which is why URA publishes separate handbooks for different land uses.
12. Height is controlled through more than one system
A site may have planning height expectations and also be subject to technical height controls.
Aviation, security, conservation, urban-design and local contextual requirements can all influence the final allowable height.
This is why a high GPR cannot be translated mechanically into a tall building. Development control has to reconcile intensity with the vertical envelope actually available.
13. Access and traffic are planning issues before they become congestion
A development can be perfectly designed internally and still fail the city if thousands of additional vehicle trips enter through one unsuitable road.
URA therefore works with agencies such as LTA on access, traffic and transport requirements.
Large projects may need traffic assessments, road improvements or specific access arrangements before the planning proposal becomes acceptable.
14. Drainage and utilities can reshape the project
A building has to connect to the physical city.
Drainage reserves, sewer or water requirements, electrical infrastructure and other utility needs can affect site layout and development feasibility.
Development control therefore acts as an integration point between land-use planning and the technical networks that make the development usable.
15. Fire-safety approval remains a different regulatory gate
URA may find a land use and development form acceptable while SCDF still requires fire-safety plans, certificates or operational conditions under the Fire Safety Act.
Planning permission therefore should not be read as “all government approvals obtained”.
Different agencies protect different public interests. The project becomes lawful only when the required gates relevant to that project are all satisfied.
16. Planning approval and building approval are different
URA focuses on planning and land-use matters. BCA and other agencies regulate building and engineering requirements within their statutory roles.
A project can therefore have planning permission and still require building-plan, structural, accessibility, fire and technical approvals before construction or occupation.
The planning approval answers “may this development concept exist here?” It does not answer every later question about how the building must be engineered.
17. Planning approval and business licensing are also different
URA’s change-of-use guidance explicitly reminds applicants that after planning approval, separate permits and licences may still be required from agencies such as SCDF, SFA or ECDA depending on the business.
A premises can therefore be planning-approved for a food-and-beverage use while the operator still needs the food-business licences and operational compliance required by SFA.
The use permission and the operating licence regulate different risks.
18. Landowner consent is not the same as planning permission
A landlord can agree to a renovation or new business and still be unable to make the proposal planning-compliant by private contract.
URA applications can require owner consent where the applicant is not the owner, but that consent is only one prerequisite.
Private ownership controls who may use the land contractually. Planning law controls how the land may be developed or used in the public planning system.
19. Land Betterment Charge can appear when planning permission raises land value
A planning approval or change in use can increase development potential and therefore land value.
URA’s current change-of-use guidance notes that Land Betterment Charge may be collected by the Singapore Land Authority for applicable changes.
The planning decision and the value-capture mechanism are distinct but connected: one changes permissible development; the other can recover part of the resulting land-value uplift for the public where the law provides.
20. CORENET X changes how large development applications move through Government
Singapore is progressively shifting building and regulatory submissions into CORENET X.
URA’s current Development Application page states that from 1 October 2025, all new projects with GFA of 30,000 m² and above must submit development applications via CORENET X. Projects of 5,000 m² and above use the IFC-SG model format, while smaller projects have lighter format options under the prevailing rules.
The objective is not merely a new upload portal. Coordinated digital submissions can reduce repeated agency handoffs and allow project information to be shared more consistently across regulators.
21. Development applications need an explicit statement of intent
URA’s August 2026 submission requirements include items such as the application form, CAD or BIM files, agency clearances where relevant and a Development Statement of Intent.
The planning authority therefore assesses more than drawings. The proposal has to explain what the development is trying to achieve and how it responds to planning requirements.
Good planning submissions make the reasoning legible rather than forcing reviewers to infer the whole concept from geometry alone.
22. Development control is contextual, not purely algorithmic
Some controls are numerical. Others require planning judgment.
URA’s 2026 guidelines repeatedly refer to site context, surrounding character, traffic, impact on neighbours and requirements of other agencies.
Two technically similar proposals can therefore receive different planning outcomes if their contexts differ materially.
This is not arbitrary if the relevant differences are real and the planning principles are applied consistently.
23. A worked example: shop becomes commercial school
Imagine a business owner wants to convert a shop unit into a commercial school.
The owner checks the approved use and whether the premises qualifies for a lodgment route. If not, a Change of Use application is submitted. URA assesses Master Plan zoning, compatibility, traffic and potential disamenity. relevant agencies may be consulted. if planning permission is granted, the operator still obtains the other licences and fire-safety approvals required before operating.
The walls may barely change. The regulatory state changes several times.
24. A worked example: new mixed-use development
Suppose a developer proposes a large mixed-use building on a site whose Master Plan zoning and GPR permit the broad concept.
Professional consultants prepare a Development Application. The project is tested against GFA, setbacks, urban design, access, technical height and agency requirements. planning permission establishes the approved planning envelope. building, structural, fire and other regulatory submissions continue through their respective processes.
The Master Plan made the opportunity possible. Development control determines whether this actual design can use it.
25. Common misconceptions
Misconception: If the zoning allows the use, no application is needed.
No. zoning is the statutory planning framework; many specific developments and changes of use still require planning permission.
Misconception: URA planning approval means construction can start immediately.
No. building, structural, fire-safety and other required approvals remain separate.
Misconception: Landlord consent makes a use legal.
No. private consent and public planning permission are separate.
Misconception: Every small renovation requires a full Development Application.
No. exemptions and lodgment schemes exist for qualifying works.
Misconception: Development control is only about buildings.
No. changes of land or premises use can require planning permission even without major physical works.
26. The deeper idea: development control is where a national plan meets one real site
The Master Plan operates at city scale. Buildings operate at parcel scale.
Development control is the translation layer between them.
It takes a broad statutory rule—Residential 2.8, Commercial, White, Business 2—and tests a specific geometry, access route, use, neighbour relationship and engineering context against it. Other agencies contribute the constraints they own. The approved result becomes a project-specific planning envelope.
That is how Singapore avoids two opposite failures: a Master Plan so vague that every building becomes an improvisation, and a planning code so rigid that every parcel must produce the same building.
The city supplies the rule. Development control tests the fit.