## Website development brief worksheet

Digital Kreativa editorial team. Published 14 November 2026.

Complete this document before requesting comparable proposals. Mark unknowns and assign a decision owner. Keep passwords, access tokens, and personal customer information out of the brief. Repeat the journey and content records as needed.

## Purpose and audience

- Organisation and offer: Complete here.
- Project owner and brief version: Complete here.
- Current site and reason for change: Complete here.
- Business outcome and available baseline evidence: Complete here.
- Primary audience and priority visitor task: Complete here.
- Other audiences and their priorities: Complete here.
- Evidence supporting these priorities: Complete here.

## First-release boundaries

- Pages and distinct layouts: Complete here.
- Languages and translation responsibilities: Complete here.
- Required functions and why they are needed: Complete here.
- Explicit exclusions and later-phase ideas: Complete here.
- Existing pages, files, and data to migrate: Complete here.
- Editing tasks staff must perform without technical help: Complete here.

## Content record

- Page or content group: Complete here.
- Source material and current readiness: Ready, awaiting review, or missing.
- Writing, entry, translation, and approval owners: Complete here.
- Images, brand assets, usage rights, and outstanding permissions: Complete here.
- Legal copy and qualified review owner: Complete here.
- Delivery dependency and agreed deadline: Complete here.

## Journey and integration record

- Visitor, starting point, and goal: Complete here.
- Actions and information required: Complete here.
- Successful result and observable acceptance test: Complete here.
- Failure, validation, and confirmation behaviour: Complete here.
- Form recipients and receiving-system verification: Complete here.
- Personal information collected and approved handling requirements: Complete here.
- Connected systems and authoritative record: Complete here.
- Information direction and failure-recovery responsibility: Complete here.
- Documentation and secure test-access owner: Complete here.

## Quality and acceptance

- Accessibility standard, scope, evaluation approach, and owner: Complete here.
- Representative users and involvement plan: Complete here.
- Browser, device, mobile, and keyboard journey coverage: Complete here.
- Performance targets, pages, conditions, and evidence required: Complete here.
- Distinction between pre-launch testing and real-user measurement: Complete here.
- Analytics and consent requirements, supplied by: Complete here.
- Content, functional, and technical approval evidence: Complete here.

## Commercial boundaries and governance

- Budget range and what it must include: Complete here.
- Implementation, third-party, and support costs to separate: Complete here.
- Required launch deadline, reason, and dependencies: Complete here.
- Reviewers, final approver, and consolidated feedback route: Complete here.
- Scope-change approval process: Complete here.
- Domain, hosting, source-file, and service-account ownership: Complete here.
- Launch authority, handover deliverables, and maintenance owner: Complete here.

## Open decision record

- Question and consequence of leaving it unresolved: Complete here.
- Decision owner and evidence required: Complete here.
- Deadline and affected work: Complete here.
- Confirmed answer and brief version updated: Complete here.

Ask each supplier to reference the brief version, state assumptions and exclusions, and explain how acceptance will be demonstrated.

## Reference guidance

- [W3C accessibility planning and policies overview](https://www.w3.org/WAI/planning/)
- [Google Web Vitals overview](https://web.dev/articles/vitals)