Submit a release for review
How the Submit for Review button works, which requirements must be met, and what gets locked when you submit.
When your release is complete, you send it to the UXEM team with the Submit for Review button.
Before you can submit it
The Submit for Review button is disabled until all required checks are green.
That checklist is in the release's Review → Summary tab. It tells you what's missing and in which section to fix it. See Checklist before your first release.
Submitting it
- Click Submit for Review.
- Confirm in the dialog: "You won't be able to edit it until it's approved or requires changes."
The release moves to In Review, the form is locked and the submission date is recorded. You'll see the notice Release submitted for review.
What happens next
The team reviews the release and finishes in one of two ways:
- Approved: it moves to Distributed and is sent to the platforms.
- Requires Changes: it comes back to you with the fixes needed.
Submitting changes to an already-distributed release
If you edit a release that's already Distributed, your changes are saved but the release stays distributed. When you're done, use Submit for Review so the team can apply the changes: the release moves to review to revalidate them before they reach the stores.
Was this article helpful?
Thanks for your feedback!
Related articles
The six release statuses in detail: what each one means, whether you can edit it, and what happens next.
What the Requires Changes status means, where to see the requested fixes, and how to resubmit the release.
What the review timeline depends on, how the recommended minimum date is calculated, and what happens if you pick a date too soon.