A brand guide cannot anticipate every partner banner, event booth, mobile screen, local-language layout, or urgent sales document. If every unusual use waits for the founder, production stalls. If every team improvises, the system gradually becomes several identities. The answer is to document who can decide what, with examples of the exceptions that need review.
The GOV.UK brand guidelines explicitly address extending a brand into new contexts and channels while allowing appropriate flexibility for audience, content, and context. GOV.UK's rules are not ARCHV's rules; the useful principle is that flexibility should be described, rather than left to guesswork.
Sort requests by their effect on the system
Use three levels. Routine adaptation follows a documented rule, such as choosing the approved light logo for a dark background or using a supported layout grid. The responsible team can proceed and save an example. Temporary exception is a one-off constraint, such as a sponsor's narrow banner or a venue's production limit. A named brand owner approves it with an expiry or campaign end date. System change proposes a new recurring component, channel pattern, or logo relationship. It needs evidence of repeated use, review by the system owner, and an update to shared guidance.
This structure adapts a published design-system practice, not an experimentally proven brand performance rule. The GOV.UK Design System contribution criteria ask whether a new pattern is useful and unique before it is developed, then whether it is usable, consistent, and versatile before publication. Its lifecycle guidance also distinguishes patterns still being tried from stable ones. A brand team can borrow that discipline without copying its government-specific requirements.
Make an exception request answerable in one screen
An exception form needs only seven fields: placement and deadline; audience; current guideline that fails; constraint or evidence; proposed version; reviewer; and whether the use will recur. Attach an image at actual size, not just a full-resolution mockup. The reviewer can approve, request a change, or escalate to a system change. Give a response deadline that matches the production calendar.
For example, a partner may insist its logo appear above yours in an event poster. The event team should not invent a new permanent co-branding rule from that one poster. It should show the contractual placement constraint, preview the hierarchy, seek the named approver's decision, and record the approved event-only file. For the broader relationship question, use the co-branding hierarchy guide.
Keep the register useful, not ceremonial
Store the approved image, decision, owner, and expiry in a searchable register. Review recurring exceptions monthly or at the next guideline update. If the same problem appears across three channels, investigate whether the guide lacks a needed pattern. If an exception is never repeated, archive it instead of turning it into a confusing new rule. The threshold is a management choice, not a universal benchmark.
Give template users the approved patterns and a clear path for asking questions. The editable template guide covers what non-designers need in the files; this workflow covers who may authorize a departure from them. A live brand system needs both.