Write for the person who needs to act
A meeting recap is not a transcript. Its job is to give everyone a shared, usable account of what happened and what comes next. For a freelancer or creative team, that might mean confirming which design direction to develop, what feedback is still needed, and when a revised draft will be ready. Someone who missed the call should be able to read the recap and understand the project’s status without asking you to retell the conversation.
Send the recap while the discussion is still fresh, using the communication channel already agreed for the project. Start with the project name and meeting date, then give a one- or two-sentence summary of the outcome. Keep background details brief. If a point does not affect a decision, a deliverable or a future discussion, it probably does not need space in the recap.
Separate decisions from ideas and open questions
The most important distinction is between what the group decided and what it merely discussed. A client saying they like a direction may not mean they have approved it. Likewise, a suggestion raised on a call is not automatically a new project requirement. Put confirmed decisions in their own short section, using direct language such as “We will develop the simpler navigation option for the next review.”
If approval was not explicit, say so. You might write, “The simpler navigation option received positive feedback; final approval is still needed.” Record unresolved questions separately, along with who can answer them. This makes uncertainty visible without turning your interpretation into a commitment. If two people expressed different preferences, describe the choice that remains rather than trying to smooth over the disagreement.
Make every next step specific
A next step needs an action, an owner and a target time. “Review the mockups” is easy to forget; “Client team: send consolidated comments on the homepage mockup by Thursday” tells people what to do. For your own work, name the deliverable rather than a vague activity: “Designer: share an updated homepage mockup for review on Monday.” If a date was not agreed, label it as proposed and ask for confirmation.
Include dependencies where they matter. If you cannot begin revisions until you receive copy or image choices, state that plainly. Keep the action list short enough to scan, and use the same project terms your client recognizes. When a task belongs to a team rather than an individual, identify the person coordinating the response if possible. Otherwise, the task may look assigned while no one knows who is responsible for sending it back.
Use a repeatable recap structure
A simple order works for most creative projects: outcome, decisions, next steps and open questions. Under outcome, summarize where the project stands. Under decisions, list only confirmed choices. Under next steps, give each action an owner and target date. Under open questions, note what still needs an answer and why it matters. You can add a brief link or reference to the relevant draft if the meeting covered several versions; make clear which version the recap concerns.
For example, a recap could say: “Outcome: We are moving forward with the layout shown in draft B, pending copy review. Decision: Keep the shorter introduction and retain the existing contact form. Next steps: Designer to update the layout and share it on Monday; client to provide approved introduction copy by Friday. Open question: The final project images have not been selected.” The example is compact, but it preserves the difference between agreed work and a remaining dependency.
Invite corrections without treating silence as approval
Before sending, check names, deliverables, dates and the wording of any approval. A recap can create confusion if it confidently records a decision that was never made. Close with a straightforward invitation to correct anything you misunderstood, especially when the meeting involved several stakeholders or changes to scope. If a proposed change affects the agreed work, record it as a request to review rather than quietly adding it to your task list.
A recap is most useful when it becomes a reference for the next conversation. At the following check-in, look back at its open questions and actions before starting new topics. This small habit helps keep feedback tied to a specific draft and makes it easier to spot what is waiting on a response. The goal is not perfect meeting notes; it is a reliable record that helps everyone make the next move.
