Treat the BORAQS professional practice subject as a decision problem, not a recital problem. Every topic — registration, contracts, development control, liability, ethics — resolves into the same three questions: which actor must act, under which instrument, and in what sequence. Build a decision log of practice scenarios: name the trigger, the correct actor, the governing framework, and the ordered steps, then check each decision against the framework itself. The exercise and rubric in the final section give you a concrete way to run that log and measure your fluency.
Where lawful practice begins: the registration boundary in fact patterns
Ground everything in the Architects and Quantity Surveyors Act framework that establishes BORAQS as regulator: who may hold themselves out, sign, and practise, and how registered firms differ from registered individuals.
The first mapping to internalise is role to authority. A question can place a draftsperson, a graduate, a registered architect, and a firm in one fact pattern and expect you to say which of them may lawfully perform and sign which act. For each actor ask three questions: is this person registered, is this entity a registered firm, and does the act performed require registration? Keeping individual and firm registration distinct matters because a firm question answered with individual-registration rules produces a structurally wrong answer even when the principle sounds right.
Worked scenario: a developer asks a CAD technician to stamp drawings 'as architect' while the supervising architect is abroad. The plausible mistake is treating this as a commercial disagreement, or advising the technician to add the architect's registration number. The better decision names three facts: the technician may not hold themselves out as an architect; the registered architect may not lend registration to work not performed or supervised; and the matter sits within the Board's statutory mandate, not private negotiation. Actor, instrument, regulator — in that order — converts a vague answer into a framework-based one.
Discipline, negligence, or offence: keeping three legal tracks apart
Triage every wrong into three separate tracks: disciplinary action under the Board's statutory powers, civil liability between private parties, and statutory offences. Each track has a different complainant, forum, and remedy.
Trace one fact pattern through all three tracks to see the difference. If defective design contributes to a wall failure, the client may sue in negligence or contract (a civil track with damages as the remedy); the Board may take disciplinary action against the registrant (a regulatory track with sanctions against registration); and if conduct crosses a statutory line under building law, a separate public track exists. In an answer, each track needs its own sentence: who initiates it, under which framework, and what remedy it produces. Practise this triage until it is automatic.
A second confusion to dismantle is how each track is assessed. A negligence claim turns on whether the professional fell below the standard of a reasonably competent practitioner, established with evidence; a disciplinary matter is assessed under the Board's own statutory powers; a statutory offence depends on the wording of the particular enactment. Write sentences such as 'this is a civil claim because the client is the complainant and the remedy is damages' — the vocabulary disciplines your reasoning and prevents the collapse of all wrongdoing into one category.
| Track | Who initiates | Governing framework | Typical remedy |
|---|---|---|---|
| Disciplinary | Complaint to, or action by, the Board | The registration statute's disciplinary mandate | Sanctions against registration, e.g. reprimand or suspension |
| Civil | Employer, client, or affected private party | Contract law and negligence | Damages or other contractual remedies |
| Statutory offence | Public enforcement under the relevant enactment | Building and planning legislation | Penalties as the specific statute provides |
Certificate before or after valuation? Running contract machinery in order
Learn the standard building contract machinery as a sequence: instruction, variation assessment, valuation, interim certificate, extension of time. Identify the contract administrator and delivery method first, because each changes who designs, certifies, and bears risk.
The architect under a standard building contract is not merely the designer but the contract administrator: the person who issues instructions, has variations valued, certifies interim payments, and assesses extensions of time within the contract's own procedures. Study the machinery in order rather than as isolated clauses, then add the delivery-method check: under a design-and-build arrangement the employer's team's certification duties shrink and the contractor's design responsibility grows. Your first decision on any scenario should be 'what delivery method is this, and therefore who administers?' — a two-second check that redirects the whole answer.
Worked scenario: a contractor emails the architect claiming variation and delay costs after verbal site instructions. The plausible mistake is issuing a certificate immediately, or adjusting a previous certificate to make the sums work. The better decision follows the machinery: confirm the instruction in writing through the contractual route, record it in the site record, assess whether it is a variation at all, value it under the contract's rules, and assess the time impact separately before certifying. Sequence and documentation, not the number itself, are what the contract protects — and reversing a certificate undermines the whole payment mechanism.
Which gate is stuck? Mapping the development-approval chain
Build the approval chain as a sequence — planning consent for use and development, county-level development control, construction-phase control — and decide first which gate a scenario actually concerns before describing any duty.
Planning consent addresses use and development of land; county development control addresses whether the specific proposal complies with zoning and building rules; construction-phase control addresses inspections and completion. A change of use is a planning question; structural drawings raise a building-control question; starting works ahead of approvals is a question about the sequence itself. Attach each party's duty to a stage — the architect's submission duty, the contractor's obligation to build per approved drawings, the employer's duty to obtain consents — so your answer says 'the contractor must not deviate from approved drawings, and deviations must be re-submitted before construction,' not the generic 'ensure compliance'. Check current statutory titles and versions as you study, since they are periodically revised.
Worked scenario: a client urges the architect to let the contractor start foundations while a planning objection is pending, promising 'the approval will come'. The plausible mistake is agreeing conditionally, treating approval as a formality. The better decision is procedural: construction must not begin ahead of the approvals the development requires, so record the advice given and the client's instruction, then decline to authorise work that depends on the outstanding consent. It matters because premature works expose the employer to enforcement and the professionals to findings about their own conduct — a risk no client letter absolves.
Scope creep and the missing engagement letter: practice management as documentation
Treat practice management as documentation discipline: a written engagement fixing services, stages, fees, and dispute route; retrievable project records; and indemnity arrangements proportionate to the practice's exposure.
The examinable core is what a well-run practice documents. An engagement letter fixes the services, the stages, the fee basis, the client's obligations, and the dispute route; project records carry instructions, minutes, drawing registers, and correspondence in a retrievable way. Scenario questions test which document governs a disagreement: when scope grows, the engagement letter and its variation mechanism decide, not the memory of a conversation. Practise naming the controlling document before you name the outcome. Distinguish professional indemnity insurance from quality systems too: insurance transfers financial consequences, while checking procedures reduce the chance of a claim arising — a junior's drafting error is answered in both registers.
Worked scenario: a sole-practitioner architect takes on a large project on a brief email, and the client later demands extra services mid-project. The plausible mistake is doing the extra work and negotiating fees afterwards, leaving scope undocumented. The better decision is to confirm in writing before proceeding: identify that the new requests fall outside the agreed services, set out the additional fee basis, and obtain the client's written acceptance under the engagement's variation mechanism. It matters because fee disputes are decided on the documented scope, and an undocumented expansion converts a payable service into a contested one.
After the instruction: continuing site duties and the evidence record
Anchor this topic on two distinctions: general versus full supervision as set by the contract and engagement, and supervision versus guarantee — the contractor remains responsible for the work and the site; the architect observes and administers.
The intensity of the architect's inspection duty scales with the supervision arrangement chosen, so a fact pattern should tell you which regime applies before you describe any duty. Answers that make the architect liable for the contractor's means and methods have confused the roles, and the same confusion infects site-safety questions, which belong primarily to the contractor as the party in control of the site. Practise the site record as an evidence system: site minutes, dated instructions, photographs, registers of submittals and defects. In a dispute, the party with a contemporaneous record can prove more — so treat missing documentation as a live issue in the answer, not a detail.
Worked scenario: on a site visit the architect notices non-conforming concrete work, but the contractor promises to 'sort it out' and the client wants no delay. The plausible mistake is accepting the verbal assurance and noting nothing. The better decision is to record the observation, issue a written instruction under the contract to remedy or reject the work, and require demonstrated conformity before the affected work is covered up. It matters because the record and the instruction are what protect both the client's building and the professionals' positions if the defect surfaces later.
Before the dispute: ethics triage, escalation steps, and the decision log
Separate ethics from disputes: a conflict changes what you may do; a fee or performance disagreement follows the contract's escalation route. Name the ethics issue and the dispute route in separate sentences, then run the decision-log exercise.
Train a simple triage: is this an ethics question (a conflict that changes what you may do) or a dispute question (a disagreement resolved under the contract's route)? Withholding a certificate to pressure an employer over unpaid fees converts a commercial dispute into a professional-conduct problem, because the certificate is a contractual duty, not a bargaining chip. Worked scenario: an employer refuses to pay certified interim amounts while the architect's firm has its own fee arrears with the same client. The plausible mistake is stopping certificates or delaying administration until paid. The better decision separates the ledgers: continue the contractual role, pursue the firm's fees through the engagement's dispute route, and record the conflict position in writing. Learn the escalation ladder precisely — negotiation, then whatever mediation or referral mechanism the contract names, then arbitration or the courts — and say which step a scenario has reached.
Exercise — the scenario decision log: collect twelve practice scenarios across the six topic areas. For each, write four lines: trigger, actor, instrument, sequence. Then score it against the rubric below. A log scoring at least 9 of 10 across your last six scenarios, with written reasons for each point, is a reasonable learning milestone — it measures decision fluency, not a predicted exam result. Redo any scenario scoring below 7 after a week, without looking at your first attempt.
- Rubric: 3 points — the governing framework is named specifically, not generically.
- Rubric: 3 points — the actor is correct, including any registration or firm-status issue.
- Rubric: 2 points — the sequence is complete and correctly ordered.
- Rubric: 2 points — a plausible wrong turn is identified and rejected with a reason.
- Readiness check: you can name the regulator, its registration categories, and the practice boundary for individuals and firms, from memory.
- Readiness check: you can trace a variation from instruction to certificate in the correct order.
- Readiness check: you can list the development-approval chain in sequence and say which stage any scenario touches.
- Readiness check: you can triage a fact pattern into disciplinary, civil, and statutory tracks in under a minute, and your last six logged scenarios score at least 9 of 10.
- Administrative note: exam dates, eligibility, fees, and logistics are matters for the regulator's own channels — confirm them directly at boraqs.go.ke.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.