MUTUAL UNDERSTANDING / 01
A preliminary brief for design, websites and digital services. Its purpose is to make the scope, responsibilities, costs and uncertainties visible before either party commits.
The shared brief — hover or focus a section for its explanation
What are we trying to achieve, for whom, and why now?
The client explains the need, intended users and desired outcome. The provider records their understanding and proposed approach. A requested solution is not automatically the right solution.
What exactly is included—and what is not?
List deliverables, features, exclusions, responsibilities, dependencies and acceptance criteria. Anything not explicitly included remains outside scope until clarified and approved.
What is required from each party, and on what terms?
Record fees, payment stages, timeline, client-supplied materials, access, review periods and decision-makers. Costs and dates remain provisional until their assumptions and dependencies are understood.
What do we not yet know?
Identify open questions, technical limitations, third-party costs, risks and assumptions. Assign an owner and due date to each. Unknowns must not be presented as promises.
What happens when the understanding changes?
New requirements, extra revisions, delays or integrations require a written impact assessment covering cost, timing and scope, plus mutual approval before the affected work proceeds.
What happens to the work, information and relationship?
Clarify intellectual property, third-party licences, confidentiality, data access, hosting, maintenance, handover, cancellation and outstanding payments before commitment.
Proceed only when both parties understand the same terms.
IF ANY MATERIAL ITEM IS UNCLEAR, PAUSE, CLARIFY AND REVISE BEFORE COMMITTING.
Complete before printing or downloading.
Capture the specific need behind this request. These notes travel with the printed or saved brief so the discussion starts with the client’s circumstances, not assumptions.