How to brief a digital partner when compliance is part of the job

Start with the business change

Describe what should be different after the work: a clearer offer, more appropriate enquiries, a shorter intake process, a maintainable content system or less manual handling. Avoid turning the current tool into the requirement unless keeping it is genuinely important.

Name the audience and the decision they are trying to make. A broad label such as ‘patients’ or ‘customers’ is rarely enough; context, readiness and eligibility can change the message and the correct next step.

Bring the regulatory context into the room early

List the frameworks, licences, internal policies and approval owners that may apply. Share previous advice and approved wording where it remains current. If the applicability of a rule is uncertain, mark it as a question rather than silently turning it into a design constraint.

The partner should know who can make the final call, how long review normally takes and whether external advice is required. Approval time is part of delivery time.

Separate evidence from assets

A folder of old brochures is not a source of truth. Provide current product information, service boundaries, approved claims, mandatory statements, brand material and analytics separately. Note which items are authoritative and which are merely reference.

Good partners will ask what can be proven, what must remain flexible and where a customer could misunderstand the overall impression. These questions are part of strategy, not a delay before design.

• Business outcome and success measure
• Priority audiences and desired next actions
• Current regulatory and approval context
• Authoritative evidence and mandatory information
• Known systems, owners and technical constraints
• Decision-maker, reviewers and realistic feedback windows

Evaluate the partner’s operating model

Ask how strategy, copy, design, engineering and review connect. A compliance-aware portfolio is useful, but the daily workflow matters more: who writes, who checks evidence, how decisions are recorded and what happens when advice changes the creative direction.

Look for a willingness to narrow the brief. A partner who recommends a smaller site, a manual test or a discovery phase may be protecting the project from expensive certainty theatre.

Treat the brief as a decision record

A strong brief changes when the team learns something material. Keep the outcome stable, record decisions and make trade-offs explicit. This gives the project enough structure to move without pretending the first document is infallible.

The brief is ready when the team understands the next decision, who will make it and what evidence they need—not when every possible question has been answered.