Five things worth automating in your week

Automate the boring middle

Most advice about automation aims too high. It promises that a tool will think for you, then delivers a rule that fires at the wrong time and quietly annoys everyone in the thread. The automations that actually stick are unglamorous: they remove a step you were going to do anyway, in exactly the way you would have done it.

Here are five we see teams keep for longer than a quarter.

1. The reminder nobody has to send

The single highest-return automation in scheduling is a second reminder. One reminder the day before catches the people who forgot; one fifteen minutes before catches the people who are in another meeting that has run long.

Two offsets cut no-shows more than any amount of confirmation copy. Send the first as an email, the second wherever the invitee already is — calendar notification, chat, or a message in the booking thread.

2. Buffers that defend themselves

A buffer is a rule that says: after a call of this type, do not let anyone book the next fifteen minutes. It sounds trivial until you notice how often a day becomes six back-to-back conversations with no time to write anything down.

Set the buffer on the meeting type, not on your calendar. A calendar block gets deleted the first time someone needs a slot; a rule attached to the meeting type survives.

3. Hand-offs on a schedule

If two people cover the same kind of call, the hand-off is usually a message: “can you take the 3pm?” That message is a rota in disguise, so write it down as one:

// Round-robin with a fairness window: the host who has taken the fewest
// calls in the last 14 days gets the next slot, ties broken by earliest free.
export function pickHost(hosts: Host[], now: Date): Host {
  const since = addDays(now, -14);
  const load = (h: Host) => h.bookings.filter((b) => b.start >= since).length;
  const free = (h: Host) => firstFreeSlot(h);

  return [...hosts].sort((a, b) => load(a) - load(b) || free(a) - free(b))[0];
}

The rule matters less than the fact that it is written down. A rota that lives in one person’s head becomes that person’s second job.

4. The follow-up you always mean to send

Every team has a follow-up they intend to send and often do not: the notes, the link, the “here is what we agreed”. Attach it to the meeting instead of to your memory. When the call ends, the thread already contains the agenda and the attendees, so the follow-up is a template with three blanks rather than a blank page.

If the follow-up needs a human sentence, automate everything except that sentence. Half-automation is not a compromise here; it is the point.

5. A weekly tidy-up

Once a week, something should look at the week ahead and tell you what is odd: a meeting with no agenda, a call with one attendee, three hours of interviews with no break, a booking page that is still open on a public holiday.

This is the automation people are most sceptical about and keep the longest. It does not act on your behalf. It just notices, on a Friday afternoon, the thing you would have noticed on Monday morning at 8:55.

What not to automate

Do not automate the decision to meet. Every tool that tries ends up booking conversations nobody wanted, which is worse than the friction it removed. The scheduling layer should make a wanted meeting effortless and an unwanted one obvious.