A landing page brief connects the promise in a campaign to the action a visitor is being asked to take. Without that connection, designers may optimise a screen while the buyer still cannot tell whether the offer fits. The brief should explain the visitor's context, the information required for a decision and what happens after a click. It is a working agreement between marketing, design and the people handling the response.

Define one visitor situation

Describe the source of the visit and the question that brought someone there. A hypothetical training provider advertising an introductory workshop should distinguish a manager buying for a team from an individual booking their own place. Their approval needs, price questions and next steps differ. If both are important, consider separate journeys rather than a page that tries to speak equally to everyone.

Record what the visitor already knows and what the campaign has promised. Include the actual advertisement or email wording in the brief, not just a general brand description. The headline and opening explanation should continue that conversation. A mismatch between a specific promise and a generic introduction makes visitors do unnecessary interpretation before they can assess the offer.

State the offer and its boundaries

Specify what is included, what is excluded and any eligibility conditions. For the workshop example, this means format, learning topics, preparation requirements and how scheduling works. Leave unknown details visibly unresolved in the internal brief and assign an owner to confirm them. Never publish invented availability or qualifications simply to make the layout feel complete.

Choose the main action according to the actual sales process. A fixed offer might support booking; a tailored engagement may need a consultation. State whether the page creates an email draft, submits a request or completes a purchase. The button, confirmation and follow-up copy must reflect what the system genuinely does. An enquiry is not a confirmed booking.

Make evidence a content requirement

List the evidence that can be published with permission: an approved sample, a product demonstration, an explanation of the process or a genuine customer statement. Where evidence is unavailable, describe the service clearly and avoid implying results. Decorative logos and invented numbers do not solve a buyer's uncertainty; they create a trust problem that a polished layout cannot repair.

Map each concern to an answer. A buyer worried about suitability may need prerequisites and exclusions. Someone worried about disruption may need a delivery outline. Someone comparing suppliers may need deliverables and responsibilities. This makes the content brief more useful than an instruction to add a testimonials section. It also reveals questions that need to be answered internally first.

Design the form around the response

Ask the response team what information they need to take the next useful action. A name, reply address and short description may be sufficient for an initial conversation. Detailed financial or operational questions may belong later. Explain why sensitive information is requested, minimise collection and agree how access, retention and deletion will be managed.

Document validation, incomplete submissions and service failures alongside the happy path. What does a person see if a required field is missing? Can they contact the team another way? Who checks the inbox or queue? For a mailto flow, explain that the visitor must review and send the draft in their own email app. Do not describe that as delivered automatically.

Specify quality checks, not just visual approval

Include mobile layouts, keyboard navigation, readable labels and clear focus states in acceptance criteria. Check the message with someone unfamiliar with the offer: can they describe what it is, who it is for and the next step? Ask them to find a limitation rather than only testing whether the page looks attractive. Useful feedback often concerns missing information.

Agree event definitions before launch, including what counts as a completed action and what is only a click. Keep measurement proportionate and subject to applicable consent requirements. A button interaction should not be reported as a qualified lead. Provide a review owner and a process for correcting inaccurate content, especially when several campaigns share one destination.

Landing page brief checklist

  • Attach the campaign message and identify the visitor situation.
  • Define the offer, exclusions and primary action.
  • Supply approved evidence or clearly state what is unavailable.
  • Map common concerns to specific page content.
  • Confirm the real form behaviour and response owner.
  • Specify mobile, accessibility and failure-state checks.
  • Agree measurement definitions and a post-launch review.

A complete brief reduces the number of decisions that have to be guessed during design. Before production begins, resolve the offer and response process with the people who own them. The page can then be judged on whether it makes that real offer understandable, rather than whether it imitates a fashionable conversion formula.