The meeting starts in ten minutes. What do you need to know?

The invitation says “Catch-up.” The person’s name is familiar. You have worked together for months, but the detail you need is somewhere in an email, a message and the notes from the last call.

Reading everything is an appealing form of procrastination. It feels like preparation, yet you can arrive knowing the history and still miss what has changed.

A meeting brief should earn its space on your screen. When you glance at it, it should tell you what today’s conversation needs to settle, what the other person is expecting, and which assumption you should check before proceeding.

The following ten-minute routine is an editorial workflow, not a tested speed claim. Use it for a returning client, colleague or collaborator. The names and exchanges in the worked example are fictional.

Start with the decision at the end

Complete this sentence: “By the end, we need to know…”

For our example, consultant Maya is meeting client Arun about a research project. “Catch up on research” is too broad. Her actual finish line is: “Decide whether to keep the interview dates after the budget review moved.”

That sentence helps her ignore irrelevant history. She needs the interview dependency, the latest budget timing and the person who can authorize the next step. She does not need to reread the original sales conversation.

Atlassian’s page-led meeting guidance similarly starts with written purpose, scope and desired outcome. That is a useful practitioner model; it is not evidence that this particular ten-minute brief will make every meeting faster. [1]

Minutes zero to three: find the last commitment

Search for the last exchange about the decision, then read the messages around it. A sentence containing a date can describe an offer, a reservation or a confirmed deadline. Preserve that distinction.

Maya finds three items:

The latest message does not replace the other two. It changes how they fit together. The interview dates remain relevant, but their status has changed from a scheduling detail into today’s decision.

Record a source and date beside a consequential fact. A link to the whole inbox is little help. A link to the exact exchange lets you recover the wording when someone remembers it differently.

Minutes three to six: check what became stale

Look for changes to the situation rather than collecting more background. Has the budget moved? Is the person you expect to meet still responsible? Is another participant now needed? Did somebody reply after the last summary was written?

Use three plain labels: confirmed, proposed, unknown. They need not become a complicated tagging system.

“Finance review is Tuesday” is confirmed by Wednesday’s message. “Start with three interviews” is Maya’s proposal. “Arun can approve that option without Finance” remains unknown. Promoting the third item to a fact would make the brief look more complete and the meeting less accurate.

If an important detail cannot be verified in the time available, turn it into an opening question. That is a useful result of preparation. A blank with a clear question is easier to work with than a confident guess.

Minutes six to eight: write the brief

Here is Maya’s finished version:

Purpose: Decide whether to keep the interview dates after the budget review moved.
Last commitment: Dates were held pending approval, not confirmed. Arun’s Monday email.
Changed since then: Finance review is now Tuesday. Arun’s Wednesday message.
Our open offer: Three interviews as a smaller first step. My Thursday email; no acceptance found.
Question to settle: Can we authorize the smaller start, or should we move the interviews?

That is enough to begin. It does not pretend to predict Arun’s answer.

The brief worksheet contains these fields and an empty version. You can use it in a document, a note or whatever meeting system your team already maintains. There is no requirement to create another dashboard.

Add a personal detail only when it genuinely belongs in the conversation. A book recommendation you were asked to send might be helpful. A collection of sensitive observations about someone’s private life is not a preparation shortcut.

The last two minutes: choose the first question

Maya’s opening could be: “I saw Finance moved the review to Tuesday. Shall we decide whether the smaller interview group can start, or whether we should move the dates?”

She is bringing context while leaving room for new information. If Arun says the budget was approved that morning, the brief has still worked: it surfaced the changing dependency immediately.

Compare that with “Are we still on for the interviews?” The shorter question hides the approval condition and may produce a quick yes from someone thinking only about calendar availability.

Good preparation often changes one question rather than producing a longer script. Leave space to listen once the meeting starts.

Keep the brief private; share the decision

A personal prep note can include questions you are still checking. It should not automatically become the shared record. After the conversation, write the agreed outcome, owner and next date in the appropriate shared place. Keep any unresolved item visibly unresolved.

For the source-finding part, Kluro’s preparation workflow brings earlier exchanges and open promises back into view. Use the original message when wording matters. Copy the worksheet into the place you use for your own preparation.

At the end of the call, the brief should be out of date in a useful way: the question has an answer, or the next step has an owner. That is the moment to write the follow-up, rather than preserving the prep note as though it were the final decision.

About the example

The scenario and time allocation were written for this article. They illustrate a source-first approach; no client record, productivity experiment or measured time saving is represented. Product references were checked against Kluro’s published preparation page and current repository. [2]