This guide develops foundations for the SACAP Professional Practice Examination in South Africa. Begin with professional responsibilities, then connect practice management and contracts to design decisions and construction processes. Each concept includes an original worked situation and a specific error to avoid. Contract examples state their assumptions; actual decisions require the applicable appointment, building contract and regulatory requirements.
Registration and professional responsibilities
1. Registration and appointment answer different questions
Professional registration concerns a person’s recognised status within the regulatory framework. An appointment defines the services and responsibilities agreed for a particular project. Neither should be treated as a substitute for the other. Before accepting work, establish the applicable registration position, competence and written scope without assuming that an examination result alone authorises every architectural service.
Worked example: A client requests design and site administration. The practitioner checks the applicable registration requirements and records both services in the appointment before proceeding.
Mistake to avoid: Treating a signed client appointment as proof that all requested work is permitted.
2. Competence is specific to the task
Competence combines relevant knowledge, experience and the ability to recognise limits. Familiarity with one building type does not automatically establish competence for another. Divide an unfamiliar commission into tasks, identify specialist inputs and establish suitable review arrangements. A useful decision is whether a task can be performed reliably, needs supervision or should be assigned to another competent professional.
Worked example: An architect experienced in houses receives a laboratory brief and arranges specialist input for containment requirements before developing the layout.
Mistake to avoid: Assuming that general architectural experience removes the need for specialist assessment.
Context reference: SACAP
3. Conflicts require disclosure and management
A conflict arises when another interest could influence professional judgement, or reasonably appear to influence it. Identify the interest before making the affected decision. Disclosure should explain its relevance, followed by an appropriate management measure. Depending on the circumstances and applicable rules, that measure may involve independent assessment, restricted participation or declining the affected role.
Worked example: A practice director has a financial interest in a tendering supplier. The relationship is disclosed and the director leaves the supplier evaluation to an independent assessor.
Mistake to avoid: Assuming that personal confidence in being fair makes disclosure unnecessary.
Context reference: SACAP
4. Contract administration requires evidence-based judgement
An architect’s role can include advising the client and making assessments under a building contract. When exercising an assessment function, use the contract’s criteria and supporting evidence. Client preference is not itself evidence of entitlement. First identify the capacity in which the architect is acting, because advocacy, design advice and contractual assessment involve different responsibilities.
Worked example: A client wants a payment reduced because the contractor was difficult at a meeting. The assessor values the work using the agreed contractual basis.
Mistake to avoid: Using certification to reward cooperation or punish an unrelated disagreement.
Context reference: SACAP
5. Confidentiality includes controlled information sharing
Project information should reach people who need it for an authorised purpose. Confidentiality does not mean withholding information required for legitimate coordination or an applicable obligation. Establish what may be shared, with whom and through which channel. Separate public project material from personal, commercial and security-sensitive information, and seek clarification where disclosure duties or permissions are uncertain.
Worked example: A services consultant receives relevant drawings, while the client’s unrelated financing correspondence remains outside the coordination package.
Mistake to avoid: Sending an entire project folder when a limited information package would suffice.
Context reference: SACAP
6. Supervision must match the consequence of error
Delegation transfers work, but responsibility depends on the appointment and applicable professional rules. Effective supervision identifies who prepares, checks and authorises an output. More consequential or unfamiliar tasks need appropriately experienced review. Checking should occur early enough to correct errors before issue, rather than relying on a signature after decisions have already reached the project team.
Worked example: A junior team member prepares an escape-route drawing. An experienced reviewer checks the design assumptions before the drawing is issued.
Mistake to avoid: Treating an unchecked signature as evidence that meaningful supervision occurred.
7. Continuing development should address competence gaps
Continuing professional development supports competence as methods, responsibilities and knowledge change. Its practical value comes from identifying a gap, learning relevant material and applying it critically. Administrative categories and recognition requirements must be checked with SACAP’s current guidance. Attendance alone does not establish that a practitioner can safely perform an unfamiliar task without further experience or specialist assistance.
Worked example: After repeated envelope coordination problems, a practitioner studies moisture-control principles and revises the practice’s drawing review checklist.
Mistake to avoid: Equating a course attendance record with competence in every related service.
8. Public consequences belong in design decisions
Professional judgement considers how a proposal affects occupants, neighbours and other users as well as the client. Identify foreseeable consequences and bring material concerns to the appropriate decision-makers. Where a concern requires specialist assessment or regulatory confirmation, obtain that input. A client’s acceptance of inconvenience does not establish that effects on other people have been adequately addressed.
Worked example: A proposed delivery entrance conflicts with a pedestrian route. The architect records the conflict and coordinates a safer arrangement with the relevant designers.
Mistake to avoid: Assessing a design solely through the client’s immediate cost preference.
Context reference: SACAP
9. Statutory obligations and contractual promises are distinct
Regulatory obligations arise from the applicable legal framework; contractual promises arise from agreements. A project can satisfy one set of requirements while still failing another. Identify the relevant obligation before choosing a remedy or decision route. Avoid assuming that a client instruction, consultant agreement or contract clause changes a requirement imposed by an authority.
Worked example: A client approves a layout, but a required authority review remains outstanding. Client approval resolves the design preference, not the regulatory process.
Mistake to avoid: Treating agreement between project parties as a substitute for required regulatory compliance.
Context reference: SACAP
10. A useful decision record captures reasons and authority
A decision record should identify the issue, available information, decision-maker, reasons and required follow-up. This allows later readers to distinguish an authorised decision from a discussion or unresolved proposal. Record significant assumptions and qualifications contemporaneously. The value lies in reconstructing what was known and agreed, rather than merely accumulating correspondence without a clear outcome.
Worked example: Meeting minutes record that the client selected Option B, subject to cost confirmation, with the architect responsible for obtaining that confirmation.
Mistake to avoid: Recording ‘Option B discussed’ as though it proves an unconditional instruction.
Context reference: SACAP
Managing an architectural practice
11. Translate the brief into measurable requirements
A brief should distinguish objectives, constraints and acceptance criteria. Objectives describe the desired outcome; constraints limit available solutions; acceptance criteria help evaluate proposals. Resolve contradictions before detailed design develops. A clear requirement is observable and connected to the client’s use, whereas a vague adjective leaves different parties free to assume different meanings.
Worked example: Instead of ‘a flexible meeting room’, the brief requires two independently usable spaces that can combine for a larger meeting.
Mistake to avoid: Beginning detailed design while contradictory capacity and area requirements remain unresolved.
Context reference: SACAP
12. Define services through deliverables and boundaries
A service appointment should identify what will be produced, when it will be provided and which inputs are needed from others. Clarify exclusions and interfaces rather than relying on a broad phrase such as ‘full architectural services’. Deliverables describe outputs; responsibilities describe actions. Both matter because a drawing list alone does not explain coordination, review or administration obligations.
Worked example: The appointment includes tender drawings and tender queries, while specialist acoustic design is assigned to a separately appointed consultant.
Mistake to avoid: Assuming that a specialist service is included because its result appears on architectural drawings.
Context reference: SACAP
13. Service changes need an impact assessment
A change to the professional service scope can affect effort, programme, deliverables and other appointments. Compare the request with the agreed baseline before proceeding. Explain the consequences and document the appropriate agreement. A client’s design choice and a change to the architect’s services are related but distinct: some choices fit existing services, while others require additional work.
Worked example: After approving a single layout, the client requests three alternative layouts. The architect assesses the extra work and agrees the revised service scope.
Mistake to avoid: Accepting repeated additional deliverables without clarifying their effect on the appointment.
Context reference: SACAP
14. Estimate fees from explicit workload assumptions
A workload estimate links tasks, hours and assumed charge rates so that its basis can be reviewed. It is an internal planning calculation, not an official tariff. Separate included expenses, taxes and specialist services where relevant. Revisit the estimate when scope or assumptions change, because a precise calculation cannot compensate for omitted tasks.
Worked example: An illustrative estimate uses 30 hours at R650 and 12 hours at R900: R19,500 + R10,800 = R30,300 before separately identified additions.
Mistake to avoid: Presenting the calculated total without stating the scope and rate assumptions.
Context reference: SACAP
15. Profit and cash flow measure different things
Profit compares recognised income and expenses; cash flow compares money received and paid. A practice can report a surplus while lacking cash to meet immediate commitments. Track expected receipt dates alongside expenditure dates. For a simplified exercise, state whether figures exclude tax, opening balances and financing so that the conclusion follows from the information given.
Worked example: Recognised income is R100,000 and expenses are R85,000, giving R15,000 profit. Receipts of R70,000 against R85,000 paid produce a R15,000 cash outflow.
Mistake to avoid: Assuming that a profitable project necessarily supplies enough cash this month.
Context reference: SACAP
16. Resource planning includes review capacity
A project resource plan must allow for preparation, coordination, checking and authorisation. Available staff hours are not interchangeable when tasks require different experience. Identify bottlenecks at the review stage as well as the production stage. If several deliverables need the same reviewer simultaneously, adding drafting capacity alone may not improve the issue date.
Worked example: Two teams finish drawings on Friday, but one reviewer needs a day for each package. The manager staggers completion to allow both reviews.
Mistake to avoid: Scheduling all production to finish at the deadline with no allowance for checking.
Context reference: SACAP
17. Consultant interfaces need assigned ownership
Consultant coordination depends on clearly assigned design inputs, outputs and interface decisions. Identify who designs each element, who supplies supporting information and who resolves conflicts. Coordination does not automatically transfer a specialist’s design responsibility to the architect. Record the agreed allocation and investigate gaps where two parties each assume the other is responsible.
Worked example: A roof plant platform needs architectural screening and structural support. The interface register assigns each design and sets a joint coordination review.
Mistake to avoid: Leaving an interface undesigned because both consultants describe it as outside their scope.
Context reference: SACAP
18. Quality assurance prevents recurring errors
Quality assurance establishes repeatable processes intended to prevent errors; quality control checks a particular output. Use both. A drawing review may catch a missing dimension, while a revised checking process reduces the chance of repeating it. Concentrate checks on consequential project risks and recurring weaknesses rather than treating a completed checklist as proof that the design is correct.
Worked example: A review finds inconsistent door references. The team corrects the issue and adds a cross-check between plans, schedules and specifications.
Mistake to avoid: Correcting one drawing without addressing the process that repeatedly creates the discrepancy.
Context reference: SACAP
19. Document control distinguishes status from revision
A revision identifies a change to a document; status explains its intended use. A recent drawing may still be unsuitable for construction if it is issued only for review. An issue register should identify recipients, revisions and status, while superseded information is clearly controlled. Project teams need to know which authorised information governs a particular activity.
Worked example: Revision D is issued for coordination. Revision C remains the construction issue until the authorised construction package is formally updated.
Mistake to avoid: Assuming that the highest revision letter automatically authorises construction.
Context reference: SACAP
20. Continuity planning protects essential project functions
Continuity planning identifies how essential work can continue when a key person, system or office becomes unavailable. Prioritise access to current documents, outstanding decisions and contractual communications. Establish backups and authorised substitutes appropriate to confidentiality and project responsibilities. A technical backup is useful only if the team can restore and interpret the information it contains.
Worked example: When a project lead is absent, a designated colleague uses the decision register and current issue set to manage an urgent coordination meeting.
Mistake to avoid: Keeping crucial project knowledge only in one person’s email account or memory.
Context reference: SACAP
Procurement and building contracts
21. Procurement allocates design and construction responsibilities
A procurement route determines how design, construction and associated responsibilities are organised. Compare routes through the client’s priorities, available information and capacity to manage interfaces. Labels alone do not establish the actual allocation: appointments and contracts must be examined. A route that permits earlier construction may also create different coordination demands and exposure to unresolved design decisions.
Worked example: A client considering early construction identifies which design packages must be complete before work begins and who will coordinate the remaining packages.
Mistake to avoid: Choosing a procurement label without examining the resulting responsibility allocation.
Context reference: SACAP
22. Tender comparisons require a common basis
Tender totals are comparable only when they address equivalent scope and stated assumptions. Identify exclusions, qualifications and pricing discrepancies before ranking bids. Make transparent comparison adjustments without silently changing an offer. Clarifications should follow the applicable procurement procedure. An adjusted comparison figure helps analysis, but it does not automatically become the tenderer’s agreed contract price.
Worked example: Bid A is R960,000 but omits an illustrative R70,000 item. Its comparison total is R1,030,000, exceeding complete Bid B at R1,010,000 by R20,000.
Mistake to avoid: Selecting the lowest headline amount before checking what it includes.
Context reference: SACAP
23. Evaluation criteria should precede evaluation
Procurement evaluation needs criteria appropriate to the project and consistent with the applicable procedure. Establish how price, capability, programme and other relevant factors will be assessed before reviewing offers. Separate mandatory compliance checks from comparative judgement. A defensible recommendation explains the evidence behind each conclusion and records qualifications or unresolved matters.
Worked example: A refurbishment tender requires experience in occupied buildings. The evaluation examines relevant project evidence consistently across bidders rather than favouring an impressive presentation.
Mistake to avoid: Inventing a new selection criterion after seeing which tenderer it benefits.
Context reference: SACAP
24. Agreement depends on more than a document title
Contract formation and enforceability depend on applicable law and the parties’ communications, not simply whether a file is labelled ‘contract’. For practical analysis, identify the parties, proposed obligations, acceptance, conditions and unresolved terms. Avoid making legal conclusions from incomplete correspondence. Clarify ambiguous instructions before mobilisation and obtain appropriate legal advice where the existence or terms of an agreement are disputed.
Worked example: An email says ‘proceed once finance is approved’. The team seeks confirmation of that condition and the agreed terms before treating it as unconditional authorisation.
Mistake to avoid: Ignoring an express condition because a message contains the word ‘proceed’.
Context reference: SACAP
25. Authority follows the appointed role
A project participant’s title does not establish authority to change price, scope or completion obligations. Locate the relevant delegation in the appointments and contract. Distinguish someone who may request information from someone who may issue a contractual instruction. When authority is unclear, use the agreed confirmation route before representing a request as binding.
Worked example: A facilities manager asks for additional sockets. The request is referred to the authorised decision-maker before a contractual change is instructed.
Mistake to avoid: Treating every request made during a site visit as an authorised variation.
Context reference: SACAP
26. Payment valuation must avoid double counting
A payment assessment should distinguish cumulative value from the amount payable in the current period. Apply previous payments and relevant deductions according to the chosen contract and valuation basis. State whether retention figures are cumulative or current-period deductions. Supporting measurements and records matter because a mathematically correct subtraction can still rest on an incorrect valuation.
Worked example: For an assumed cumulative valuation of R200,000, previous payments of R150,000 and total retention held of R10,000, the current amount is R40,000 before other adjustments.
Mistake to avoid: Paying the cumulative value again without deducting amounts already paid.
Context reference: SACAP
27. A variation changes the contractual baseline
Assess a proposed variation against the work already required by the contract. A requested alteration may change the baseline, while correcting nonconforming work may simply fulfil an existing obligation. Establish the instruction, scope, valuation and time implications using the applicable procedure. Do not decide entitlement merely because someone performed additional physical work.
Worked example: The contract requires six washbasins. Adding a seventh changes the baseline; replacing an incorrectly installed specified basin requires separate assessment as corrective work.
Mistake to avoid: Treating every extra site activity as automatically payable additional work.
Context reference: SACAP
28. Allowances are not the same as final prices
An allowance provides for work or an item whose final cost is not yet settled. Its treatment depends on the contract, including how actual expenditure, attendance and adjustments are handled. Identify the allowance’s scope and assumptions before comparing it with a later quotation. Do not equate an allowance with a fully defined fixed-price obligation.
Worked example: An illustrative R50,000 allowance is replaced by an assessed R62,000 amount. The difference is R12,000 before any separately applicable contractual adjustments.
Mistake to avoid: Adding the full R62,000 while leaving the original R50,000 allowance in the total.
Context reference: SACAP
29. Delay assessment separates event, effect and entitlement
A delay event does not by itself establish an extension of time. Examine what happened, its effect on the completion path and the contract’s entitlement and notice provisions. Distinguish delay to an activity from delay to overall completion. Keep the time assessment separate from any claim for additional money, because their contractual tests may differ.
Worked example: A late finish selection affects an activity with available float. The assessor checks whether completion actually moved before recommending any time adjustment.
Mistake to avoid: Awarding the event’s full duration without analysing its effect on completion.
Context reference: SACAP
30. Retention and guarantees serve different mechanisms
Retention withholds an agreed amount from payment; a guarantee or other security creates a separate mechanism governed by its terms. Their purposes may overlap, but their operation is different. Check amounts, release conditions and any demand requirements in the actual documents. Neither mechanism establishes that defective work may be accepted without addressing the underlying performance obligation.
Worked example: A project has retention and a guarantee. The administrator checks each instrument’s release conditions instead of assuming completion releases both automatically.
Mistake to avoid: Treating all forms of security as interchangeable deductions from a certificate.
Context reference: SACAP
Regulatory decisions and coordinated design
31. Land-use permission and building approval address different matters
A project may involve separate controls over land use and the building proposal. Establish the applicable South African and local authority requirements rather than assuming one approval resolves every issue. Land-use questions concern matters such as permitted activities and development constraints; building review addresses the proposal under the relevant building requirements. Map each process to the decision it actually establishes.
Worked example: A proposed office conversion is checked for permitted use separately from the building alterations submitted for the required authority review.
Mistake to avoid: Assuming that an approved use proves every proposed building alteration is acceptable.
Context reference: SACAP
32. Site due diligence turns unknowns into constraints
Site due diligence identifies information that may materially affect the proposal before design assumptions become expensive commitments. Relevant enquiries can include boundaries, access, existing services, ground information and recorded restrictions. Distinguish verified information from assumptions and identify who must confirm each uncertainty. A visible feature on site does not establish its legal position, capacity or suitability for the project.
Worked example: A design assumes access through an existing gate. The team verifies the boundary and access position before locating the main entrance there.
Mistake to avoid: Using an observed site condition as proof of a confirmed development entitlement.
Context reference: SACAP
33. Determine which requirements apply before checking compliance
Compliance checking begins with applicability: the building’s use, work type, location and relevant approval conditions. Identify the governing regulations and referenced standards through current authoritative documents. Keep their respective roles clear, and confirm the applicable editions where necessary. A checklist copied from another project can miss requirements or introduce irrelevant ones if its assumptions are not examined.
Worked example: A team adapting a residential checklist for a public facility first checks the proposal’s applicable use and requirements before reviewing drawings.
Mistake to avoid: Assuming that the newest standard automatically governs every existing project.
Context reference: SACAP
34. Prescriptive and performance approaches need different evidence
A prescriptive approach checks specified provisions; a performance approach demonstrates an intended outcome through an accepted assessment method. The available routes and approval requirements must be confirmed for the actual project. An alternative solution requires appropriate evidence and competent assessment. Merely describing a design as innovative does not demonstrate that it achieves the required performance.
Worked example: A proposed alternative wall assembly is supported by suitable performance evidence and assessed through the applicable approval route before specification.
Mistake to avoid: Substituting a designer’s confidence for the evidence required to justify an alternative.
Context reference: SACAP
35. Fire strategy requires coordinated assumptions
Fire-safety design connects occupancy, escape, compartmentation, materials and relevant systems. These elements should be coordinated against the applicable requirements by appropriately competent designers. Changes to use or layout can invalidate earlier assumptions. At architectural coordination level, identify conflicts and obtain the necessary assessment; do not infer compliance from an isolated feature such as an exit sign.
Worked example: A room changes from storage to an assembly use. The team refers the revised occupancy assumptions for fire-strategy review before finalising the layout.
Mistake to avoid: Retaining the original fire strategy after changing assumptions on which it depended.
Context reference: SACAP
36. Accessibility depends on a continuous usable route
Accessibility is assessed across a person’s journey, including arrival, entrances, circulation and access to relevant facilities. A compliant-looking component does not establish that the complete route works. Check interfaces, operating conditions and the applicable requirements. Consider how users encounter doors, level changes and information together, while obtaining specialist input where the project requires it.
Worked example: An accessible entrance leads to a corridor interrupted by an unaddressed level change. The team revises the route rather than counting the entrance alone as sufficient.
Mistake to avoid: Assessing isolated ramps or doorways without checking the connected journey.
Context reference: SACAP
37. Structural changes require design coordination
Architectural changes can affect load paths, stability and structural detailing even when they appear visually minor. Identify the structural interface and obtain assessment from the responsible structural designer before issue. Coordinate openings, supports and loads through controlled information. An architectural drawing should not imply approval of a structural alteration that the relevant designer has not assessed.
Worked example: A larger opening is proposed in an existing wall. The architect obtains structural assessment and coordinates the resulting design before issuing revised construction information.
Mistake to avoid: Assuming that an apparently small opening has no structural consequence.
Context reference: SACAP
38. Services coordination needs space and access
Building services need physical routes, installation space and future access, not merely symbols on plans. Coordinate these requirements with structure, finishes and operational use. An arrangement can fit geometrically while remaining unserviceable. Resolve significant clashes before construction and identify the designer responsible for confirming each system’s technical performance.
Worked example: A ceiling layout accommodates a unit but leaves no maintenance access. The team adjusts the access arrangement with the services designer before finalising the ceiling.
Mistake to avoid: Checking that equipment fits while ignoring how it will be maintained.
Context reference: SACAP
39. Envelope diagnosis distinguishes moisture mechanisms
Moisture symptoms may result from rain penetration, condensation, plumbing leakage or other sources. Similar staining does not establish a common cause. Examine location, timing, weather and building-use patterns before selecting an investigation. Envelope design should coordinate continuity at junctions, with appropriate specialist assessment where needed. Avoid prescribing a remedy until the mechanism is sufficiently understood.
Worked example: Staining appears after heavy rain beside a window junction. The team investigates weather-related ingress rather than immediately attributing it to internal condensation.
Mistake to avoid: Choosing a cosmetic repair from the appearance of the stain alone.
Context reference: SACAP
40. Existing-building work requires verified existing information
Alterations depend on understanding existing conditions and the consequences of proposed changes. Old drawings may be useful evidence, but their accuracy and relevance need checking. Identify concealed or uncertain conditions and establish suitable investigation and approval steps. Existing occupation or long-standing use does not establish that a proposed alteration needs no regulatory consideration.
Worked example: An archived plan shows a service shaft, but a measured survey finds a different arrangement. The team updates the design baseline before developing alterations.
Mistake to avoid: Treating an old approved drawing as a complete record of what currently exists.
Context reference: SACAP
Liability, rights and dispute management
41. Reasonable care differs from a guaranteed result
A professional obligation to exercise reasonable care and skill differs from a promise that a particular outcome will occur. The actual duty depends on the appointment and applicable law. Examine wording that could extend obligations beyond services the practitioner can control. A disappointing outcome needs investigation; it does not alone prove that professional care was deficient.
Worked example: A client requests a guaranteed approval date. The architect explains the external dependencies and proposes an obligation framed around properly performing the agreed submission services.
Mistake to avoid: Promising certainty about an authority’s decision when that decision is outside the practice’s control.
Context reference: SACAP
42. Analyse alleged negligence through separate questions
A useful general framework examines the relevant duty, alleged departure from that duty, causal connection and claimed loss. Applicable legal tests require proper advice. Separate these questions rather than moving directly from dissatisfaction to blame. Evidence that an error occurred still needs to be connected to the responsibility undertaken and the consequences being claimed.
Worked example: A claim concerns an omitted detail. The team checks the appointed service, the expected standard, what followed from the omission and the documented loss.
Mistake to avoid: Treating any project loss as proof that the architect breached a duty.
Context reference: SACAP
43. Causation requires a supported chain of events
Causation asks how an alleged act or omission contributed to a particular consequence. Timing alone is insufficient: an event occurring first does not establish that it caused the later loss. Reconstruct the relevant sequence using records and consider alternative explanations. Keep technical diagnosis separate from any legal conclusion about liability.
Worked example: A late drawing is blamed for a delivery delay, but purchase records show the order was already delayed by an unresolved client selection.
Mistake to avoid: Assigning all subsequent delay to the first recorded problem without checking the actual sequence.
Context reference: SACAP
44. Responsibility analysis must include every relevant actor
Project losses can involve decisions by clients, designers, contractors and suppliers. Identify each actor’s obligation and contribution before reaching a conclusion. A client instruction may be relevant evidence, but it does not automatically remove a professional duty to explain a foreseeable concern. Responsibility allocation and any legal apportionment require the actual agreements, facts and applicable law.
Worked example: A client insists on a cheaper finish after receiving a recorded suitability concern. The assessment considers both the advice and the client’s subsequent decision.
Mistake to avoid: Assuming either that client choice excuses everything or that the architect controls every decision.
Context reference: SACAP
45. Risk clauses must match the responsibility undertaken
Contractual risk can exceed the practical control a consultant has over an outcome. Review obligations, indemnities, warranties and liability provisions together with scope. Identify wording that assumes responsibility for another party’s performance or an uncontrolled event. Obtain appropriate legal and insurance advice on material clauses rather than assuming familiar-looking wording has a harmless effect.
Worked example: A draft appointment makes the architect responsible for every contractor delay. The practice seeks advice and clarification before agreeing to that allocation.
Mistake to avoid: Reviewing the fee carefully while overlooking clauses that substantially expand exposure.
Context reference: SACAP
46. Insurance cover depends on the actual policy
Professional indemnity insurance does not automatically cover every allegation, contractual promise or project activity. Examine the policy’s insured services, limits, exclusions and notification conditions. Timing may be material under the policy wording. When a potential circumstance arises, consult the policy and insurer’s required process promptly without inventing a universal rule about when cover applies.
Worked example: A client alleges a design error. The practice checks notification requirements and contacts its insurer through the specified process before making commitments.
Mistake to avoid: Assuming that purchasing insurance eliminates the need to examine its conditions.
Context reference: SACAP
47. Notices need the right recipient, content and timing
A contract or appointment may require notice through a specified channel, with particular information and timing. Identify the applicable provision before treating ordinary correspondence as sufficient. Preserve evidence of transmission and receipt as appropriate. Notice supports a process; it does not itself prove the substance of a claim or establish the amount recoverable.
Worked example: A project issue appears in meeting minutes, but the contract requires a separate notice to a named recipient. The administrator follows that stated procedure.
Mistake to avoid: Assuming that general awareness of an issue satisfies every formal notice requirement.
Context reference: SACAP
48. Payment, ownership and permission to use are distinct
Rights in drawings and other project material depend on applicable law and agreements. Paying an invoice does not by itself explain every ownership or permitted-use question. Distinguish possession of a file from permission to reproduce, modify or reuse its contents. Clarify the intended project use and seek advice where rights are disputed.
Worked example: A client requests editable drawings for reuse on another site. The practice checks the appointment’s rights provisions before agreeing to that separate use.
Mistake to avoid: Assuming that access to a digital file establishes unrestricted permission to reuse it.
Context reference: SACAP
49. Dispute mechanisms perform different functions
Negotiation seeks direct agreement; mediation uses a facilitator; adjudication, arbitration and court processes operate under their applicable rules and authority. Their availability and effects depend on the contract and law. Identify the agreed sequence and the decision being sought. Do not assume that entering one process suspends every notice obligation or project responsibility.
Worked example: A valuation dispute is first discussed between the parties, then referred through the contract’s stated process when agreement cannot be reached.
Mistake to avoid: Selecting a dispute route without checking whether the agreement requires a particular procedure.
Context reference: SACAP
50. Settlement should define the issue it resolves
A settlement needs clear terms about the dispute, agreed actions, payment and any remaining obligations. Establish who has authority to agree and whether advice or insurer involvement is required. Avoid assuming that informal labels automatically create legal protection. A settlement of one valuation issue should be distinguished from a release covering other claims or future obligations.
Worked example: The parties agree a revised amount for one disputed variation and expressly record that unrelated defects remain subject to the existing process.
Mistake to avoid: Using broad release wording without understanding which rights or obligations it may affect.
Context reference: SACAP
Construction administration and project closeout
51. Construction information must work as a coordinated set
Drawings, schedules and specifications describe different aspects of the same work. Check their agreement at significant interfaces before issue. Where documents conflict, use the contract’s interpretation and clarification procedures rather than inventing a universal hierarchy. A coordinated set enables the contractor to understand dimensions, materials and performance requirements without choosing between contradictory instructions.
Worked example: A plan identifies Door D12 as glazed, while its schedule describes a solid leaf. The team resolves the discrepancy before issuing the package.
Mistake to avoid: Assuming that every document conflict can be resolved by always preferring drawings.
Context reference: SACAP
52. Programme float depends on the dependency network
A programme links activities through dependencies and durations. The longest path determines the earliest completion under the stated assumptions; other paths may have float. A shorter activity is not necessarily less critical. For simple calculations, state assumptions about resources and calendars, since constraints outside the diagram can change the result.
Worked example: Two independent paths take 11 and 8 days. With equal calendars and no resource conflict, completion is 11 days and the shorter path has 3 days’ float.
Mistake to avoid: Adding durations of parallel activities as though they must occur sequentially.
Context reference: SACAP
53. Site observation has defined coverage and limits
Site observation should be planned around the appointed service, project risks and opportunities to inspect work before concealment. A periodic visit records what was observed at that time; it does not establish continuous oversight. Communicate significant findings through the appropriate process. The contractor’s obligations and the professional’s observation responsibilities should be assessed separately under their agreements.
Worked example: A visit identifies an unresolved junction before it is enclosed. The architect records the location and obtains the responsible designer’s assessment.
Mistake to avoid: Treating a site visit report as proof that all concealed work was inspected.
Context reference: SACAP
54. Information requests should isolate the unresolved issue
A useful request for information identifies the relevant location, documents, discrepancy and decision needed. Track its response and any effect on dependent work. An answer may clarify existing requirements or initiate a change; determine which before issue. Do not let an information response bypass the authority and procedures required for contractual instructions.
Worked example: A contractor cites a conflicting soffit dimension and requests confirmation. The response identifies the governing dimension and checks whether the correction changes contracted work.
Mistake to avoid: Answering a vague query with a broad sketch that creates further ambiguity.
Context reference: SACAP
55. Shop-drawing review needs a stated purpose
Shop drawings develop fabrication or installation information within the contractor’s and specialist’s responsibilities. Review them against the appointed review scope and the design intent, while checking interfaces requiring coordination. Clarify the meaning of review status. A reviewer should not imply that every dimension, method or specialist calculation has been independently verified when that assessment was not undertaken.
Worked example: A joinery submission is reviewed for layout and specified finishes; an unresolved services clearance is referred for coordination before fabrication.
Mistake to avoid: Using an unqualified approval stamp without identifying what the review actually covered.
Context reference: SACAP
56. Site discrepancies require verification before redesign
When construction information and site conditions disagree, verify the measurement, reference points and document status first. Then identify the cause and obtain the appropriate design decision. Avoid instructing a workaround from an unconfirmed report. Preserve the original evidence, since the resolution may have implications for responsibility, cost and programme.
Worked example: A reported opening is 100 millimetres narrower than shown. The team checks the survey and current drawing before coordinating a revised component.
Mistake to avoid: Redesigning immediately around an unverified dimension supplied without clear reference points.
Context reference: SACAP
57. Defect records should describe observable nonconformity
A defect record should identify the location, observed condition and relevant requirement, with supporting evidence where useful. Distinguish confirmed nonconformity from a matter needing investigation. State the required response through the applicable process without assuming the technical remedy before assessment. Clear records support verification of correction and reduce disagreement about what was reported.
Worked example: A record identifies a particular door whose installed finish differs from the schedule, with a photograph and document reference for the responsible party.
Mistake to avoid: Writing ‘poor workmanship throughout’ without identifying inspectable conditions or requirements.
Context reference: SACAP
58. Completion is assessed against the contract’s definition
Completion milestones have meanings and consequences defined by the chosen contract. Assess the applicable criteria and supporting evidence rather than relying on appearance or percentage complete. Outstanding work, operational readiness and required documentation may affect the assessment differently. Occupation, certification and final closeout should not be assumed to be interchangeable events.
Worked example: A building looks finished, but an essential contractual readiness requirement is outstanding. The assessor checks the milestone definition before issuing a certificate.
Mistake to avoid: Declaring completion solely because almost all visible construction work is finished.
Context reference: SACAP
59. Handover information must support operation
Handover connects completed construction with the information needed to use and maintain it. Identify required records, manuals, training and responsibility for their production early enough to obtain usable outputs. Distinguish design information from verified records of the installed work. A folder’s existence does not establish that its contents are accurate, complete for the agreed purpose or understandable.
Worked example: The handover team finds a manual for a different equipment model and requests the correct installed-system information before closing that item.
Mistake to avoid: Accepting a large document package without checking its relevance to the installed building.
Context reference: SACAP
60. Post-completion review separates symptoms from obligations
After completion, reported problems may involve defects, operation, maintenance or changed use. Gather evidence before assigning responsibility and follow the relevant contractual process. Track each issue to a documented outcome. A performance review can also reveal lessons for later design, but that learning exercise should not replace assessment of outstanding project obligations or technical concerns.
Worked example: A room is reported as uncomfortable. The team compares installed operation and actual occupancy with the design assumptions before deciding which specialist investigation is needed.
Mistake to avoid: Classifying every user complaint as either a construction defect or misuse without investigation.
Context reference: SACAP
Official context sources
Examination identity verified:
Browse all study guides