How to prepare for a client call in five minutes

Preparing for a client call can take five minutes if the notes from last time are in order: open the right account, reread the last meeting's decisions and action items, check your own, decide what you need from this call, and close the previous client's windows. This guide is for freelance developers and consultants who move between several clients' calls on Google Meet and Microsoft Teams in one day. It covers a minute-by-minute routine, the three questions to answer before joining, a longer checklist for calls that matter, and how to keep one client's context out of another's meeting.

What can you do in five minutes before a client call?

Five things, one a minute. The point is not to read everything; it is to arrive knowing what was agreed, what you owe, and what you want.

Minute	What to do
1	Open the right account or browser profile and the meeting link. Check it is the client's account, not yours
2	Read the last meeting's decisions and action items. Only those, not the whole notes
3	Check your own items: done, not done, and the reason for anything late
4	Write down the one thing you need from this call, and the one thing they are likely to ask you
5	Close the last client's tabs, editor windows and chat. Join a minute early

Minute five is the one people skip. It is also the one that prevents a screen share showing another client's repository, dashboard or name.

What three questions should you answer before you join?

What did we agree last time, what do I owe them, and what do I need from this call. If you can answer all three, you are prepared for a routine meeting.

1. What did we agree last time? The decisions and the dates, in a sentence each. If you cannot find them in a minute, your notes are the problem; notes for recurring client meetings has a format that puts them at the top.
2. What do I owe them, and is it done? Your action items, with their due dates. Anything late gets a one-sentence reason and a new date, ready to say.
3. What do I need from this call? One thing: a decision, some access, an answer to an open question. Write it where you will see it during the call. If the call ends without it, ask before anyone leaves.

The third question is what turns a status call from a report into a meeting. Running a weekly client status meeting shows how to frame it as a decision with options.

What do you say if you are late on an action item?

Say it first, before anyone asks, with the reason and a new date. Waiting to be asked turns a delay into a discovery.

A script that works:

"Before we start: I said I'd have the export on staging by Tuesday. It isn't there yet, because the bank's file format changed and the import needed rework. It will be on staging by Thursday, and I'll message you when it is."

One sentence for what, one for why, one for when. No long apology, no detail about the code unless they ask. Then move on to the agenda. If the delay touches something the client is waiting on, say what it affects: "That means the review on Friday will show the import but not the export."

What is the longer checklist for a call that matters?

Twenty to thirty minutes, for a kickoff, a sprint review, a renegotiation, a call with a new stakeholder, or a conversation you expect to be difficult.

• Read the last two or three meetings' notes, not just the last one, and the decision log if you keep one.
• Check email and chat since the last call for anything promised outside a meeting.
• List who is attending and their roles. Note anyone new, and check how their name is spelt and said.
• Prepare the numbers you may be asked for: hours used, dates, budget spent, how many requests are open.
• Decide your ask and your fallback. "I need the test account this week; if not, I need someone to own getting it."
• List the questions the client asked last time that you have not answered yet.
• For a demo, check staging, the demo data and screen sharing on the device you will use. The sprint review guide has the rest.
• Decide in advance what you will not agree to on the call, and the sentence you will use. The scope creep guide has several.

For a first meeting after signing, the kickoff agenda replaces most of this list.

How do you prepare when there are no notes from last time?

Rebuild what you can, then ask. The email thread, the calendar invitation and any messages since the call usually hold the decisions; the action items are harder.

Open the meeting with a short recap and invite correction: "As I remember it, last time we agreed to start with the import, and you were going to check the year-end dates. Have I got that right?" Clients respect the question, and correcting a recap takes them thirty seconds. Whatever they say becomes the first lines of this meeting's notes, and this time you keep them. Taking notes while running a video call helps when you are the one talking.

How do you keep one client's context out of another client's call?

Separate the accounts, close the windows, and leave a gap between calls. Back-to-back meetings for different clients are where context leaks: a tab left open during a screen share, a notification with the other client's name, an example from the wrong project.

• One browser profile per client account. It keeps sign-ins, tabs and history apart; managing several Google accounts covers the setup.
• Close, do not minimise. Before a screen share, close the last client's editor windows, dashboards and chat. Share a single window rather than the whole screen when you can.
• Silence notifications during calls, so a message preview from Client A cannot appear while Client B watches.
• Never use one client's work as an example in another's call, even anonymised. The other client will recognise the shape of it sooner than you expect.

The wider habit is in keeping client meeting notes separate.

How does TrackHeros help you prepare for a client call?

TrackHeros is an AI meeting notetaker that keeps each client's Google Meet and Microsoft Teams meetings in a workspace of their own, so the last meeting's notes are already where you need them. The unified calendar shows every connected calendar's meetings in one read-only view, labelled and coloured by client, and the Analytics page lists the next 7 days and the action items due.

Each meeting's notes have the same shape, so minute two is the same every time: decisions, then action items, each with the owner as heard and the due date as it was said, resolved to a date. The "Action items" page lists everything committed to across every client, labelled with its client and the meeting it came from, with an owner filter that starts on "Assigned to me". That answers "what do I owe them?" for every client at once, each row kept to its own client.

For anything more, open the client and ask: "what did we agree last time, and which action items were mine?" The answer comes only from that client's meetings, with citations to who said it and when, and each citation plays the recording from that moment. You can dictate the question instead of typing it; the audio is not stored. There are no credits to spend on asking. More at ask your meetings and action items.