Managed publishing: schedule a release without babysitting the Console

Managed publishing lets you prepare a release and choose when it goes live, instead of publishing the moment you hit the button. It is useful when a launch is coordinated with a campaign, a support team, or a date you cannot move.

It is not a way to skip review, and it is not a guarantee that a release will appear at an exact minute. It is a control for the publish step, not the review step.

What it changes

Without managed publishing, a release can go live as soon as it is ready and approved. With managed publishing enabled, releases wait in a "ready to publish" state until you publish them, or until a scheduled time you set.

That gives you time to:

• review the release one more time;
• coordinate with marketing or support;
• avoid publishing while the team is asleep;
• publish several changes together;
• check the store listing and declarations before users see them.

When it helps

Managed publishing is a good fit for:

• a launch with a fixed date;
• a release that depends on a partner or press embargo;
• a team that needs a final sign-off;
• an update that should go out during support hours;
• a set of changes that should appear together.

It is less useful for a small bug fix that you want live immediately. In that case, the extra step can slow you down.

How to use it

The exact labels can change, but the flow is usually:

1. Enable managed publishing in the publishing overview.
2. Prepare the release as usual.
3. Send it for review if required.
4. Check the release, store listing, and declarations.
5. Publish manually, or set a scheduled time.
6. Confirm the release is live.
7. Watch vitals and support after launch.

If you schedule a time, check the time zone. A launch at "10:00" can mean a very different hour for your users and your team.

What it does not do

Managed publishing does not:

• speed up Google's review;
• guarantee a release at the exact scheduled minute;
• fix a policy problem;
• replace a staged rollout;
• let you publish an app that has not been approved.

If review takes longer than expected, the schedule may slip. Plan the date with buffer, especially for a first release.

A pre-schedule checklist

• Release is uploaded with a higher version code.
• Store listing and screenshots are final.
• Content declarations and Data safety are current.
• Pricing and country availability are correct.
• Release notes are written and localized if needed.
• Support has the details.
• Someone is available after launch.
• The scheduled time is in the right time zone.
• A rollback or fix plan exists.

Managed publishing and staged rollouts

These are different controls and can work together. Managed publishing decides when the release starts. A staged rollout decides how many users receive it once it starts.

For a bigger update, you might schedule the start and then roll out gradually. For a small fix, you might skip the schedule and use a small staged rollout.

The short version

• Managed publishing holds a release until you publish or schedule it.
• It is useful for coordinated launches and final checks.
• It does not skip review or guarantee an exact minute.
• Check the time zone and have support ready.
• Use it with a staged rollout for larger updates.

Next: the Google Play publishing checklist, or testing tracks and releases.