Is a fortnightly meeting better than a weekly one?

It depends on how fast the work changes. Fourteen days suits most ongoing team and management conversations, since it allows something to finish between meetings. Weekly is better for new starters, live incidents and anything with a deadline inside the month.

Is the first and third Tuesday of the month a fortnightly cadence?

No. That rule produces 24 meetings a year rather than 26, and it leaves a three-week gap whenever a month contains five Tuesdays. A true fourteen-day cadence must be anchored to a start date and repeated every two weeks.

Why are agile sprints usually two weeks long?

Because fourteen days is long enough to deliver something demonstrable and short enough that planning, review and retrospective do not consume too much of the cycle. Keeping the length fixed also makes the work completed in one sprint comparable with the last.

What happens when a recurring meeting falls on a public holiday?

Move it by a day or two rather than skipping it. Skipping doubles the gap to twenty-eight days, which usually breaks the rhythm permanently and lets items accumulate. Shifting the occurrence keeps the following meetings on their original dates.

Fortnightly Meeting Cadence Explained

Every recurring meeting is a bet about how fast work changes. Weekly assumes a lot happens in seven days; monthly assumes very little happens in thirty. The fortnightly meeting sits between them, and it has quietly become the default cadence for one-to-ones, team reviews and software sprints because fourteen days is usually the honest answer: long enough for something to have finished, short enough that a wrong turn is still cheap to reverse.

This article covers why the interval works, where it is used, why a fourteen-day series drifts against the calendar in ways that surprise people, and how to keep one running for a year without it quietly collapsing into a monthly. To see how long is left until the next one, set a countdown to any date.

Why Choose a Fortnightly Meeting Cadence?

Because fourteen days is the shortest interval at which most knowledge work produces something worth discussing, and the longest at which a mistake is still fresh enough to fix cheaply. Weekly generates status updates; monthly generates archaeology.

There is a second, structural reason. Fourteen days is a whole multiple of seven, so a fortnightly series always falls on the same weekday and can occupy a fixed slot in the diary permanently. Nobody has to check what day it is on. That single property is why fourteen days beats ten or twenty as a working interval, despite those being perfectly reasonable numbers otherwise, and it is the same reason pay runs and bin rounds settled on it. The unit's history and definition are covered in what is a fortnight.

The Two-Week Sprint

The two-week sprint is the most common iteration length in agile software teams, and the reasoning behind it is the same. A sprint has to be long enough to deliver something demonstrable after planning, building and testing, and short enough that a full planning, review and retrospective cycle does not consume a disproportionate share of it.

Fixing the length matters as much as choosing it. Because every sprint is the same fourteen days, the amount of work completed in one can be compared with the last, which is the only reason velocity means anything. Teams that stretch a sprint to finish an unfinished item lose that comparability immediately. Holding the boundary and letting work roll over is almost always the better trade.

Fortnightly One-to-Ones

A fortnightly one-to-one is the standard compromise in management: frequent enough that problems surface before they harden, infrequent enough that the conversation has substance rather than a recital of the week's calendar.

The interval is not universal, and the exceptions are predictable. Weekly suits new starters, anyone in a role that has just changed, and anyone in difficulty, because the support has to arrive faster than the problems do. Monthly suits senior, stable reports who mainly need unblocking rather than direction. The default sits at fourteen days because most reports, most of the time, are neither of those cases. The rule of thumb worth holding is that the cadence should be set by the rate at which the person's context changes, not by the manager's diary pressure.

Why a Fortnightly Meeting Series Drifts Against the Calendar

Because 26 occurrences a year cannot be distributed evenly across twelve months. Ten months will contain two meetings and two will contain three, and which months those are changes every year, since 26 fortnights cover only 364 days and each series slips a day or two earlier annually.

This produces the most common scheduling mistake in the whole subject: setting a rule such as the first and third Tuesday of the month and believing it is a fortnightly cadence. It is not. That rule yields 24 meetings a year, and in any month with five Tuesdays it leaves a three-week gap between the third Tuesday and the next month's first. If you want fourteen days, you must anchor to a date and repeat, not anchor to the month. The underlying arithmetic is in how many fortnights in a year.

How to Keep the Cadence on Rails

Most fortnightly series decay into monthly ones within a year, and always for the same handful of reasons. These are the practices that prevent it:

Anchor to a start date: create the series as repeat every two weeks from a named date, never as a monthly rule with two dates in it.
Move, do not skip: when a meeting collides with a public holiday, shift it by a day or two. Skipping turns fourteen days into twenty-eight and the rhythm rarely recovers. Local councils do the same thing with fortnightly bin collections at Christmas, shifting the round rather than cancelling it.
Keep a rolling document: one running agenda that both sides add to between meetings, so the first ten minutes are not spent remembering what happened.
Log decisions, not discussion: a fortnightly series accumulates 26 conversations a year, and without a decision log the same question returns every third meeting.
Check the clock change: a fixed weekday slot shared across countries moves by an hour when daylight saving starts and ends on different dates in each, so revisit international slots in spring and autumn.
Review the cadence twice a year: ask whether fourteen days is still right rather than assuming it. The interval should be a decision, not an inheritance.

When Fourteen Days Is the Wrong Interval

It is wrong whenever the rate of change does not match it. Live incidents, launches and anything with a deadline inside a month need weekly or daily contact, because a fortnightly rhythm will deliver its next checkpoint after the moment it could have helped.

At the other end, governance meetings, board reporting and strategic reviews usually want monthly or quarterly spacing, since the underlying numbers do not move meaningfully in fourteen days and a fortnightly version of them simply generates reporting work. Note too that the word itself is regional: American colleagues will read biweekly, which unhelpfully also means twice a week, so write every two weeks in any invitation crossing that divide. The vocabulary question is covered in fortnight in British and Australian English. To count the exact days between two occurrences, use the fortnight calculator, or check where the current cycle sits on the current fortnight tracker.

Conclusion

A fortnightly meeting works because fourteen days is long enough to produce something and short enough to correct something, and because a multiple of seven holds a fixed weekday slot forever. Anchor the series to a start date rather than to the month, move it around holidays instead of skipping, keep a rolling agenda and a decision log, and accept that two months a year will contain three meetings. Set a countdown to any date to see how long is left until the next one, or explore the rest of fortnight.now.

Fortnightly Meeting Cadence: Why Two Weeks Works