A post is forgiving. If you publish at a bad hour, people scroll back and find it later. A live call is not forgiving. Members are either there or they are not, and if they are not, you are talking to four people and an empty chat.
That difference changes the whole timing question. Posting timing is about catching a peak. Go-live timing is about reach — maximising the number of distinct members for whom the slot is genuinely workable.
Is there a single best hour to go live on Skool?
There is no single best hour to go live on Skool. Nobody publishes a credible platform-wide figure, and any specific hour you find in an article is invented or borrowed from a study about a different platform.
Four reasons the answer cannot be universal:
- Timezone spread. A live call has no replay-equivalent for attendance. If your members span eight time zones, some slot is going to be someone's 2am, permanently.
- Niche. A community of full-time operators can meet at 11am on a Wednesday. A community of people building something on the side cannot. Ask the blunt question: are your members at work when your call runs?
- Community size. With sixty members, you can literally ask them. With two thousand, you need the data, because the loudest respondents to a poll are not representative.
- What the call is. A drop-in Q&A, a taught workshop and an accountability session have different attendance economics. People will rearrange their day for a workshop and will not for a hangout.
Should I schedule my live call at my community's busiest hour?
Schedule your live call for reach rather than for the peak: the busiest single hour is usually the wrong choice, and reach-first thinking is the mental model that fixes most bad scheduling decisions.
Imagine your activity curve has a tall spike at one hour and a broad, lower plateau across three others. The instinct is to take the spike. For a post, that instinct is right.
For a live call it is often wrong, because the spike may be a small group of very active members who are active at that hour and also active at other hours. Scheduling into the spike serves people you were going to reach anyway. Scheduling into the plateau can reach a wider set of distinct members, including some who are only ever available in that band.
Skoolgrades' Go-Live timing card is built on exactly this principle — an inclusive, reach-first ranking. It is trying to maximise the number of members for whom a slot works, not to find the single hottest hour. That is a genuinely different optimisation and it usually produces a different answer.
A slot that is fine for ninety people beats a slot that is perfect for twenty.
Where does the go-live timing recommendation come from?
The go-live timing recommendation comes from your own community's aggregate activity curve, not from any platform benchmark. Timing readouts, including go-live, live in the Business Dashboard at /reports/dashboard, and they are included on every Skoolgrades plan.
They are derived from your community's aggregate activity curve — when your members are demonstrably doing things — rather than from any platform benchmark.
One honest limitation, stated on purpose. We tried inferring individual members' timezones from their profiles and behaviour. It was unreliable, often wrong by several hours. So we do not use it, and we do not pretend to. Timing comes from the aggregate curve, and DM timing separately uses the raw activity window rather than a per-person guess.
Practically, that means the card can tell you with reasonable confidence when your community as a body is awake and engaged. It cannot tell you the perfect hour for one specific member in Auckland. For a live call, the aggregate is the right unit anyway — you are scheduling one event for many people.
Reading a two-hump curve
The most common real-world shape for a Skool community with any international membership is two humps: a European-ish band and an Americas-ish band, with a gap in between.
If that is your curve, stop looking for a compromise hour. The hour between the humps is usually bad for both groups rather than acceptable to both. Better options:
- Alternate. Run the same session in hump A one week and hump B the next, on a fixed rotation so people can plan.
- Pick one and be explicit. Choose the larger hump, say clearly that this is the slot, and serve the other group a different way — an async thread, a recording with a live comment window, a written recap.
- Split the format. Put the taught content in the recording and use the live slot purely for Q&A, which lowers the cost of missing it.
Whatever you choose, say it out loud to the community. Unexplained scheduling reads as favouritism; explained scheduling reads as a decision.
How do I work out my own go-live slot by hand?
You can work out a go-live slot by hand in an afternoon, with no tooling, by bucketing your community's comment timestamps by hour and counting distinct members per bucket.
- Pull the timestamps of your community's comments over the last four to eight weeks. Comments, not likes — Skoolgrades counts engagement as comments plus polls precisely because a like predicts nothing.
- Bucket by hour of day and by day of week, separately, in one fixed timezone.
- Ignore your own activity. You are always around; including yourself skews the curve toward whenever you happen to work.
- Count distinct members per bucket, not total actions. This is the reach-first correction done by hand. Three people commenting twenty times is not the same as twenty people commenting once, and for a live call the second one is what you want.
- Cross-check against attendance if you have run calls before. Actual attendance beats inferred availability every time.
Step four is where most hand-rolled versions go wrong. Raw action counts are dominated by your most active members, who are the people least at risk of missing a call.
What raises live attendance more than picking the right hour?
A fixed slot, personal invitations, a concrete reason to attend live, a same-day reminder and a recording all raise live attendance more than the hour you pick. Timing is worth getting roughly right and not worth agonising over. Bigger levers, in rough order:
| Lever | Why it moves the needle |
|---|---|
| A fixed, unchanging slot | People can only build a habit around something predictable |
| Naming people who should be there | A personal invitation is not comparable to a feed post |
| A clear reason to attend live | "Bring your question" beats "join the call" |
| A reminder within a few hours of start | Most no-shows are forgetting, not declining |
| Recording, and saying so | Removes the fear of missing it, which paradoxically raises attendance |
That second row is where a lot of quiet upside sits. Inviting the twelve members who asked about the topic personally will do more for attendance than moving the call an hour.
Skoolgrades supports that directly: build the list in Targets — pick a recommended group, describe who you want in plain language, or paste a post URL and pull everyone who engaged with it — then draft one message either verbatim or personalised per member, approve every draft, and send them from the extension panel one click at a time. Nothing auto-sends. That is a deliberate design choice: blast-style DM automation is how owners get flagged and how members learn to ignore their inbox.
What should I do after the live call?
After the live call, feed the result back into the next scheduling decision and publish a recap. Note attendance, note which members were new to attending, and note who you expected and did not get. Two or three cycles of that will tell you more than any benchmark.
And publish something afterwards. A short recap post with the key points and an @mention of anyone who asked a good question keeps the value alive for everyone who missed it, and quietly advertises the next one. The what to post framework covers the shape of that.
So when should I go live on Skool?
Go live in the slot that reaches the most distinct members of your own community. Do not go looking for the best time to go live on Skool, because it does not exist as a universal figure. Go looking for the slot that reaches the most distinct members of your community — which is a reach question, not a peak question, and often not the same hour.
Derive it from your own activity curve, count distinct members rather than raw actions, pick a fixed slot and defend it, and invite the specific people who should be there. If you want the posting-side version of this argument, best time to post covers it, and member activity tracking covers where the underlying curve comes from.