Study Part 3 by practising the routing decision behind each scenario, not by memorising clause text: identify the role you occupy, select the correct instrument (instruction, notice, certification, statutory submission), and specify the evidence trail. Then test yourself against written scenarios and your own project records using the rubric in this guide.
Separating the Registered Architect's Statutory Role from Contractual Duties
Registration gives you duties to the public and the Board; your appointment gives you duties to a client and a contractor. Sound exam reasoning labels which track a question targets before answering it.
A registered architect in Malaysia holds authority from two different places. The statute and professional conduct rules govern registration, the use of the title and stamp, and responsibilities attached to submissions made to authorities. The contract between the parties governs how works are administered: instructions, certification, and payment. The difficulty is that a single routine act, such as approving a material or certifying a stage, triggers both tracks at once, and study notes that merge them produce answers citing conduct rules for a contract question, or contract machinery for a conduct question.
Apply this by tagging every practice scenario at the start: is this about my standing as a registered person, or my performance under an engagement? A scenario about a non-registered person preparing submissions belongs to the first track; a scenario about a disputed certificate belongs to the second. Once tagged, use that track's vocabulary and evidence. Drill this by writing a one-line label on top of each practice question you attempt; if you cannot label it, you have not understood the scenario yet.
Turning Client Changes into Proper Contract Instructions
A change asked for in a meeting is not yet a variation. The correct route is a written instruction through the channel the contract recognises, with valuation and client authorisation recorded.
The core difficulty in contract administration is that several instruments look similar but do different jobs: an architect's instruction directs work, a variation order records and values a change to the works, and a site record merely documents what was observed. Practice scenarios often begin with an informal request because that is how changes arrive on real projects, with a conversation in a meeting or a phone call. The reasoning you must demonstrate is converting that conversation into the instrument the contract recognises, in the right sequence, before cost and time consequences harden.
Scenario one: after award, the client asks in a site meeting to relocate a corridor wall. The plausible mistake is replying by email, 'please proceed as discussed,' then issuing a variation order weeks later with a different written description. The contractor prices from the email, the variation order says something else, and the valuation becomes contested. The better decision: issue a formal instruction describing the change, confirm the client's authorisation of the cost implication, enter it in the variation register, and let the valuation follow the described change. It matters because the contract recognises one instruction channel; informal channels create parallel records that undermine every later assessment.
| Site event | Instrument to use | Evidence to attach | Follow-up record |
|---|---|---|---|
| Client requests a design change | Written instruction describing the change | Client authorisation of cost and time impact | Variation register entry with valuation |
| Unforeseen condition delaying work | Instruction plus a notice trail from the contractor | Programme analysis, photographs, dated observations | Extension-of-time assessment with reasons |
| Work not in accordance with documents | Instruction rejecting or requiring rectification | Marked-up drawings, inspection record | Certification position and re-inspection note |
Assessing Extension of Time Without Inventing Facts
Extension of time, loss and expense, and practical completion are three different questions needing different evidence. Separate the events, the tests, and the documents before forming an assessment.
Delay reasoning fails when these three concepts are blended. An extension of time adjusts the completion date and rests on whether an event entitles the contractor to more time under the contract's provisions. Loss and expense is a money question with its own substantiation. Practical completion is a state-of-works judgement, not a date calculation. A defensible assessment names the concept being decided, states the test applied, and matches the evidence to that test, rather than writing one general narrative that covers none of them precisely.
Scenario two: the contractor requests six weeks, citing late structural steel deliveries. The plausible mistake is granting all six weeks on the strength of a sympathetic report. The better decision: separate the events shown in the records, note that some weeks also carry weather and other site matters, assess each event's causation against the programme the contract recognises, and state the reasons and dates in the assessment itself. It matters because an unexplained global award is difficult to defend later, while an event-by-event assessment shows the reasoning and survives scrutiny even if a party disagrees with the outcome.
Checking Site Substitutions Against Approved Plans and By-Laws
Your statutory responsibility attaches to the drawings and documents approved through submission. A substitution that affects a regulated element must be checked against those documents, not accepted as site equivalence.
By-law knowledge is better studied as a checking process than as a list to recite. For each element, ask what requirement governs it, which approved document shows compliance, and what would change if the detail were altered. This frames the Uniform Building By-Laws and related statutory requirements in Malaysia as a reason to revisit submissions, which is how the obligation operates in practice during construction, when changes arrive as substitution requests and value-engineering proposals.
Scenario three: a contractor proposes replacing a solid wall with a glazed screen to improve daylight, claiming the alternative is 'equivalent.' The plausible mistake is agreeing on site because the material looks adequate. The better decision: compare the proposal with the approved plans, ask whether the affected element carries a regulated function such as fire performance or separation, and treat any change to that element as an amendment requiring revised documentation before the work proceeds. It matters because the submitting person's responsibility runs to what was approved, and an undocumented substitution replaces a checked document with an unchecked verbal assurance.
Matching Procurement Routes to Risk Allocation
Procurement choices decide who carries design development, price certainty, and coordination risk. Explain a route by the risks it shifts, then connect it to the contract administration it implies.
Project management questions reward risk reasoning rather than route names. A traditionally procured, fully designed project places design risk with the design team and gives the client price certainty measured against complete documents. A design-and-build arrangement transfers design development to the contractor, which changes who the architect's client-facing duties run to and how instructions work. Management-oriented arrangements trade price certainty for speed and coordination overhead. For any scenario, articulate the client's priorities first, then argue the route from those priorities.
Practice by writing one sentence per route naming the risk it transfers and one sentence naming the administration consequence, for example who evaluates changes and against what documents. Then test the combination on scenarios: a client needing an early start with unfinished design points one way; a client needing firm cost before commitment points another. If you can state the trade-off and its contractual consequence, the reasoning transfers to whatever specific arrangement the exam scenario describes.
Building Case-Study Evidence You Can Defend Under Questioning
Prepare case-study material as decisions with reasons and records, not as project descriptions. For every choice, be ready to name the alternative rejected and the document that evidences the decision.
Case-study discussion is strongest when organised as a chain: situation, options considered, decision, instrument used, evidence produced. Rebuild one package of your own project experience in that chain. Where the real project was informal, say so and describe what a fully documented version would have contained. That honesty converts ordinary experience into exam-ready reasoning, because the question being tested is judgement about process, not the glamour of the building.
Practical exercise: pick one construction-stage episode from your experience and draft three documents from scratch, an instruction describing a change, a variation register entry with a stated basis of valuation, and a short delay assessment with reasons. Expected observations: your first drafts will lack quantification, will not cross-reference the document that authorised the change, and will use conversation summaries where dates and drawings belong. Self-check rubric, one mark each: instruction route named; contractual or statutory basis stated; quantities or time impacts given where relevant; authorisation and date recorded; register cross-referenced. Aim to improve draft to draft; these marks are learning milestones, not predictions of exam outcomes.
A Six-Week Preparation Sequence and Concrete Readiness Checks
Study in rotating themes rather than by document length: conduct, contract machinery, statutory checking, procurement, then integration. Finish when you can route any scenario to instrument plus evidence unaided.
A realistic adaptable sequence: weeks one and two, build the role and conduct track, then the contract machinery track, writing your own one-page summaries of who may instruct, certify, and decide. Week three, statutory checking: take a simple plan and practise tracing elements to requirements and to the documents that show compliance. Week four, procurement and project management trade-offs. Week five, write full answers to scenario questions under time pressure. Week six, rebuild your case-study chain and re-run the weakest topic. Compress or extend the proportions to fit your available time.
Readiness checks: you can label any scenario as statutory, contractual, or documentary within a minute; you can draft an instruction and its register entry without a template; you can state, for three substitutions, whether the approved document needs revisiting and why; you can argue a procurement route from a client's stated priorities; and your case-study chain survives a colleague's cross-examination. Administrative matters such as eligibility and scheduling are set by the Board, so confirm current requirements directly with Lembaga Arkitek Malaysia rather than relying on secondary sources.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.