For each practice scenario, train a three-step written habit: (1) name the duty at stake and to whom it runs, (2) name the controlling document or approval process, (3) recommend a documented action within your authority. Comparing the client engagement with the construction contract, and planning approval with building compliance, distinguishes these two relationships clearly in your answers.
Where client loyalty ends and public duty begins in scenario questions
Ethical scenarios test whether you identify whose interest is at risk before advising a client. The TTIA frames architecture in Trinidad and Tobago as ethical practice accountable to the public, so answers should place public safety and honest representation ahead of client preference.
Worked scenario one: a developer client asks you to present drawings as your own work when a former employee produced most of them, and to submit them quickly 'before anyone raises questions.' The weak response is to focus on the commercial pressure and agree informally, perhaps through a friendly conversation with no record. The stronger decision is to decline misrepresentation in writing, attribute authorship accurately, and separate that refusal from the legitimate parts of the commission you can still support. The reason this matters: an architect's drawings are relied on by authorities, builders, and future occupants, and honest representation is what makes that reliance reasonable.
To structure an answer like this, follow a fixed sequence: state the duty and to whom it runs; name the specific misrepresentation risk; state what you will do instead; and record the advice in writing. Contrast this with a design-studio answer, which would argue about the drawings themselves. Here the drawings are almost irrelevant — the tested judgment is that a professional cannot lend their signature or credentials to a false account of authorship, regardless of the fee at stake or the relationship with the client.
Conditions of Engagement versus the construction contract: keeping two relationships straight
Practice questions mix two separate relationships: your engagement by the client and the client's contract with a contractor. The TTIA publishes Conditions of Engagement for architects; answers go wrong when obligations from one relationship are attributed to the other.
A recurring confusion: a scenario says 'the contract requires the architect to inspect weekly,' and the question is which contract. Your Conditions of Engagement with the client define your services, fee basis, and duties — for example, periodic site visits at defined stages. The construction contract between client and contractor defines the contractor's obligations and may give you defined functions under it, such as issuing instructions or certificates. If a scenario describes a dispute over defective work, the tested move is to locate each party's obligation in the correct document before answering, because your liability to the client and the contractor's obligations to the client arise from different sources.
Train this by rewriting scenarios: take any practice situation and ask three questions — what does my engagement require of me, what does the construction contract require of the contractor, and what does either document require me to do about the other party's performance? Write one sentence per question. Over a week of practice scenarios, this habit becomes automatic, and it protects you from answers that, for example, promise the client weekly inspections you never agreed to, or assume you can direct the contractor when your engagement provides only observation and reporting.
| Aspect | Conditions of Engagement | Construction Contract |
|---|---|---|
| Parties | Architect and client | Client and contractor |
| Defines | Scope of architectural services, fee basis, stages | Contractor's scope, time, payment, quality obligations |
| Your role under it | Principal providing services | Defined functions such as instruction or certification, if stipulated |
| Typical scenario hook | Client demands extra services at the original fee | Contractor requests an extension of time or variation |
| Answer habit | Cite what your engagement actually covers | Cite the contractor's obligations, not yours |
Planning permission and building approval: sequencing advice you can defend
Regulatory answers reward separating land-use planning consent from technical building compliance, and treating each as a gate before construction. Advise clients on sequence in writing, and direct them to verify current requirements with the relevant authorities.
Worked scenario two: a client, eager to start, asks you to tell the contractor to begin site clearing 'since the drawings are already in for approval.' The plausible mistake is to agree verbally, reasoning that early works are harmless and the relationship is at stake. The better decision is a short written memo that distinguishes the approval stages, states that no approval yet exists, notes that early works could proceed without authorization, and recommends waiting until the relevant consents are issued — while confirming you will respond quickly to any requests from authorities. This matters because the architect who channels an instruction to start is no longer a bystander; they have participated in a decision with legal exposure.
For answers of this kind, name the processes in general terms — planning or land-use consent on one track, building or technical approval on another — without quoting specific thresholds or provisions from memory. A defensible answer identifies the distinction, describes the correct sequence, and adds that the client should confirm current requirements and forms with the responsible divisions, since requirements change. Candidates lose defensive strength by inventing precise legal content; the safer, and more professional, answer commits to verifying the live requirements rather than reciting possibly outdated ones.
Contract administration scenarios: instructions, variations, and certificates
Administration scenarios test whether you know which instrument to use. A site instruction directs work already in scope, a variation changes scope, and a certificate values or releases payment — each creates a different record trail.
Worked scenario three: a contractor tells your site supervisor that weeks of heavy rainfall have delayed the programme and asks for extra time informally, and your supervisor replies 'we'll sort it out.' The mistake is the informal response: it acknowledges a claim without triggering the contract's notice process, creating ambiguity about entitlement and dates. The better decision is to require the contractor's written claim, note the dates and weather conditions claimed, and respond through the formal mechanism the contract provides, keeping your own contemporaneous site records. The point is not that the contractor is wrong — weather may well justify relief — but that entitlement can only be assessed on a documented claim through the correct channel.
A related habit is distinguishing your instruments when you write: if the scenario asks you to deal with a kitchen repositioned after fittings were ordered, decide whether this is an instruction within the original scope or a variation requiring agreement on cost and time, and say which. If it asks about payment, describe what the certificate does and the records that support it. Write one practice paragraph per instrument each study week. Answers that name the correct instrument and its record trail read as professional competence; answers that blur an instruction into a variation read as uncertainty about the architect's authority.
- Site instruction: directs or clarifies work within the existing scope; record date, description, and any cost or time implications to be resolved.
- Variation: changes the agreed scope; requires documented agreement on adjustment to cost, time, or both before work is treated as authorized.
- Certificate: formally values work or releases payment; must trace to verified records of what has been executed.
- Site records: contemporaneous notes, photographs, and correspondence that later substantiate every claim or decision above.
Technical and design standards answers: argue from intent, then commit to verification
Technical questions are best answered by linking each design decision to its purpose — storm exposure, heavy rainfall, heat, ventilation — and stating that details will be verified against current national standards rather than asserting specific numeric thresholds from memory.
In a Trinidad and Tobago context, the environmental reasoning you already possess is the valuable part: heavy wet-season rainfall drives roof drainage and detailing decisions; hurricane exposure drives structural anchorage and opening protection; sustained heat and humidity drive cross-ventilation, shading, and material durability, including corrosion resistance near the coast. An answer that traces a detail to one of these drivers demonstrates applied judgment. An answer that recites a number with no stated source or verification step demonstrates the opposite, because standards are revised and an architect citing stale figures creates real risk on a live project.
Structure every technical answer in three sentences: the design intent, the category of standard that governs it, and the verification commitment. For example: the parapet and gutter detail is intended to shed intense wet-season rainfall clear of the wall; it falls under weather-resistance and drainage provisions; and the specification will be checked against the current applicable national standards before tender. If a scenario contrasts a new building with a renovation, add the difference explicitly — existing structures constrain what can be achieved, so the answer should identify the achievable performance and where it departs from the standard for new work.
A timed decision-memo exercise with a self-check rubric
Once per study session, convert one topic into a scenario and write a 15-minute decision memo. Score it against a fixed rubric; the observations you record about your own writing are the revision material.
The exercise: draw one scenario from your own practice reading — a client pressure, a contractor claim, an approval question — and write a memo of roughly 150 words in 15 minutes. Structure it in four moves: the duty and to whom it runs; the controlling document or process; the recommended action within your authority; and the record you will create. Expected observations when you review: your first drafts usually open with facts rather than the duty, name no document, and propose actions that exceed the architect's role. Catching those three patterns on your own memos is the fastest way to stop repeating them.
Self-check rubric — score each memo one point per item: (1) the duty and the party owed it are stated in the first two sentences; (2) the controlling document, contract, or approval stage is named; (3) the recommended action is within an architect's actual authority; (4) a written record or communication is specified; (5) nothing is asserted that requires verification you have not committed to. Five points is a strong memo; three points indicates the structure needs another pass the following session. Treat these as learning milestones for your practice writing, not as predictions of any exam outcome.
An adaptable preparation sequence and concrete readiness checks
Rotate weekly through the topic areas — ethics, engagement and practice management, regulatory framework, contract administration, technical standards — converting each into memo practice, then finish with mixed scenarios under time.
A realistic adaptable sequence: weeks one and two, build the memo habit using ethics and client-pressure scenarios only, since these need no technical content. Week three, add the engagement-versus-contract distinction and rewrite three practice scenarios to identify which document governs. Week four, practice approval-sequencing memos and the two-track distinction. Week five, contract administration scenarios — instructions, variations, certificates. Week six, technical answers built on design intent plus verification. Week seven onward, mix all types randomly at 15 minutes each. Adjust the weighting toward whatever your rubric scores lowest; the sequence is a framework, not a schedule imposed from outside.
Readiness checks before you conclude preparation: you can state, from memory, the four moves of a decision memo and apply them to an unfamiliar scenario; you can explain in two sentences the difference between the Conditions of Engagement and the construction contract; you can describe the planning-versus-building distinction without inventing legal detail; you can classify an instrument as instruction, variation, or certificate and name its record trail; and five consecutive mixed memos score four or more on the rubric. For administrative matters — eligibility, format, scheduling, fees — confirm current details directly with the TTIA at ttia-architects.org rather than relying on secondary summaries.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.