Ask for changes to an existing project
Send a clear change request that the team can compare with the original scope.
What you need
- Your existing conversation or reference
- The current version and requested changes
Identify the version
Name the file, page or deliverable you reviewed and include a date or version when possible. Describe what should change and why. For several changes, use a numbered list and separate essential corrections from optional additions.
Explain the impact
Mention any new deadline, additional format or dependency. Ask whether the change affects the agreed scope, price or schedule, and wait for that clarification before treating the change as confirmed.
I have an open conversation
Keep the changes with the original project.
Add the change list
Open the matching request in your cabinet, or return to the service's direct line if you used it as a guest. Send the version and change list in that thread so the original brief stays available.
My project is handled by email
Use the existing email exchange.
Reply with the project reference
Reply to the project email with your change list and reference. If you cannot find the exchange, use the published contact email and include enough details to identify the project.
Sending a message does not automatically approve extra work or change the agreed terms.
If it doesn't work
The conversation is closed
If the message box is disabled, use Contact. Include the original reference and ask how to continue the project discussion.
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