Use these 60 concepts to develop professional judgement in UK architectural practice. Each concept connects a principle to a resolved scenario and a mistake to avoid. Begin with conduct and legal foundations, then work through appointments, business management, project delivery and construction contracts. In each scenario, identify the relevant evidence, decision-maker and consequences.
Professional conduct and ethical judgement
1. Qualification, registration and membership
A qualification demonstrates educational achievement, registration establishes regulatory status, and professional membership establishes an association relationship. These are separate checks. ARB identifies its Register as the definitive record of UK architects; neither an examination result nor a membership claim alone verifies someone's registration.
Worked example: A consultant lists a professional practice qualification and RIBA membership. Before recording their registered status, the practice checks the ARB Register and matches the individual.
Mistake to avoid: Treating a qualification certificate or membership badge as proof of registration.
Source: Home - Architects Registration Board; RIBA
2. Honest statements about uncertain evidence
Professional advice should distinguish observations, assumptions and conclusions. Confidence in presentation must reflect confidence in the underlying evidence. When new information changes a material conclusion, correct the advice and explain its consequences to those relying on it. Keep a record of both the original basis and correction.
Worked example: A feasibility report assumes an existing wall is non-structural. Investigation disproves this, so the architect revises the layout recommendation and flags the cost implications.
Mistake to avoid: Leaving an earlier assurance uncorrected because the latest drawing quietly incorporates the change.
3. Conflicts require more than disclosure
A conflict can arise from financial interests, personal relationships or competing duties. Disclosure makes the connection visible but does not establish that the work can proceed impartially. Assess whether independent review, withdrawal from a decision or declining the role is necessary. Record the assessment and any agreed safeguards.
Worked example: A director's sibling owns a tendering firm. The director declares the connection and leaves tender evaluation to an independent colleague under an agreed process.
Mistake to avoid: Assuming that declaring a relationship automatically makes every subsequent recommendation acceptable.
4. Competence is specific to the task
Assess competence against the actual assignment, its complexity and the consequences of error. Delegation needs appropriate supervision, review and access to specialist knowledge. Experience in one building type or design stage does not automatically establish competence for another. Identify limits before committing the practice to a service.
Worked example: A team experienced in offices accepts a laboratory feasibility study only after securing specialist input for containment requirements and defining who reviews that advice.
Mistake to avoid: Using general architectural experience as evidence of competence in every specialist system.
5. Public interest and escalation
Project decisions affect occupants, neighbours and future users as well as the client. When a material concern arises, describe the evidence, foreseeable consequences and action needed. Escalate through appropriate project or professional channels if it remains unresolved. The response should reflect urgency without overstating what has been established.
Worked example: A proposed access arrangement appears to obstruct emergency access. The architect records the concern, requests competent review and escalates when the issue remains unanswered.
Mistake to avoid: Treating client approval as sufficient reason to leave a serious unresolved concern unaddressed.
Source: Home - Architects Registration Board; RIBA
6. Confidentiality and purpose-limited sharing
Share project information for a defined purpose with appropriate recipients. Permission to collaborate does not automatically permit publication or reuse. Where legal or professional obligations may require disclosure, establish the applicable basis and obtain advice when necessary. Limit any justified disclosure to relevant information and retain a clear record.
Worked example: A consultant needs occupancy figures for analysis. The architect provides the required totals without forwarding a client spreadsheet containing named employees and unrelated personal details.
Mistake to avoid: Sending an entire information package when only a small, relevant extract is needed.
7. Communication that enables participation
Effective professional communication makes the decision understandable to its audience. Consider language, accessibility, technical knowledge and how information is presented. Invite questions and check understanding of consequential choices. A signed approval may document a decision, but it does not by itself demonstrate that the implications were explained clearly.
Worked example: A client struggles with plans. The architect uses a simple spatial diagram and explains access implications before the client selects an entrance option.
Mistake to avoid: Repeating technical terminology more loudly instead of changing the explanation.
Source: Home - Architects Registration Board; RIBA
8. Environmental comparisons need consistent boundaries
Compare environmental options over consistent boundaries, including relevant construction, use, maintenance and replacement effects. Separate measured information from assumptions. A favourable result for one stage does not establish overall superiority. Explain sensitivity to uncertain lifespans or operating patterns rather than presenting a single estimate as an unquestionable answer.
Worked example: Two facade options are compared over the same study period. The option needing replacement includes that replacement impact, preventing a misleading comparison of initial impacts alone.
Mistake to avoid: Comparing one option's lifecycle impact with another option's manufacturing impact.
Source: RIBA
9. Complaints, corrections and potential claims
A complaint requires a fair investigation; it is neither automatic proof of fault nor something to dismiss defensively. Establish the facts, follow the practice's complaints process and communicate next steps. Distinguish immediate service improvements from decisions about liability or compensation, obtaining contractual and insurance advice where appropriate.
Worked example: A client complains about unanswered queries. The practice checks correspondence, appoints a contact and resolves communication gaps while separately investigating an alleged financial loss.
Mistake to avoid: Promising compensation before establishing the facts and checking relevant advice and policy requirements.
10. Respectful decisions and fair treatment
Professional respect applies to clients, colleagues, contractors and affected communities. Assess contributions on relevant evidence rather than status, identity or stereotypes. Provide a fair route for raising concerns, and address behaviour that prevents participation. Disagreement can be firm and documented without becoming personal or dismissive.
Worked example: A junior colleague identifies a coordination error during review. The chair examines the drawing evidence and assigns correction rather than dismissing the concern because of seniority.
Mistake to avoid: Confusing a person's position in the organisation with the reliability of their evidence.
Source: Home - Architects Registration Board; RIBA
UK legal and regulatory foundations
11. Establish the applicable UK jurisdiction
Planning and building-control frameworks differ across the United Kingdom. Start with the project's location, then identify the relevant authorities, procedures and current requirements. Advice from another UK nation may be informative but cannot establish local compliance. Record jurisdiction-specific assumptions before selecting forms, guidance or approval sequences.
Worked example: A practice reuses a checklist from a Manchester project for work in Cardiff. It first checks Welsh requirements and replaces items that do not apply.
Mistake to avoid: Assuming a familiar English approval procedure applies unchanged throughout the United Kingdom.
Source: Home - Architects Registration Board; RIBA
12. Planning and building compliance are separate
Planning addresses the acceptability of development in its setting, while building regulations address specified aspects of building performance and construction. The assessments interact but answer different questions. Track their requirements separately and coordinate resulting design changes. Approval through one process does not establish approval or compliance through another.
Worked example: An extension receives planning permission. The team still develops the technical information needed for the applicable building-control process before treating the proposal as ready for construction.
Mistake to avoid: Describing planning permission as confirmation that the technical design complies with building regulations.
Source: Home - Architects Registration Board; RIBA
13. Guidance and evidence of compliance
Guidance helps explain ways to address requirements, but compliance depends on the applicable framework and the actual proposal. Identify the requirement, relevant guidance, design evidence and unresolved questions. Where an alternative approach is proposed, obtain competent justification rather than assuming similarity to a familiar detail is sufficient.
Worked example: A standard detail is unsuitable for an unusual junction. The team obtains specialist assessment of the proposed alternative and records its basis and limitations.
Mistake to avoid: Copying a recognised detail without checking whether its assumptions fit the project.
Source: Home - Architects Registration Board; RIBA
14. Approval conditions create project dependencies
Read an approval together with its conditions and associated documents. Identify what must be provided, who is responsible and when the requirement affects progress. Track unresolved conditions explicitly. The existence of an approval does not establish that every activity may proceed; the actual wording and applicable procedure govern.
Worked example: An approval requires drainage information before a specified stage. The programme includes preparation and review of that information as a dependency rather than an optional later task.
Mistake to avoid: Recording an approval as complete while overlooking conditions that constrain subsequent work.
Source: RIBA
15. Public permission and private land rights
Public approvals and private rights are distinct. Boundaries, access rights, restrictions and ownership arrangements can affect whether a proposal can be implemented. Identify uncertainty early and obtain competent legal investigation. Architectural drawings should not present an assumed entitlement as established merely because a public authority accepts the development.
Worked example: A proposed servicing route crosses neighbouring land. The architect flags the access dependency for legal confirmation before recommending the route as a reliable project solution.
Mistake to avoid: Assuming planning permission grants access across land controlled by someone else.
Source: Home - Architects Registration Board; RIBA
16. Heritage significance before intervention
Establish relevant heritage designations, significance and constraints before deciding how to alter a building. Required assessments and consents depend on the work and jurisdiction. Specialist investigation should inform the proposal early. A visually minor alteration may affect significant fabric, so size alone is an unreliable measure of its acceptability.
Worked example: A small ventilation opening would remove part of a historically significant panel. Conservation advice leads the team to investigate a less intrusive route.
Mistake to avoid: Assuming a small physical change has negligible heritage consequences or requires no further assessment.
Source: RIBA
17. Contractual services and regulatory roles
An appointment defines contractual services, while applicable legislation may create separate project roles and duties. Similar role titles can have different meanings under different frameworks. Establish each role's legal basis, competent appointee and interfaces. Do not assume a commercial exclusion removes a duty imposed by the applicable regulatory framework.
Worked example: A project team uses one role title in two compliance discussions. It checks each framework separately and records the distinct responsibilities and appointments.
Mistake to avoid: Treating matching titles as proof that two regulatory roles are interchangeable.
Source: Home - Architects Registration Board; RIBA
18. Contract obligations and negligence allegations
Contractual analysis starts with the obligations agreed between parties. A negligence allegation concerns the applicable duty, conduct, causation and loss. These questions may overlap but should not be collapsed into one assumption. When assessing a dispute, organise the evidence and obtain legal advice rather than inferring liability from an undesirable outcome.
Worked example: A leaking roof prompts review of the architect's agreed services, design records, specialist input and construction evidence before conclusions are drawn about responsibility.
Mistake to avoid: Assuming a defect alone proves that the architect breached every relevant obligation.
19. Professional care and outcome guarantees
An obligation to exercise professional care differs from a promise that a specified result will always be achieved. Wording can alter the risk accepted, particularly when outcomes depend on others. Identify assurances extending beyond the intended service and obtain contractual and insurance review before accepting them.
Worked example: A draft appointment promises that no approval will ever be delayed. The practice seeks revised wording because authority decisions and third-party information are outside its complete control.
Mistake to avoid: Accepting absolute assurances as harmless marketing language in a binding appointment.
20. Copyright ownership and licences
Authorship, copyright ownership, possession of files and permission to use them are different matters. Examine the appointment and relevant agreements to establish permitted purposes, recipients and conditions. Delivery of a model does not automatically settle rights to adapt it for another development. Obtain advice where ownership or licence terms are disputed.
Worked example: A client wants to reuse a housing design on a second site. The practice checks the original licence and agrees the permitted reuse before releasing adapted information.
Mistake to avoid: Assuming that paying an invoice automatically permits unrestricted reuse of every design file.
Source: RIBA
Professional appointments and client responsibilities
21. Define services through deliverables
An appointment should identify parties, services, deliverables, exclusions and responsibilities in understandable terms. Broad stage labels alone may leave expectations unresolved. Connect each promised output to its purpose and level of development, then check consistency across the proposal, fee schedule and executed agreement.
Worked example: A client expects detailed joinery drawings within an outline design service. The appointment clarifies the included outputs and identifies detailed joinery design as a separate service.
Mistake to avoid: Assuming both parties attach the same meaning to an undefined design-stage label.
Source: Home - Architects Registration Board; RIBA
22. Client authority and decision routes
Identify who can instruct the architect and approve design, budget or service changes. Stakeholders may contribute useful views without holding decision authority. Establish a route for conflicting instructions and record significant approvals. For organisational clients, verify authority rather than assuming the most senior meeting attendee can bind the client.
Worked example: A tenant requests a layout change, but the landlord's project manager controls instructions. The architect seeks that manager's approval before committing to redesign.
Mistake to avoid: Treating every stakeholder request as an authorised instruction from the contractual client.
Source: Home - Architects Registration Board; RIBA
23. Fee mechanisms allocate uncertainty
A fixed fee requires defined scope and assumptions; time charges require agreed rates and reliable records; percentage fees require an agreed calculation basis. Each mechanism allocates uncertainty differently. Specify expenses, applicable taxes and adjustment procedures so changes in work or project value do not create avoidable ambiguity.
Worked example: An illustrative 2% fee uses an agreed £600,000 cost basis, producing £12,000 before stated extras. The agreement explains which cost changes affect that basis.
Mistake to avoid: Quoting a percentage without defining the amount to which it applies.
Source: RIBA
24. Additional services need their own assessment
A change to construction scope does not automatically authorise a change to professional fees. Assess whether the request creates services beyond the appointment, explain the additional work and follow the agreed approval procedure. Record fee and programme implications while distinguishing urgent project decisions from commercial agreement.
Worked example: A client replaces an approved kitchen layout. The architect identifies extra coordination hours and seeks approval for the additional service before carrying out the redesign.
Mistake to avoid: Assuming any construction variation automatically entitles the practice to an unspecified extra fee.
Source: Home - Architects Registration Board; RIBA
25. Information dependencies and reliance
Services often depend on information from the client or other consultants. State what is needed, when, and any limits on its use. Assess whether received information is suitable for the decision. If a dependency is unmet, explain the consequence rather than silently replacing missing evidence with an apparently settled assumption.
Worked example: A structural layout depends on a measured survey. When the survey is delayed, the architect issues the developing layout with the dimensional assumption clearly identified.
Mistake to avoid: Passing uncertain third-party information into final deliverables without checking or identifying its limitations.
Source: Home - Architects Registration Board; RIBA
26. Liability provisions need coordinated review
Appointments may contain liability limits, exclusions, indemnities or allocation provisions. Their effects depend on wording, context and applicable law. Review them together with the services and insurance arrangements, using appropriate advisers. A stated financial limit should not be treated as proof that every exposure is capped or insured.
Worked example: A draft includes a liability cap alongside a broad indemnity. The practice obtains legal and insurance review of their interaction before accepting the agreement.
Mistake to avoid: Reviewing a headline cap while ignoring provisions that may create separate or wider obligations.
27. Third-party obligations change the risk picture
A warranty or other third-party arrangement may create obligations to someone outside the original appointment. Establish the beneficiary, scope, permitted reliance and relationship to existing terms. Check consistency and insurance implications before signing. Providing project information and accepting an enforceable obligation are different decisions.
Worked example: A lender requests a warranty with broader obligations than the architect's appointment. The practice seeks aligned terms and appropriate advice rather than signing it as routine correspondence.
Mistake to avoid: Treating a third-party document as administrative paperwork with no additional risk.
Source: Home - Architects Registration Board; RIBA
28. Novation and the change of client relationship
Novation can replace an existing contractual relationship with a new one under agreed terms. In design-and-build projects, this may change whom the architect serves and how instructions are received. Examine the actual documents, earlier work, responsibilities and potential conflicts rather than assuming a universal effect from the label.
Worked example: After a proposed novation, the architect checks who can instruct design changes and how advice previously given to the developer will be treated.
Mistake to avoid: Continuing the previous client's instruction route after the contractual relationship has changed.
Source: Home - Architects Registration Board; RIBA
29. Suspension and termination require controlled handover
When services pause or end, follow the appointment's relevant procedures and obtain advice where necessary. Identify unfinished tasks, document status, authorised access and continuity responsibilities. Distinguish issued information from drafts. An orderly handover reduces the chance that another participant relies on work beyond its intended state or purpose.
Worked example: A commission ends during technical design. The practice provides a status schedule identifying issued packages, unchecked drafts and unresolved consultant interfaces.
Mistake to avoid: Releasing every working file without explaining which information is incomplete or unsuitable for reliance.
Source: Home - Architects Registration Board; RIBA
30. Choose a dispute route after defining the issue
Dispute processes differ in purpose, formality and effect. Start by defining the disputed obligation, evidence and desired resolution, then check the appointment and applicable framework. Negotiation, mediation and formal determination are not interchangeable. Obtain advice on available routes without assuming every dispute has identical procedures or deadlines.
Worked example: A disagreement concerns whether redesign was included in the fee. The practice assembles the scope and instruction records before proposing a focused negotiation.
Mistake to avoid: Selecting a formal process before identifying what is disputed and which arrangements apply.
Source: Home - Architects Registration Board; RIBA
Practice management and business decisions
31. Build a fee from defined costs
A cost-based fee estimate starts with expected staff hours and appropriate internal cost rates, then adds other project costs and a deliberate allowance for uncertainty and profit. State what the rates include to avoid double counting overhead. Compare the result with the service actually promised, rather than treating it as a universal market fee.
Worked example: A service needs 120 hours at an inclusive internal cost of £45 per hour plus £600 external costs. Estimated cost is £6,000 before profit or risk allowances.
Mistake to avoid: Adding overhead twice when the hourly cost already includes it.
Source: RIBA
32. Markup and margin use different denominators
Markup expresses profit relative to cost; margin expresses profit relative to revenue. Confusing them can produce an unintended fee. For a target margin, divide cost by one minus the margin. These calculations depend on a consistent cost definition and do not establish whether the proposed service can be delivered reliably.
Worked example: With £8,000 cost, a 25% markup gives a £10,000 fee and 20% margin. A 25% margin requires £8,000 ÷ 0.75, approximately £10,666.67.
Mistake to avoid: Adding 25% to cost and calling the result a 25% profit margin.
Source: RIBA
33. Cash forecasts follow receipt dates
Profitability and cash availability answer different questions. A cash forecast starts with opening cash, adds expected receipts and subtracts payments in their expected periods. Separate invoiced amounts from collected money. Test uncertain collection dates because salaries and other commitments may fall due before a profitable commission generates cash.
Worked example: Opening cash is £9,000, expected receipts are £7,000 and payments are £12,000. Closing cash is £4,000; delayed receipts would reduce that balance.
Mistake to avoid: Counting an issued invoice as cash already available to pay staff.
Source: RIBA
34. Capacity must match workload by skill and period
Translate commitments into staff demand across the programme, distinguishing skills and review responsibilities. Annual totals can conceal a short-term bottleneck. Account for leave, supervision and non-project work when estimating capacity. Resolve overload through realistic sequencing, staffing or scope decisions rather than assuming nominal headcount provides unlimited availability.
Worked example: Two projects each need 30 review hours next week, but the only qualified reviewer has 24 available hours. The practice changes deadlines before promising both reviews.
Mistake to avoid: Averaging demand across a year and overlooking an immediate specialist bottleneck.
Source: Home - Architects Registration Board; RIBA
35. Utilisation needs a defined measure
Utilisation is meaningful only when its numerator and denominator are specified. Project time, chargeable time and collected fee income are different measures. Training, review and administration also consume capacity. Interpret utilisation alongside quality, recovery and workload information; a high percentage alone does not demonstrate profit or sustainable performance.
Worked example: A colleague records 96 project hours from 128 available hours, giving 75% project utilisation. That figure does not reveal whether those hours were billable or recovered.
Mistake to avoid: Comparing utilisation percentages calculated using different definitions.
Source: RIBA
36. Work in progress is not automatically recoverable
Work in progress records work performed but not yet billed under a defined accounting approach. Its existence does not guarantee a contractual entitlement or collection. Review recorded time against scope, approved changes and charging terms. Identify unrecoverable effort early instead of allowing a large balance to disguise project underperformance.
Worked example: Forty hours were spent on an unapproved alternative. Before treating them as recoverable work in progress, the manager checks whether the appointment permits charging for that work.
Mistake to avoid: Assuming every recorded hour can eventually become a paid invoice.
Source: RIBA
37. Insurance and notification obligations
Professional indemnity insurance responds according to the actual policy, including its insured activities, exclusions and notification provisions. It is a risk-financing arrangement, not a substitute for competent service. When a concern could fall within policy notification requirements, obtain timely advice from the appropriate insurer or adviser.
Worked example: A client alleges financial loss from advice. The practice preserves records and promptly seeks advice about notification under its policy rather than waiting for formal proceedings.
Mistake to avoid: Assuming an allegation can be ignored until it becomes a court claim.
38. Payment controls and independent verification
Separate payment approval, execution and reconciliation where practicable. When a small team cannot fully separate roles, use compensating independent review. Verify altered bank details through a trusted contact route established independently of the change request. Retain evidence linking payments to authorised invoices and reconcile discrepancies.
Worked example: An email announces new consultant bank details. The finance manager calls the consultant using an existing verified number before updating the payment record.
Mistake to avoid: Verifying changed payment details using only the phone number contained in the suspicious message.
Source: RIBA
39. Correct the output and the underlying process
Quality management distinguishes correcting a defective deliverable from preventing recurrence. Investigate how the error passed through preparation, review and issue controls. Select a proportionate process change and check its effectiveness. Adding a checklist without addressing unclear responsibility, inadequate time or missing expertise may leave the original cause untouched.
Worked example: An incorrect schedule is reissued. Investigation also reveals no assigned checker, so the practice assigns review ownership and checks subsequent schedules for recurrence.
Mistake to avoid: Treating correction of one drawing as evidence that the recurring process failure is solved.
Source: Home - Architects Registration Board; RIBA
40. Continuity depends on recoverable information
Business continuity planning identifies essential services, information and people needed during disruption. Backups must be restorable, intelligible and accessible to authorised colleagues. Plan cover for key responsibilities and client communication. Test recovery arrangements proportionately, because the existence of a backup file alone does not demonstrate operational readiness.
Worked example: A project lead becomes unavailable. An authorised deputy uses the current decision register and document index to identify urgent approvals and continue client communication.
Mistake to avoid: Keeping backups while allowing passwords, project knowledge and decision history to reside with one person.
Source: Home - Architects Registration Board; RIBA
Design coordination and project delivery
41. Translate the brief into assessable requirements
Separate needs, preferences, constraints and proposed solutions. Turn broad ambitions into criteria that can guide option selection and review, with an identified decision-maker for conflicts. Avoid prescribing a solution before understanding the problem. An agreed brief provides a basis for assessing change rather than relying on shifting recollections.
Worked example: A client asks for a larger reception. Discussion establishes that the need is queue accommodation, so the team compares layout options against expected waiting demand.
Mistake to avoid: Treating the first suggested physical solution as the underlying requirement.
Source: RIBA
42. Information quality must fit the decision
Assess information by its date, method, coverage, accuracy and limitations. A source adequate for early feasibility may be inadequate for detailed construction coordination. Identify missing evidence and assign investigation responsibilities. Increase information confidence before consequential decisions instead of allowing polished drawings to conceal uncertainty.
Worked example: An old estate plan supports initial site orientation but lacks reliable levels. The architect requests a suitable survey before fixing drainage-related floor levels.
Mistake to avoid: Assuming information becomes more reliable merely because it has been transferred into a detailed model.
Source: Home - Architects Registration Board; RIBA
43. Responsibility matrices expose interface gaps
A responsibility matrix distinguishes preparing, providing input, coordinating, checking and approving deliverables. Reconcile it with appointments and obtain agreement from relevant parties. Its purpose is to expose gaps and overlaps, particularly where systems meet. Several contributors do not automatically create a single accountable coordinator.
Worked example: The architect and services engineer both contribute to plant access design. The matrix assigns coordination to one role and identifies who checks equipment clearance information.
Mistake to avoid: Marking several parties as involved without assigning ownership of the combined interface.
Source: Home - Architects Registration Board; RIBA
44. Cost forecasts distinguish commitments and uncertainty
Keep budget, estimate, committed expenditure, approved changes and forecast final cost distinguishable. Explain inclusions and avoid double counting allowances. Contingency represents defined uncertainty, not unlimited funding. Reconcile changes in the forecast by their causes so the client can understand whether scope, prices or risk assumptions have changed.
Worked example: A forecast contains £420,000 base cost, £18,000 approved additions and £22,000 remaining contingency: £460,000 total, assuming the additions are not already included.
Mistake to avoid: Adding approved changes twice because the revised base estimate already contains them.
Source: RIBA
45. Critical paths depend on relationships
A programme needs activity dependencies as well as durations. Under its stated assumptions, the longest dependent path determines earliest completion. Shorter paths may have float, but resource restrictions can alter the result. Reassess the critical path when sequencing changes instead of assuming the longest individual task is always critical.
Worked example: A five-day survey followed by eight-day design takes 13 days. A parallel ten-day study finishes earlier, so the survey-design path controls completion under these assumptions.
Mistake to avoid: Selecting the ten-day activity as critical solely because it has the longest individual duration.
Source: RIBA
46. Risks and issues need different responses
A risk concerns an uncertain future event; an issue has already occurred. Describe cause, event and consequence, then assign an owner and response. Qualitative ratings organise attention but are not objective measurements of certainty. Update the record when circumstances change, including when a risk becomes an issue.
Worked example: Possible late survey delivery is a risk. Once the delivery date is missed, it becomes an issue requiring a revised information plan and programme decision.
Mistake to avoid: Leaving an actual delay on the risk register without initiating issue resolution.
Source: Home - Architects Registration Board; RIBA
47. Document status controls permitted use
Revision identifiers show change history, while issue status communicates intended use. Both must be clear. Maintain an agreed document-control process, including superseded information and recipient records. A later revision is not necessarily approved for construction, and uploading a file does not demonstrate that affected participants received an authorised issue.
Worked example: Revision C develops a detail for coordination only. The issue record preserves that status, preventing the contractor from treating it as an authorised construction release.
Mistake to avoid: Assuming the highest revision letter identifies information suitable for every purpose.
Source: RIBA
48. Coordination includes function and access
Coordination extends beyond geometric clash detection to performance, maintenance access, sequence and consistent requirements. A model can be free of collisions yet contain an unusable system. Combine digital checks with competent review and record resolutions. Verify that changes reach all affected drawings, specifications and schedules.
Worked example: A valve clears adjacent pipework in the model but cannot be reached after a ceiling is installed. Coordination relocates access before the package is issued.
Mistake to avoid: Declaring coordination complete because automated clash detection reports no intersections.
Source: Home - Architects Registration Board; RIBA
49. Site observations have defined limits
A site visit records observations at a particular time within an agreed service. It does not establish that concealed work or every construction activity has been checked. Record locations, evidence, limitations and follow-up responsibilities. Refer matters requiring specialist assessment to competent participants without presenting limited observation as continuous supervision.
Worked example: During a visit, the architect observes one installed window type. The report identifies the sampled location and requests clarification of a visible discrepancy without certifying all windows.
Mistake to avoid: Turning a limited site observation into a blanket assurance about unseen or unexamined work.
Source: Home - Architects Registration Board; RIBA
50. Handover and performance evaluation
Handover requires usable operational information as well as attention to the physical works. Check agreed responsibilities for manuals, training, records and unresolved items. Later performance evaluation compares actual use with the brief. Distinguish observed symptoms from demonstrated causes before recommending improvements or attributing responsibility.
Worked example: Users report overheating after occupation. The team reviews operating settings, occupancy and measured conditions before concluding whether design assumptions or operation explain the problem.
Mistake to avoid: Assigning a cause to poor performance from a user complaint alone.
Source: Home - Architects Registration Board; RIBA
Procurement and construction contract administration
51. Procurement routes allocate responsibilities
Compare procurement routes against design control, programme, cost predictability and the client's management capacity. Traditional arrangements generally separate the client's design team from construction; design-and-build generally places an agreed design and construction scope with the contractor. Actual responsibilities depend on the contracts, including any appointment transfers.
Worked example: A client values direct design control but has limited coordination capacity. The team explains the management responsibilities associated with the proposed route before recommending it.
Mistake to avoid: Choosing a route by name without examining who retains each important responsibility.
Source: RIBA
52. Tender comparison requires equivalent scope
Evaluate tender inclusions, exclusions, qualifications, allowances, programme and relevant capability alongside price. Preserve original offers and make comparison adjustments transparent. Where differences cannot be reliably priced, identify the uncertainty rather than inventing a precise adjustment. A lower headline figure can conceal omitted work or incompatible assumptions.
Worked example: Tender A is £480,000 including joinery; Tender B is £465,000 excluding joinery estimated at £25,000. The adjusted price comparison is £480,000 against £490,000.
Mistake to avoid: Recommending the lowest headline tender before checking whether the offers cover equivalent work.
Source: RIBA
53. Pricing mechanisms determine quantity consequences
A lump-sum mechanism prices an agreed scope, while remeasurement values quantities under agreed rules. Neither eliminates the need for clear information and change administration. Determine which quantities, rates and risks the actual contract allocates to each party. Do not assume a quantity difference always creates the same payment consequence.
Worked example: Under a stated remeasurement arrangement, 140 measured units at £32 each produce £4,480, subject to the agreed measurement and valuation provisions.
Mistake to avoid: Applying a remeasurement calculation to a lump-sum item without checking the contractual basis.
Source: RIBA
54. Contract administration powers and judgement
Authority to instruct, assess or certify derives from the relevant contract and appointment. Identify each power and its required procedure. When the role requires independent or impartial evaluation, assess evidence against the contractual basis rather than adopting the client's preferred outcome. Being the designer does not automatically confer every administrative power.
Worked example: A client requests a lower valuation to gain negotiating leverage. The administrator assesses the eligible work under the contract rather than adjusting the figure to serve that tactic.
Mistake to avoid: Assuming the administrator must adopt the client's commercial preference when making a contractual assessment.
Source: Home - Architects Registration Board; RIBA
55. Clarifications and instructions have different effects
A request for information seeks an answer; a clarification explains existing requirements; an instruction may authorise a change under the contract. Examine substance, authority and procedure rather than relying only on a document title. Resolve contradictions through the applicable process and keep affected information consistent.
Worked example: A response changes a specified finish to a different material. The administrator checks whether a formal instruction is required instead of treating the response as cost-neutral clarification.
Mistake to avoid: Calling a scope change a clarification to avoid assessing its contractual consequences.
Source: RIBA
56. Construction changes affect several control systems
A proposed change can affect design coordination, cost, programme, approvals and future operation. Identify the reason, authority and consequences before implementation where practicable, following the actual contract. Keep estimates distinct from agreed valuations. Track consequential changes rather than recording only the immediately visible item.
Worked example: Relocating a partition also changes lighting, ventilation and finishes. The change assessment includes those interfaces before the authorised instruction is issued.
Mistake to avoid: Pricing the partition alone and overlooking related services, sequencing and approval implications.
Source: Home - Architects Registration Board; RIBA
57. Cumulative valuation and current amounts
A cumulative assessment measures eligible value to date, then applies the contract's relevant adjustments and accounts for previously certified amounts. State simplifying assumptions before calculating. Valuation, certification and actual payment remain distinct events. Treatment of materials, retention and deductions must follow the actual contract.
Worked example: Eligible cumulative value is £200,000. Assuming 5% retention applies to all of it and £150,000 was previously certified, the current amount is £40,000 before other adjustments.
Mistake to avoid: Subtracting previous cash receipts where the calculation instead requires previously certified amounts.
Source: RIBA
58. Payment procedures and notices
Construction payment arrangements can involve applications, assessments, notices and payment obligations with distinct functions. Identify who must act, the relevant calculation basis and the applicable timing under the contract and legal framework. Use a project-specific calendar and appropriate advice; one contract's terminology or deadlines cannot safely be assumed for another.
Worked example: An application arrives. The administrator checks the applicable assessment and notice responsibilities and records the required actions rather than merely forwarding it to accounts.
Mistake to avoid: Assuming a payment application, certificate and required notice are always interchangeable documents.
Source: RIBA
59. Delay analysis and financial entitlement
Time entitlement and financial entitlement are separate assessments. Establish the event, programme effect, causation, relevant contractual provisions and supporting records. A delay may affect critical completion without automatically establishing additional payment. Conversely, disruption can have consequences that are not captured by counting calendar days alone.
Worked example: A late decision interrupts critical work. The administrator examines completion impact separately from the contractor's claimed costs and checks the basis for each.
Mistake to avoid: Assuming every extension of time automatically carries the same entitlement to additional money.
Source: RIBA
60. Completion and defects require separate judgements
Completion depends on the actual contractual definition and condition of the works. Distinguish incomplete work, defects, handover information and later maintenance responsibilities. Identify who makes each assessment and what evidence is needed. Occupation, a contractor's declaration and contractual completion may have different significance.
Worked example: A client starts using a building while required commissioning records remain unresolved. The administrator assesses completion against the contract rather than treating occupation as conclusive.
Mistake to avoid: Assuming the client's occupation automatically settles completion and all outstanding obligations.
Source: Home - Architects Registration Board; RIBA
Sources
Source context:
Browse all study guides