Plan the day before it starts
Launch day timeline planner
A launch is spread across several channels and, usually, several time zones. Enter your launch date and time, your own zone, the zones where your audience lives and the channels you will post on. The planner lays out the day in your local time, shows what each slot is in every audience zone, and marks anything that lands outside 07:00 to 22:00 there.
Everything is calculated in this page with the time zone data built into your browser. Nothing is uploaded or saved. The calendar file uses UTC times, so it opens at the right moment in any calendar app.
Enter the launch date.
How to use it
- Set the launch moment. Pick the launch date, the time you want the first post to go out, and the time zone you will be working in.
- Choose your audience zones and channels. Tick the zones where the people you want to reach live, and the kinds of channel you will use: your own site, directories, newsletter, social posts and communities.
- Read the timeline and fix the flags. Each row shows your local time and the same moment in every audience zone. Slots outside 07:00 to 22:00 in a zone are marked. Move the launch time or the gap between posts until the slots that matter to you are inside the window.
- Export the plan. Copy the Markdown table into your notes, or download the .ics file and import it into your calendar so each task and post arrives as a reminder at the right time.
How the timeline is built
Time zone arithmetic uses the Intl API in your browser, which reads the IANA time zone database. The launch time you type is a wall clock time in your zone and is converted to one exact UTC instant, so daylight saving changes are handled by the data and not by adding fixed hours. On a day when the clocks change, a day is 23 or 25 hours long, and T-24h means exactly 24 hours before the launch instant, which may be a different clock time the day before.
Channels are placed in a fixed order: your own site first, then directories, newsletter, social posts and communities, one slot per channel, spaced by the gap you choose. The gap is limited to 30 to 60 minutes. Posting everything in the same minute makes it hard to reply to each audience and to see which channel sent which visitors; a short stagger keeps the whole sequence inside one attention window. This is a planning convention, not a measured optimum.
The awkward-hour flag is a fixed rule: a slot is flagged for a zone when its local time is before 07:00 or from 22:00 onward. It does not know your audience's habits, public holidays or weekends. The task list follows a common pattern: preparation at T-24h, a final check at T-1h, hourly check-ins for twelve hours after launch, and a review at T+24h. The calendar file contains one event per row, each with a UTC start time.
Questions
Why is T-24h not the same clock time as the launch?
Because the planner subtracts exactly 24 hours from the launch instant. If the clocks change in your zone between the two moments, the day was 23 or 25 hours long and the clock time shifts by an hour. That is correct behaviour, not a bug.
What does the 07:00 to 22:00 flag mean?
A slot is flagged for an audience zone when the local time there is before 07:00 or at 22:00 or later. It is a simple, fixed rule for avoiding the middle of the night. It does not say anything about when your audience is most active.
Will the calendar file show the right time in my calendar?
Yes. Every event is written with a UTC start and end time, so your calendar converts it into your own zone when you import it. The tool's tests parse the exported file and compare each time with the planned instant.
Can I use more than one launch on the same day?
Run the planner once per launch. Each export is a separate file, and the events carry unique identifiers, so importing two plans does not overwrite one with the other.
What if I cannot cover every audience zone?
You usually cannot. The summary tells you how many of your audience zones are inside the 07:00 to 22:00 window at the launch time. Pick the zones that matter most and accept that the rest will see the posts later.
Does anything I enter leave my browser?
No. The plan is built and exported in this page. Nothing is sent to a server or stored.