WorkerKit

Travel Buffer Guardian

Blocks travel time around your flights, trains and off-site meetings, keeps those holds honest when a trip moves, and emails you a brief the night before.

Language model

Apps: Calendar, Email

About this kit

Back-to-back calendars assume you teleport. A 3:40 PM flight sits on the calendar as a 3:40 PM flight, so a 2:00 PM call gets booked on top of it and you take that call from a security line, or miss the plane.

Travel Buffer Guardian watches your calendar for anything that moves you: flights, trains, off-site meetings, anything with a real address instead of a video link. For each one it works out the door-to-door time from your home base, taking the hour of the day and how long the same journey took you last time, and blocks it as a hold on your calendar so nobody books over it.

When a trip moves, the holds move with it. The worker reads travel confirmations and change notices in your inbox, matches them to the trip, re-times the buffer, and works out which meetings now sit inside it. For meetings that need a heads-up it writes the email as a draft and leaves it in your drafts folder, so you decide whether it goes.

The evening before every travel day it emails you a brief: your leave-by time, the day in order, what is booked and sourced, and what it could not protect.

What it touches. Your calendar, to read the events around each trip and to create and re-time its own buffer holds. Your email, to read travel confirmations, send the brief to you, and draft anything addressed to other people. Optionally a chat app, for a direct message when a flight moves.

What it never does. It never moves, edits, cancels or replies to a meeting that is not its own buffer hold; conflicts get reported, not resolved. It never emails your colleagues or customers by itself: everything addressed to another person is a draft. It never invents a departure time, because every time it acts on comes from a specific booking email or calendar event it can name, and anything it worked out rather than read is labelled as an inference.

How it works

Calendar

Reads the events around every trip so it knows what a buffer would collide with, and writes the buffer holds themselves. Those holds are the only events it ever creates or changes; real meetings are read, never touched.

Email

Reads travel confirmations and change notices to learn when each trip really departs, sends the night-before brief to the mailbox owner, and saves drafts for anything addressed to other people.

App access

Calendar

Visible fields

Allowed operations

Email

Visible fields

Allowed operations

Team Collaboration

All conversations

Allowed operations

Setup inputs

Browse every worker kit