Calendar days. Not business days.
Google's closed-testing requirement is 14 continuous days, and weekends and public holidays count. The clock does not pause because your team is off, your testers are travelling, or your country has a holiday.
That is good news for planning: you can calculate the finish date with a normal calendar. It is bad news if you assumed the test would only count working days.
What "14 days" means in practice
A tester who opts in on a Monday should complete 14 continuous days the following Sunday week. The exact Console update may lag, but the requirement is based on continuous participation, not on your working schedule.
If a tester opts in on Friday, the weekend is part of their 14 days. You do not get to skip Saturday and Sunday.
Time zones
Google's systems operate across time zones, and your testers may be in different countries. Do not plan to the hour unless you have a reason to.
The practical approach:
- get opt-ins in as early in the day as possible;
- use the Console's requirement status as the authority;
- add a buffer day before applying;
- avoid scheduling the application for the last hour of the last day.
A one-day buffer is cheap. A premature application is not.
Do holidays pause the test?
No. A public holiday is a normal calendar day for the requirement.
If your testers are less active during a holiday, that is a feedback and usage issue, not a formal pause. The opt-in clock keeps running. This is another argument for starting with 14–15 testers rather than exactly 12.
Do business days matter at all?
They matter for support and review, not for the 14-day requirement.
Google's review team does not promise a decision within a fixed number of business days. The testing clock is separate from the review queue.
If you are planning a launch date, treat the testing window and the review window as two different estimates.
How to calculate your finish date
- Find the opt-in date of the tester who will be the last to complete 14 days.
- Add 14 calendar days.
- Add one buffer day for Console update and verification.
- Apply after the Console shows the requirement is satisfied.
If you add a replacement late, use their opt-in date, not the original tester's date.
The short version
- The requirement uses calendar days.
- Weekends and holidays count.
- Each tester has their own 14-day window.
- Business days matter for support, not for the clock.
- Add a buffer before applying.
Next: when does the 14-day clock start? or closed testing days not counting.
Our team’s note
If this answered the question but your situation still feels messy, send us the screenshot or the rejection email. Some things are easier to solve in a two-minute conversation than another article.