WELCOME TO THE
Library
Pull something off the shelf. I write most weeks about the parts of an event nobody sees.
New on the shelf
everything on the shelf
How to manage dietary requirements at a retreat
A guest tells you at registration that she can't eat something; you send the list to the caterer, and the plated meals go perfectly. Then there's a reception with forty unlabeled things on trays. This post covers what to collect, who it goes to, and the step that catches an error before it reaches somebody.
The event planning form that replaced nine emails
Somebody on your team turns up with the wrong number, and they were told the right one in a conversation three weeks ago. This post covers why that keeps happening even when everyone communicates well, the event planning form that fixed it on a nine-hundred-person conference, and the three things that make written capture actually hold.
The event planning checklist, from first decision to debrief
Every event planning checklist you've found covers the same eight things and leaves out the twenty that actually catch people. This one runs from the first decisions through the debrief, with the real tasks in each phase and a rough sense of how far ahead to start.
Run of show meaning: the production document for your day
You've written the agenda; it covers what's happening and when, and something still feels missing when you picture the actual morning. The piece you're looking for is a separate document written for a different set of people. This post covers what goes on a run of show, who gets one, and how to build yours.
The event day briefing your team actually needs
The document your team reads over coffee the morning of decides how much of the day comes back to you. This post covers what has to be in it so that nobody needs to find you between sessions.
What belongs in your event planning spreadsheet
Everything you're currently tracking across six documents and a notes app could live in one place. This post covers what belongs in that document, how it's organized, and what it feels like to open one thing instead of six.
The event planning checklist for your last two weeks
The final fourteen days generate a lot of activity and not all of it is useful. This checklist is built around what genuinely needs confirming in that window, rather than what feels most urgent at 10pm.
Hidden event costs: the categories every template leaves out
The costs that ruin an event budget are almost never the big obvious ones. They're service charges, early load-in fees, and the categories no template thinks to list. This post covers where they hide and what to ask before you sign.
Where your speaker information lives changes everything
Bios in one folder, travel details in an email thread, slides in a shared drive nobody can find. This post covers what changes when speaker information lives in one place, both for you and for the speakers themselves.
What actually happens between "the venue is booked" and event day
Impressive names, strong bios, and a room that somehow never quite lifts. It happens more than anyone admits and it isn't about the speakers being wrong. This post covers what determines whether a lineup lands once everyone is in the room.
What event day feels like when your team has the full picture
Your team can only run the day without you if the document in front of them answers what they'll actually need. This post covers what has to be in it, what usually gets left out, and how it changes event day.
The event logistics spreadsheet your team needs to execute without you
Your team can only run the day without you if the document in front of them answers what they'll actually need. This post covers what has to be in it, what usually gets left out, and how it changes event day.
Your event has multiple versions right now. Here’s why that matters.
Your event currently exists in four places and they don't quite match: the doc you share, the notes on your phone, the vendor emails, and the version in your head. This post covers why that matters more than it seems and what to do about it.
The difference between planning your event and running your event
Connected tools and a working setup are two different achievements. This post covers how the pieces fit together so that registration, confirmations, and reminders keep moving without you remembering to push them.
The brief that lets your retreat team decide without you
A good brief tells your team what to do. A better one tells them enough to make the call themselves when you're mid-session and unreachable. This post covers the difference and what has to be in the second kind.
The five elements that make a retreat feel professionally held
Guests can always tell when an event is being run well, though most of them couldn't tell you why. This post covers the five things they're picking up on, and how each one gets built before anyone arrives.
Retreat contingency planning 101: Stay steady when things shift
Something will move. A speaker's flight, the weather, the room setup you confirmed twice. Contingency planning means deciding what you'll do about it now, rather than at 6am on event day on four hours of sleep. This post covers how.
The one document you need to keep your retreat on track
When every moving piece of a retreat lives in one document, the whole event stops depending on what you remember. This post covers what belongs inside it, how it gets built, and what changes for your team once it exists.
How to successfully execute a retreat after the planning is done
Planning ends and running begins, and the two ask entirely different things of you. Most hosts prepare thoroughly for the first and improvise the second. This post covers what execution actually requires and what to build before you get there.
How to prevent your retreat from falling apart (even if you’re a first-time host)
Something changes in a client relationship after you've been in a room together. She replies faster, refers more freely, and renews without a conversation about it. This post covers what actually happens in that room and why an afternoon does what a year of posting cannot.
A guest tells you at registration that she can't eat something; you send the list to the caterer, and the plated meals go perfectly. Then there's a reception with forty unlabeled things on trays. This post covers what to collect, who it goes to, and the step that catches an error before it reaches somebody.