Recurring scheduling

Recurring workflow scheduling best practices

Recurring scheduling fails quietly — a DST shift moves a call by an hour, a holiday lands on a payday, a teammate's region changes. A few practices stop the silent failures.

Jump straight into the matching tool — your inputs stay private to your device.

Anchor recurring slots in UTC

Local-time recurring rules drift twice a year because of DST. UTC anchors stay stable, and each region simply renders the local equivalent. Use the meeting planner to publish both views.

Audit the two DST weeks every year

The two weeks where US and EU DST switches don't align silently move every transatlantic recurring meeting by an hour. Pre-check those weeks in March and October and broadcast adjustments early.

Tie recurring deadlines to business days, not calendar days

'Every two weeks on Friday' breaks the moment a holiday lands on Friday. Use the business-days calculator to express recurring deadlines in working-day terms so the cadence survives holidays.

Store the recurrence — don't rebuild it

Save the recurring slot, the city group and the deadline cadence in your workspace. Restoration is the entire point of recurrence: the workflow should resume on its own.

Frequently asked

Should every recurring meeting be in UTC?

The source of truth should be UTC. Display whatever local time matches the audience — but the rule itself stays in UTC.

How often should I audit recurring schedules?

Monthly is enough for most teams, plus the two DST weeks. Anything more frequent is usually a sign the underlying structure (group, working hours) needs updating.

Related guides

Keep going

Related tools

Continue your workflow

Pick the operational workflow that fits — your saved setups, recent tools and shared schedules stay in sync.

Save this workflow to your workspace

Continuity across sessions — your saved setups, recent tools and shared schedules in one calm operational space.