Use this checklist when briefing a development partner and handing a finished website over to your client. Agree responsibilities, review launch checks, add your notes and save a copy.
Your working brief
0 of 35 items reviewed
No email is needed. Browser saving is optional and keeps this brief on this device. With saving off, refreshing clears your work. Do not include passwords or sensitive client information.
No notes added.
A completed fictional example ↗
Illustrative brief / Northline studio website
People: Agency lead owns client communication; the client marketing lead approves content; weekly review on Tuesday.
Scope: Five public pages, one enquiry form and a content editor. Before launch, check the phone menu, form error messages and links from the old website.
Content: Approved desktop and phone designs and final text supplied before the build, including error and confirmation messages.
Technology: Existing WordPress site; record the page addresses to keep, browsers to test and where enquiry emails should go.
Access: Individual invitations to the code and test website. Client owns domain, hosting and analytics. No passwords in the brief.
Release: Agency lead approves the test website; development lead checks launch and the plan to restore the old site if needed. Handover includes editing notes, account access and support responsibilities.
Start a conversation
A brief doesn’t need every answer.
Share what you know, identify the open decisions, and work out the next step together.
