# Managed Publishing: Controlling Exactly When Your Update Goes Live

> A build can pass review and still not go live until you say so. Here's what managed publishing actually controls, and why that gap between approval and release is genuinely useful.


**Key points:**
- Managed publishing splits review approval from the actual release, so passing review doesn't mean your update goes live automatically.
- The update sits ready and waiting until you choose to publish it yourself.
- This gives you real control over timing. Lining a release up with marketing, support being ready, or just dodging bad timing.
- It's optional, not forced. You can still publish right away the moment review finishes if that fits better.

An update can clear review and still be fully in your hands to decide when it actually reaches anyone.

## What this setting actually splits apart

Without this on, an update usually goes live on its own the moment it clears review. With it on, those two events split apart. Review approval happens on its own clock, one you don't control directly. The actual release happens whenever you decide to trigger it, which you control fully. The update sits in a ready, approved state in between, waiting on you instead of going out the second it's cleared.

| | Without this control | With this control |
|---|---|---|
| Review passes | Update goes live on its own | Update sits ready, waiting |
| Who picks the release time | The review process itself | You, whenever you choose |

## Why that gap is genuinely useful

Review timing isn't something you control closely. It can finish earlier or later than you expect, which makes an automatic release a bit of a gamble on timing you never actually picked. Splitting approval from release means your real go-live moment can be deliberate instead. Timed to match a marketing push. Timed to a support team that's ready for extra questions. Or just picked to avoid a day and hour that would clash with something else already happening.

> **Real-world scenario:** A team had a marketing push planned to go out alongside a big update, timed carefully to a specific morning. Review finished two days earlier than they'd expected. Without this control, the update would have gone live well before the campaign was ready to back it up, with excited users arriving to nothing set up yet to catch them. Because the update sat approved and waiting instead, they released it right when the campaign actually launched, instead of scrambling to catch up with an update that had already gone out early.

## When an immediate release still makes sense

This isn't a tool that always calls for waiting. Plenty of updates have no real timing need, and publishing the moment review clears is perfectly fine for those. The real value shows up when timing genuinely matters. A planned campaign. A support team's own schedule. Dodging a release landing right before a weekend when nobody's watching for problems. Having the option is the real win, not a rule to always use it.

## What to actually do about it

1. **Use this control when your release timing actually matters.** A campaign, a support team's readiness, or just dodging bad timing are all real reasons to wait.
2. **Don't feel you have to delay every release just because you can.** Plenty of updates have no real timing need worth planning around.
3. **Remember review finishing isn't the same as going live, once this is on.** Make sure you've actually triggered the release once you're ready, since nothing happens on its own at that point.
4. **Plan your timed releases around this gap on purpose.** It's the tool that makes a precisely timed launch possible, instead of hoping review finishes at a good moment.

[AppRankr's Rank Tracker](/rank) tracks your real rank around a release, a useful way to see how a well-timed launch actually went.

