Spatial Programming
Lập chương trình không gian
Verify area, function, and zoning against the approved design brief — compare options within the model from pre-design stage.
Common tools
Revit Space, ArchiCAD Zone, model-linked area spreadsheets
Value delivered
Catches area requirement gaps early, avoiding costly late-stage redesign
Adoption in Vietnam
Rarely formally applied in Vietnam but implicitly performed during architectural design.
Level of Information Need (LOIN)
G = Geometry · A = Alphanumeric · D = Documentation (ISO 7817-1:2024 method). A blank cell means this use sets no specific requirement for that discipline/stage.
| Discipline | Concept | Schematic | Developed | Technical | As-built / Operation |
|---|---|---|---|---|---|
| Architecture | G1·A2·D0 | G2·A2·D0 | — | — | — |
| Structure | — | — | — | — | — |
| Mechanical | — | — | — | — | — |
| Electrical | — | — | — | — | — |
| Plumbing | — | — | — | — | — |
Critical stages: Concept · Schematic
Rationale: ARCH-only space/room program check. Geometry is secondary (G1 bounding rooms at ST1 → G2 schematic cells at ST2); A2 is the real driver — room areas, space standards and equipment requirements measured against the brief (per AIQS Book of Areas). No documentation linkage needed.
What it really is
Spatial Programming is the use of a BIM model to verify and confirm the area, function and zoning of each functional area against the design brief approved by the appointing party, starting at the pre-design stage — before schematic/basic design begins. Unlike an architect estimating areas on paper or by eye while sketching a floor plan, this use turns every room, lobby and corridor into a Room or Space object whose area the model calculates automatically, carrying both a target area and an actual area so the two can be compared any time the design changes. The point is not a pretty floor plan but a living reconciliation table — required versus modelled — that surfaces functional areas that are short on space, over-sized, or missing entirely while a fix is still cheap. It also lets several layout options be compared side by side inside the same model, so the option that best meets the brief is chosen before committing, rather than discovering an area shortfall once detailed design is already underway.
When to use
Worth doing from the concept and schematic design stages onward for any project with a complex brief, many functional areas, or several layout options to compare — hospitals, schools, offices, apartment buildings, hotels. Especially important once the appointing party has approved specific area targets per functional area and needs objective evidence that the design complies before appraisal submission or fundraising.
Prerequisites
- •A design brief approved in writing by the appointing party, with an area and function target table per functional area — without it there is nothing to reconcile against
- •A concept massing or preliminary architectural model built to a level that Room/Space objects can be attached to — depends directly on Design Authoring at a low LOIN
- •A unified space classification and functional-area naming system agreed among the appointing party, architect and other stakeholders
- •An agreed area-measurement convention — net clear usable area or centre-line area — shared between the design brief and how Room boundaries are set in the model
- •Someone able to configure the target-area parameter and export the comparison schedule directly from the model
Inputs
Appointing party · .xlsx / .pdf
Appointing party · project consultant · .xlsx
Architect · .rvt / IFC
BIM Coordinator · .xlsx
Appointing party · .pdf
Appointing party · architect · .pdf / .xlsx
Outputs
Required-versus-modelled area reconciliation table
.xlsx / xuất từ Revit Schedule → Appointing party
Accepted when: Every functional area is within the agreed tolerance or its variance is clearly explained
Area and function variance report
.pdf / .xlsx → Appointing party · design consultant
Accepted when: Each variance states its cause and proposed fix, not just the delta
Model with Room/Space objects matching the finalised brief
.rvt / IFC → Downstream design task team
Accepted when: Area and zoning meet the approved targets and are ready as the basis for schematic/basic design
Space-program sign-off record
.pdf → Appointing party
Accepted when: Signed off by the authorised decision-maker before the next design stage proceeds
General workflow
Prepare the design brief and area target schedule
The appointing party and the project consultant define the list of functional areas, target areas, adjacency requirements and expected occupancy for each. This target table must be approved in writing before it enters the model — otherwise later reconciliation has nothing to compare against.
Appointing party + project consultant · Design brief template (Excel) — no BIM software needed yet → Approved design brief with an area target schedule
Model Room/Space objects per functional area
The architect creates Room (architectural) or Space (MEP/energy) objects for each functional area directly on the concept massing model, naming and classifying them to match the target table. The actual area is calculated automatically from the room boundaries that were set.
Architect · Revit (Room & Area) · Forma (initial massing) → Model with Room/Space objects for each functional area
Assign the target area as a shared parameter
Add a "Target Area" shared parameter to every Room/Space and populate it from the approved target table. The parameter travels with the object inside the model permanently, instead of sitting in a separate spreadsheet that quickly goes stale.
BIM Coordinator · Revit (Shared Parameter) · Dynamo for Revit → Room/Space objects carrying both a target area and an actual area
Extract the area comparison schedule
Build a Room/Space schedule listing the target area, the modelled area and the percentage variance for each functional area, updating automatically whenever the model changes — no manual re-measurement needed.
BIM Coordinator · Revit (Schedule/Quantities) → Required-versus-modelled area reconciliation table
Reconcile and produce the variance report
Compare each functional area against the variance tolerance agreed in the BEP (for example ±5%), flag areas exceeding it and state the cause — a mismatched area-measurement rule, a mid-stream function change, or a revised requirement from the appointing party.
BIM Coordinator + design consultant · Model-linked area spreadsheet (Excel + Revit Schedule) → Area and function variance report
Present the report and decide on the option
Present the variance report to the appointing party, who decides whether to keep the targets, adjust areas, merge or split functional areas, or model an additional layout option for comparison before committing.
Appointing party + architect · Model-based walkthrough meeting — Revit or Forma to present the options → Space-program decision
Update the model and lock the space program
The architect revises the Room/Space objects per the decision, re-confirms the comparison table is within tolerance, then publishes the model with the space program locked as the basis for schematic/basic design.
Architect · Revit · Forma Data Management (publish to the CDE) → Model with the space program locked, published to the CDE
Diagram
↺ Each time the layout option changes, repeat from the Room/Space modelling step — the area comparison table is a living sheet, not a one-off snapshot
Common pitfalls
The modelled area matches the target table, but the built area falls short and must be extended or re-approved
Cause: The model measures area to the wall centre-line while the brief specifies net clear usable area — the two conventions are incompatible but nobody noticed because both are simply called "area"
Fix: Agree the area-measurement convention between the brief and how Room boundaries are set in the model from day one, and state it in the BEP
Nobody looks at the area reconciliation table, and the design drifts into the next stage while variances remain unresolved
Cause: No agreed tolerance threshold and nobody assigned to close out the decision
Fix: Set a tolerance (for example ±5%) in the BEP and require the appointing party to sign the sign-off record before the model is locked
Every time the layout option changes, the whole area table must be rebuilt by hand
Cause: The area table was built as a standalone spreadsheet, disconnected from the Room/Space objects in the model
Fix: Attach the target area as a shared parameter directly on Room/Space and export the table straight from the model instead of remeasuring by hand
In Vietnam, area verification is often done loosely or skipped because nobody is formally assigned to "spatial programming"
Cause: This use is rarely named formally in Vietnamese contracts — it is implicitly folded into the lead architect's day-to-day work without being split out as a distinct control step
Fix: Make spatial programming an explicit control gate in the BEP and coordination schedule, even without naming the use formally in the contract
Measuring effectiveness
Functional areas with |modelled area − target area| / target area within the agreed tolerance, divided by the total number of functional areas
Benchmark: no independent benchmark — set an internal target
(Total modelled area − total target area) / total target area, across all functional areas
Benchmark: no independent benchmark — set an internal target
Count the number of reconcile → report → decide cycles until the sign-off record is signed
Benchmark: no independent benchmark — set an internal target
Working days from design-brief approval to the space-program sign-off record
Benchmark: no independent benchmark — set an internal target
Legal basis
There is NO requirement specific to spatial programming in Decree 217/2026/NĐ-CP — this use applies under Art. 8 generally, with no clause naming area-and-function reconciliation on its own. Specifically: Art. 8(1)(a) mandates BIM for new-build works Grade II and above from the feasibility study or economic–technical report stage — precisely the stage at which spatial programming typically happens in practice. Art. 8(2) assigns the scope, content and information requirements to the contract, which is the basis for writing the area targets to be reconciled and the acceptable variance tolerance into the EIR/BEP. To make it binding, these must be stated explicitly in the design brief and the contract — the law does not automatically mandate area reconciliation for this individual use.
Sources
Only official sources (legislation, standards) and peer-reviewed academic work are cited. No vendor marketing figures or press sources. Reference only — does not replace legal advice.