Skool Calendar: schedule events without timezone confusion
An event time needs a full date and timezone, especially around seasonal clock changes.

An invitation saying at six leaves too many questions unanswered when members join from several countries. Treat the date, time and timezone as one combined piece of information. Then check recurrence, duration and the connection location. Our recommendation is to review these fields before announcing the event, not after the first confused questions appear in the feed or someone has already planned around the wrong interpretation.
The fields to review
Official guidance says to open Calendar and click the plus button to add an event. The form includes a title, date, time, duration and an adjustable timezone. It also supports daily, weekly, monthly or annual recurrence and options for ending a series. The location can be Skool Call, Zoom, Meet or a physical address for an in-person gathering. Add instructions that match the location you actually choose.
Do not rely on one fixed offset year-round
As a recommendation, identify the timezone using a recognisable city or region and check the conversion for the specific date. Madrid and other locations may change seasonal time on different dates, or not change at all. A time difference that works for one session should therefore not be copied unchecked across an entire season. Do not assume how every device will display it: ask members to confirm the actual event when uncertainty remains.
Worked example: coaching between Madrid and Bogotá
A tutor wants her session to remain at 18:00 in Madrid. On 21 October 2026, that corresponds to 11:00 in Bogotá; on 28 October, it corresponds to 12:00 after Madrid's seasonal clock change. This example shows why specific dates need checking. If the goal were instead to keep Bogotá's time fixed, the scheduling reference should reflect that decision rather than silently changing which audience the timetable prioritises.
Checklist before announcing
- Check date, time, timezone and duration together.
- Review the next occurrence when enabling a recurring series.
- Verify the location and connection instructions.
- State which local time should remain fixed for international participants.
- After any change, confirm that the announcement and event agree.
Skool documents event reminder emails sent 24 hours before the event. Their receipt depends on the relevant preferences, so do not use reminders as a substitute for a correctly configured and clearly communicated invitation.
Explore PowerUpSkool features to support your community operations.
ContinueSources and documentation
Frequently asked questions
Is putting the time in the description enough?
Not as an organising method. Configure the event fields and use the description to clarify the timezone reference, avoiding contradictions between the two.
Turn this guide into work done in your community
PowerUpSkool reads your Skool community and shows you daily who is going quiet, which threads need replies and what message to send. Free to start; Pro with a 15-day trial.
Keep reading
The Skool app: what you can do from mobile and what you can't
The Skool app is built for consuming the community, not managing it. Knowing exactly where that line sits saves you half an hour a day.
How to reduce churn in your Skool community
Nobody cancels out of nowhere. There are three quiet weeks before it, and they can be seen and reversed.
Invite members to Skool with CSV: prepare a safe import
A CSV invitation is more than an email: it can grant access without a purchase or membership request.
Skool course access: unlock rules and manual exceptions
Before granting an exception, identify the course rule and confirm which member needs access.