Scheduling checklist

Operational meeting scheduling checklist

Most meeting failures happen before the invite is sent. This checklist runs in under two minutes and catches the silent issues — wrong DST week, working-hours conflict, missing recording default — that cost the most.

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

1. Confirm every attendee's local time

Render the proposed slot in each attendee's local time using the meeting planner. If anyone lands before 08:00 or after 18:00 local, escalate before sending.

2. Check the DST week

If the meeting falls in the two weeks where US and EU DST switches differ, the time shifts by an hour for one side. Confirm against the world clock before sending.

3. Check regional holidays

Run the business-days calculator against the team's holiday list. A meeting on a regional holiday gets quietly skipped — usually by the most important attendee.

4. Decide the recording default upfront

Any cross-region meeting where one side is dialing in outside 08:00–18:00 local should record by default. Set it before the invite goes out, not after the first complaint.

5. Pin to the workspace

Save the slot and group to the workspace so the next iteration restores in one click. Recurring invites compound only when they're restored, not rebuilt.

Frequently asked

How long should the checklist take?

Under two minutes once the team's city group is saved. The first run takes longer because you're building the substrate; every run after that is fast.

Do I need to run it for every meeting?

For recurring slots, run it once and re-audit monthly. For one-off cross-region meetings, every time — that's where silent failures hide.

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.