Use these 60 concepts to connect architectural principles with practical decisions about design, clients and project delivery. Start with professional responsibilities and regulatory distinctions, then apply them to technical design, practice management and contracts. Each concept includes a worked example and a specific error to avoid. Professional standards provide context; the technical and commercial examples illustrate general principles whose application depends on the project.
Professional conduct and ethical judgement
1. Qualification, membership and registration
An academic qualification, membership of a professional organisation and regulatory registration establish different facts. None should be presented as interchangeable. ARB identifies its Register as the definitive record of UK architects. Describe your own status accurately and verify another person's registration through the relevant record before relying on a professional title.
Worked example: A graduate holds an architecture qualification and belongs to a professional organisation. Neither fact establishes ARB registration; a separate Register check is needed.
Mistake to avoid: Treating a Part 2 qualification as proof of registered architect status.
Context reference: Home - Architects Registration Board
2. Standards and supporting behaviours
ARB's Architects Code has six standards covering honesty, public interest, competence, professional practice, communication and respect. These standards must be met; supporting behaviours illustrate ways to meet them. An alternative approach requires an accountable explanation. The 2025 Code replaced the 2017 edition, while historical events may require their contemporaneous context.
Worked example: A practice uses a different communication procedure from an illustrative example. It explains how that procedure still delivers clear, timely and accountable communication.
Mistake to avoid: Assuming every illustrative behaviour is a separate mandatory rule.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
3. Facts, assumptions and professional honesty
Separate what is known from what is assumed and what remains unresolved. A polished drawing does not strengthen weak underlying evidence. Material uncertainty should be visible to anyone relying on the information. When an assumption changes, identify the affected decisions and correct the record rather than silently replacing the previous conclusion.
Worked example: An existing wall thickness is estimated from photographs. The designer labels it provisional and postpones a dependent junction decision until a suitable survey confirms it.
Mistake to avoid: Presenting an estimated dimension as a surveyed measurement.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
4. Public interest beyond the client brief
Architectural decisions affect occupants, neighbours, maintainers and future users as well as the paying client. Consider foreseeable consequences for these groups when comparing options. Explain material concerns and use appropriate escalation where they remain unresolved. Client approval is a project decision, not evidence that wider professional responsibilities have been satisfied.
Worked example: A client prefers a blank service frontage. The designer identifies its effect on pedestrian visibility and develops a screened alternative that preserves sightlines.
Mistake to avoid: Using client preference as the sole justification for a consequential decision.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
5. Task-specific competence and supervision
Competence depends on the task, its complexity and the support available. General design experience does not establish expertise in every technical system. Allocate work to suitable people, define review responsibilities and seek specialist input where necessary. Delegation should transfer a task clearly while preserving appropriate oversight and coordination.
Worked example: A junior designer develops a façade layout. A competent specialist reviews movement and moisture interfaces before the coordinated information is issued.
Mistake to avoid: Assuming an experienced designer can independently resolve every specialist interface.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
6. Conflicts of interest and impartial judgement
A conflict can arise from financial, personal or organisational interests that influence, or appear to influence, a recommendation. Identify the connection before making the decision. Disclosure starts the assessment; it does not automatically resolve the problem. Consider whether independent review, reassignment or declining the role is needed to protect judgement.
Worked example: A designer's sibling supplies cladding. The connection is disclosed, and an independent colleague conducts the comparison without the designer influencing the recommendation.
Mistake to avoid: Assuming disclosure alone makes any conflicted recommendation acceptable.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
7. Confidentiality and purposeful disclosure
Share project information for a defined purpose with appropriate recipients. Permission to use information within a commission does not establish permission to publish it. Where disclosure duties or restrictions are uncertain, obtain suitable advice. Any justified disclosure should be limited to relevant information rather than the entire project record.
Worked example: A consultant needs room dimensions for an assessment. The practice shares the relevant drawings without including unrelated client financial correspondence.
Mistake to avoid: Sending the complete project folder because some information is relevant.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
8. Respectful and inclusive participation
Respect includes enabling people to contribute meaningfully, not merely inviting them to a meeting. Consider communication formats, access needs and power differences. Gather varied perspectives without asking one participant to represent an entire group. Record how feedback affects decisions so consultation becomes useful evidence rather than a ceremonial exercise.
Worked example: A consultation offers spoken discussion and written responses. A participant's written account reveals an access problem that the meeting discussion missed.
Mistake to avoid: Equating attendance with an equal opportunity to influence the design.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
UK regulatory and legal distinctions
9. Establishing the applicable UK jurisdiction
Identify the project's UK nation before selecting planning or building-control guidance. Procedures, terminology and requirements are not uniform across the United Kingdom. Establish the relevant authority and applicable current documents for the actual work. Familiar guidance from another nation can inform questions, but cannot demonstrate local compliance.
Worked example: A team transfers a project checklist from England to Scotland. It reviews the checklist against the Scottish project's applicable procedures before using it.
Mistake to avoid: Treating a UK-wide project location as sufficient regulatory identification.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
10. Planning permission and building compliance
Planning generally considers development in its setting, while building regulations address specified aspects of building performance and construction. These assessments answer different questions. Coordinate both within the design, but do not treat an outcome under one process as approval under the other. Identify any additional consent processes relevant to the proposal.
Worked example: A proposed extension receives planning permission. The team continues resolving its building-performance requirements rather than treating permission as technical approval.
Mistake to avoid: Assuming planning permission confirms the construction details are compliant.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
11. Approval conditions and project dependencies
An approval can contain conditions that require information, agreement or action at a particular stage. Read the decision with its associated documents and translate conditions into tracked tasks. Assign responsibility and identify dependent activities. Whether work may proceed depends on the actual wording and applicable procedure, not the existence of an approval alone.
Worked example: A decision requires agreement of an external material before its installation. The team records that dependency and obtains the required agreement before that activity.
Mistake to avoid: Recording an approval as complete while leaving its conditions unmanaged.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
12. Public approvals and private land rights
A public approval and the right to use land are separate matters. Boundaries, access rights and other private interests can affect a design even when development is acceptable to an authority. Flag uncertainties for competent legal investigation. Avoid turning incomplete ownership information into a definitive statement about what the client may build.
Worked example: An approved access proposal crosses neighbouring land. The team treats permission to use that land as a separate unresolved matter requiring legal confirmation.
Mistake to avoid: Assuming an authority's approval grants rights over another person's property.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
13. Heritage significance before intervention
A building's heritage significance concerns why particular fabric, spaces or relationships matter. Establish relevant designations and investigate significance before selecting interventions. Consent requirements depend on the jurisdiction and proposed work. Specialist advice can identify where adaptation is compatible with significance and where an apparently minor change may have substantial consequences.
Worked example: Before proposing replacement windows, a team investigates whether their materials and proportions contribute to the building's significance and reviews alternatives with a conservation specialist.
Mistake to avoid: Judging heritage impact solely by the physical size of the alteration.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
14. Contractual services and statutory roles
An appointment defines agreed services, while applicable legislation may establish separate roles and duties. Similar role titles do not prove identical responsibilities. Identify the relevant framework, actual appointments and interfaces. A contractual exclusion should not be assumed to remove an applicable legal duty; obtain appropriate advice where responsibilities are unclear.
Worked example: An appointment excludes a specialist assessment. The team identifies who will provide it and separately checks whether the architect retains any applicable coordination responsibilities.
Mistake to avoid: Assuming an excluded service automatically eliminates every related responsibility.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
15. Copyright ownership and permitted use
Possessing a drawing or model does not establish ownership of its copyright or unrestricted permission to reuse it. Distinguish authorship, ownership and any licence in the relevant agreement. Check the permitted purpose, project and recipients before reuse. Where rights are disputed, seek advice rather than treating file access as authorisation.
Worked example: A client receives drawings for one site and requests their reuse elsewhere. The practice checks the agreed licence before authorising the second use.
Mistake to avoid: Treating payment for services as automatic permission for unlimited reuse.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
16. Traceable compliance decisions
A useful compliance record identifies the requirement considered, evidence examined, decision made and outstanding limitations. Link it to the relevant document revision. Later design changes may invalidate earlier conclusions, so assess their effect explicitly. Consultation should be recorded accurately without presenting a limited comment as unrestricted approval.
Worked example: A review accepts a particular door arrangement. When the layout changes, the team reopens that assessment instead of carrying its earlier conclusion into the revised drawing.
Mistake to avoid: Retaining a compliance conclusion after changing the information it assessed.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
Design, sustainability and building technology
17. Spatial requirements and measurable briefs
Translate activities into spatial requirements before fixing a layout. Distinguish net usable space from circulation, servicing and other allowances, and state the area convention used. Evaluate relationships as well as totals: a building can contain enough area yet function poorly because essential activities are disconnected or competing uses overlap.
Worked example: Four rooms require 25 square metres each, giving 100 square metres of room area. Circulation and support space must be assessed separately.
Mistake to avoid: Presenting the sum of room areas as the complete building area.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
18. Site evidence and investigation limits
Match site information to the decision it must support. Check coverage, date, method and limitations rather than relying on visual detail alone. Missing evidence should become an explicit investigation need or provisional assumption. Assign responsibility for resolving it before dependent design choices become difficult to change.
Worked example: A topographical survey covers the boundary but omits an adjacent retaining structure. The team requests further information before fixing the proposed building's relationship to it.
Mistake to avoid: Assuming a detailed survey includes every feature relevant to the design.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
19. Context, scale and urban relationships
Context analysis should explain relationships between a proposal and surrounding spaces, movement patterns, building forms and uses. Matching one dimension does not establish compatibility. Compare alternative massing arrangements using consistent views and criteria. Distinguish observed characteristics from subjective preferences so the design response has an understandable basis.
Worked example: Two options share the same height. The narrower option preserves a visible gap between buildings, so it better meets the brief's identified townscape objective.
Mistake to avoid: Using height alone as a complete measure of contextual fit.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
20. Orientation, daylight and solar gain
Daylight availability, direct sunlight and solar heat gain are related but different design considerations. Orientation, obstruction, glazing and shading affect them differently. Assess the intended use and relevant climate rather than assuming more glazing always improves performance. Decisions should consider visual comfort and seasonal overheating as well as useful light.
Worked example: A west-facing workspace has evening glare. The team compares shading and glazing options instead of increasing window area to pursue daylight alone.
Mistake to avoid: Treating daylight improvement and reduced overheating as automatically aligned.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
21. Thermal resistance and U-value
For a simplified planar construction, thermal resistances in series are added, and U-value is the reciprocal of total resistance. A lower U-value indicates lower steady-state heat transfer per unit area and temperature difference. Actual assessments must include appropriate surface resistances, construction details and limitations of the chosen method.
Worked example: If the complete assumed resistance is 4.0 square metre kelvins per watt, U equals 1 divided by 4.0, or 0.25 watts per square metre kelvin.
Mistake to avoid: Adding individual layer U-values instead of adding their thermal resistances.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
22. Thermal bridges at construction junctions
A thermal bridge is a local path of increased heat transfer caused by geometry or material continuity. Good performance across an insulated wall does not establish good performance at its junctions. Review connections, penetrations and changes of construction with suitable assessment. Junction temperatures can also affect local moisture conditions.
Worked example: A continuous metal element crosses an insulated envelope. The team flags the junction for specialist assessment rather than relying only on the wall's planar U-value.
Mistake to avoid: Assuming thick insulation eliminates every junction-related heat-loss path.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
23. Steady-state fabric heat transfer
A simplified fabric heat-transfer calculation uses heat flow equals U-value multiplied by area and temperature difference. It estimates one component under stated conditions, not total building demand. Ventilation, other surfaces, solar gains and time-dependent effects require separate consideration. Keep units explicit so the result is interpreted as power rather than energy.
Worked example: For U = 0.30, area = 40 square metres and temperature difference = 20 kelvins, estimated heat flow is 240 watts.
Mistake to avoid: Calling a result in watts an annual energy consumption figure.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
24. Moisture sources and condensation risk
Moisture can enter construction through rain, leaks, ground sources, construction processes or indoor humidity. Condensation occurs when conditions allow water vapour to become liquid. Similar staining can therefore have different causes. Diagnose the source and relevant physical conditions before selecting an intervention; appearance alone cannot establish the mechanism.
Worked example: A damp patch appears after rainfall beside a damaged junction. The team investigates water entry rather than prescribing a condensation remedy from appearance alone.
Mistake to avoid: Assuming every damp internal surface is caused by condensation.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
25. Ventilation and uncontrolled infiltration
Ventilation provides an intended means of air exchange; infiltration is uncontrolled leakage through the envelope. Improving airtightness does not remove the need for suitable ventilation. Assess indoor air quality, moisture and thermal performance together. A design should identify how air exchange is provided rather than relying on accidental gaps.
Worked example: A refurbishment reduces uncontrolled leakage. The team reviews the ventilation strategy because the former leakage cannot be treated as a dependable air supply.
Mistake to avoid: Equating an airtight building with a building that needs no ventilation.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
26. Embodied and operational environmental impacts
Embodied impacts arise from materials and construction-related processes; operational impacts arise from building use. Comparing alternatives requires consistent boundaries, periods and assumptions. A low-impact material may not compensate for poor operational performance, while replacement can create additional embodied impact. State uncertainties rather than combining unlike figures into an apparent total.
Worked example: Two façade options are compared over the same assumed period, including initial production, anticipated replacement and modelled operational effects, rather than production alone.
Mistake to avoid: Comparing one option's lifecycle total with another's manufacturing impact only.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
27. Service life and replacement cycles
Durability affects resource use, maintenance and lifecycle cost. Compare alternatives over a common study period and specify how replacements are counted. Service-life estimates depend on exposure, detailing, maintenance and use. Treat an assumed replacement cycle as a scenario to test, not a guarantee that the component will fail on a fixed date.
Worked example: Over 30 years, a component assumed to last 10 years is installed initially and replaced at years 10 and 20: three installations.
Mistake to avoid: Counting a replacement at the study period's endpoint when no subsequent use is assessed.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
28. Structural load paths and specialist boundaries
A load path describes how forces pass through connected elements to supporting construction and the ground. Architectural changes can alter that path even when individual elements remain visible. Identify affected interfaces and obtain competent structural assessment. Recognising a potential structural consequence is different from having authority or expertise to approve its resolution.
Worked example: A proposed opening interrupts a wall supporting construction above. The designer refers the changed load path for structural assessment before finalising the proposal.
Mistake to avoid: Assuming a retained wall remains structurally equivalent after an opening is added.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
29. Sound insulation and room reverberation
Sound insulation limits transmission between spaces; absorption affects reflected sound within a space. They address different problems. Soft finishes may reduce reverberation without adequately controlling sound passing through a separating construction. Diagnose whether the concern involves transmission, internal reflections or both before selecting a design response.
Worked example: Acoustic panels improve speech clarity in a meeting room, but conversations remain audible next door. The separating construction needs a separate transmission assessment.
Mistake to avoid: Treating absorptive finishes as proof of adequate sound insulation.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
30. Inclusive access as a continuous journey
Access should be evaluated across the complete journey: approach, entrance, circulation, destination and use. A single accessible feature cannot compensate for a disconnected route. Consider different mobility, sensory and cognitive needs, and obtain appropriate user input. Applicable requirements still need checking for the project's jurisdiction and circumstances.
Worked example: An entrance is accessible, but the intended meeting room is reached only by stairs. The team revises the route or room location to provide continuity.
Mistake to avoid: Assessing the entrance in isolation from the spaces it serves.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
Architectural practice management
31. Workload forecasting by time and skill
Translate commissions into required hours for each period and skill category. Compare that demand with genuinely available capacity, allowing for supervision and other commitments. Annual totals can conceal short-term bottlenecks. Update the forecast when scope or programme changes rather than assuming the original staffing plan remains achievable.
Worked example: Two projects each need 60 review hours next week. With only 80 suitable hours available, the practice must resolve a 40-hour capacity gap.
Mistake to avoid: Using spare hours from unsuitable staff to conceal a specialist shortage.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
32. Fee basis and allocation of uncertainty
A fixed fee prices an agreed service scope; a time charge depends on recorded time and agreed rates; a percentage fee requires a defined cost basis. Each allocates uncertainty differently. State assumptions, exclusions and adjustment procedures. A charging method cannot compensate for an appointment that leaves the service boundaries unclear.
Worked example: A fixed fee includes one agreed design revision. A request for three further alternatives is assessed through the appointment's additional-service procedure.
Mistake to avoid: Assuming a fixed fee covers unlimited changes to an undefined service.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
33. Break-even cost and fee margin
A simplified project break-even figure adds labour cost, allocated overhead and other project costs. It excludes profit unless profit is explicitly added. Distinguish margin, calculated against fee income, from markup, calculated against cost. State allocation assumptions so the calculation supports a management decision rather than implying a universal pricing rule.
Worked example: Costs of £8,000 and a fee of £10,000 produce £2,000 profit: a 20% margin and a 25% markup.
Mistake to avoid: Calling a 25% markup on cost a 25% profit margin.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
34. Profit and cash availability
Profit measures income and costs under the relevant accounting basis; cash measures receipts and payments. A profitable commission can create a cash shortage when payment arrives after expenditure. Review performance and liquidity separately. Neither an issued invoice nor an expected commission should be treated as money already available to pay immediate obligations.
Worked example: A project shows £3,000 profit, but its £12,000 invoice remains unpaid. The practice still needs cash for salaries due this week.
Mistake to avoid: Using reported profit as evidence that immediate payments can be funded.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
35. Cash-flow forecasts and timing scenarios
Calculate closing cash from opening cash plus expected receipts minus expected payments. Place amounts in the periods when money is expected to move, not when work occurs. Test uncertain receipt dates separately. A forecast becomes more useful when it exposes the consequence of delayed collection rather than assuming every invoice is paid promptly.
Worked example: Opening cash of £9,000 plus £5,000 receipts minus £11,000 payments gives £3,000 closing cash. Delayed receipts would instead produce a £2,000 shortfall.
Mistake to avoid: Forecasting invoice issue dates as though they were payment dates.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
36. Quality checks and corrective action
Quality controls make consequential reviews repeatable and traceable. After an error, distinguish correcting the affected output from addressing the process that allowed it. Investigate the cause, introduce a proportionate response and check whether it works. A completed checklist provides evidence of an action, not automatic evidence that the information is correct.
Worked example: A schedule error is corrected, then its cause is traced to an unsynchronised template. The template and review process are updated to prevent recurrence.
Mistake to avoid: Repairing the document while leaving the recurring source of error intact.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
37. Document revision and issue status
Revision identifies a document's sequence of changes; issue status identifies its intended use. Both matter because a recent draft may be less suitable for reliance than an earlier authorised issue. Use controlled records to identify recipients and superseded information. Keep models, drawings and schedules aligned rather than assuming one updated file updates everything.
Worked example: A new coordination draft is circulated for review. It is clearly distinguished from the construction issue so recipients do not build from unresolved information.
Mistake to avoid: Assuming the newest revision is automatically authorised for construction.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
38. Continuity and recoverable project records
Continuity planning identifies essential services, critical records and authorised cover during disruption. A backup is useful only if it can be restored and understood. Test recovery, preserve appropriate access controls and document responsibilities. Avoid dependence on one person's memory, private account or undocumented filing conventions for essential project information.
Worked example: During a project lead's absence, an authorised colleague restores the current issue register and identifies outstanding decisions from the shared records.
Mistake to avoid: Treating an untested backup as proof that work can resume.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
Professional services and client relationships
39. Service scope, deliverables and interfaces
An appointment should distinguish activities from deliverables and explain what each output is intended to support. Identify exclusions, dependencies and responsibility for coordination. A missing service remains a project need even when excluded from one appointment. Check that the client understands how that need will be met by another participant.
Worked example: The architect excludes a measured survey but needs reliable dimensions. The appointment identifies client provision of a suitable survey before dependent design work.
Mistake to avoid: Excluding a task without identifying how its essential output will be obtained.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
40. Client authority and conflicting directions
Identify who may approve scope, budget and design on the client's behalf. Consultation feedback and formal instructions have different functions. Where several representatives participate, establish a decision route and escalation process. Conflicting directions should be resolved through that route before consequential work proceeds, with the agreed decision recorded.
Worked example: A facilities manager requests a layout change that conflicts with the project sponsor's brief. The architect obtains a decision from the agreed authorised representative.
Mistake to avoid: Treating every stakeholder comment as an authorised client instruction.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
41. Option appraisal against consistent criteria
Compare options against criteria derived from the brief, such as function, cost, environmental impact and adaptability. Keep boundaries and assumptions consistent. Where criteria conflict, explain the trade-off rather than hiding it in an unexplained overall score. Identify which judgement belongs to the client and what professional advice supports it.
Worked example: Option A costs less initially; option B permits easier future subdivision. The client selects B because adaptability is an agreed priority, accepting the stated cost difference.
Mistake to avoid: Changing evaluation criteria to make a preferred option appear strongest.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
42. Forecasts, ranges and confidence
A forecast estimates a future outcome using current information; it is not automatically a commitment. Explain the assumptions driving uncertainty and distinguish known amounts from allowances. Use ranges where they communicate uncertainty meaningfully. Update the forecast when evidence changes and identify the decisions that could reduce or increase the uncertainty.
Worked example: An early estimate ranges from £180,000 to £220,000 because existing-condition work is unresolved. Investigation narrows that uncertainty before the client commits to an option.
Mistake to avoid: Presenting the midpoint of a range as a guaranteed final cost.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
43. Progress reports that support decisions
A useful progress report distinguishes completed work, unresolved matters and decisions required. State consequences and relevant timing so the client can act. Tailor technical detail to the decision rather than listing activity without interpretation. Communicate material emerging problems early enough for alternatives to remain available.
Worked example: The report states that the plan is coordinated but the façade choice remains open, and explains that a decision is needed before supplier information can be completed.
Mistake to avoid: Reporting a percentage complete without explaining what prevents the next step.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
44. Changes to professional services
A change to the building and a change to the architect's service are separate questions. Assess whether a request adds redesign, meetings, coordination or other work beyond the appointment. Explain the service, fee and programme consequences through the agreed procedure. Do not assume construction authorisation also authorises additional professional charges.
Worked example: Replacing a finish causes little construction change but requires several new visual studies. The architect agrees that additional design service before undertaking it.
Mistake to avoid: Using the value of building work as the sole measure of additional service effort.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
45. Complaints, facts and service recovery
A complaint requires assessment; it is neither automatic proof of fault nor something to dismiss defensively. Establish the concern, relevant facts and desired resolution. Follow the practice's process and explain next steps. Keep corrective action distinct from disputed liability, and obtain appropriate advice where the matter may involve a claim.
Worked example: A client complains about an unexplained revision. The practice reviews the correspondence, clarifies the reason and improves reporting while separately assessing the disputed fee.
Mistake to avoid: Assuming that resolving a communication problem also resolves every liability question.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
46. Transparent invoices and charging records
Connect each invoiced amount to the agreed charging basis and relevant work. Distinguish fees, agreed expenses and any applicable taxes. Time charges require reliable records and agreed rates; staged fees require the agreed milestone basis. Show prior billing where needed so the client can reconcile the cumulative amount.
Worked example: Twelve hours at £75 produce a £900 fee before any applicable taxes or separately agreed expenses. The invoice identifies the work and charging period.
Mistake to avoid: Combining unrelated charges into a single unexplained professional fee.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
47. Meetings, decisions and action ownership
Meeting records should separate discussion, decisions, actions and unresolved questions. Give actions an owner and relevant timing, and provide an agreed route for corrections. Minutes do not automatically function as contractual instructions. Where formal authorisation is required, identify the separate document or procedure that provides it.
Worked example: Minutes record a proposed entrance change as unresolved and assign the client an approval action. The team waits for the required authorisation before implementing it.
Mistake to avoid: Turning a recorded suggestion into an instruction merely by circulating minutes.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
48. Ending services and controlled handover
When services finish, pause or end early, follow the appointment's relevant procedures and obtain advice where needed. Identify outstanding work, document status, permissions and continuity responsibilities. Distinguish completed information from unresolved drafts. A clear handover helps the receiving party assess what can be relied upon and what still requires investigation.
Worked example: A departing practice lists issued drawings separately from incomplete details and identifies unresolved consultant interfaces, preventing the successor from treating every file as finished.
Mistake to avoid: Handing over files without explaining their status and limitations.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
Procurement and construction contracts
49. Procurement priorities and retained responsibilities
Procurement organises design, construction and commercial responsibilities. Compare routes against project priorities, including timing, design control and cost predictability. No route removes all uncertainty. Identify what remains with the client and whether the team can manage it. Recommendations should explain their assumptions rather than describe one route as universally best.
Worked example: A client prioritises early specialist input. The team compares routes that permit it and explains the resulting implications for design control and remaining client decisions.
Mistake to avoid: Selecting a route from its label without mapping actual responsibilities.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
50. Traditional and design-and-build responsibilities
In a conventional traditional arrangement, the client's designers develop the design and a contractor constructs the work. Design-and-build generally places an agreed design and construction scope with the contractor. Actual allocation depends on the documents and any appointment transfers. Trace each design package rather than assuming a route label settles every interface.
Worked example: A design-and-build contractor takes responsibility for a defined envelope package, while a client-appointed specialist retains another package. The interface is explicitly allocated.
Mistake to avoid: Assuming design-and-build transfers every design responsibility without checking the agreements.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
51. Tender comparison on equivalent scope
Headline tender prices are comparable only when their scope and assumptions are understood. Review exclusions, allowances, qualifications and programme alongside price. Record any comparison adjustments transparently while preserving the original offer. Where a qualification cannot be reliably priced, explain that uncertainty instead of manufacturing an apparently exact adjusted total.
Worked example: Tender A is £420,000 but excludes a comparable £25,000 item. Its adjusted comparison is £445,000, exceeding an inclusive £438,000 Tender B.
Mistake to avoid: Recommending the lowest headline price without examining excluded work.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
52. Pricing mechanisms and quantity changes
A lump-sum arrangement prices an agreed scope; remeasurement values actual quantities under agreed rules. These mechanisms respond differently to quantity differences. Neither removes the need to define work or administer changes. Examine the actual contract before deciding whether a changed quantity affects payment, and keep measurement evidence traceable.
Worked example: Under an assumed remeasurement rate of £40 per square metre, 125 measured square metres produce £5,000. That result cannot automatically be applied to a lump-sum arrangement.
Mistake to avoid: Assuming every quantity increase creates payment at a schedule rate.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
53. Contract documents and inconsistent information
Drawings, specifications, schedules and conditions must be read together. Where they conflict, identify the discrepancy and follow the contract's clarification or interpretation process. There is no universal hierarchy that can safely be assumed. Record the resolution and update affected documents so different participants do not continue relying on incompatible descriptions.
Worked example: A drawing shows timber doors while the schedule lists metal. The discrepancy is formally clarified and both documents are aligned before procurement proceeds.
Mistake to avoid: Assuming drawings always override specifications without checking the contract.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
54. Contract administration authority and judgement
Powers to instruct, assess or certify come from the relevant contract and appointment. Attendance at meetings or authorship of the design does not create those powers. Establish the required procedure and decision basis. Evaluative functions should use contractual criteria and relevant evidence rather than simply reproducing either party's preferred commercial position.
Worked example: A consultant identifies a valuation issue but lacks certification authority. It provides evidence to the appointed decision-maker rather than issuing a certificate itself.
Mistake to avoid: Confusing technical involvement with contractual authority to decide.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
55. Construction changes and formal authorisation
A proposed construction change needs a clear scope, reason, authorisation route and assessment of consequences. Distinguish clarification of existing requirements from an instruction that changes them. Follow the contract's procedure and track unresolved cost or time effects. Informal discussion should not be allowed to obscure whether work was actually authorised.
Worked example: A contractor proposes moving a partition. The team records the proposal and obtains the required instruction before treating the revised location as authorised work.
Mistake to avoid: Treating agreement to investigate an option as approval to construct it.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
56. Cumulative valuation and previous certificates
A cumulative valuation assesses eligible value to date, then accounts for amounts previously certified and any applicable adjustments. Valuation, certification and payment are distinct events. The treatment of materials, deductions and retention depends on the contract. State simplifying assumptions before calculating so the example does not imply a universal payment formula.
Worked example: Assuming no other adjustments, £96,000 eligible cumulative value less £71,000 previously certified leaves £25,000 for the current certificate.
Mistake to avoid: Certifying the full cumulative value again instead of deducting previous certificates.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
57. Time entitlement and financial entitlement
An event's effect on completion time and its financial consequences require separate assessments. Examine causation, programme impact and the relevant provisions for each. A time adjustment does not automatically establish additional payment. Follow the actual contract's notice and evidence requirements rather than assuming universal deadlines or remedies.
Worked example: A delayed decision affects critical work. The administrator assesses its time consequences separately from whether the contract supports the contractor's claimed additional costs.
Mistake to avoid: Assuming an extension of time automatically proves entitlement to compensation.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
58. Dependencies, critical paths and float
A programme's earliest completion depends on activity durations and relationships. Under stated assumptions, the longest dependent path controls completion; shorter paths may have float. Resource limits and changed dependencies can alter that conclusion. Diagnose the affected path before claiming that any delayed activity necessarily delays the whole project.
Worked example: Parallel paths last 12 and 9 days. With no other constraints, the shorter path has 3 days of float before it affects the 12-day completion.
Mistake to avoid: Adding parallel activity durations as though the activities occur sequentially.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
59. Completion, occupation and defects
Completion must be assessed against the contract's definition and relevant evidence. Distinguish incomplete work, defects and subsequent maintenance. Client occupation may be significant but does not by itself answer every completion question. Identify who makes the assessment and how outstanding items are recorded under the applicable project arrangements.
Worked example: A client starts using part of a building while specified work remains unfinished. The administrator assesses contractual completion separately from the fact of occupation.
Mistake to avoid: Treating occupation as automatic proof that all contractual completion criteria are met.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
60. Disagreement records and proportionate resolution
When a contractual disagreement arises, separate agreed facts, disputed interpretations and requested outcomes. Preserve relevant records and identify the contract's applicable resolution route. Early clarification may resolve an information gap, while other matters need appropriate professional advice. Avoid promising a legal result from incomplete correspondence or treating every disagreement as evidence of misconduct.
Worked example: A disputed change is reconstructed from the instruction, revised drawing and valuation record. The parties agree its scope before addressing the remaining price disagreement.
Mistake to avoid: Arguing about the amount before establishing what work was authorised.
Context reference: Architects Code: Standards of Conduct and Practice - ARB
Source references
Professional standards checked:
All study guides