A Confluence meeting notes template is a reusable page layout for recording the purpose, attendees, discussion, decisions, and follow-up actions from a meeting. You can copy the blank template below into a Confluence page, then save it as a reusable page template if your space and permissions allow.
What a Confluence meeting notes template does
A template gives meetings a consistent structure without deciding what the group must discuss. Instead of starting with a blank page, the note-taker gets prompts for details that are easy to forget, such as who owns an action and when it is due. Consistent notes also make it easier for someone who missed a meeting to find the decision or next step later.
In Confluence, a meeting-notes layout can be an ordinary page that people duplicate, or a page template available when creating a page. The exact template options and page-creation controls can differ by Confluence version, space configuration, and permissions. A simple copied page works too; a formal template is mainly useful when the same format will be used repeatedly.
Meeting notes are a practical record, not necessarily a word-for-word transcript. They should help readers understand what happened and what happens next. Keep the level of detail appropriate to the meeting, and avoid recording sensitive or irrelevant personal information.
Confluence Meeting Notes Template
| Field | Meeting details |
|---|---|
| Meeting title | |
| Date and time | |
| Location or meeting link | |
| Facilitator | |
| Note-taker | |
| Attendees | |
| Purpose and desired outcome | |
| Agenda topic | Owner |
| Discussion notes | |
| Decisions | |
| Action item | Owner and due date |
| Open questions or risks | |
| Next meeting |
Filled-in sample
Sample only; all details are fictional. For a weekly planning meeting, the title might be “Project Northstar — Weekly Planning,” with the date “12 May,” facilitator “Mina Lee,” and attendees “Mina, Dev, Sam.” The purpose could read: “Agree on the order of work for the next sprint.” Under decisions, record “Start with the account-settings update.” Under actions, write “Prepare a draft review checklist — Dev — 15 May.” This illustrates the useful level of specificity: a reader can tell what was agreed, who is responsible, and when the action is due.
What to include and why
Each field should help someone prepare, understand the conversation, or follow through. The template can be shortened for a quick check-in or expanded for a planning session, but these elements are a useful starting point:
- Meeting details: Give the page a recognizable title and add the date, time, location or meeting link, facilitator, and note-taker. A consistent naming pattern makes related pages easier to scan.
- Attendees: Record participants and, when useful, people who were invited but absent. Avoid assuming that a page’s viewer already knows who attended.
- Purpose and agenda: State the intended outcome and list topics in the order they will be discussed. An owner for each topic can help the group prepare and keep the conversation focused.
- Discussion notes: Capture the points needed to explain decisions, unresolved questions, and context. Summarize rather than transcribing every comment.
- Decisions: Make conclusions easy to find. If a decision has conditions, a scope limit, or a reason that will matter later, include that context.
- Actions: Use a clear verb, one accountable owner, and a due date or agreed checkpoint. If no date was agreed, say so rather than inventing one.
- Open items and next meeting: Carry unresolved questions forward and state when or where the group expects to revisit them.
For action items, a separate table with columns for task, owner, due date, and status can be more practical than a paragraph. Confluence pages can also use editor features such as tables and task lists, depending on the version and configuration. A task list is convenient for tracking completion on the page; a plain action table may be easier to review when ownership and dates matter most.
How to create and reuse the page
Start by deciding where the notes belong. A page in a project or team space is often easier for the relevant group to locate than a page stored among unrelated documents. Check that the people who need the notes can access that space; the page’s visibility follows the space and page permissions in effect.
- Create a page in the appropriate space, or open an existing meeting-notes page that is safe to copy.
- Add the meeting details, agenda, notes, decisions, and action fields from the template. Use headings to separate sections and a table when rows or owners need to be compared.
- Give the page a clear title, such as the team or project name followed by the meeting date. Add links to relevant background pages when readers need more context.
- For repeat use, save the structure as a page template if the available Confluence controls and your permissions support it. Otherwise, keep a clearly identified source page and copy it for each meeting.
- Before sharing, check the page title, date, action owners, links, and audience permissions. After the meeting, update the notes while the discussion is still fresh.
Keep the reusable source page free of meeting-specific decisions and personal details. If you copy a previous meeting’s page, remove old attendees, dates, action items, and comments that do not belong in the new record. Treating the copy as a fresh page helps prevent an outdated deadline or decision from being mistaken for current information.
Adapt the template to the meeting
One format does not fit every meeting. A short stand-up may need only a date, attendees, blockers, and actions. A project kickoff may need goals, scope, roles, assumptions, and risks. A decision meeting benefits from a clear question, options considered, the decision-maker, and the final outcome. Add fields only when they serve a real purpose; an overly long form can make people skip the useful parts.
Consider the readers as well as the people in the room. A team’s working notes may use shorthand familiar to its members, while a cross-team summary should explain acronyms and link to background information. If the page is meant to be a brief record, label it as a summary so readers do not assume it is a complete transcript.
For recurring meetings, preserve a stable structure so that people know where to look, but review the layout occasionally. Remove prompts that are never used and add a field when the team repeatedly has trouble finding the same kind of information. A template should support the meeting, not turn note-taking into an administrative task of its own.
Make decisions and action items easy to follow
Notes are most useful when they distinguish conversation from outcome. “Discussed onboarding” does not show whether anything was decided. A stronger entry might say, “Decision: use the revised onboarding checklist for the next release; review the results at the following planning meeting.” If the group did not reach a conclusion, record that the question remains open and name the next step for resolving it.
Use action items that can be checked later. “Look into the issue” is vague; “Compare the two proposed import workflows and share a recommendation” identifies a result. Assign one directly responsible owner even when several people will help. If responsibility is shared, name the lead and note the collaborators. Put dates in a consistent, unambiguous format to reduce confusion across teams.
Link an action to a relevant project page or task when that helps people continue the work, but do not assume a link alone explains the commitment. Keep a short description and owner in the notes as well. At the next meeting, review open actions and either mark them complete, update their status, or agree on a new next step.
Common problems and how to avoid them
- Notes read like a transcript: Long verbatim discussions are difficult to scan. Summarize the reasoning needed to understand the outcome and preserve exact wording only when it is important.
- Actions have no owner or date: A task without accountability is easy to lose. Add an owner and an agreed deadline, or mark the missing detail for confirmation.
- Old information carries over: Reused pages may retain stale actions, attendees, or decisions. Review every copied field before publishing the new notes.
- The page is hard to find: Use a predictable title and store it in the relevant space. Link to the notes from a recurring meeting page or another useful index when appropriate.
- Readers cannot access it: Check that the intended audience has permission to view the page. Do not put restricted information in a broadly accessible space just because it is convenient.
- The template becomes too complicated: Too many mandatory-looking sections can discourage timely notes. Keep the core fields and make optional sections clearly optional.
Another common misconception is that a meeting-notes page automatically tracks every action. The page records what the group wrote there; it does not guarantee that owners will see or complete the work. Follow-up may require reminders, links to the team’s work-tracking process, or a review at the next meeting.
Page template, copied page, or another format?
A saved Confluence page template is useful when many people create the same kind of notes and the space offers a suitable reusable-template option. A copied source page is often simpler for a small team or for organizations where template creation is restricted. In either case, decide who maintains the source and how changes to the layout will be communicated.
A plain document can be preferable when people need to take notes offline, distribute a printable agenda, or work outside the Confluence space. A dedicated task or project-tracking system may be better for ongoing ownership and status reporting; the meeting page can still capture the decision and link to those tasks. Choose the format based on where readers will look and how the information will be maintained, rather than adding tools for their own sake.
Frequently Asked Questions
Does Confluence have a built-in meeting notes template?
Template availability can vary by Confluence version, space, and administrator settings. Look at the page-creation options in your space; if a suitable template is not available, create a reusable source page or ask a space administrator about adding one.
How do I create a meeting notes template in Confluence?
Create a page with the sections your meetings need, then save it as a reusable page template if that option is available to you. If not, keep a clean source page and copy it for each meeting, removing all old meeting-specific content.
What should meeting notes include?
At minimum, include the meeting title and date, attendees, purpose or agenda, key discussion points, decisions, and action items with owners. Add due dates and open questions when they help readers follow up.
Can I use a table for meeting actions?
Yes. A table with task, owner, due date, and status columns makes responsibilities easier to scan. A task list can also work for simple completion tracking, but choose the format your team will actually maintain.
How should I title recurring meeting notes?
Use a consistent pattern that identifies the team or project and the date, for example, “Planning — 2026-11-02.” Consistency makes pages easier to recognize and sort, especially when a meeting has many installments.
Who should have access to meeting notes?
Share them with the people who need the record, while following your organization’s access rules. Check the page and space permissions before sharing, especially when the discussion includes information that should not be broadly visible.