October calendar: five Thursdays and one clock change

October is the month where a calendar that has been behaving all year quietly stops matching reality. Two things cause it, and neither is visible in a month grid. The month contains five of some weekdays and four of the others, which throws off any commitment counted as "four times a month". And in its final week, clocks in Europe have already gone back while clocks in North America have not, so recurring meetings between the two shift by an hour for one side. Both are predictable. Both are worth handling before the month starts rather than during it.

The shape of the month

October 2026 runs from Thursday 1 October to Saturday 31 October. Thirty one days, laid out across five rows of a month grid.

That start and end produce an uneven week count:

Weekday	Times it occurs in October 2026
Thursday	5 (1, 8, 15, 22, 29)
Friday	5 (2, 9, 16, 23, 30)
Saturday	5 (3, 10, 17, 24, 31)
Sunday to Wednesday	4 each

Anyone with a standing Thursday commitment gets an extra one this month. Anyone whose reporting or invoicing runs on Mondays gets the usual four. The imbalance is ordinary arithmetic, but it lands on the parts of a schedule that were never counted precisely in the first place: a weekly one to one, a Friday deployment window, a Saturday class.

In Japan there is exactly one public holiday in the month. Sports Day falls on the second Monday of October, which is 12 October in 2026, and it is one of the holidays fixed to a weekday rather than a date. That is worth knowing if a holiday feed is being relied on, because a holiday that moves each year cannot be hand entered once and forgotten.

Five Thursdays, and where the extra one goes

The practical consequence of an uneven month is that capacity planning built on "four weeks" runs short by one occurrence for three of the seven weekdays.

A weekly sixty minute meeting on a Thursday costs four hours in a normal month and five in this one. Three Thursday commitments cost fifteen hours rather than twelve. That extra three hours has to come from somewhere, and because nothing on the calendar announces it, it comes out of whatever was not booked: the focused work, the buffer, the travel.

The fix is to count before the month rather than after it. Switch to a month view, count the occurrences of each recurring commitment, and compare the total against what the month was assumed to hold. Anything that turns out to run five times either gets one instance cancelled deliberately or gets accepted as a real cost. What should not happen is the third option, where the fifth occurrence silently displaces something that was never scheduled and therefore never missed on paper.

There is a related trap at the end of the month. October has 31 days and November has 30, so anything set to repeat on the 31st has no matching date next month. Different systems resolve that differently, with some falling back to the last day of the following month and some skipping it entirely. A monthly task that quietly disappears in November usually started life on an October 31st.

The same arithmetic works in the other direction for anything billed or delivered monthly. A retainer covering four sessions is exposed in a five week month. A subscription that renews on the 31st has no equivalent date in November. Both are small, and both are the kind of small thing that produces an email exchange nobody wanted.

The last week is when meetings across borders move

This is the part that costs the most and gets noticed the least.

In the United Kingdom and across the European Union, clocks go back on the last Sunday in October. In 2026 that is 25 October. In the United States and Canada, daylight saving time does not end until the first Sunday in November, which in 2026 is 1 November. Japan does not observe daylight saving at all, so its offset never changes.

From 26 October to 31 October, the usual gap between Europe and North America is therefore one hour different from what it has been all summer, and different again from what it will be in November.

A recurring event stores a start time and a time zone. When the zone shifts, the event keeps its local time in the zone it was created in and moves for everybody else. A weekly call created at 16:00 London time stays at 16:00 in London through the change and lands an hour earlier for a participant in New York during that one week. A call created at 09:00 New York time stays at 09:00 there and lands an hour later in London. Which way it moves depends entirely on where the organiser was when the series was created, which is not something most attendees know.

Three things make this survivable:

Find the series before the week arrives. Any recurring meeting with participants in a different daylight saving regime is a candidate. There are usually fewer than ten.

Check the time zone stored on the event, not the time displayed. The display is converted for the viewer and looks correct in every zone. The stored zone is what determines who moves.

