Coordination Call Recap: Turn Notes Into Action Items

This happens after almost every coordination call. Six people spend 40 minutes finding a real problem, and the call ends with a plan that is not written down anywhere. Today's situation is a cross-team coordination call. Your team reviews a clash between the ductwork and the ceiling on level three, and the room agrees on a fix. The call goes well. What you do in the next 10 minutes decides if the team acts on it or forgets it.

Start with the facts. State what was reviewed and what was found, in one or two sentences, no more. We reviewed the ductwork clash on level three. We agreed on a fix before it reaches fabrication.

You do not recommend that someone send a recap. You own it, and you send it yourself, right after the call. To confirm we are on the same page and can meet our dates, here is a recap of today's coordination call. That line does the confirming for you. It tells the room this is a record of what people agreed to. It is not a request for approval.

PMs often skip the next step. Doing it well is what gets the reply. Every owner and every date in this recap was confirmed out loud in the meeting, so the message records what people agreed to in the room. This recap asks for explicit confirmation, since the fabrication date is expensive to lose and the building owner sits outside the team. Reply to confirm your item and date, or flag it now if that date does not work. A routine update inside a team with an established process can use a shorter form instead. Reply with corrections by tomorrow at 5 PM your time, or the plan moves ahead as written.

Here is the same recap, phrase by phrase, so you can hear why each part is there. Open by confirming you are on the same page and can meet the dates, before anyone has to ask. To confirm we are on the same page and can meet our dates, here is a recap of today's coordination call. This line makes the recap a record of what was agreed. Nobody has to guess whether it is open for debate.

State the facts in one sentence. We reviewed the ductwork clash on level three and agreed on a fix before it reaches fabrication. Notice this sentence does not explain the whole meeting. It names the topic and the outcome. That is enough.

Now the three action items, and this part makes the recap something people can act on. Each item gets an owner, a task, and a date. 1. I will issue the revised routing by Wednesday. 2. Structural will confirm hanger clearance by Thursday. 3. You will confirm the ceiling height change with the owner by Friday.

Two phrase swaps for that pattern, so you can adapt it to your situation. 1. Instead of I will issue, you can say I will send or I will have ready. 2. Instead of will confirm, you can say will verify or will sign off on. Keep the structure the same. Owner, task, date. That structure is what makes the sentence easy to scan when nobody has time to read carefully.

Close with the reply request. Reply to confirm your item and date, or flag it now if Friday does not work. This sentence asks for a reply, which most recaps don't, and it gives people a chance to raise a problem early, before Friday.

One more line, optional but useful when the group is larger or the stakes are higher. I will track all three until they close. That sentence tells the team you'll keep following up, and people reply honestly when they know someone is tracking deadlines.

Two things to avoid. 1. Do not write a recap that reads like meeting minutes, a list of everything anyone said. Nobody replies to that, because nothing in it asks for anything back. 2. And do not soften the reply request into an apology. Sorry to bother you, but could you confirm when you get a chance? That kind of line trains people to treat your deadlines as optional. Reply to confirm is not rude. It is clear.

Now let's practice. I'll say a short phrase, then pause. Repeat it out loud in the pause. This first round is slow, full forms, no contractions.