A useful brief starts with a problem, not a feature list.
Five questions that turn an early idea into a more useful technical conversation.

Describe the work as it happens today
Start with the people doing the task, the tools they use and the result they need. A specific example is more useful than a request for a modern platform. Describe where information is copied, where decisions wait and what happens when a step fails. Leave room for a smaller solution than the one you first imagined.
Choose an outcome you can observe
Define a practical result: a visitor can find the correct service and send an enquiry; a colleague can record a request without entering it twice; an approved report can be produced from a known data source. Avoid making revenue, rankings or customer behaviour an acceptance condition that implementation alone cannot control.
Separate the essential from the later
List the minimum screens, roles, records and actions needed to achieve that result. Identify useful additions separately. This is not a promise to ignore future requirements: it is a way to give the first engagement a clear finish. New requirements can then be priced and scheduled as informed decisions.
Name the constraints and the owner
Explain the systems that must stay, the access that is available and any sensitive data involved. Identify who can approve requirements, provide materials and accept a change. Do not send passwords, live customer records or payment details in an ordinary enquiry. Access can be arranged securely when the scope requires it.
Write down what a useful handover means
The project brief should say which source files, setup instructions, release notes and training are included. A simple website and an internal application have different handover needs. Agree where the work will run, who pays provider fees and who owns ongoing operations. A short brief with clear answers creates a better starting point than a long list of unprioritised features.