18 March 2026
When to recommend waiting on a store submission
A go / wait call is only useful if the reasons are specific enough for product and engineering to act overnight.
“Wait” is an expensive word when billboards are printed. We still say it when the alternative is a rejected build or a first-week crash spike that erases the campaign.
Thresholds we use in practice
We recommend waiting when any of the following hold and cannot be fixed before the planned submit time:
- The release cannot be reproduced from the tagged commit with the documented signing materials
- A crash in a primary revenue or account-creation path reproduces on a stock device in staging
- Store metadata claims capabilities the binary does not expose
Conditional-go
Many reviews land here: ship after a short list of fixes with named owners and a re-check of those items only. Conditional-go is not politeness — it is a scoped contract so the team does not reopen the entire architecture debate on submission day.
After the call
A Remediation Roadmap Session is useful once the launch noise settles, especially if “wait” exposed deeper structural debt that should not be debated during freeze week.