Start with the situation.
Give it a useful shape.
A concise brief helps connect an idea to a reviewable first result. It does not need to predict every future feature.
You can begin with a few paragraphs and one concrete example. The questions below help turn that description into a conversation about scope. They are a planning aid rather than a quotation, contract, or requirement to complete every field before contacting us.
Open the plain-text worksheetWho is the experience for?
Describe the intended audience and the situation around the screen. A first-time visitor comparing options needs different context from a returning user completing a familiar task. Avoid reducing the audience to a device type or an abstract demographic.
What should become possible?
Write the task in ordinary language. Explain what the person needs to understand, choose, or produce. A single representative example can help connect a broad idea to an interaction that can be designed and reviewed.
What needs to be decided first?
Identify the assumption that deserves attention: the sequence, the explanation, the amount of information, or the behavior of a control. If several questions compete, choose which one the first prototype or implementation should address.
What is already in place?
Mention the current website, platform, content, identity arrangements, or integration requirements. Confirm available access without sending credentials. A requirement that depends on another service needs a clear account of what that service can actually provide.
What should the first delivery contain?
Distinguish a concept, a prototype, and a production implementation. Name the deliverables and the review approach. Record what remains outside the first scope so that future additions can be discussed as changes rather than silently assumed.
Who will look after it?
Identify who will receive the files, manage the hosting environment, update content, and make later decisions. Any support arrangement, maintenance responsibility, or service commitment should be specifically agreed.
Keep the unknowns visible.
A project can have open questions. Record them, identify who can resolve them, and explain how they affect the proposed first result. A clear uncertainty is easier to work with than an unstated assumption.
Scope, timing, costs, approval responsibilities, and ongoing support should be agreed separately for an engagement. The brief supports that discussion without replacing it.
Send an initial inquiry