How to Prepare for a Meeting Quickly: A 90-Second Checklist

Every serious prep framework lands on the same three questions. What did we discuss last time. What did I commit to. What does a good outcome look like today. The advice stacked around them is mostly agendas, invites and timeboxing, written for whoever called the meeting. Follow it when the meeting is yours. It is not much use at 1:58 for a two o'clock somebody else booked.

Of the three, the third is free. You decide it on the walk over. The first is usually recoverable: scroll the thread, open the calendar entry. The second is different. A promise you made and forgot is the only one that can cost you something, and it's the one your systems are worst at holding.

Here's the version that fits in the walk from your desk to the room. It assumes you didn't call this meeting. Run it in order.

• Ten seconds, the outcome. Finish this sentence: I'll be happy if we leave having decided X. If you can't finish it, say so in the first minute.
• Twenty seconds, the invite. Purpose, who is actually coming, and whether a document is attached that everyone will assume you read.
• Twenty seconds, last time. Not the whole history. The state you left it in, and whatever was still open when you stopped talking.
• Thirty seconds, what you owe them. Every promise you made since you last spoke, and whether you put a date on it. This is the step that goes wrong.
• Ten seconds, your one question. Write it down. It's the first thing to fall out of your head when the meeting opens on somebody else's agenda.

Four of those five come out of something you can open. A calendar entry, a thread, an attachment. The fourth doesn't. Nothing you own holds the sentence you said out loud at minute forty-seven, so a routine that looks complete still leaves you exposed on the one line that costs you.

With your own manager, and more so with theirs, the exposure is time. You get asked about something you raised six weeks ago, in a conversation neither of you wrote down. Spend the thirty seconds on your commitments, not a status update.

With a client or a prospect, spend it on their objections. What they pushed back on last time is what they'll push back on again, and repeating an answer they already rejected is worse than having none ready.

When the meeting is yours, the advice everybody gives is suddenly the right advice. Put the outcome at the top of the invite. Keep the topics short enough that people read them. Send it early enough that someone can tell you it's the wrong meeting. Running a meeting is a different job from walking into one, and conflating the two is why so much prep advice misses.

And if you were added to an invite with a two-word title, the fastest prep isn't research. Ask the organiser what they want out of it. Occasionally it cancels the meeting.

Think about where you actually make commitments. The last two minutes of a call, after the agenda is done and everyone's relaxed. In a hallway, on the way out. On the phone in the car. Those are the moments people say "sure, I'll send you that" and mean it, and they're all moments where typing is impossible or rude.

So look at what your tools hold. Email has what was written down, a fraction of what was agreed. The CRM has the four lines somebody logged on a Friday. The calendar knows when, not what. The commitment you made at minute 47 exists in two places: your memory and theirs. Only one of you is going to bring it up, and it won't be you.

The standard fix is to write it up straight afterwards. Good advice, and it fails for a boring reason. The minute after a meeting is the minute the next one starts. Which is why prep keeps looking like a memory problem when it is really a recording problem.

Connect a calendar, a CRM and an inbox, and half an hour before each meeting a brief lands in your inbox or Slack. Who's coming, deal stage, open tickets, and a prior-interactions section. For attendee research it beats anything you'd assemble by hand.

The prior-interactions section is the one you care about, and it's built on sand. It replays what was logged, which is a polite way of saying it is empty when you logged nothing. So the brief is thinnest for the meetings you needed it for most.

• Prep agents and briefing assistants. Excellent at who, and at where the deal stands. Blind to anything that only ever existed as speech.
• Meeting bots and notetakers. A solid record of a scheduled video call. They can't join a phone call, a coffee, or a chat in someone's office.
• Your inbox and the CRM notes field. Both assume a version of you who writes things up on Friday. That version does not exist.

Worth saying plainly: Pastok does none of the research half. No calendar connection, no CRM, no LinkedIn lookup, and no idea you have a meeting at two. If you need background on a stranger, use one of the tools above. What follows solves the other half.

If the missing input is what was said, the work happens in the previous meeting, and it has to ask nothing of you while the conversation is running.

Pastok records from the Apple Watch. You start it, it never starts on its own, and once running it keeps going passively until you stop it. No bot joins and nothing is installed on anyone else's device. It works the same for a video call, a phone call, or two people in a room.

If you don't wear a Watch, the same session starts on the iPhone, and a running session hands over between the two in either direction. The wrist is still the version that survives a whole working day. A phone sits in a pocket, and its battery is already spoken for.

The consequence is what you don't have to do. At minute 47, when you say you'll send the revised timeline by Thursday, you do nothing. No phone, no note, no wrap-up ritual. The sentence is on the record in the words you used, and it comes back as a transcript, an activity entry, highlights and action items.

On recording other people: say you do it, say why, and say what you keep. It is a smaller conversation than it feels like the first time. Where something is told to you in confidence, don't record it.

The thirty-second step stops being recall and becomes a lookup. Because the search matches meaning rather than keywords, you don't have to remember the phrasing anyone used. Standing outside the room, phone in hand, one question:

• "What did I promise on the last call with this client, and did I put a date on it?"
• "Everything still unresolved from my last two conversations with my manager."
• "What did they push back on last time, in their words?"

If you'd rather not do even that, put it on a schedule. A Skill is an instruction you write once in ordinary language. It runs on demand, on a schedule, or when Pastok detects a particular kind of conversation. Monday at eight: "For everyone I spoke with in the last two weeks, list what's open and what I said I'd do."

Count the actions and it's two. Start capture when the meeting starts, ask one question before the next one. It's worth it where a relationship runs across many conversations: recurring clients, your manager and theirs, hiring loops. If everything important already lives in one short email, the email is enough.

Nobody disagrees about the five steps. What nobody solves is where the fourth answer comes from when the promise was spoken and never typed. Fix that one meeting earlier and the ninety seconds get easy. Not a scramble through threads, but a straight answer about what was said.

• AI meeting notes for consultants
• Communication skills self-evaluation
• AI meeting recorder for in-person meetings