Meta Ad Schedules: Confirm the Account Clock and Saved Launch Window

A Meta ad schedule is ready when its saved dates and clock basis match the business’s approved operating window. “Start at nine” leaves too much unresolved: which date, which time zone and which campaign setting?
Write the requirement in the business clock, translate it into the clock used by the actual configuration, then reopen the saved version and check both endpoints. This review helps prevent an accurate-looking schedule from running in the wrong hours.

Define the window before changing settings
Record the first permitted start and required stop, including dates and time zone. Separately record any recurring hourly restriction. A campaign launch, a daily delivery pattern and a budget change are different instructions and need separate acceptance.
Keep the reason beside the restriction. Collecting inquiries for a later reply may be useful outside staffed hours. Promising an immediate conversation requires suitable coverage. Choose the operating promise first, then a delivery plan that supports it.
Meta’s official budget and schedule training covers the relevant concepts. Use the options available for the actual campaign and budget setup; an older tutorial or another account does not establish which controls you have.
Record the clock the configuration actually uses
Capture the ad account identifier, observed time zone and chosen scheduling basis. Record the operating time zone separately. Use dated conversions: seasonal clock changes can alter the difference between named zones, and a remembered offset may belong to a different month.
Meta’s official ad-account model contains time-zone information, while its ad-set model represents start and end times. The practical lesson is to retain both clock and timestamp evidence. The models do not establish how every editor presents a schedule.
If the configuration offers a viewer-based clock or another basis, check the chosen setting’s meaning. Applying an account-clock conversion to a different scheduling basis can create the very error the review is meant to prevent.
Catch a seven-hour shift in a worked example
Worked example (fictional): a service business approves 09:00–17:00 on 9 November in an operating clock fixed at UTC+02:00 for that date. The reviewed account clock is UTC−05:00 over the same interval. These assumed offsets describe this example, not a named location or an account default.
Business requirement: 09:00–17:00 on 9 November in the operating clock.
Correct account window: 02:00–10:00 on 9 November, because the operating clock is seven hours ahead.
Entered account window: 09:00–17:00, which converts to 16:00 on 9 November through 00:00 on 10 November in the operating clock.
The entered window overlaps the intended eight staffed hours for only one hour. Seven intended hours are omitted and seven fall after the approved window. This comparison cannot predict the spending error: delivery need not be uniform across the hours.
Correct both endpoints and reopen the saved version
The builder sets 02:00 and 10:00 on 9 November through the available supported controls. A second reviewer reopens the saved configuration, checks its date and clock basis, then converts both endpoints back to the operating requirement.
Include the date in the check even when the time looks correct. A midnight boundary, an incorrect end date or a seasonal change during a longer campaign can invalidate an otherwise sensible conversion.
Inspect any recurring pattern, campaign-level restriction or operational dependency that could affect the window. For a campaign spanning a clock change, review the relevant dated intervals separately. Leave unsupported or unclear behaviour unresolved until the responsible person can demonstrate it.
Separate a saved schedule from an applied change
Keep three states in the review: intended window, applied configuration and observed delivery. A field screenshot shows what was visible at one moment. It does not establish that an update was applied or that ads began delivering.
Meta’s saved-draft guidance is the platform reference for publishing saved edits. Confirm the current apply or publish outcome in the account, then inspect delivery after the authorised release. Do not treat a saved edit as proof of an active change.
Hold the launch when a date, clock basis or endpoint is unresolved. The approval record should contain the business requirement, saved window, independent conversion, applied outcome and person checking the first permitted period. Compare any later delivery concern on the same time basis before declaring a fault.
Keep the response plan and spending review connected
Name the inquiry queue owner, coverage and fallback response. Someone who clicked near the end of a delivery window may complete an inquiry later, so closing the window should not leave an accepted request unowned.
Our guide to following up Meta ad inquiries covers that handoff. Use our budget pacing guide for the separate spending check; correct hours do not establish even daily spend.
Bring the observed account clock and dated operating requirement to our Meta Ads management service. We can help turn them into a saved schedule your team can verify and monitor.
Comments