Quality management for a design practice — ISO 9001

ISO 9001 starts with context, not procedures.

• Identify interested parties and their requirements (§4.2) — clients, planning authorities, insurers, staff
• Scope the QMS to the services the practice actually sells (§4.3)
• Publish a quality policy leadership signs and staff can quote (§5.2)

Objectives must be measurable or they are slogans.

• Derive objectives from the policy and client feedback (§6.2)
• Risk-assess the delivery pipeline: fee pressure, novel typologies, software change (§6.1)
• Plan changes to the QMS deliberately, never by drift (§6.3)

Competence is demonstrated, not asserted (§7.2) — keep evidence per role, not per person.

• Map required competences to the practice's role profiles
• Control documented information: templates, standards, project records (§7.5)
• Keep design tools and environments calibrated to project requirements (§7.1.3)

§8.3 is the clause a design practice lives in.

• Plan design stages with explicit review, verification and validation gates (§8.3.2)
• Hold design inputs complete before production: briefs, surveys, statutory constraints (§8.3.3)
• Control design changes with impact review — fee, programme, compliance (§8.3.6)

Evaluation closes the gap between the QMS on paper and the practice in fact.

• Track client satisfaction with evidence beyond repeat business (§9.1.2)
• Run internal audits on the processes that earn fees, not just the easy ones (§9.2)
• Hold management review on a fixed cadence with decided actions (§9.3)

A defect repeated is a system choice.

• Record nonconformities from project reviews, client complaints and audits (§10.2)
• Fix the cause, not just the instance — then check the fix held
• Feed improvement back into objectives and training (§10.3)