Brief a four-language service request without leaving the release undefined
A useful brief describes the customer task, the source decisions and the evidence that will make the first release acceptable. It should also show where a plausible future feature has deliberately been left for later. The following fictional brief concerns a Belgian equipment supplier adding a new maintenance-request journey to an existing website.
The task and the approved first release
Customers need to understand which equipment the service covers, choose a request language and send a request with the correct equipment reference. Staff need to receive a traceable request for review. Receipt does not confirm availability, price or a visit.
The first release includes an approved service page in English, Dutch, French and German; corresponding navigation and summary cards; one equivalent request form per language; correction messages; and an agreed receiving view. Technical project communication is in English. The client names a reviewer for each published language and an owner for the underlying service rules.
The equipment list already has a maintained reference source. The brief names that source and its owner instead of asking the website to invent a new catalogue. It also records which fields can be requested publicly and which information belongs in a later secure exchange.
Make the content decision concrete
Source statement S-12 says that the supplier reviews requests for the listed equipment families and confirms the next step separately. The first draft says “Book your maintenance visit,” which promises a stronger outcome than S-12 establishes. The owner replaces it with a request instruction and requires the same meaning in all four versions.
The source record includes covered equipment, excluded work, the request action and the person authorized to approve changes. Reviewers approve language against that record. If the service owner changes S-12, the affected language approvals are reopened rather than silently treated as permanent.
Define the receiving result
The approved fixture R-74 selects equipment E-17 and French as the desired reply language. The receiving staff view must show R-74, E-17, the contact details and the submitted explanation. The displayed French page title is not used as the equipment identifier.
A separate German request R-75 concerns equipment E-18. Its reference, language and equipment remain independent. Staff can distinguish a newly received request from one already reviewed. No automatic scheduling or invoice creation belongs to this release.
The brief identifies the existing receiving tool and the access needed to inspect it. If its supported interface cannot receive the agreed fields, that is a dependency to resolve before committing to the final implementation. A developer cannot verify the staff outcome from the public form alone.
State the deferred work and the reason
A proposed customer portal would allow customers to view request history and uploaded reports. The organization has not yet decided which account can see records across multiple sites. The first release therefore retains the existing approved follow-up method and does not expose historical documents through a new login.
The future portal has a specific prerequisite: an approved relationship among customer account, site and document access, with representative fixtures. This is different from leaving an undefined “phase two” in the proposal. The owner knows what decision would make the next estimate useful.
Record acceptance and ownership
| Acceptance question | Evidence required |
|---|---|
| Does each page describe S-12 accurately? | Named language reviewer and approved revision |
| Does the request identify the right equipment? | R-74/E-17 and independent R-75/E-18 receiving checks |
| Can the visitor correct an error? | Approved message, retained values and successful retry in isolation |
| Is receipt distinguished from acceptance? | Page, confirmation and staff status agree |
| Can the client maintain the release? | Ordinary editor changes an approved sentence and verifies affected surfaces |
The proposal can now identify implementation, review, provider dependencies and continuing maintenance separately. Use the release worksheet to manage the actual language approvals. Send a short version of this brief through the project enquiry, leaving credentials and private customer records out of the first message.