How to use the Event Post Timing Planner
- Describe the event. Add the name, the start date and time, and the time zone your audience lives in. Pick launch, webinar, sale or livestream.
- Choose your daily post time. The days-before and day-after posts go out at this audience time. Morning is a safe default; the tool keeps every post out of the 22:00 to 07:00 band.
- Review the seven posts. Read the sequence in order. Posts that the quiet-hours rule moved are marked, and any step that no longer fits before the event says so.
- Fill in and export. Replace the placeholders in curly braces with your details, then download a CSV for your calendar or content tracker, or an .ics file for your calendar app.
How the event planner works
What it builds
The planner turns your event start into seven fixed offsets. Day-based steps are calendar days before or after the event date in the audience zone, so a change of clocks in between does not shift them. The three hour step is exactly 180 minutes of real time before the start.
The result is a table with the audience date and time, the UTC time, whether the quiet-hours rule moved the post, and a draft you can edit. The CSV has the same columns as the table, in the spirit of the Content Calendar Builder, so the plan drops into a calendar or tracker.
Rules and sources
The quiet-hours rule is a fixed convention, not a platform rule: no post from 22:00 to 07:00 in the audience zone. Time zone math uses your browser's Intl data, which follows the IANA time zone database. The .ics file follows RFC 5545 from the IETF, with UTC times and one 15 minute reminder event per post.
The countdown cadence is a common launch pattern, not a measured result. It is a starting point for planning, not a prediction of reach.
Limitations
The tool plans when to post and gives draft wording; it does not know your audience's real peak times, holidays or the best day of the week. Use your own analytics, or the Best Time to Post Calculator, to adjust the daily time. Nothing you enter leaves your browser.
Frequently asked questions
What are the seven posts?
Fourteen days, seven days, three days and one day before the event, three hours before it, the moment it starts, and one day after for the recap. The day-based posts go out at your daily posting time in the audience zone, and the three hour and live posts are tied to the start time.
What does the quiet-hours rule do?
Any post that would go out between 22:00 and 07:00 in the audience zone is moved to 07:00 the next morning, or to 07:00 the same day if it falls after midnight. The step is marked as moved, with the original time. If the move would put a pre-event post at or after the start, the step carries a warning so you can post earlier by hand.
Is the post text written by AI?
No. The drafts are plain templates, one set for each event type, with the event name, date, time and zone filled in. Everything else is a placeholder in curly braces, such as {link} or {benefit}, for you to complete in your own voice.
Which time zone should I choose?
The zone where most of your audience is, not where you are. If the audience is split across regions, run the plan once for each main region, or use the Posting Time Team Converter to see the same moment in several zones.
What if the event itself is at night for the audience?
The live post moves to the next morning and a warning explains why. For a late event, a post just before the start, at the three hour step or by hand, usually works better than a live post nobody sees until the morning.
Does the plan survive a clock change?
Yes. Each post is placed at a wall-clock time in the audience zone, then converted to a UTC moment, so a 09:00 post stays at 09:00 local before and after daylight saving changes. The CSV and .ics file include the UTC time so the post is unambiguous.