How to stop people booking meetings outside your working hours

The fastest way to stop people booking meetings outside your working hours is to make those slots impossible to pick in the first place. Don't ask invitees to respect your boundaries by email, and don't rely on declining bad requests after the fact. Instead, define your real availability once inside your scheduling tool, store it correctly, and let the booking page only ever show open slots. When that is set up properly, a 7 a.m. or Sunday-night meeting simply never appears as an option, no matter who is booking or where they live.

Below is the full playbook: why this keeps happening, the settings that actually fix it, the timezone trap that quietly reopens your evenings, and how to handle the edge cases like one-off exceptions, urgent clients, and global teams.

Why people keep booking the wrong times

It is almost never malice. People book the times you make available to them. If your scheduling link offers 8 a.m. to 8 p.m., someone will eventually take 8 a.m. If your calendar shows free space because you blocked nothing, a colleague will drop a call into your lunch. The system is doing exactly what you told it to do, which is the good news, because the system is also where you fix it.

Three forces push meetings into your off-hours, and they stack on top of each other:

1. Loose availability windows. The default working day in most tools is wide open, and most people never narrow it.
2. Timezone mismatch. Your 6 p.m. cutoff is someone else's lunchtime. If the tool shows your slots in the invitee's timezone (which it should), a late slot for you can look perfectly reasonable to them.
3. No buffer or notice rules. Even inside business hours, back-to-back bookings and same-minute requests feel like they land 'outside' any sane working rhythm.

And much of that after-hours work is not chosen. In the same Slack survey, 54% of the people logging on outside standard hours said they did it because they felt pressured to, not because they wanted to. A booking link that quietly hands out your evenings is one more source of that pressure. Closing the slots removes the pressure at the source.

The core fix: define availability once, let the page enforce it

Every serious scheduling tool, Calenkli included, separates two things: your weekly availability (the hours you are willing to meet) and your live calendar (when you are actually busy). The booking page shows the intersection. Get the first one right and the wrong slots disappear permanently.

1. Set narrow, honest weekly hours

Open your availability settings and set the exact start and end of each working day, per weekday. If you stop taking calls at 5 p.m., set 5 p.m., not 6. If Fridays are for focus work, leave Friday closed. Be honest rather than generous: every hour you leave open is an hour someone can take. Most boundary problems are solved entirely at this step.

2. Block the rest with a recurring rule, not willpower

For protected time inside the working day (lunch, a standing focus block, school pickup), create a recurring busy event on the calendar your tool reads from, or use the tool's own blocked-time feature. The booking page treats that block as busy and skips it. You are not declining requests anymore; you are preventing them.

3. Add minimum notice and buffers

Two rules stop the 'meeting in nine minutes' problem and the no-gap pileup:

• Minimum notice (lead time): require at least, say, 12 or 24 hours before a slot can be booked. This kills last-minute requests that always seem to land at the edges of your day.
• Buffers before/after: add 10 to 15 minutes around each meeting so nothing stacks wall-to-wall and your last call doesn't bleed past closing time.
• Daily cap: limit the number of meetings per day so a single open afternoon can't become five back-to-back calls.

The timezone trap that reopens your evenings

This is the one that catches careful people. You set a clean 9-to-5, then someone in another country books you at 9 p.m. and you wonder how. The answer is almost always that your availability was interpreted in the wrong timezone, or your tool stored times loosely and shifted them.

Done right, a good scheduler stores all your availability in UTC internally and converts at the edges: your 9-to-5 stays your 9-to-5 in your home timezone, and the invitee sees the matching local times on their side. A visitor in Tokyo and a visitor in Lisbon both get accurate slots, and neither can pick a time that is outside your hours, because the conversion happens before the page is drawn.

That reminder figure matters here for a subtle reason: when you tighten your hours, you sometimes shift a few meetings to less convenient (but in-bounds) slots. Reminders keep those kept. In the Imperial study, non-attendance fell from 18.1% without a reminder to 11.2% with one. Closing bad slots plus reminding people about the good ones protects both your calendar and your attendance rate.

Handle the real-world exceptions without reopening the floodgates

Strict hours fail when they can't bend at all, so people stop trusting the link and go back to email. Build the exceptions into the system instead.

Separate event types for separate rules

Create distinct event types with their own availability. A 'New client intro' can run 9 a.m. to noon only; an 'Existing client check-in' can run wider; an after-hours 'Emergency call' type can be unlisted and shared only with the handful of people who genuinely need it. Each link enforces its own boundary, so 'available to VIPs' never means 'available to everyone.'

Date overrides for one-offs

Travelling next Thursday and only free in the morning? Use a date-specific override rather than editing your weekly hours and forgetting to change them back. Overrides expire on their own, which is exactly what you want from a temporary exception.

Qualify and redirect before the slot is taken

Some bookings shouldn't happen at all, at any hour. A pre-booking form with a few qualifying questions, plus conditional logic, lets you route people before they hold time: a prospect outside your service area gets redirected, an unqualified lead gets pointed to a resource instead of a slot, and only the right people reach your calendar. This is boundary-setting on who, not just when.

A boundary your calendar can actually keep

Telling people your hours is a wish. Removing the slots is a rule. The difference between the two is a few minutes in your availability settings: narrow weekly hours, a recurring block for protected time, minimum notice and buffers, the correct timezone, and separate event types for the genuine exceptions. Set those once and the after-hours request stops being something you decline and starts being something that never reaches you.

Pick one tool, do a single test booking from an outside browser to confirm an invitee can't reach your evenings, and you're done. The boundary holds itself from then on.