Preparing for a meeting out of your email is a retrieval job. You’re answering six short questions, and their answers were written on six different days, in threads about six other subjects. The whole pass takes about ten minutes if you run it the evening before.
- The list is the same every time. What was agreed. What you owe. What they asked and never got. What’s changed since. What you want out of the hour. What you need them to leave having agreed to.
- Retrieval is what costs. In the largest logged study of people finding things in their own mail, one look-up ran about a minute. Searching beat the elaborate folder structures people had built.
- The evening before is the one pass that can still fix something. Roughly half of what a good pass turns up is something you owe. Found at 4:30, it’s an email. Found at 9:58, it’s an apology.
- The note it produces goes in the calendar entry, because that’s where you’ll be at 9:58.
What follows is the list, the pass that answers it, the six lines it produces, and the four kinds of meeting that need a different version of the whole thing.
The six questions a prep pass answers
“Get ready for the Henderson call” is a mood, which is why prep feels open-ended. Turn it into six questions and it becomes a list you can finish. That’s the difference between ten minutes and a vague forty.
What was agreed last time, in the words that were used. Decisions in email are short and badly labeled. “Fine by us, go with option B” arrives as the fourth line of a reply about something else, and the subject line still says whatever the thread was already about. Your memory will be smoother than the record and slightly wrong. A smooth wrong memory is worse than a blank one, because you say it with confidence.
What you promised. This is the highest-yield question on the list, and the one almost everybody skips. The answers sit in messages you wrote, and your own sent mail is where they stay. “I’ll get you the revised scope by Friday” is a sentence you typed three weeks ago. It comes up at minute four, and it comes up from their side.
What they asked that never got answered. It’s a question in the third paragraph of a message you replied to on a different point. That’s the most common way a reasonable person drops a reasonable request. Find it before they repeat it. The debt running the other way, where you asked and got silence, is a different problem with different fixes, and it has its own guide in unanswered emails, and the threads that come back.
What has changed since, and which version they’re holding. The usual way a client meeting goes wrong is a mismatched fact. You’re discussing the fourth draft, they’re looking at the second, and it takes twenty minutes to surface. So the question is which number reached them, and when, and whether anything since has moved it.
What you want out of the hour. One sentence, written before you go in. If it comes out blank, that’s real information, and it’s arrived early enough to act on. A blank purpose is a shape problem rather than a preparation problem, and shape problems get solved outside the meeting. The version of this that shows up earlier, while the thing is still being arranged, is in ending the meeting scheduling back-and-forth.
What you need them to leave having agreed to. The last one was yours. This one is theirs. A decision, a document, a date, a name, an introduction. A meeting with no ask ends in “great, let’s keep in touch”, and you pay for it a month later when nothing has moved.
There’s a seventh thing, and it’s a look rather than a question. Read the attendee list first. A third name changes what you can say out loud and what you want in front of you. Sometimes it changes what the meeting is. A controller added to a scoping call means the conversation is about money, whatever the invitation says it’s about.
Why your inbox will not hand them to you
Mail is stored in the order it arrived. The archive is organized around days, and your six questions are organized around one engagement. The nearest thing to a container is the thread, and the thread leaks in every direction. The decision arrives in a forward. The number arrives as an attachment on a different thread. The constraint arrives from a third party who’s sitting the meeting out. Six questions, three or four threads, all of them filed under the day they landed.
There’s a decent measurement of what that costs. In 2011, Steve Whittaker, Tara Matthews and three colleagues instrumented a corporate mail client and logged 345 long-term users through more than 85,000 refinding actions. It’s still the largest published look at people finding things in their own mail. Two results matter here. A single finding sequence, meaning one thing gone looking for, averaged a little over a minute. And the second result is about folders. On people who build complex ones, the paper’s finding is that “these preparatory behaviors are inefficient and do not improve retrieval success”. Going through a folder “took approximately one minute, more than twice as long as scrolls, with both searches and sorts being relatively short (around 15s)”.
That was one enterprise mail client fifteen years ago, and your mailbox is its own thing. So read it for the shape rather than the seconds. The shape is what you need.
Three things follow from it.
Prep is mostly retrieval, so run it as a list of questions. A minute a look-up, six questions, a few of them needing two attempts, and most of your ten minutes is gone before you read a word for meaning. “Go and read the Henderson thread” is how forty minutes disappears. At the end of it you still can’t say what you promised.
Filing pays for something else. The folders you built answer the question you had on the day you built them. Today’s question is a different one. What pays here is being able to find things at the moment you look.
Search by person and date, not by keyword. The decision was written in whatever words that person happened to reach for, and you’re guessing at them from six weeks away. A name plus a two-week window is a set small enough to read, and a query that lands every time. Read newest first. Stop when the next message stops changing any of your six answers.
That stopping rule is what keeps this to ten minutes. A genuinely long chain is a different job, the forty-message one where you want the history rather than the current state. It has its own method and its own guide: how to catch up on a long email chain.
The pass that can still fix something
There are two prep passes, and they do different jobs. Most people only ever attempt the second one.
The first runs the evening before, or at the end of the day for everything on tomorrow. The second runs in the two minutes before the meeting starts. That one’s a refresher of a note you already wrote.
The distinction that matters is which of them can still act. Roughly half of what a real pass turns up is a thing you owe: the document that never went, the question nobody answered, the number that moved after they last saw it. Found at 4:30 the day before, each of those is an email you send in ninety seconds, and then you walk in clean. Found at 9:58, it’s an apology, and the opening of the meeting goes on your housekeeping instead of their problem.
There’s also a plain reason the gap between two meetings is the worst place in the day for this. Your attention is still in the last meeting. Microsoft’s Human Factors Lab put 14 people into video meetings wearing electroencephalogram caps and published the result on April 20, 2021. In the study, across “two straight hours of back-to-back meetings, the average activity of beta waves…increased over time”. And for the people given no breaks, “the transition period between calls caused beta activity, or stress levels, to spike” (checked September 6, 2026). Fourteen people is a small study, run by a company that sells meeting software, so take the direction and leave the magnitude.
The direction is supported by something older and more careful. Sophie Leroy’s 2009 paper in Organizational Behavior and Human Decision Processes named the effect attention residue. Its abstract describes the working day it comes out of exactly: a typical workday “entails switching between several work activities, including projects, tasks, and meetings.” Across two experiments, people struggled to “transition their attention away from an unfinished task”, and performance on the next one suffered for it. The unfinished task you carry into the 10:30 is the 10:00.
So batch it. One sitting at the end of the day covers everything tomorrow: ten minutes for a real client meeting, two for a standing one, and nothing at all for the ones where you’re a listener. The prep for a full day of meetings is one pass at one desk.
If the day genuinely has no room for that sitting, the answer is a shorter list of meetings. That’s a calendar decision rather than a preparation one.
Ten minutes, in the order that pays
Run it in this order. It’s sorted by yield per minute, so if you get cut off halfway, the parts that carry the risk are already done.
The invitation, thirty seconds. Who’s coming, how long it runs, where it happens, and whether the description says anything. An empty invitation tells you something too: the other side is still working out what this is for. Writing one that carries enough for the person receiving it is a craft of its own.
Your own sent mail to them, two minutes, newest first. You’re scanning for first-person verbs: I’ll send, I’ll check, I’ll come back to you on. Those are the commitments. They’re the one part of this list where being wrong follows you into the meeting.
Their last three messages, three minutes. Read for questions rather than for content. A question mark is the cheapest thing in the world to scan for. The unanswered one is almost always sitting in a message you did reply to.
The attachment, two minutes. The version that matters is the last one that actually left your outbox, and the date it left. What they’re holding is what you sent them, which is frequently two revisions behind the file on your own disk.
The note, three minutes. Six lines. The next section has them.
Six lines, and where to keep them
The output of the pass is short enough to read at a stoplight. Something close to this:
Henderson, Thursday 10:30, half an hour, video. Also on it: Dana, their controller.
Agreed August 14: phase two starts in October, fixed fee.
I owe: revised scope, promised August 28, never sent. Going this afternoon.
They owe: headcount for the fall, asked twice, no answer either time.
Changed: moving the start to October moved the fee. They’re holding the second draft, so the figure in front of them is out of date.
I want: sign-off on the scope, or a date by which it comes.
Six lines and a header. All of it is retrieval, because analysis is what you’re for.
Where it lives matters more than it sounds like it should. Put it in the description of the event on your own calendar. The calendar is what’s already open at 9:58, and a document in a folder is a document you go looking for. A note you have to find brings back the exact cost the pass existed to remove.
Keep it off the invitation you send other people. Half of this note is yours alone: what you owe, what you want out of the hour, and the observation that they’ve now ignored the same question twice. An invitation carries what the other person needs in order to arrive ready, which is a smaller and more generous object. Keeping the two apart is what keeps a private line about a slipped promise off somebody else’s screen.
Then the move that makes all of this compound. When the meeting ends, spend sixty seconds adding what was decided to the same note. Next time, question one is already answered in the words that were actually used. The pass for a recurring meeting collapses to two minutes and a check for what moved. That note is the only artifact in this subject that makes the next round cheaper rather than the same price again. If you’d rather it lived as a task with the thread and the files attached to it, that arrangement is described in one summary for an email thread, its files and tasks.
Four meetings that need a different pass
The six questions assume a continuing relationship with a history in your mailbox. Four common meetings break that assumption in different places.
The standing meeting. Prep is the delta since last time, and it costs two minutes because last time’s note already exists. The failure here is walking in with nothing to say, so the half hour becomes a status recital neither of you would have booked on purpose. The question that saves it is the sixth one: what do you need agreed today. If the answer comes out blank, that’s worth saying out loud, and it’s usually the moment a weekly meeting quietly becomes a monthly one.
The meeting somebody booked with you. They called it, so the six questions belong to them. The one that matters to you is why now. Read the last thing they sent, then look for what changed in their world: a deadline that landed, an invoice, a new name on their side, a project that was supposed to have finished. If it’s still genuinely unclear, ask, in a line, the day before: “so I bring the right things, is this about the October start or the invoice?” That reads as attention. The usual cause of a mystery meeting is a booking that came through a page with an empty notes field, which is one of the honest limits of booking links that show real availability.
The first meeting with somebody you’ve never written to. The archive is one message deep, so the pass is different in kind. The material is the message they did send, the referral thread behind it, and the signature block, which tells you the size and shape of the business faster than a website will. Read their single message twice. It’s usually the whole brief, and the words they used for their own problem are the words to use back at them.
The meeting you were added to. Somebody put you on a thread at message thirty and then on an invitation, and the history belongs to other people. Catching up on that thread is its own job. The prep question narrows to one thing: what specifically is being asked of you, by whom, and by when. Settle that before the meeting, in a note to whoever added you. The alternative is finding out on the call, in front of people you’ve never met.
When you have four minutes and no note
The salvage version, in order.
Four minutes: read your sent mail to that person, newest first, and stop there. It answers the one question you can’t bluff. Being vague about what was agreed is survivable and normal. Being wrong about what you promised is the failure people remember, because that’s the one that reads as not caring.
One minute: read the last message they sent you. That’s it. Leave the thread alone. You’ll get partway through and arrive distracted, and one clear fact beats half a chain.
And there’s a permission worth taking. It’s fine to ask. “Remind me where we landed on the scope” is a sentence a client hears as attention, provided you know what you owe them. What sounds unprepared is being told about your own commitment by the person you made it to. So spend your four minutes on the promises, and ask about the rest.
Reading during the meeting is the one thing that shows. Both of you can tell, and on video it’s unmistakable.
What preparation cannot rescue
Four limits, worth naming so you spend on this only what the subject repays.
A meeting that should not have been booked. A good pass makes a pointless meeting well informed, and it stays the same length. The decision about whether the hour was worth holding was made a week earlier, when the invitation went out with a blank description.
Material that never came through your mailbox. The phone call, the text message, the thing agreed in a corridor, and the message that went to your colleague. That last one is the common case in a small firm, and it’s a shared-visibility problem rather than a prep problem: when you stop having to ask who has it.
A meeting you never saw. Everything here assumes the meeting is sitting on the calendar you actually look at. When it’s on the other one, the calendars are the thing to fix first, and that’s the problem reconciling two calendars closes.
Your own attention, if the pass and the meeting are separated by another meeting. This is the residue point again, and it’s the reason the note is six lines. A note you can reread in twenty seconds survives the transition. A page of research stays on the page.
Walking in already holding it
Every one of those six questions is a retrieval question. Retrieval is the half a mailbox can reasonably do for you, rather than the half you do at 4:30 in the afternoon. That’s where Point sits.
Point is a full email client over the mailbox you already keep. The thread, the attachment it carried, the meeting it produced and the task that came out of it are one object. That’s the shape the six questions want.
Each conversation carries a plain summary, so what was agreed is a line rather than a scroll. Attachments collect in one list, each one still carrying the conversation it came in on, so which version they’re holding is a glance. An ask made of you in the third paragraph becomes a task, so it survives lunchtime. The things you handed off are tracked and brought back to you, so the two debts in the middle of the list are written down before you go looking for them. And you can go looking for something by what you remember of it rather than the exact words somebody used, which is how anybody remembers a decision from six weeks ago.
The timing is yours as well. A short briefing gathers what needs you, and you choose when and how often it arrives. So the pass that wants to happen the evening before happens the evening before, rather than in the ninety seconds you were never going to have.
Three limits worth naming.
The last two questions on the list stay yours. What you want out of the hour, and what you need agreed, are the two that make the meeting worth holding.
What can be gathered is what came through your mail and your calendar. A commitment made on the phone lives outside that, and no product is going to find it.
And Point acts as well as finds, so the autonomy setting is held per action type rather than as one switch over everything. Review is where it starts, so a drafted reply or a proposed time reaches you before it reaches a client. You raise a given kind of work once you’ve watched enough of it go out the way you’d have sent it yourself. Setting how much your inbox does on its own goes through the positions one at a time, undoing what Point did covers the record behind them and the point where an undo runs out, and benefits has the rest of it.
Common questions
How do I prepare for a client meeting when everything is in my email?
Answer six questions rather than reading the correspondence. What was agreed last time. What you promised. What they asked that never got answered. What’s changed since, and which version they’re holding. What you want out of the hour. And what you need them to agree to before they leave. Find the answers by searching on the person and a date range rather than on keywords. Read newest first, and stop when the next message stops changing an answer. It takes about ten minutes and produces six lines.
When is the right time to prep for a meeting?
The evening before, or at the end of the day for everything on tomorrow. That’s the window where prep can still fix something, and roughly half of what a real pass finds is a thing you owe: the document that never went, the question nobody answered. Found the day before, that’s a ninety-second email. Found at 9:58, it’s an apology delivered in the first ten minutes of somebody else’s meeting.
What should I do if the meeting starts in five minutes?
You’re fine. Read your own sent mail to that person, newest first, and stop there. It answers the question you can’t recover from being wrong about, which is what you promised and when. Then read their most recent message if there’s time. Leave the thread alone. One clear fact beats half a chain, and it’s fine to ask them where you left things as long as you know what you owe.
Should I put my meeting notes in the calendar invitation?
Keep them separate. The prep note is yours, and half of it is your own business: what you owe them, what you want out of the hour, and the fact that they’ve ignored the same question twice. Put that in the description of the event on your own calendar, where you’ll be at 9:58 anyway. The invitation carries what they need in order to turn up ready, which is a smaller object and a different piece of writing.
Do folders and labels make meeting prep faster?
The evidence says not much. The largest logged study of email refinding found that people who build complex folder structures do rely on them. The effort spent building them buys no improvement in whether a message is found, and going through a folder took about a minute against roughly fifteen seconds for a search. Filing answers the question you had when you filed. Meeting prep asks a question that arrived later, which is why searching on a person and a date beats any structure you could have built in advance.
How do I prep for a meeting somebody else booked with me?
The six questions assume you know what the meeting is for, so replace them with one: why now. Read the last thing that person sent, then look for what changed on their side, whether that’s a deadline, an invoice, a new name or a project that should have finished. If it’s still unclear the day before, ask in a single line what to bring, phrased around being useful. It reads as attention, and it’s far cheaper than guessing.
Why does prep never happen in the gap between two meetings?
Because your attention is still in the last meeting. Microsoft’s own EEG research reported that in two straight hours of back-to-back meetings stress-associated beta activity built up, and that for people given no breaks the transition between calls was where it spiked (checked September 6, 2026). Sophie Leroy’s work on attention residue found the same thing from the other side: people struggle to move their attention off an unfinished task, and their performance on the next one suffers. So move the pass to the evening before, and keep the note short enough to reread in twenty seconds.
The short version
Meeting prep out of an inbox is retrieval, and it goes wrong when people treat it as reading. Six questions cover almost every meeting. What was agreed. What you owe. What they asked and never got. What changed, and which version they hold. What you want. What you need agreed. Answer them by searching on a person and a date range, newest first, stopping when the messages stop changing your answers.
Run the pass the evening before, because that’s the version of it that can still send the thing you forgot to send. Write six lines. Keep them in the calendar entry rather than a document. Spend a minute after the meeting adding what was decided, which is what makes the next one cost two minutes instead of ten. Then accept three limits. A meeting that should never have been booked is still pointless once you’ve prepped for it. What came in by phone stays outside the mailbox. And the pass wants a real sitting, rather than the ninety seconds between two calls.
A coach seeing the same dozen people every month is mostly running the two-minute version, and the note carrying forward is the entire trick. A consultant walking into a client’s office with their controller in the room runs the full pass every week, and the question that earns its keep is which version of the numbers the room is holding. Everyone in the trades Point is built for sits somewhere between those, and one sentence covers all of them: know what you promised before they remind you.