Describe the situation before the solution
A useful brief starts with a problem. Instead of “we need five pages”, write “customers cannot distinguish our services and repeatedly ask the same questions”. Add the audience, priority service and desired visitor action. The page structure can then follow those needs rather than an arbitrary number.
A short example
A service business works remotely. It wants to explain three services separately and receive enquiries carrying the selected service. It has a logo and photographs, but the copy needs editing. It needs two languages at launch. One person approves content; another will maintain it. This is enough to start a scope discussion without inventing a technical specification.
Gather materials in one place
Collect available logo formats, brand colours, photographs with usage rights, service descriptions and verified project information. Add current contact details and existing information documents. Distinguish finished material from content still to create. Explain references precisely: is it the layout, photography or way the offer is presented that you like?
Agree responsibilities and access
Name the person preparing and approving each content item. Record who controls the domain, hosting and email. Do not put passwords in the brief; share access separately through an agreed method. Finish with open questions and items that can wait. Missing materials need not prevent a discussion, but should be reflected in the scope.
A practical handover checklist
Collect vector logo files, colours and licensed fonts, service descriptions, current contact details, publishable photographs and copy requiring approval. Give each file a purpose and an approver. A file called “final2_new” without context can easily end up on the wrong page.
An example of a testable requirement
Replace “modern contact section” with: “the visitor selects a service, enters an email and description, receives a submission message; the team gets the selected service and can reply to the visitor”. Include the missing-email scenario. This is a requirement you can check at handover.
Choose one person to consolidate feedback, agree content deadlines and define how changes are submitted. Share confidential material and passwords separately through an agreed secure channel.