Shared meeting notes template for decisions and action items

This shared meeting notes template gives you a clear record without a transcript of every sentence. It keeps three things apart: what was discussed, what was decided and what someone agreed to do. Copy the blank version below, then look at a filled-in example and tips for writing decisions and action items.

Copy this shared meeting notes template

End with: “Next review: [date or trigger]. Corrections: [who to send them to, and by when].” The square brackets are placeholders for you to fill in. They aren't Caletus merge fields and won't create tasks.

A filled-in example from a client meeting

Here's the template filled in for a made-up client meeting. The people, decisions and dates are invented for this guide.

The team looked at three anonymized examples of users asking where to find the setup checklist. Priya said the examples point to a visibility problem but don't show how common it is. Leo asked for a small evidence review before anyone considers a redesign.

Decision: look into checklist visibility first. Leo approved the investigation, not a redesign budget or a release date. Open question: does the problem affect most new users, or only one onboarding path?

Notice what the record leaves out. It doesn't promise a redesign, claim agreement from people who weren't there, or turn a loose idea into a deadline.

Write decisions so nobody mistakes them for discussion

A discussion note might say: “The team considered moving the checklist.” A decision says: “Leo approved testing a more visible checklist link with the agreed pilot group.” The first is background. The second tells people what happens next.

Include conditions when they matter. “Go ahead after finance approves” and “Go ahead” are very different instructions. If nobody decided anything, write that down and name who needs to settle it.

Silence isn't approval. Read the decision back during the meeting, or ask the decision owner to confirm it afterward. The note owner's job is to record what happened, not to create agreement that never happened.

Write action items people can follow up on

“Look into the issue” leaves everyone guessing. “Review five approved support examples and summarize the questions that keep coming up” tells the owner what to deliver and gives the reviewer something to check.

Give each action one owner, even when several people help. Write a full date like October 9, 2026, not “next Friday,” which gets confusing once the note is forwarded. Add a time and time zone only when the deadline really needs it.

Keep proposed actions apart from accepted ones. Nobody should find a task with their name on it in a recap they never agreed to. Confirm each owner before you mark an action as accepted.

Decide who can read and edit the notes

Attending a meeting, reading the notes and editing them can be three different permissions. A client who joined the call doesn't automatically need every project note. And internal notes may hold details that don't belong in a client recap.

Share with the smallest group that needs the notes, and keep internal material out of the shared version. Link to approved files instead of pasting confidential details into a widely shared page. Review access when someone leaves the project.

When you correct the notes, keep decisions clear. Don't edit an approved decision so it looks like it always said something else. Add a dated correction instead, or use your notes tool's own revision process.

Using shared meeting notes in Caletus

Caletus's meeting tools include shared notes, and its paid plans add AI meeting notes with action items. The Caletus meeting management page shows how notes fit into a meeting.^[1][2]

Before you use them with a client, run a quick test. Have the host write some harmless notes, then ask a second person to check what they can see and edit, whether the notes survive leaving and rejoining, and where to find them after the meeting.

If the notes feature fits how you share information, use the template above inside it so every record looks the same. If you need tighter sharing limits than it offers, keep the official record in another approved tool and send people a link.

An action table in your notes won't create tasks in your project tool. Adding someone's name to a row doesn't notify them, and it doesn't mean they accepted the task. If you use AI notes, review them first with this AI meeting summary checklist.

Close the loop after the meeting

Before sharing, the note owner checks names, dates, decisions and who can see the notes. Then send a short recap that links to the record, lists the next actions and asks for corrections.

A correction request can be one line: “Please check the decision and your action by [review date], and tell [note owner] about any missing conditions or wrong details.” If a decision needs explicit sign-off, don't treat a lack of replies as approval.

At the next review, check each action against its “done when” column. Mark finished work as complete instead of deleting it, so the context stays. Carry open questions forward with an owner, or record a decision to drop them.

Good shared notes don't need to be long. They need to tell a colleague or client what happened, what's still uncertain and what each person will do next. To see where notes fit in the bigger picture, read about the Caletus meeting workflow from booking to follow-up.

• shared meeting notes
• action items
• meeting template
• client collaboration