A useful project brief starts with the people who will use the product. Explain whether they are customers, readers, team members or another audience. Describe the main task they should be able to complete. This might be finding information, sending an enquiry, managing content or using a particular tool. A clear goal gives design and development decisions a shared direction.
Next, outline the content and features you already have. Existing text, images, brand materials and example screens can help explain your expectations. Separate essential features from ideas that could come later. If the project replaces an existing website or application, include its address and describe what currently works well. Point out any confusing steps or recurring problems you would like to improve.
Technical details are useful when they affect the project. Mention an existing hosting service, content management system, application platform or integration. If people need accounts, describe what each type of user can access. If the product needs multiple languages, list them early. These details help define the work before individual screens and features are discussed.