The template
Google Docs agenda structure
[Date] Meeting Title
Top of document, becomes the H1 heading.
Purpose
One sentence stating the outcome the meeting must produce.
Attendees
@-mention each attendee. Mark required vs optional.
Pre-read
Linked documents, bullet-point context, anything attendees should consume before joining.
Agenda
Numbered list of topics with time allocations. Each topic owned by a named person.
Notes (live capture)
Empty section before the meeting; filled during it. Structured by agenda item.
Decisions
List of decisions made, with rationale captured in one or two sentences each.
Actions
@-mention assigned owner, action, deadline. Use the Assignment feature for tracking.
Parking lot
Items raised but deferred. Comment thread on each for async resolution before the next meeting.
Three workflows
Pre-meeting, during-meeting, post-meeting
Pre-meeting (24 hours before)
Meeting organiser creates the document, fills in the static sections (title, purpose, attendees, agenda skeleton), and shares with edit access. Attendees add to the agenda: topics they want to raise, questions they have, pre-reads they want others to see. The Calendly research published in their 2024 State of Meetings report found that meetings with pre-read shared more than 4 hours in advance finished 12 minutes earlier on average than meetings with the agenda landing in the invite an hour before.
Key conventions:
- Link the agenda doc in the calendar invite body
- Give edit access to required attendees, view to optional
- Use comment threads (not inline edits) for questions on existing content
- Set a soft cutoff: agenda locks at start of meeting, additions go to parking lot
During meeting (live capture)
Designated note-taker captures structured notes under each agenda item. The note-taker is not the facilitator (different roles, both important). For virtual meetings, screen- share the document so attendees see the notes as they are typed, which catches misattribution in real time. Use the comment feature for side-conversations that should not interrupt the main thread.
Key conventions:
- One designated note-taker; others add only to comment threads
- Decisions captured in the Decisions section as they happen, not retrofitted
- Actions captured with @-mention immediately when assigned
- Parking lot items captured with one line and a name (so the topic can be followed up)
Post-meeting (within 2 hours)
Organiser cleans up the notes (fixes typos, organises run-on thoughts), confirms decisions are clear, and tags any actions that need to migrate to the project management tool. Share the link to the cleaned document in the team channel as the meeting record. For recurring meetings, archive the current section by moving it below the new section added for next week.
Key conventions:
- Clean up within 2 hours while memory is fresh
- Convert actions to tasks in PM tool if appropriate
- Resolve comment threads that have been addressed
- Share the cleaned doc as the canonical record
FAQ
Common questions about Google Docs agendas
Why use Google Docs for meeting agendas instead of email?
Three reasons. First, Google Docs allows attendees to add topics, questions, and pre-reads to the agenda before the meeting, producing a co-authored agenda that reflects what people actually want to discuss. Second, the agenda gets edited live during the meeting, so notes and decisions are captured in real time without a separate scribe doc. Third, the agenda becomes the meeting record afterwards, with comments serving as threaded discussion and @-mentions assigning actions to specific people. Email agendas cannot do any of these.
Who should own the Google Docs agenda?
The meeting organiser, typically the facilitator or the person who scheduled the meeting. Ownership means: creating the document, sharing with attendees with edit access, setting up the structure, and ensuring it gets archived after the meeting. For recurring meetings, the same person usually owns the rolling document; for one-off meetings, ownership rotates with who called the meeting.
Should attendees have edit or view access?
Edit access for active participants, view access for observers. Edit access enables attendees to add topics before the meeting, take notes during, and add follow-up comments after. The downside is the risk of accidental edits to other people's text; this is rare in practice and the collaboration benefit is substantial. View-only access for attendees who only need to read the outcomes is appropriate for larger meetings.
How do you handle the agenda document for recurring meetings?
Rolling document with reverse-chronological dated sections at the top, archived sections at the bottom. The current week's agenda lives at the top so attendees see it first. After the meeting, that section becomes the historical record. New agenda for next week added above it. This pattern keeps all meeting history in one document for easy search, while keeping the current agenda the most visible.
Can Google Docs replace a project management tool for action tracking?
For small teams (under 8 people) with simple action tracking, yes. Use the @-mention to assign and the Assignment feature (right-click the @-mention) to make it trackable. For larger teams or complex workflows, the action items captured in Google Docs should be exported to a proper project management tool (Asana, Linear, Jira, Monday.com) after the meeting. Google Docs is a great notes capture but not a great long-term task tracker.
How do you keep a Google Docs agenda from becoming chaotic during a meeting?
Designate a single note-taker who is responsible for the structured notes. Other attendees can add comments and side-notes but the structured notes go through one person to maintain coherence. The note-taker does not have to be the facilitator (often shouldn't be); a separate scribe lets the facilitator focus on the conversation. For virtual meetings, the screen-shared document lets everyone see the notes as they're typed, which prevents misattribution of decisions.
Related
Other tool-specific and format templates
Notion meeting agenda
Database-driven pattern for recurring meetings with action-item rollups.
Meeting minutes
How the post-meeting record differs from the live agenda doc.
Recurring meetings
Structure for weekly and recurring meetings that benefit most from the rolling-doc pattern.
Effective agenda principles
Five elements every agenda needs, tool-independent.