Write a brief another person can follow

A useful brief describes the work without prescribing its implementation too early. The following prompts are a written preparation exercise. They do not submit information or calculate a project price.

Start with the task

Name the person who begins and the result they need. “An overseas buyer identifies a product variant and requests a quote” is more useful than “add a modern catalogue.” Explain what the business should do after receiving the request.

Record the current path in a few sentences. Include the page or tool, what information is available and the point where someone has to intervene. Use fictional or appropriately prepared examples instead of private customer data.

Identify the record and its owner

Which system should contain the current request? Who can correct it? Which details are copied elsewhere, and why? If these answers are unknown, record the uncertainty. It may be the first thing the project must investigate.

Name provider accounts and relevant documentation without supplying credentials. Account ownership and supported interfaces can determine whether a proposed connection is feasible.

Describe a useful first finish line

Choose an observable result. For example: a quotation request preserves the product reference, staff can locate the relevant specification, and an incomplete request remains visibly unresolved. Include a correction or interruption that would expose a weak design.

List the content and language review needed for that result. A technical contact may not be qualified to approve commercial wording in each language, so identify the reviewer separately.

State constraints that change the choice

Mention systems that must continue operating, contractual dates, existing records, accessibility needs and decisions requiring professional advice. Explain the consequence of the constraint. A preferred launch date and a provider contract ending are different planning facts.

Finish with a small decision list: what is known, what needs checking and who can answer. Leave room for the developer to recommend a smaller or different intervention when the evidence supports it.

Send a short version through the enquiry page. The handoff planner can help if you are unsure which transition to describe.