Guide · Architecture governance

The architecture exception and waiver process

Sometimes a project genuinely can't follow a standard. The question is whether that deviation is visible and time-boxed — or quietly becomes permanent technical debt. That's what an exception process is for.

Why you need one

Standards without a way to deviate get ignored under delivery pressure. A formal exception process lets teams deviate when justified — openly, with a record — instead of doing it silently.

How it works

• Request — the team documents the deviation, the reason, and the risk.
• Assess — the Design Authority weighs the justification and impact.
• Decide — grant, grant with conditions, or reject.
• Time-box — every waiver has an expiry and a remediation plan.
• Track — all live exceptions sit in a register that's reviewed regularly.

Time-box everything

A waiver with no expiry is just permanent debt with paperwork. Every exception should have a date by which the deviation is resolved or re-justified.

Review the register

The exception register is one of the most honest signals of architectural health. A growing pile of ageing waivers is an early warning; bring it to every Design Authority.