Tell the team your project deadline
Provide a clear target date and the constraints behind it so the schedule can be discussed alongside the scope.
What you need
- Your preferred delivery date
- Any launch date, review time or dependencies
Separate delivery from launch
Decide when you need the files or result, not only when the public launch happens. Leave room in your plan for your own review and for work that depends on the delivery. State which date is fixed and which is flexible.
Enter the target date
Open the service request form and use its deadline field. Write an unambiguous date, and add a time zone when an exact time matters. Explain the launch or dependency in the technical brief.
Choose the timeline option
Review Standard and Express where shown. Express requests priority scheduling; availability and its quote are checked separately after scope review. Do not treat selecting it as confirmation of a delivery date.
Ask for a schedule confirmation
Send the brief with the date, required deliverables and readiness of your materials. Ask which milestones and review points can be agreed. If your deadline changes later, notify the team in the existing project conversation.
A preferred date in a form is a request for scheduling, not a confirmed commitment.
If it doesn't work
The deadline is close
State the fixed date and the smallest useful result you need by then. Ask what can be delivered within that scope rather than assuming the entire project can be accelerated.
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