Key Takeaways
A well-managed approval process begins before the first submission is prepared. Clear professional responsibility, consistent information, and disciplined follow-up help keep URA, BCA, and SCDF requirements aligned.
- Appoint the Qualified Person (Architect/PE) early and define statutory responsibilities.
- Confirm planning parameters, site conditions, and the proposed use before design development.
- Coordinate URA Written Permission, BCA Building Plan, and SCDF fire safety requirements as one workflow.
- Keep drawings, calculations, document versions, and approval conditions consistent across submissions.
- Treat construction records and final clearances as part of the approval roadmap, not an afterthought.
1. Establish the project team and approval strategy
Singapore building projects often involve several authorities, consultants, and approval stages. The process is easier to manage when responsibility is assigned at the beginning rather than discovered through comments or rejected submissions. A practical approval strategy should connect the planning, building control, and fire safety workstreams. It should also reflect the project’s intended use, scale, and site conditions.
Define the Qualified Person (Architect/PE) and statutory responsibilities
The Qualified Person (Architect/PE) is central to the statutory submission process. Depending on the work, the appointed Architect or Professional Engineer prepares and submits the relevant plans and takes responsibility for the professional coordination required by the applicable regulations. The project owner should confirm the appointment, scope of work, and professional roles in writing.
The QP should be involved while the scheme is still being formed, not only when drawings are ready for filing. Their early review can identify gaps in authority requirements, consultant coordination, and documentation. For background on the role and statutory duties, review this guide to the Qualified Person in Singapore, then verify the professional’s standing through the Singapore practitioners register.
Confirm the project scope, site constraints, and proposed use
Start with a plain description of the proposed works: new construction, addition and alteration, change of use, refurbishment, or a combination. Record the site address, lot information, existing use, number of storeys, approximate floor area, and any known restrictions. These facts influence the approval route and should remain consistent in every later submission.
Site constraints deserve equal attention. Existing structures, adjoining properties, access arrangements, drainage, conservation considerations, and party-wall conditions can affect both design and programme. A short project brief agreed by the owner, QP, and consultants is a useful reference when detailed decisions begin to multiply.
Map URA WP, BCA BP, and SCDF FSC requirements
The three approval streams are related but not interchangeable. URA Written Permission addresses planning matters such as use and development parameters. BCA Building Plan approval concerns building works and technical compliance, while SCDF fire safety review focuses on life safety, access, fire protection, and related provisions. The project team should map each requirement against the drawings, calculations, declarations, and supporting documents needed.
This map should identify dependencies as well as deliverables. A change to the use or layout can affect fire safety assumptions; a revised fire compartment can affect the building plans. The purpose is not to force every submission into one package, but to make the consequences of each design decision visible.
Build a coordinated submission schedule and responsibility matrix
A schedule should show the information needed for each submission, the person responsible for producing it, the reviewer, and the decision date. Stellar Structures describes its service as combining engineering, architectural, and interior design solutions with regulatory submissions and approvals. That integrated, one-stop approach can simplify coordination when the relevant disciplines are brought together under a defined review process.
Set review gates before each filing. At each gate, confirm that the drawing list, calculations, forms, and supporting evidence use the same project data. The QP remains responsible for the statutory submission, but a clear internal matrix prevents technical tasks from being left between disciplines.
2. Prepare the information required before submission
Authority submissions are only as reliable as the information behind them. Missing title details, uncertain existing conditions, or inconsistent surveys can create comments that are difficult to resolve later. Preparation should therefore begin with source information, followed by coordinated design inputs and targeted consultations. The objective is a dependable project record that every consultant can use.
Verify land use, zoning, and approved planning parameters
Check the site’s current planning status and any approved parameters before committing to a detailed scheme. Confirm the permissible use, development intensity, height or envelope controls, setbacks, access expectations, and any conditions attached to earlier approvals. If the proposal involves a change of use or a material alteration, identify that issue early and discuss the correct route with the QP.
Do not rely on assumptions carried over from a neighbouring site or an old feasibility study. Planning parameters can be specific to the property and approval history. The verified information should be recorded in the project brief and reflected in the first coordinated drawing set.
Gather site, survey, title, and existing-building documentation
The team should assemble the documents that establish what exists and what can legally be changed. Depending on the project, this may include a topographical or measured survey, title information, approved plans, previous permissions, structural records, utility information, and photographs of the existing building. Existing-building work benefits from a careful comparison between records and site observations.
A document register helps distinguish confirmed information from items still awaiting verification. It also gives the QP a clear basis for identifying risks before submission. If a survey reveals an unexpected condition, the design can be adjusted while the cost and programme remain manageable.
Coordinate architectural, structural, mechanical, and fire safety inputs
Coordination should take place before drawings are formatted for submission. Architectural plans establish the arrangement and intended use; structural and mechanical inputs affect space, loads, services, and construction; fire safety design tests escape, compartmentation, protection, and access. Each discipline should review the others’ assumptions rather than working from isolated backgrounds.
A short interdisciplinary review can focus on the items most likely to cause rework. For an active project, the following sequence is practical:
- Freeze the project use, occupancy assumptions, and principal dimensions.
- Overlay structural grids, shafts, plant spaces, and service routes.
- Test escape paths, fire-rated separations, access, and emergency provisions.
- Record unresolved interfaces and assign an owner and due date.
After the review, issue one coordinated background for the submission drawings. The list is useful only if its open items are closed or clearly identified before filing; otherwise, coordination problems simply move into the authority review.
Identify supporting reports, clearances, and agency consultations
Some proposals require reports, clearances, or prior discussions beyond the core drawing package. Identify these by reviewing the site’s history, the proposed use, the scale of works, and known technical sensitivities. Where an agency consultation is appropriate, record the question asked, advice received, date, and any conditions that affect the design.
This record should not replace formal approval. It gives the team an audit trail and helps prevent contradictory explanations in later submissions. It also allows the owner to understand which matters are resolved and which remain subject to authority review.
3. Navigate the URA Written Permission submission
URA Written Permission is the planning checkpoint for many development proposals. The submission should explain the project clearly enough for the authority to assess its use, form, access, and relationship to the applicable planning controls. A technically attractive design can still face delay if its planning basis is unclear. Early alignment between the owner and QP is therefore valuable.
Determine when URA Written Permission is required
The need for Written Permission depends on the nature of the proposed development and the planning implications of the work. New development, additions, alterations, and changes in use should be screened against the applicable planning requirements before detailed design proceeds. The QP can advise on the likely route and whether previous permissions or conditions affect the proposal.
Keep a written record of the basis for the chosen route. This is especially helpful when a project combines interior changes with external works, a change of use, or an increase in intensity. Clear scoping reduces the risk of treating a planning matter as only a building-control matter.
Develop plans that address use, envelope, access, and planning controls
URA plans should make the proposed use and physical outcome easy to understand. Show the site context, relevant dimensions, building envelope, access arrangements, levels, and other planning information required for the application. The drawings should tell one consistent story from the written description through to the plans and schedules.
Avoid presenting unresolved alternatives as though they were an approved scheme. If an issue needs a planning decision, identify it and frame the supporting explanation carefully. A concise, coordinated package is generally easier to review than a larger set containing conflicting options.
Coordinate planning details with the Qualified Person and project consultants
The QP should lead the planning submission while consultants provide the discipline-specific information needed to support it. Architects, engineers, and specialists should check that their inputs use the same site boundary, levels, areas, use description, and design assumptions. The owner should also review the application narrative because it can create commitments that affect later stages.
For owners and developers, this is a useful point to confirm how professional responsibility is allocated. General information on professional roles can be found in this overview of professional engineering and architectural responsibilities, although the project team should rely on the applicable Singapore requirements for the actual submission.
Manage URA comments, revisions, and written approval conditions
When comments arrive, separate them into planning decisions, drawing corrections, clarifications, and conditions to be carried forward. Assign each response to a named person, then have the QP review the complete reply for consistency. Avoid answering one comment in a way that silently changes another part of the scheme.
Once Written Permission is issued, read its conditions as design and programme inputs. Record each condition, responsible party, evidence required, and trigger date. Approval is not the end of coordination; it establishes the planning basis that the subsequent building and fire safety submissions must respect.
4. Coordinate the BCA Building Plan submission
The BCA Building Plan submission translates the approved planning concept into a buildable and compliant set of documents. It brings architectural intent together with structural, accessibility, drainage, and other technical requirements. The submission should be developed from the approved planning information, while still allowing the technical design to be resolved properly. Consistency at this stage protects both approval progress and construction quality.
Translate the approved planning scheme into compliant building plans
Begin by carrying the approved use, footprint, levels, envelope, and access arrangements into the building plan set. Any difference between the planning scheme and the technical drawings should be identified, assessed, and addressed through the proper channel. A small dimensional change can have wider implications when it affects floor area, escape, structure, or services.
The architectural set should include enough information for the authority to understand the completed building. Plans, sections, elevations, schedules, and details should use matching references and dimensions. Do not allow a later drafting update to alter the approved planning basis without review.
Check structural, accessibility, drainage, and technical requirements
Technical checking should be systematic rather than limited to a final drawing review. Confirm that structural assumptions match the architectural arrangement, accessible routes are continuous, drainage provisions are coordinated, and plant or service spaces are adequate. Existing-building projects may require additional investigation where the available records are incomplete.
The review should also consider interfaces that are easy to miss: thresholds, ramps, risers, penetrations, roof drainage, refuse arrangements, and maintenance access. These details can influence multiple drawings, so they should be tracked as coordinated decisions instead of isolated mark-ups.
Align architectural drawings with engineering calculations and specifications
Calculations and specifications must describe the same building shown in the drawings. Check model or calculation inputs against dimensions, materials, loads, openings, and proposed systems. Where a calculation relies on an assumption, that assumption should be visible to the relevant consultant and reflected consistently in the documents.
Stellar Structures provides engineering, architectural, and interior design solutions as part of a one-stop service. For a project using that integrated arrangement, the practical benefit is a single coordinated review across those disciplines; the statutory QP and individual consultant responsibilities still need to be clearly defined.
Track BCA submissions, amendments, and approval conditions
Maintain a submission log showing the filing date, reference number, drawing revision, responding party, comments, and status of each condition. When an amendment is proposed, compare it with both the approved planning scheme and the fire safety design. The log should make it possible to identify which drawings changed and why.
At approval, transfer every condition into the construction compliance register. Conditions that appear administrative may still require certificates, inspections, updated details, or evidence at completion. Treating them as live tasks keeps the project from reaching handover with an incomplete approval record.
5. Integrate SCDF fire safety requirements
Fire safety should be developed alongside the building plan rather than appended after the layout is fixed. Escape, compartmentation, fire protection systems, and fire engine access can affect the plan, section, structure, façade, and services. Early coordination gives the team more ways to resolve issues without compromising the approved planning intent. It also gives the owner a clearer view of the systems and records needed for completion.
Establish the fire safety strategy before detailed plan submission
Set out the basic fire safety strategy before finalising detailed layouts. Confirm the intended use and occupancy assumptions, travel paths, exits, compartmentation approach, fire-rated construction, alarm and protection systems, and emergency access requirements. The design team should state its assumptions clearly and test them against the proposed building arrangement.
The strategy must be carried into drawings, calculations, specifications, and construction details. If one document changes, the related fire safety information should be reviewed at the same time. This prevents a compliant-looking plan from being undermined by an inconsistent detail elsewhere.
Coordinate escape routes, compartmentation, fire protection, and access
Fire safety coordination is an exercise in interfaces. Exit widths and travel distances must work with room layouts; fire-rated walls and doors must align with structure and services; protected shafts must remain usable; and access provisions must work with the site arrangement. The review should cover both new work and the conditions of any retained building.
Walk through the plan as an occupant and as an emergency responder. Check where people move, where smoke could spread, how doors operate, and whether equipment and access zones remain available. Record any deviation from the agreed strategy before it becomes embedded in construction information.
Prepare fire safety drawings, calculations, and supporting documents
The fire safety package should be complete, legible, and coordinated with the architectural and engineering submissions. Include the drawings, calculations, specifications, system information, and supporting documents required for the relevant review. Use consistent room names, levels, occupancy assumptions, and reference numbers throughout.
A document checklist is helpful, but it should be paired with a technical review. The QP and fire safety consultant should confirm that the evidence supports the actual design rather than describing an earlier version. This is where disciplined revision control becomes a safety measure, not merely an administrative preference.
Resolve SCDF comments without creating conflicts with URA or BCA approvals
SCDF comments should be assessed for their effect on planning and building-control documents before revisions are issued. A change to an exit, fire-rated wall, access route, or plant room may alter area calculations, elevations, structure, or services. The response should therefore identify related drawings and obtain the necessary consultant reviews.
Keep the explanation factual and traceable. Where a requested change cannot be made without affecting an approval condition, the QP should determine the appropriate consultation or amendment route. Resolving one comment by creating a new inconsistency only transfers the delay to another agency or to construction.
6. Manage submission sequencing and cross-agency coordination
The order of submissions should follow the project’s dependencies, not a generic template. Some work can proceed in parallel, while other work should wait for a planning decision or a confirmed technical assumption. The project team should make that distinction deliberately and revisit it when the scheme changes. A shared information baseline is essential throughout.
Decide which approvals can proceed in parallel
Parallel work can shorten the programme when the underlying assumptions are stable. For example, technical coordination may progress while a planning submission is under review, provided that the team marks the work as subject to the planning outcome and does not treat it as final. The QP should define the limits of parallel development and the points that require a confirmed approval.
A simple dependency review should ask what decision each submission relies on and what would need to change if that decision differs. This keeps programme optimism from becoming rework. It also helps the owner understand which early activities are low-risk preparation and which represent a commitment.
Maintain consistent project data across all authority submissions
Use one controlled set of core project information: site identifiers, use, floor areas, levels, dimensions, occupancy assumptions, consultant names, and drawing references. Each submission can have its own forms and technical focus, but its basic facts should not drift. Consistency is a control measure, not just a presentation preference.
The following comparison can help the team assign its checks before each filing:
| Information area | URA Written Permission | BCA Building Plan | SCDF fire safety |
|---|---|---|---|
| Proposed use | Planning use and development basis | Use reflected in building plans | Occupancy and fire safety assumptions |
| Site and access | Context, access, and planning controls | Site and building technical coordination | Emergency access and fire engine provisions |
| Drawings | Planning drawings and supporting plans | Architectural and engineering plans | Fire safety plans and system information |
| Conditions | Written Permission conditions | Building Plan approval conditions | Fire safety comments and conditions |
After each submission, update the shared register rather than maintaining separate informal notes. The table is a coordination prompt; it does not replace the detailed requirements or the QP’s review of the actual application.
Control drawing revisions, document versions, and approval references
Every issued document should carry a revision, date, status, and clear relationship to the submission or approval it supports. Superseded drawings should be removed from active circulation, while an archive preserves the record of what was filed and approved. This is particularly important when consultants work on overlapping packages.
Before issuing a revision, compare it against the last authority-approved version and list the affected documents. A short change note can explain whether the revision is administrative, corrective, or a material design change. That distinction helps the QP decide whether further authority action is needed.
Escalate design conflicts and material changes through the right channels
Not every conflict needs escalation to an authority, but every material change needs professional review. First identify the affected approval, technical discipline, and construction activity. Then ask the QP to determine whether the matter can be resolved within the approved scope or requires a formal amendment, consultation, or resubmission.
Owners should avoid instructing contractors to proceed on the basis of an email that has not been incorporated into the controlled documents. A prompt decision is useful only when it is recorded, reviewed, and communicated to everyone relying on it.
7. Move from approvals to construction completion and FSC
Approval documents become valuable during construction only when they are translated into controlled information and checked on site. The final stage connects approved design, actual installation, inspections, testing, and handover records. Fire safety completion is part of that chain, not a separate administrative exercise. The project team should plan the evidence requirements before works are substantially complete.
Convert approved plans into controlled construction documents
Issue construction documents from the approved baseline and identify any approved conditions that affect the contractor’s work. Drawings, specifications, schedules, and details should be coordinated before they are released. If shop drawings or substitutions change the design intent, route them through the agreed review process.
Stellar Structures’ stated one-stop service spans design, regulatory submissions, and approvals. Where the same firm is engaged across relevant design disciplines, the owner can use a coordinated document review process from approval into construction, while retaining the required statutory sign-offs and site responsibilities.
Manage changes, inspections, and compliance records during construction
Construction teams should maintain records of inspections, tests, product information, approved substitutions, site instructions, and outstanding defects. The record should show what was installed and how it was verified. Photographs and commissioning documents can be useful supporting evidence when they are dated, identifiable, and connected to the relevant system or location.
Changes should be reviewed before installation wherever possible. A late alteration to a door, wall, ceiling, service route, or fire protection system can affect several approval documents. Early review gives the team a chance to resolve the issue properly rather than reconstructing compliance at handover.
Prepare the SCDF Fire Safety Certificate submission and supporting evidence
The Fire Safety Certificate process requires the completed works and fire safety provisions to be demonstrated through the relevant application and supporting evidence. Confirm the applicable submission route, required certificates, inspection results, test records, as-built information, and professional declarations with the QP and fire safety team. The evidence should describe the building as constructed, not merely as designed.
Begin assembling the package before the final weeks of the project. Missing test reports or unresolved installation details can delay completion even when the drawings were approved earlier. A live closeout schedule gives contractors and consultants time to obtain corrections and complete outstanding checks.
Confirm final clearances, outstanding conditions, and handover documentation
Before handover, reconcile the approval register against the completed work. Confirm that URA, BCA, and SCDF conditions have been addressed, that required inspections and tests are recorded, and that as-built drawings match the installed systems. Any unresolved item should have an owner, action, and agreed route to closure.
The final handover set may include approvals, certificates, warranties, operation and maintenance information, inspection records, approved amendments, and current drawings. Keeping this information orderly supports the owner, facilities team, MCST, contractor, and future consultants long after the submission process is over.
Conclusion
A clear approval roadmap connects professional responsibility, verified site information, coordinated design, authority submissions, construction records, and final fire safety certification. When the team treats each approval as part of one controlled process, it can respond to comments with fewer contradictions and carry conditions through to handover with greater confidence.
Frequently Asked Questions
What is a Qualified Person (Architect/PE)?
A Qualified Person is the appointed registered Architect or Professional Engineer responsible for the relevant statutory submission and professional coordination required for the project.
When should the Qualified Person be appointed?
The QP should be appointed at the early planning or feasibility stage so the approval route, responsibilities, and design constraints can be assessed before detailed work begins.
What does URA Written Permission address?
URA Written Permission generally concerns planning matters such as proposed use, development parameters, building form, site context, and access arrangements.
What is covered by a BCA Building Plan submission?
A BCA Building Plan submission addresses the building design and relevant technical compliance, including coordinated architectural, structural, accessibility, drainage, and related information.
Why should fire safety be coordinated early?
Fire safety provisions can affect layouts, exits, compartmentation, structure, services, and access. Early coordination reduces the risk that a later fire safety change will conflict with planning or building approvals.
Can URA, BCA, and SCDF submissions proceed in parallel?
Some preparation and technical work may proceed in parallel when its assumptions are stable, but the QP should identify dependencies and confirm which decisions must be settled first.
What documents are needed before Fire Safety Certificate completion?
The required evidence depends on the project, but may include approved and as-built drawings, inspection and test records, certificates, commissioning information, declarations, and closeout documentation for outstanding conditions.