Use this guide to reason through architectural practice scenarios: identify responsibilities, check governing documents, calculate implications and explain a defensible decision. Each concept combines a practical foundation, a resolved example and a specific mistake to avoid.
Architectural Practice and Professional Conduct
1. Competence and appropriate specialist input
Assess competence against the actual task, including its complexity, consequences and required expertise. A familiar building type can contain unfamiliar technical systems. Define which work the architectural team can undertake and which requires specialist advice, while retaining coordination and review responsibilities within the agreed appointment.
Worked example: A practice experienced in offices accepts a laboratory project. It engages laboratory planning expertise before fixing layouts because ordinary office experience does not resolve containment and equipment requirements.
Mistake to avoid: Assuming experience with a building's general category establishes competence in every specialist system.
Context reference: Home | Board of Architects
2. Conflicts of interest
A conflict arises when another interest could influence professional judgment. Identify financial, personal and competing appointment interests early. Disclosure alone does not resolve every conflict: assess whether consent, separation of responsibilities or declining the affected task can preserve independent judgment under applicable professional requirements.
Worked example: An architect evaluating suppliers owns shares in one bidder. The interest is disclosed, and evaluation responsibility is reassigned through the client's agreed process.
Mistake to avoid: Treating a declared interest as automatically acceptable without addressing its effect on decisions.
Context reference: Home | Board of Architects
3. Turning a client brief into measurable requirements
A useful brief separates objectives, constraints and acceptance criteria. Translate broad preferences into requirements that can be evaluated, while recording unresolved assumptions. Budget, programme, functional needs and operational priorities may conflict; identifying those conflicts allows the client to make informed choices before design progresses.
Worked example: A client requests a flexible meeting suite. The brief defines three room configurations, their intended capacities and the required changeover time, making alternative layouts comparable.
Mistake to avoid: Treating an attractive concept image as proof that functional requirements have been agreed.
Context reference: Home | Board of Architects
4. Defining the professional appointment
An appointment should make services, deliverables, responsibilities, exclusions and decision authority understandable. Distinguish producing information from reviewing another party's work and from administering a contract. Clarify dependencies, such as client information or consultant inputs, because they affect what can be delivered and when.
Worked example: The appointment includes tender drawings but excludes furniture procurement. When furniture selection is requested, the architect agrees an additional service before committing staff time.
Mistake to avoid: Assuming every task connected with the project is included in the original architectural fee.
Context reference: Home | Board of Architects
5. Reasonable care and performance promises
Distinguish an obligation to exercise professional care from a promise that a particular outcome will occur. They involve different commitments and risks. Before accepting performance wording, identify who controls the outcome, what evidence can verify it and whether the appointment and insurance accommodate the commitment.
Worked example: A client asks the architect to guarantee final energy bills. The architect proposes defined design analysis and verification services because bills also depend on occupancy and operation.
Mistake to avoid: Promising an outcome controlled partly by others without examining the contractual consequences.
Context reference: Home | Board of Architects
6. Confidentiality and controlled information sharing
Project information should reach people who need it for an authorized purpose. Separate public material from confidential commercial, personal or security information. Check permission, recipients and disclosure obligations before sharing; confidentiality may require controlled disclosure rather than either unrestricted circulation or absolute secrecy.
Worked example: A consultant needs site dimensions but not the client's financing terms. The architect sends the relevant survey extract through the agreed project channel.
Mistake to avoid: Forwarding an entire correspondence chain when only one attachment is needed.
Context reference: Home | Board of Architects
7. Design authorship and permitted use
Distinguish authorship, ownership and permission to use design material. Paying for services or possessing a drawing does not, by itself, explain all permitted uses. Check appointment terms and applicable law before reusing drawings, modifying another author's work or publishing project images.
Worked example: A client wants to reuse a completed design on another site. The architect checks the agreed licence and assesses site-specific redesign instead of treating the original drawings as transferable instructions.
Mistake to avoid: Assuming access to a drawing permits unrestricted reuse, alteration or publication.
Context reference: Home | Board of Architects
8. Decision records and professional communication
A useful decision record identifies the issue, alternatives, decision maker, instruction and resulting actions. Distinguish a discussion from an authorized decision. Record qualifications and unresolved items accurately so later readers can understand what was agreed without reconstructing conversations from fragmented messages.
Worked example: Meeting minutes record that the client approved the smaller lobby, subject to an accessibility review. The design team completes that review before treating the layout as settled.
Mistake to avoid: Recording a conditional preference as an unconditional instruction.
Context reference: Home | Board of Architects
9. Delegation, supervision and checking
Delegation assigns work; it does not automatically establish that the output is suitable for issue. Match supervision to task complexity and staff experience. Identify who prepares, checks and authorizes information, and give reviewers the brief, interfaces and assumptions needed to perform a meaningful check.
Worked example: A junior prepares door schedules. A reviewer checks them against room requirements, consultant information and the current plans before the authorized issue.
Mistake to avoid: Using a senior person's signature as a substitute for an actual review.
Context reference: Home | Board of Architects
10. Professional indemnity and contractual exposure
Professional indemnity insurance has defined scope, limits, exclusions and notification conditions. Compare proposed services and contractual commitments with the actual policy rather than assuming all professional work is covered. Insurance informs risk management but does not establish competence or remove the need for careful performance.
Worked example: A proposed appointment includes responsibility for a specialist service. The practice checks that service and its contractual wording with its insurance adviser before acceptance.
Mistake to avoid: Assuming a policy's headline limit confirms coverage for every appointment obligation.
Context reference: Home | Board of Architects
Building Control and Regulatory Framework
11. Applicable requirements and document authority
Separate legislation, regulatory requirements, referenced standards, guidance and contractual specifications. Their authority and applicability differ. Establish the current requirements for the project and determine which documents are incorporated or applicable; a familiar technical recommendation should not be presented as a mandatory Singapore requirement without verification.
Worked example: A specification cites an older standard while current project guidance references a newer one. The team verifies applicability and resolves the discrepancy before issuing the specification.
Mistake to avoid: Treating every published guideline as law or assuming the newest document automatically governs.
Context reference: Home | Board of Architects
12. Planning acceptability and technical compliance
Planning considerations address matters such as land use and development form, while technical building requirements address matters such as safety, accessibility and performance. These are distinct review questions. Establish the actual Singapore approval pathways and their dependencies rather than treating a favourable decision in one process as sufficient for every other process.
Worked example: A proposed extension fits the intended development form, but its escape arrangement remains unresolved. The team addresses both issues before describing the proposal as ready.
Mistake to avoid: Assuming planning acceptability proves that the building's technical design is compliant.
Context reference: Home | Board of Architects
13. Submission responsibilities and coordination
Identify each required submission, its responsible professional and the information it depends on. Responsibility should follow applicable requirements and appointments, not convenience. Coordinated information matters because one discipline's changes can invalidate assumptions in another discipline's submission; current Singapore submission roles must be checked in official guidance.
Worked example: A plant-room relocation changes structural loading and service routes. The architect coordinates the affected specialists before revised submission documents are finalized.
Mistake to avoid: Assigning submission responsibility merely to whoever can produce the drawings fastest.
Context reference: Home | Board of Architects
14. Using a compliance matrix
A compliance matrix connects a requirement with its applicability, design response, evidence, responsible person and status. It exposes missing information and unresolved interpretations. It should track evidence rather than merely collect ticks, and must be updated when the design, use or governing requirements change.
Worked example: An accessibility entry links the route requirement to a marked plan and a pending door review. The item remains open until both pieces of evidence are checked.
Mistake to avoid: Marking compliance complete because a requirement appears somewhere in a drawing note.
Context reference: Home | Board of Architects
15. Occupancy assumptions and design consequences
Intended use and occupancy assumptions influence design checks, including circulation and evacuation. Identify which occupancy method the applicable framework requires before calculating. A change in use or layout can alter the relevant assumptions even when floor area remains unchanged; verify the resulting requirements rather than retaining earlier conclusions.
Worked example: A room changes from storage to an event space. The team reassesses occupancy and associated provisions because the earlier storage assumptions no longer describe its use.
Mistake to avoid: Using a convenient occupancy estimate without checking its basis or applicability.
Context reference: Home | Board of Architects
16. Continuity of escape arrangements
Assess an escape arrangement as a continuous system from occupied areas to the required destination. A satisfactory individual door or corridor does not establish that the whole route works. Examine connected spaces, changes in level, obstructions and interfaces against applicable requirements, using verified criteria rather than remembered dimensions.
Worked example: A plan shows a clear corridor, but its discharge passes through a proposed locked service room. The route remains unresolved despite the corridor's apparent adequacy.
Mistake to avoid: Checking isolated route segments while overlooking a blocked or unsuitable connection.
Context reference: Home | Board of Architects
17. Accessibility as a connected journey
Accessibility depends on connected movement and usable facilities, not the presence of one feature. Review arrival, entrance, circulation, changes in level and intended destinations together. Dimensions and provisions must follow current applicable requirements; the foundational question is whether a person can complete the intended journey.
Worked example: An entrance is accessible, but the only meeting room lies beyond an unresolved level change. The team revises the route rather than declaring the building accessible from its entrance alone.
Mistake to avoid: Treating an accessible entrance as proof that all intended facilities are accessible.
Context reference: Home | Board of Architects
18. Design changes and approval implications
A design change can affect regulatory assumptions as well as construction information. Before implementation, identify affected approvals, supporting calculations and discipline interfaces. Determine through current procedures whether further review or submission is needed, and distinguish internal design acceptance from any required external authorization.
Worked example: Replacing a stair arrangement changes circulation and structural coordination. The team checks approval implications and updates the affected documents before releasing the change for construction.
Mistake to avoid: Assuming a change is minor because its drawing revision occupies little space.
Context reference: Home | Board of Architects
19. Inspection evidence and hidden work
Inspection provides evidence about conditions observed at a particular time; it does not automatically prove every concealed or unobserved element. Plan review points around work that will become inaccessible, with responsibilities determined by appointments and applicable requirements. Record observations, limitations and unresolved issues accurately.
Worked example: A ceiling inspection occurs after services are enclosed. The record identifies inaccessible areas and requests appropriate supporting evidence instead of asserting that all concealed work was inspected.
Mistake to avoid: Reporting comprehensive verification when the inspection covered only visible samples.
Context reference: Home | Board of Architects
20. Contract completion and permission to occupy
Contractual completion decisions and regulatory permission to use a building answer different questions. Their evidence, decision makers and consequences may differ. Check the contract and current Singapore requirements separately, and coordinate outstanding conditions so that a project milestone is not mistaken for permission to occupy.
Worked example: The team considers a contractual completion milestone, but required occupation documentation remains outstanding. The client is told that the two statuses must be resolved separately.
Mistake to avoid: Treating a contract administrator's completion decision as sufficient regulatory permission to occupy.
Context reference: Home | Board of Architects
Contract Administration and Management
21. Contract documents and order of precedence
Read the executed contract to establish which documents form the agreement and how inconsistencies are resolved. Drawings, specifications, schedules and amendments may conflict. An order of precedence helps interpretation where provided, but does not remove the need to identify discrepancies and obtain a properly authorized resolution.
Worked example: A drawing specifies one finish and a schedule another. The administrator checks the contractual precedence provision and documents the resolution before procurement proceeds.
Mistake to avoid: Assuming specifications always override drawings regardless of the actual contract.
Context reference: Home | Board of Architects
22. Roles, authority and contractual decisions
Different project participants may advise, instruct, assess or approve, with authority defined by the contract and appointments. Map those powers before acting. The client's commercial preference does not itself establish the contractual basis for an administrator's assessment, and an architect's title does not establish unlimited authority.
Worked example: A client asks that payment be reduced for an unrelated grievance. The administrator assesses the application using the contract's payment provisions and relevant evidence.
Mistake to avoid: Confusing the client's wishes with the administrator's contractual decision criteria.
Context reference: Home | Board of Architects
23. Valid instructions and informal requests
Check who may issue instructions, the required form and any confirmation procedure. A conversation, marked-up sketch or email can have different contractual significance depending on the agreement. Record what was requested and obtain the required authorized instruction before treating an informal request as a change to the works.
Worked example: During a visit, a stakeholder requests another partition. The architect records the request and routes it through the contract's instruction process rather than approving immediate installation.
Mistake to avoid: Assuming any project participant's request is a valid contractual instruction.
Context reference: Home | Board of Architects
24. Identifying a variation
Compare the proposed change with the agreed contractual scope before describing it as a variation. A changed requirement, correction of defective work and clarification of an existing obligation are different situations. Check the contract's definition, instruction process and records to establish the appropriate treatment.
Worked example: The client requests a higher-grade floor finish than the contracted product. The administrator identifies the scope change and follows the contract's variation procedure.
Mistake to avoid: Calling every additional task a variation without checking what the contractor already owed.
Context reference: Home | Board of Architects
25. Valuing changed work
Variation valuation follows the contract's agreed methods, which may use existing rates, adjusted rates or another basis. Check quantities, applicability and assumptions before calculating. An existing rate is useful only when its scope and conditions suit the changed work; arithmetic cannot resolve an inappropriate valuation basis.
Worked example: An applicable agreed rate is SGD 80 per square metre. Adding 12 square metres gives SGD 960 before any separately applicable contractual adjustments.
Mistake to avoid: Applying a familiar rate to materially different work without examining its suitability.
Context reference: Home | Board of Architects
26. Payment assessment and cumulative amounts
Distinguish the cumulative value assessed from the amount due for the current period. Check previous amounts, contractual deductions and supporting evidence using the payment mechanism actually agreed. An application is a request for payment, not proof that every claimed item has been earned.
Worked example: Assessed cumulative value is SGD 240,000 and previous certified value is SGD 180,000. The period difference is SGD 60,000 before applicable deductions.
Mistake to avoid: Treating the cumulative assessed total as the amount payable again this period.
Context reference: Home | Board of Architects
27. Critical path and delay effects
A delayed activity affects completion only through its relationship with the programme, available float and other events. Examine the relevant sequence and contemporaneous records rather than adding all delay durations. Programme impact is a factual analysis; contractual entitlement requires a separate examination of the agreement.
Worked example: A delivery slips four days on an activity with six days of available float. With no other effects, the slip consumes four days of float without moving completion.
Mistake to avoid: Assuming every late activity extends the project's completion date by the same duration.
Context reference: Home | Board of Architects
28. Time claims, notices and evidence
Separate the occurrence of an event, its effect on completion and the contractual basis for a time adjustment. Check notice requirements, relevant causes and supporting records in the actual agreement. A time adjustment does not automatically establish an entitlement to additional money; the two assessments may require different provisions.
Worked example: Late information delays a critical activity. The administrator examines notices, information-release records and programme effects before deciding the time claim under the contract.
Mistake to avoid: Granting time or money solely because an event appears on a list of project problems.
Context reference: Home | Board of Architects
29. Defects, damage and maintenance
A defect concerns failure to meet the applicable contractual requirement; damage and maintenance issues can have different causes and responsibilities. Compare the observed condition with specifications, records and use history. Describe evidence before attributing responsibility, and follow the contract's processes for investigation and correction.
Worked example: A damaged door is reported after equipment relocation. The team checks installation records and the incident history before deciding whether it reflects defective work or later damage.
Mistake to avoid: Assigning every post-completion fault to the contractor without investigating cause and obligation.
Context reference: Home | Board of Architects
30. Dispute definition and escalation
Define the disputed issue, relevant facts, contractual provisions and requested outcome before escalating. Separate agreed facts from contested interpretations. Follow the agreement's dispute process and seek appropriate legal advice where needed; informal negotiations should be recorded clearly without inventing procedural deadlines or powers.
Worked example: The parties agree the extra quantity but disagree about the applicable rate. The administrator isolates the rate issue and assembles the tender and instruction records.
Mistake to avoid: Escalating a broad accusation when the actual disagreement is a specific valuation question.
Context reference: Home | Board of Architects
Project Procurement and Tendering
31. Procurement routes and design responsibility
A procurement route organizes who develops design, who constructs and how appointments connect. In a conventional separate design-and-construction arrangement, those contracts are separate; design-and-build commonly places design and construction within one contractor's scope. Actual responsibility, retained client design and interfaces depend on the executed documents.
Worked example: A client chooses design-and-build but retains an initial concept. The team defines which concept requirements are fixed and which design development the contractor must undertake.
Mistake to avoid: Assuming a procurement route's name fully describes every participant's design responsibility.
Context reference: Home | Board of Architects
32. Allocating risk to the party able to manage it
Risk allocation affects price, behaviour and project resilience. Examine who can investigate, control or mitigate each risk and whether the proposed allocation is understandable. Transferring a risk contractually does not make it disappear; bidders may price uncertainty, qualify their offers or fail to manage an unrealistic allocation.
Worked example: Ground conditions remain uncertain. The client considers investigation and a clearly defined contractual treatment instead of expecting an unexplained fixed price to eliminate uncertainty.
Mistake to avoid: Equating maximum risk transfer with minimum total project cost.
Context reference: Home | Board of Architects
33. Prequalification and relevant capability
Prequalification asks whether a bidder has relevant capacity and capability before detailed price comparison. Assess experience, resources, proposed personnel and evidence appropriate to the project. A large turnover or impressive portfolio can be useful information, but neither alone establishes that the proposed team can deliver this particular work.
Worked example: A complex refurbishment requires work around occupied areas. A bidder's relevant occupied-building experience is examined rather than relying only on its new-build portfolio.
Mistake to avoid: Treating company size as a substitute for evidence of project-specific capability.
Context reference: Home | Board of Architects
34. Consistent tender information
Comparable tenders require a consistent information baseline. Control the issue of documents, clarifications and amendments so bidders understand the same scope and assumptions. Follow the applicable procurement rules and confidentiality arrangements; inconsistent information can distort price comparisons and create later disagreement about what was offered.
Worked example: A clarification changes the specified glazing. The tender manager issues a controlled addendum to all participating bidders through the agreed process.
Mistake to avoid: Giving a material scope clarification privately to only the bidder who asked.
Context reference: Home | Board of Architects
35. Bills of quantities and pricing discrepancies
Quantities, rates and totals should reconcile, but discrepancy treatment depends on the tender rules and contract. Identify arithmetic errors separately from scope omissions and qualification issues. Do not silently change a bidder's offer or assume a universal correction method; use the stated clarification and evaluation process.
Worked example: A line shows 25 units at SGD 120 but totals SGD 2,500. The arithmetic product is SGD 3,000, and the discrepancy is addressed under the tender procedure.
Mistake to avoid: Correcting a tender total without checking which figure the procurement rules treat as governing.
Context reference: Home | Board of Architects
36. Clarifications, addenda and document control
A clarification explains information; an addendum changes or supplements the tender baseline. Their effects can overlap, so classify the content rather than relying on its title. Track affected documents, issue dates and acknowledgements, and allow the procurement process to address material changes before bids are finalized.
Worked example: An answer introduces a new acoustic requirement. It is incorporated into a formal tender amendment because bidders must price additional scope.
Mistake to avoid: Hiding a material scope change inside an informal question-and-answer response.
Context reference: Home | Board of Architects
37. Tender evaluation on a comparable basis
Evaluate offers against the stated criteria and a common scope. Compare price with quality, programme, capability and relevant risks where the procurement method allows. Separate the tendered price from evaluation adjustments, and document assumptions so the recommendation can be understood and checked.
Worked example: Bid A is SGD 1.80 million but omits SGD 0.15 million of required work. Its adjusted comparison is SGD 1.95 million, above a complete SGD 1.90 million bid.
Mistake to avoid: Selecting the lowest headline figure before checking exclusions and scope completeness.
Context reference: Home | Board of Architects
38. Qualifications and alternative proposals
A qualification changes the basis on which a bidder offers to perform; an alternative proposes a different solution. Identify their technical, commercial and contractual effects. Compare alternatives against stated requirements and resolve qualifications through the permitted process rather than treating every bid as fully compliant.
Worked example: A bidder offers a shorter programme only if the client supplies equipment earlier. The evaluation records that dependency instead of comparing the completion date in isolation.
Mistake to avoid: Accepting an attractive programme while ignoring the conditions that make it achievable.
Context reference: Home | Board of Architects
39. Award readiness and resolved terms
Before recommending award, confirm that the preferred offer and intended contract describe the same scope, price basis, programme and responsibilities. Record resolved clarifications and identify outstanding conditions. A recommendation should distinguish confirmed commitments from assumptions that still require agreement.
Worked example: The preferred bidder's exclusions are resolved, but its proposed specialist remains unconfirmed. The recommendation identifies that outstanding condition rather than presenting the package as fully settled.
Mistake to avoid: Assuming tender discussions automatically become binding contract terms without appropriate incorporation.
Context reference: Home | Board of Architects
40. Procurement lead times and release dates
Work backward from the required installation date through manufacturing, delivery, approvals and design release. Procurement planning exposes decisions that must occur before site activity begins. Treat lead times as project-specific information to verify, and account for dependencies rather than using a supplier's production duration as the entire procurement period.
Worked example: Installation is needed in week 20. Production and delivery take eight weeks, and review takes two; information must be ready by week 10.
Mistake to avoid: Starting procurement only eight weeks before installation while forgetting the preceding review period.
Context reference: Home | Board of Architects
Professional Fees and Financial Management
41. Fee basis and service assumptions
A fee can be agreed using a lump sum, time charges, a percentage basis or a combination. Each method needs clear scope and assumptions. Examine what determines payment, which expenses are included and how changes are handled; no general fee method establishes a mandatory Singapore rate.
Worked example: A lump-sum proposal assumes two design options and one tender exercise. Those assumptions are written into the offer so later additional work can be assessed.
Mistake to avoid: Comparing fee totals without comparing the services and assumptions they cover.
Context reference: Home | Board of Architects
42. Additional services and fee changes
A changed project does not automatically establish a fee adjustment. Compare the requested work with the appointment, identify additional effort and follow the agreed change mechanism. Record scope, resources and fee agreement clearly so professional service changes do not become invisible increases in workload.
Worked example: A client requests an additional design option. At 18 agreed chargeable hours and SGD 150 per hour, the proposed additional fee is SGD 2,700.
Mistake to avoid: Doing substantial extra work before clarifying whether and how it will be paid.
Context reference: Home | Board of Architects
43. Cash flow and working capital
Cash flow tracks when money enters and leaves the practice. A profitable appointment can still create a cash shortage if receipts arrive after wages and other expenses. Forecast payment timing as well as totals, distinguish expected receipts from confirmed cash and update the forecast when collection dates move.
Worked example: Opening cash is SGD 40,000, expected receipts are SGD 20,000 and monthly outgoings are SGD 50,000. Closing cash is forecast at SGD 10,000.
Mistake to avoid: Assuming an invoiced fee is already available to pay current expenses.
Context reference: Home | Board of Architects
44. Profit and cash are different measures
Profit compares recognized income with associated expenses; cash measures receipts and payments. Their timing can differ because of invoicing, collection and outstanding obligations. Assessing practice health requires both views, using the appropriate accounting treatment rather than interpreting the bank balance as profit.
Worked example: A simplified period records SGD 100,000 revenue and SGD 80,000 expenses, giving SGD 20,000 profit. If only SGD 60,000 has been collected, cash tells a different story.
Mistake to avoid: Calling every increase in the bank balance profit without examining its source.
Context reference: Home | Board of Architects
45. Staff cost and billable capacity
A staff member's project cost extends beyond basic salary, and available working time is not all billable. Estimate employment costs, overhead allocation and realistic billable capacity when planning fees. Use actual practice data where available; no universal utilization percentage determines whether an architectural practice is viable.
Worked example: Annual allocated cost is SGD 90,000 and forecast billable time is 1,200 hours. The cost per billable hour is SGD 75 before profit allowance.
Mistake to avoid: Dividing salary by all calendar working hours and treating the result as a sustainable charge rate.
Context reference: Home | Board of Architects
46. Break-even contribution
Contribution is revenue less variable costs; it helps cover fixed costs before producing profit. Under a simplified model, break-even revenue equals fixed costs divided by the contribution margin ratio. State the cost classifications and assumptions because staffing and overhead behaviour may change as workload changes.
Worked example: Monthly fixed costs are SGD 30,000 and the contribution margin ratio is 60%. Break-even revenue is SGD 30,000 divided by 0.60, or SGD 50,000.
Mistake to avoid: Dividing fixed costs by the profit margin instead of the contribution margin.
Context reference: Home | Board of Architects
47. Contingency and defined allowances
A contingency provides for uncertainty within the stated budget basis; an allowance identifies money for a particular item whose detail may remain unresolved. Keep them distinguishable so uncertainty is visible. Neither label removes the need to define scope, ownership and the process for approving expenditure.
Worked example: A budget includes SGD 25,000 for an unresolved equipment package and SGD 15,000 for identified project uncertainty. The two sums are tracked separately.
Mistake to avoid: Using contingency to conceal an omitted known requirement or counting the same risk twice.
Context reference: Home | Board of Architects
48. Life-cycle cost and present value
Life-cycle comparisons include relevant initial, operating, maintenance and replacement costs over a stated period. Discount future costs when comparing them in present-value terms. State assumptions about timing, discount rate and performance; a lower purchase price alone does not establish the lower overall cost.
Worked example: Using an assumed 5% annual discount rate, a SGD 10,000 cost due in two years has present value SGD 10,000 divided by 1.05 squared, approximately SGD 9,070.
Mistake to avoid: Comparing an undiscounted future cost directly with today's expenditure while claiming a present-value comparison.
Context reference: Home | Board of Architects
49. Budget, commitments and forecast final cost
A budget is an approved financial baseline; a commitment is an amount already contracted or otherwise obligated. Forecast final cost also includes expected remaining expenditure and changes. Keep these categories separate to avoid treating unspent budget as freely available when much of it is already committed.
Worked example: Committed cost is SGD 800,000 and expected uncommitted work is SGD 150,000. Forecast final cost is SGD 950,000 against a SGD 1 million budget.
Mistake to avoid: Adding paid invoices to full commitments when those invoices are already included in the committed total.
Context reference: Home | Board of Architects
50. Receivables ageing and collection risk
Receivables ageing groups unpaid invoices by their status relative to agreed payment dates. Distinguish invoices awaiting normal payment from overdue or disputed balances. Review concentration and reasons for delay, because a large receivable from one client can create risk even when total invoiced revenue appears healthy.
Worked example: Of SGD 70,000 outstanding, SGD 50,000 from one client is past its agreed due date. The forecast is revised and the disputed items are investigated.
Mistake to avoid: Treating every outstanding invoice as equally collectible at the originally expected date.
Context reference: Home | Board of Architects
Design Management and Construction Technology
51. Design interfaces and coordination ownership
An interface occurs where one discipline's decision affects another's work. Assign responsibility for producing information, checking compatibility and resolving conflicts. Coordination requires more than overlaying drawings: intended performance, access, dimensions and assumptions must agree across the interface.
Worked example: A duct route conflicts with a structural beam. The team considers structure, services and ceiling requirements together and records the agreed coordinated solution before issue.
Mistake to avoid: Assuming each discipline's internally consistent drawings will automatically fit together.
Context reference: Home | Board of Architects
52. Design freeze and controlled change
A design freeze establishes an agreed baseline for downstream work; it does not mean changes become impossible. After that point, assess proposed changes for technical, cost, programme and approval effects. Obtain the relevant decisions and update affected information so construction does not proceed against incompatible baselines.
Worked example: After tender, the client relocates toilets. The team identifies drainage, structure, finishes and approval implications before releasing a coordinated revision.
Mistake to avoid: Updating the architectural layout while leaving dependent consultant information on the previous baseline.
Context reference: Home | Board of Architects
53. Information purpose and issue status
Information needs an identifiable purpose and permitted use, such as review, tender or construction, according to the project protocol. Status explains readiness; revision identifies a particular version. A detailed drawing is not automatically authorized for construction merely because it appears technically complete.
Worked example: A contractor receives a detailed layout marked for coordination review. The team clarifies its status and issues the authorized construction information through the agreed process.
Mistake to avoid: Using drawing detail or apparent completeness as a substitute for checking issue status.
Context reference: Home | Board of Architects
54. Revision control and superseded information
Revision control identifies what changed, when it changed and which information is current. Maintain coordinated registers and clearly manage superseded documents through the project protocol. A revision record should help recipients locate consequential changes rather than merely announce that a new file exists.
Worked example: A door width changes from 900 millimetres to 1,000 millimetres. The plan and schedule are revised together, and the previous issue is marked superseded.
Mistake to avoid: Replacing a file without identifying affected documents or informing people relying on the earlier issue.
Context reference: Home | Board of Architects
55. Buildability and construction sequence
Buildability asks whether the design can be constructed with realistic access, sequencing, tolerances and resources. Identify temporary-condition and construction-method interfaces for discussion with appropriately responsible specialists. Do not assume permanent design adequacy establishes safety during every construction stage or transfer method responsibilities informally.
Worked example: A large replacement unit fits its final room but cannot pass through the planned access route. The team coordinates delivery access and installation sequence before enclosing the space.
Mistake to avoid: Checking only the finished arrangement while overlooking how components reach their final positions.
Context reference: Home | Board of Architects
56. Moisture pathways through the building envelope
Envelope moisture performance depends on controlling entry, providing appropriate drainage and managing drying. Water can move through openings, joints and material interfaces by different mechanisms. Review the assembly as a connected system and seek suitable technical evidence rather than assuming one surface treatment resolves every pathway.
Worked example: Leak staining occurs beside a window after wind-driven rain. The investigation examines the window-wall interface and drainage continuity instead of immediately blaming the glass.
Mistake to avoid: Treating visible staining as proof of the entry point or prescribing sealant without diagnosis.
Context reference: Home | Board of Architects
57. Condensation and surface temperature
Condensation can occur when a surface temperature falls below the dew-point temperature of adjacent air. Insulation, thermal bridges, air leakage and humidity affect the risk. Distinguish condensation from rain penetration through observation and appropriate analysis; appearance alone may not establish the mechanism.
Worked example: Indoor air has a dew point of 18°C and a local surface is 16°C. Condensation is possible at that surface because it is below the dew point.
Mistake to avoid: Assuming all dampness is a rain leak or that additional insulation always resolves every moisture mechanism.
Context reference: Home | Board of Architects
58. Movement and material compatibility
Materials move differently with temperature, moisture and loading. Connections and interfaces must accommodate the relevant movement while maintaining required performance. For a simple freely expanding element, thermal length change equals expansion coefficient multiplied by original length and temperature change; actual restraint conditions require further assessment.
Worked example: A hypothetical material with coefficient 10 × 10⁻⁶ per °C spans 20 metres. A 30°C rise produces 0.006 metres, or 6 millimetres, of free expansion.
Mistake to avoid: Treating calculated free expansion as the movement of a restrained assembly without checking its behaviour.
Context reference: Home | Board of Architects
59. Tolerance accumulation at interfaces
Nominal dimensions do not guarantee fit because fabrication and installation tolerances accumulate. Compare the largest permitted component with the smallest permitted opening, considering the agreed tolerance model. Coordinate adjustment capacity and installation needs; statistical assumptions should not replace a conservative fit check without justification.
Worked example: An opening is 1,010 ±5 millimetres and a component is 1,000 ±3 millimetres. Worst-case clearance is 1,005 minus 1,003, leaving 2 millimetres.
Mistake to avoid: Using the nominal 10-millimetre clearance while ignoring the permitted dimensional variation.
Context reference: Home | Board of Architects
60. Evaluating material substitutions
Assess a proposed substitute against the required assembly performance, compatibility, durability, maintenance and supporting evidence. Similar appearance or a single matching property does not establish equivalence. Check contractual and approval implications, and obtain appropriate specialist review where performance or safety depends on the complete system.
Worked example: A cheaper cladding panel matches the colour but uses a different fixing system. The team reviews the assembly evidence and interfaces before deciding whether substitution is acceptable.
Mistake to avoid: Approving a substitute from a sample's appearance without checking the performance of the installed assembly.
Context reference: Home | Board of Architects
Sources
Examination identity verified:
All study guides