Decide once, in writing. Either the meeting keeps its time for the organiser and everyone else absorbs the shift, or the series is moved for that week. Saying nothing is the option that produces two people on a call and two people who thought it was an hour later.

For anyone whose week regularly spans time zones, showing a second zone alongside the main one turns this from a calculation into something visible on the grid. The Features page covers where that setting lives.

Where October sits in the working year

The month is dense for reasons that have nothing to do with its length.

For organisations on a calendar year, October opens the final quarter, which means the last full quarter to affect the year's figures. For Japanese companies whose financial year starts in April, 1 October opens the second half, which brings its own round of reviews and target setting. For anyone in education, the autumn term is fully underway. The result is a month that collects planning meetings, budget conversations, and reviews on top of the ordinary load.

That has a specific effect on a calendar. Planning meetings are scheduled by other people, land in whatever gaps exist, and tend to be an hour long by default. A month that begins with several open afternoons ends with none, and the change happens through individually reasonable decisions. The only defence that works is to book the work before the meetings arrive, because an empty slot is treated as available by every scheduling tool ever built.

Doing that requires knowing what actually needs doing in the month, which is why counting the recurring load first matters. The two exercises are the same exercise.

Getting an October calendar onto a Mac

There are three ways to have the month in front of you, and they suit different purposes.

A subscribed holiday calendar is the most reliable way to get public holidays right, because the feed updates when the dates move. Subscribed feeds are read only, which is the correct behaviour: nothing local should be able to edit a national holiday. Adding one is a one time action that keeps working in later years.

Google Calendar covers the browser case, with one limitation worth stating exactly. Its own documentation says:

While you can't download and install Calendar on your computer, you can use it offline.

Offline use is Chrome only. Google's support pages state that offline access is not supported in Firefox, Safari, or Microsoft Edge. Creating a new calendar is also browser only, so a plan to separate October's project work into its own colour coded calendar has to start in a browser tab even if the day to day viewing happens elsewhere.

A native calendar app for Mac covers the third case, which is having the month available without a tab, with keyboard access and a menu bar entry. Which of the three is right depends less on features than on how often the month gets consulted. A month checked twice a day belongs somewhere that opens instantly.

Making thirty one days readable

A month grid with five rows and a full schedule turns into a wall of text. Three adjustments help more than any others.

Colour by category, not by calendar. Most people colour by account, which produces two or three colours and no information. Colouring by what the block is for, such as external meetings against internal against focused work, makes the shape of the month visible at a glance.

Use a custom range instead of the month. A view set to two or three weeks shows enough of October to plan against while still showing times of day, which a month view does not. Google Calendar allows a custom range in view options, and most native calendars allow the number of days to be set directly.

Print from a range, not from the month. A printed October is still the fastest way to plan with someone who is not looking at the same screen, and a printed month view usually loses the times. Printing two weeks at a time keeps the hours legible on a single sheet, which is what makes the printout useful rather than decorative.

Accept that side by side does not work above the day view. Google's documentation is explicit that side by side calendars are unavailable in week and month view. Anyone trying to compare two people's Octobers in a month grid is attempting something the tool does not do, and the time is better spent on a day view or on a shared availability check.

Entering the month's commitments is its own bottleneck, particularly in a planning heavy month where events are agreed verbally and typed up later. Writing a full sentence and letting it become an event, rather than filling a form per item, is the difference between capturing an agreement in the meeting and capturing it that evening from memory. The Entering events page shows what that looks like.

What to change first

Before 1 October, do two counts. Count how many times each recurring commitment falls in the month, and mark the ones that occur five times. Then list every recurring meeting with someone in a different daylight saving regime and decide, in writing, what happens to it in the week of 26 October. Both take fifteen minutes and both prevent problems that are much more expensive once the month has started. If the second count keeps producing the same headache every spring and autumn, Caltimate shows a second time zone next to the main one so the shift is visible rather than calculated.