Prepare a useful project brief
A clear brief helps the team understand what exists, what needs to change and what you expect to receive.
What you need
- Your current materials
- The intended result and any constraints
Explain the starting point
Open the relevant service and find its request form. In the current-situation field, describe what you have now, who uses it and the problem you want to solve. A concrete example is more useful than a general statement that something needs improvement.
Describe the outcome
Use the desired-outcome field for the change you need. Name the audience, platform and deliverables. If you have a measure of success, explain it as a goal rather than a guaranteed result.
Write the specification
In the technical brief, list required pages, formats, languages or integrations. Separate essential requirements from optional ideas. Mention existing brand or technical constraints and who will approve the work.
Add practical details and review
Put references in the links field and your target date and budget in their fields. Check your name and email, then read the complete request for contradictions before sending. Keep a copy of the wording for later discussion.
Keep the main brief concise; use the attachment or reference fields for supporting material.
If it doesn't work
The form asks you to complete fields
Check current situation, desired outcome, technical brief, name and email. These are required in the service request form. Filling only the links or deadline does not replace them.
Last checked: 9 September 2026
Was this helpful?
Still stuck?
Tell support which step stopped you and what you saw. Never send passwords, verification codes or full payment-card details.
Contact support