Meeting Agenda Template (Free) + 6 Examples

Most agendas are a list of nouns. "Q3 budget." "Roadmap." "Hiring." Nobody can tell from that list what the meeting is supposed to produce, so everyone shows up to talk about the topic and leaves having talked about the topic. The meeting worked exactly as designed. The design was the problem.

A working meeting agenda template does one thing a topic list can't: it forces you to say, before anyone joins, what each item should produce and who's responsible for producing it. Below is one master template you can copy for almost any meeting, plus six versions shaped to specific formats — weekly team, one-on-one, project status, client or external, all-hands, and a meeting whose only job is to make a decision.

Each template is followed by a filled-in example. And because some meetings have enough peculiarities to need their own treatment, this page points to deeper guides where that's true rather than pretending one page can cover everything.

What's in here

• What makes an agenda actually work
• The master meeting agenda template
• Which agenda for which meeting
• 1. Weekly team meeting agenda
• 2. One-on-one agenda
• 3. Project status agenda
• 4. Client or external meeting agenda
• 5. All-hands agenda
• 6. Decision-making meeting agenda
• How and when to send it
• Five ways a good agenda still fails
• Frequently asked questions

What makes an agenda actually work

Four properties separate an agenda that changes a meeting from one that just sits in the invite. Miss any of them and you're back to a list of nouns.

A desired outcome on every item. This is the one that does the heavy lifting. Each line should name what it produces — a decision, an agreement, a ranked list of options, or shared understanding of something specific. "Project update" isn't an output. "Decide the Phase 2 scope" is. The practical test: could someone in the room say out loud that the item is finished? If not, the outcome isn't written clearly enough.

An owner on every item. A name next to each line, and that person prepares the item, opens it, and is accountable for landing the outcome. Unowned items produce the most circular conversation in any meeting, because everyone assumes someone else brought the context. They're also the items most likely to reappear next week completely unchanged.

A timebox on every item. Either clock times (9:05–9:20) or durations (15 min) — pick one and use it consistently. Timeboxing does two jobs: it stops the first topic from eating the last one, and it gives everyone a shared, visible sense of pace. Two rules make it stick. The timeboxes have to add up to less than the meeting length so there's buffer for transitions. And items go in priority order, most important first, so that when you run long it's the least important item that gets dropped rather than whatever happened to be last.

Pre-reads, with instructions. If people need to read something first, link it, say how long it is, and say explicitly whether to read it beforehand or whether reading time is built into the meeting. "See attached" attached to a 14-page document is not a plan. Some teams have gone the other way entirely and open the meeting with silent reading time, which is unglamorous and works remarkably well, because it removes the assumption that everyone did homework.

Tip: put a verb at the front of every agenda line. Decide, approve, choose, rank, review, brief. The verb makes the outcome obvious and it makes lazy items impossible to write, because you'll notice there's no verb that fits "Q3 budget."

Try it on your next recurring meeting and count how many standing items you can't find a verb for. Those are the items to cut.

The master meeting agenda template

Copy this one if you're not sure which to use. It fits anything from a 30-minute working session to a 90-minute planning meeting — adjust the number of items, not the structure.

Template — master meeting agenda

[MEETING NAME]
Date: [Day, Month DD] · Time: [Start–End, time zone] · Where: [Room / link]
Attendees: [Names — and why each person is needed]
Chair: [Name] · Notes: [Name]

Purpose: [One sentence. What has to be true when this ends.]

Pre-read: [Link] — [length] — [read before / we'll read together]

Agenda

• [0:00–0:03] Purpose and agenda check. Owner: [Chair] — Outcome: anything urgent that isn't listed gets added or deferred, out loud.
• [0:03–0:20] [Verb + the most important item]. Owner: [Name] — Outcome: [decision / agreement / options ranked]
• [0:20–0:35] [Verb + second item]. Owner: [Name] — Outcome: [___]
• [0:35–0:45] [Verb + third item]. Owner: [Name] — Outcome: [___]
• [0:45–0:50] Actions and close. Owner: [Chair] — Outcome: every action read back as owner + task + date.

Parked / not this meeting

• [Item] — [where it goes instead, and when]

Filled example — master format

PRICING & PACKAGING — WORKING SESSION
Date: Thursday, Aug 13 · Time: 10:00–10:50 a.m. PT · Where: Room 4 / Google Meet
Attendees: Sofia Ruiz (owns the pricing model), Danny Kwon (finance approval), Mira Patel (customer research), Otto Lindqvist (engineering feasibility)
Chair: Sofia Ruiz · Notes: Otto Lindqvist

Purpose: Leave with a per-seat price for the mid-tier plan that finance will sign off on.

Pre-read: Pricing sensitivity summary — 3 pages — please read before, we won't recap it.

Agenda

• 10:00–10:03 Purpose and agenda check. Owner: Sofia — Outcome: anything urgent added or deferred now.
• 10:03–10:20 Decide the mid-tier per-seat price. Owner: Sofia — Outcome: one number, or a written list of what's blocking the number.
• 10:20–10:35 Choose which two features move up from the top tier. Owner: Mira — Outcome: two features named, with the research reason for each.
• 10:35–10:45 Confirm the migration path for existing accounts. Owner: Otto — Outcome: agreement on grandfathering, or a spike scheduled to answer it.
• 10:45–10:50 Actions and close. Owner: Sofia — Outcome: actions read back with owners and dates.

Parked

• Annual vs monthly discount ratio — needs the finance model first. Danny brings it to the Aug 27 session.
• Enterprise tier naming — not this group. Marketing decides async by Aug 20.

Notice how little of that is topics. Every line has a verb, a name, and something the room can point at and call finished. That's the whole difference, and it takes about four extra minutes to write.

Which agenda for which meeting

Match the format to what the meeting is supposed to produce, not to how important it feels. A few meeting types have enough specifics to deserve their own guide, and those are linked in the last column.

Those four linked guides go well past what fits here — sales meetings have their own pathology around status readouts, kickoffs live or die on whether roles get named in the room, staff meetings drift into announcements, and emergency meetings need a structure that works when everyone is stressed and half the facts are wrong. If your meeting is one of those, start there.

1. Weekly team meeting agenda

The workhorse, and the one most likely to have quietly become a status readout. The fix is structural: routine updates move to a channel before the meeting, and the live time goes to things that need more than one brain.

Template — weekly team meeting

[TEAM] WEEKLY — [Day], [Time] · [Link] · 40 min
Purpose: Unblock the team and agree what matters most this week.
Before we meet: Everyone posts a 3-line update in [channel] by [time]: shipped · next · blocked.

• [0:00–0:05] Review the async updates. Owner: [Lead] — Outcome: the two or three that need discussion get flagged; the rest are read, not repeated.
• [0:05–0:20] Clear the blockers. Owner: whoever is blocked — Outcome: every blocker has a named unblocker and a date.
• [0:20–0:30] Decide [this week's one real decision]. Owner: [Name] — Outcome: decided, or the missing input is named with who's getting it.
• [0:30–0:35] Set the week's priority. Owner: [Lead] — Outcome: one thing the team agrees matters most.
• [0:35–0:40] Actions and close. Owner: [Lead] — Outcome: owner + task + date, read aloud.

Filled example — weekly team meeting

SUPPORT OPS WEEKLY — Monday, 9:30 a.m. ET · Google Meet · 40 min
Purpose: Unblock the team and agree what matters most this week.
Before we meet: 3-line update in #support-ops by 9:00.

• 9:30–9:35 Review async updates. Owner: Ayanna — Outcome: flag the queue backlog and the new macro rollout for discussion; skip the rest.
• 9:35–9:50 Clear the blockers. Owner: whoever's blocked — Outcome: named unblocker and date for each. Known going in: Jules is waiting on billing API access (8 days), Rosa needs a decision on refund authority limits.
• 9:50–10:00 Decide whether weekend coverage moves to a rotation. Owner: Ayanna — Outcome: decided, or name what's missing.
• 10:00–10:05 Set the week's priority. Owner: Ayanna — Outcome: one thing. Proposed: get first-response time back under 4 hours.
• 10:05–10:10 Actions and close. Owner: Ayanna — Outcome: actions read back.

2. One-on-one agenda

The critical structural choice here is whose meeting it is. A 1:1 where the manager brings all the items is a status meeting with two people. Their agenda goes first, and it goes first every time, because the moment it becomes optional it evaporates.

Template — one-on-one

1:1 — [Manager] & [Report] · [Day, time] · 30 min · [Recurring: weekly / biweekly]
Shared doc: [Link — both add items during the week]

• [0:00–0:03] Check the open items from last time. Owner: both — Outcome: each one closed, still moving, or explicitly dropped.
• [0:03–0:15] Your agenda. Owner: [Report] — Outcome: whatever you brought gets a real answer or a date for one.
• [0:15–0:23] My agenda. Owner: [Manager] — Outcome: feedback given, context shared, questions answered.
• [0:23–0:28] The longer thread. Owner: both — Outcome: one step on the career, skill, or growth conversation — not every week, but on purpose.
• [0:28–0:30] Actions. Owner: [Manager] — Outcome: what each of us does before next time.

Filled example — one-on-one

1:1 — Marcus & Priti · Tuesday, 2:00 p.m. · 30 min · Weekly
Shared doc: /1-1/priti — both add items during the week

• 2:00–2:03 Open items. Design review process — proposal written, not sent. Conference budget — approved, done.
• 2:03–2:15 Priti's agenda. (1) Wants a decision on whether she owns the API docs or whether that's still shared with platform. (2) Asking about the scope of the Q4 reliability work.
• 2:15–2:23 Marcus's agenda. Feedback on the incident write-up — strong analysis, buried the recommendation on page 3. Context on the reorg announcement coming Thursday.
• 2:23–2:28 Longer thread. Staff engineer path — what evidence the committee looks for, and which of her current projects generates it.
• 2:28–2:30 Actions. Marcus: get an API docs ownership answer by Thursday. Priti: send the design review proposal by Friday.

3. Project status agenda

Status meetings rot into narration unless the agenda demands a position. This one asks for a status colour with a justification, forecast dates against planned dates, and — the item everyone skips — the decisions the project team can't make on its own. That last item is the reason the stakeholders are in the room at all.

Template — project status meeting

[PROJECT] — STATUS REVIEW · [Date] · 40 min · Phase: [___]
Purpose: Give stakeholders an accurate picture and get the decisions we can't make ourselves.
Pre-read: [Status report link] — sent [date]. We won't present it.

• [0:00–0:05] State the status and defend the colour. Owner: [PM] — Outcome: everyone agrees it's green, amber, or red, and why.
• [0:05–0:15] Review the slipped milestones only. Owner: [PM] — Outcome: forecast dates confirmed or changed. On-track items get no airtime.
• [0:15–0:25] Decide [the open decisions]. Owner: [Sponsor] — Outcome: each decision made or given a named decider and a date.
• [0:25–0:35] Review the top risks. Owner: [Risk owners] — Outcome: mitigation agreed, owner confirmed, review date set.
• [0:35–0:40] Actions and next checkpoint. Owner: [PM] — Outcome: actions, plus what has to be decided next time.

Filled example — project status

WAREHOUSE AUTOMATION — STATUS REVIEW · Thu Aug 6 · 40 min · Phase 2 of 4
Purpose: Accurate picture, plus two decisions we can't make ourselves.
Pre-read: Status report (2 pages), sent Tuesday. We won't present it.

• 2:00–2:05 Status: Amber. Owner: Niall — Outcome: agree the colour. Reason: conveyor commissioning is 2 weeks late and now on the critical path.
• 2:05–2:15 Slipped milestones. Owner: Niall — Outcome: confirm new forecasts. Commissioning: planned Aug 14, forecast Aug 28. Integration test: planned Sept 7, at risk.
• 2:15–2:25 Decide two things. Owner: Rosa (sponsor) — (1) Approve weekend commissioning shifts, roughly $22K. (2) Cut the returns-line scope from Phase 2 or hold the go-live date. Outcome: both decided today.
• 2:25–2:35 Top risks. Owner: risk owners — Vendor engineer availability in September (Niall). Peak-season freeze from Nov 1, which is immovable (Rosa).
• 2:35–2:40 Actions and next checkpoint. Owner: Niall — Aug 20. Decision needed then: whether integration test moves.

Tip: put "decisions we need from you" on every status agenda. Most status meetings exist because a team needs something it can't authorize on its own, but the agenda buries that under twenty minutes of progress narration and the ask arrives at minute 38 when everyone's leaving.

Put the asks in the invite and in the top third of the agenda. Sponsors who know what they're being asked to decide tend to arrive having thought about it.

4. Client or external meeting agenda

An agenda you send outside your company does double duty as a proposal for how the time gets used, and sending one is a small signal that you've prepared. Two rules: nothing internal goes on it, and the last item is always the next step, agreed live rather than promised by email.

Template — client / external meeting

[CLIENT] & [YOUR COMPANY] — [Meeting purpose]
[Date] · [Time, both time zones] · [Video link]
From [Client]: [Names, titles] · From [Us]: [Names, roles]
What we'd like to leave with: [One sentence — theirs and yours]

• [0:00–0:05] Confirm the agenda and add anything. Owner: [Us] — Outcome: their priorities are on the list before we start.
• [0:05–0:20] [Their topic first]. Owner: [Client name] — Outcome: [___]
• [0:20–0:35] [Your topic]. Owner: [Your name] — Outcome: [___]
• [0:35–0:45] Open questions both ways. Owner: both — Outcome: each question has someone answering it and a date.
• [0:45–0:50] Agree the next step. Owner: [Us] — Outcome: the next meeting or milestone, on the calendar before we hang up.

Filled example — client meeting

RIVERBEND FOODS & HALCYON SOFTWARE — Phase 1 rollout planning
Wed Aug 12 · 3:00–3:50 p.m. BST / 10:00 a.m. EDT · Teams
From Riverbend: Jules Perrin (Ops Director), Rosa Bianchi (IT Lead) · From Halcyon: me (Account Lead), Otto Lindqvist (Implementation)
What we'd like to leave with: an agreed site order for Phase 1 and a signed-off training window.

• 3:00–3:05 Confirm the agenda. Owner: me — Outcome: anything Riverbend wants added goes on now.
• 3:05–3:20 Choose the Phase 1 site order. Owner: Jules — Outcome: three sites named and sequenced. Halcyon's view: start with Bristol, smallest integration surface.
• 3:20–3:35 Agree the training window. Owner: Otto — Outcome: dates confirmed. Constraint: we need two consecutive days per site, and Riverbend's peak runs from Oct 15.
• 3:35–3:45 Open questions both ways. Owner: both — Ours: who owns master data cleanup. Theirs: what happens to the legacy system during parallel running.
• 3:45–3:50 Agree the next step. Owner: me — Outcome: technical session booked live, with Rosa's team included.

5. All-hands agenda

All-hands meetings fail in a specific way: they become a broadcast that could have been an email, and the Q&A gets four minutes at the end when everyone's checked out. So this agenda front-loads the numbers, gives questions real time, and requires that questions be collected in advance — because the ones people actually care about are rarely the ones someone is brave enough to unmute for.

Template — all-hands

[COMPANY] ALL-HANDS — [Month] · [Date, time in 2–3 zones] · 50 min
Recorded: yes, posted in [place] within [X] hours
Questions: submit in [form/channel] by [date] — anonymous option available

• [0:00–0:10] Where we are against the plan. Owner: [CEO/lead] — Outcome: everyone knows the three numbers that matter and whether they're on track.
• [0:10–0:20] One thing worth understanding in depth. Owner: [rotating team] — Outcome: the company understands one piece of work well, not five pieces vaguely.
• [0:20–0:28] Recognition. Owner: [Lead] — Outcome: specific work named, with the reason it mattered.
• [0:28–0:33] What's changing. Owner: [Lead] — Outcome: people, process, or priority changes stated plainly before rumour beats you to it.
• [0:33–0:50] Q&A — submitted questions first. Owner: [Chair] — Outcome: the hardest submitted question gets answered, not skipped.

Filled example — all-hands

HALCYON SOFTWARE ALL-HANDS — August · Thu Aug 20, 8:00 a.m. PT / 11:00 a.m. ET / 4:00 p.m. BST · 50 min
Recorded: yes, posted in #all-hands within 3 hours
Questions: submit in the form by Tue Aug 18 — anonymous option available

• 8:00–8:10 Where we are. Owner: Sofia — ARR $18.4M against a $21M plan. Net retention 108%. Cash runway 22 months. Behind on new logos, ahead on expansion.
• 8:10–8:20 Deep dive: the billing migration. Owner: Otto's team — Outcome: everyone understands why it's taking two quarters and what breaks if we rush it.
• 8:20–8:28 Recognition. Owner: Sofia — Support team cut first-response time from 9 hours to 3.5 while handling 22% more volume.
• 8:28–8:33 What's changing. Owner: Sofia — Two teams merging under one lead from Sept 1. Named, with the reason, before the rumour does it for us.
• 8:33–8:50 Q&A. Owner: Danny — 14 submitted, starting with the most-upvoted: "Are we hiring in Q4 or not?"

6. Decision-making meeting agenda

Sometimes the meeting has exactly one job. This agenda is deliberately narrow — one decision, stated as a question with a yes-or-no or pick-one answer, and a named decider stated up front so nobody spends the hour guessing whether this is a consultation or a vote.

Template — decision meeting

DECISION: [The question, phrased so it has a definite answer]
[Date] · 30 min · Decider: [Name] · Consulted: [Names] · Informed after: [Names]
Reversible? [Yes — decide fast / No — decide carefully]
Deadline: [When this stops being a choice]
Pre-read: [Options doc — options, tradeoffs, recommendation]

• [0:00–0:05] Restate the decision and the constraints. Owner: [Decider] — Outcome: everyone agrees what's being decided and what isn't.
• [0:05–0:15] Test the options. Owner: [Author] — Outcome: the strongest objection to each option is on the table.
• [0:15–0:22] Hear the dissent. Owner: [Chair] — Outcome: anyone who disagrees has said so out loud, on the record.
• [0:22–0:27] Decide. Owner: [Decider] — Outcome: the decision, plus one sentence of reasoning for the people who weren't here.
• [0:27–0:30] Who tells whom, by when. Owner: [Decider] — Outcome: communication owners and dates.

Filled example — decision meeting

DECISION: Do we build the reporting module or integrate a third-party one?
Mon Aug 10 · 30 min · Decider: Sofia Ruiz · Consulted: Otto Lindqvist, Danny Kwon, Mira Patel · Informed after: engineering, sales
Reversible? Partly — integration is reversible in about a quarter, building is not.
Deadline: Aug 14, or it misses the Q4 roadmap.
Pre-read: Options doc — three options, cost and time for each, recommendation to integrate.

• 11:00–11:05 Restate. Owner: Sofia — In scope: build vs integrate. Not in scope: whether we need reporting at all — that's settled.
• 11:05–11:15 Test the options. Owner: Otto — Build: 2 engineers for 5 months, full control. Integrate: 6 weeks, $40K/yr, we inherit their roadmap. Hybrid: rejected in the doc, ask if anyone disagrees.
• 11:15–11:22 Dissent. Owner: Danny — Known objection: Mira thinks integrating blocks the analytics product we might want in 2027. Say it here, not afterwards.
• 11:22–11:27 Decide. Owner: Sofia — The decision plus one sentence of reasoning.
• 11:27–11:30 Comms. Owner: Sofia — Otto tells engineering Tuesday. Danny updates the roadmap doc Wednesday.

How and when to send it

An agenda written an hour before the meeting is a courtesy notice, not preparation time. The common guidance is 24 to 48 hours ahead for a normal meeting, 48 to 72 hours when there are pre-reads or a genuinely complex decision, and one to two weeks for board meetings, where directors have a packet to work through and no realistic way to do it the night before.

Where you send it matters as much as when. Paste the agenda into the body of the calendar invite rather than attaching a document — it's the one place everyone will definitely look, it's readable on a phone, and it survives people forwarding the invite. If there's a pre-read, link it in the same place with its length next to it.

Two more habits worth adopting. Ask for additions when you send it, with a deadline ("anything to add, tell me by 4pm Tuesday") — that's how you find out about the thing that would otherwise hijack minute 20. And for recurring meetings, keep the agenda in one living document rather than a new file each week, so the standing structure stays stable and anyone can drop an item in as it comes up.

If you can't write the purpose line, don't send the invite. The one sentence describing what has to be true when the meeting ends is a genuine test, and a fair number of recurring meetings fail it. When they do, the honest options are to cancel, cut the frequency, or convert it to a written update — not to write a vaguer sentence.

Five ways a good agenda still fails

You can do everything above and still lose the meeting. These are the failure modes worth watching for.

It's a topic list wearing a timebox. The most common one. Items have times and owners but no outcomes, so the meeting runs on schedule and produces nothing. A topic with a clock next to it is still a topic.

It's overloaded. Nine items in an hour means each gets six minutes, which is enough to open a subject and not enough to close one. You'll finish having half-discussed everything. Three to five items is the real working range; the rest go to the parked list.

Nobody chairs it. A timeboxed agenda with no one willing to say "we're at time on this, let's take it offline" is decorative. Name a chair, and give them explicit permission to interrupt.

The first item is the easy one. Warming up with something small feels natural and it's a trap — the hard item ends up in the last eight minutes, when people are tired and watching the clock. Hardest first. It's uncomfortable and it works.

Nothing happens afterward. The most expensive failure. The meeting is good, decisions get made, and then nobody writes down who owns what, so half of it has to be re-decided in two weeks. An agenda plans the conversation; something still has to capture the outcome. That's the job of your meeting notes template, and the two documents work as a pair — the agenda's outcome column and the notes' decision list should line up item for item.

Tip: audit a recurring meeting once a quarter. Pull the last six agendas and check two things — how many standing items produced a decision, and how many times the same blocker appeared.

Standing items that haven't produced a decision in three sessions aren't agenda items. They're status updates that have found a comfortable place to live, and they belong in a channel.

The gap between "we decided something" and "the decision reached the people who needed it" is where most of the value of a well-run meeting leaks out. Recording the meeting closes some of it: Laxis records and transcribes Zoom, Google Meet, and Teams calls in 100+ languages, extracts action items with owners attached, and syncs to HubSpot or Salesforce, on a free plan with 300 transcription minutes a month. Be clear-eyed about what that buys you, though: the machine is reliable at catching every commitment and writing them down accurately, and it has no opinion about which ones were important. That judgment stays with whoever chaired the meeting. An AI meeting note-taker can't rescue a meeting that had no agenda. It just stops a good one from evaporating by Thursday.

Run the meeting. Let the follow-up handle itself.

Laxis records, transcribes, and summarizes your Zoom, Google Meet, and Teams meetings, then pulls out action items with owners attached. Free plan includes 300 transcription minutes a month.

Try Laxis Free

The bottom line

Strip away the formats and every agenda on this page is doing the same small thing: it makes you answer three questions in writing before the meeting exists. What should this produce? Who's responsible for producing it? How long is it worth?

Most bad meetings are meetings where nobody answered those questions, and most people can feel it within five minutes but can't name it. Now you can. Copy the master template, spend the four minutes, and watch how differently people show up when they know what the meeting is for.

Frequently asked questions

What should a meeting agenda include?

Six elements: the meeting purpose in one sentence, the logistics, a list of items in priority order, an owner for each item, a desired outcome for each item, and a timebox for each item. Add links to any pre-reads and reserve the final five minutes to confirm action items with owners and due dates.

How far in advance should you send a meeting agenda?

At least 24 to 48 hours before the meeting for most meetings, and 48 to 72 hours when there are pre-reads or a complex decision on the table. Board meetings usually need one to two weeks so directors can work through the packet. Anything sent an hour before is a courtesy notice, not preparation time.

How long should a meeting agenda be?

One page, and three to five items for a one-hour meeting. The reliable constraint is not page count but arithmetic: the timeboxes have to add up to less than the meeting length, with a few minutes of buffer. If your items need ninety minutes and you booked sixty, cut items rather than hoping.

What is the difference between a meeting agenda and meeting minutes?

An agenda is the plan, written and circulated before the meeting. Minutes are the official record, written during and after it. The agenda says what you intend to discuss and what each item should produce. The minutes say what was actually decided, who committed to what, and in formal settings how each vote went.

How do you write a desired outcome for an agenda item?

Name the artifact the item should produce, using a verb. A decision, an agreement, a ranked list of options, or shared understanding of something specific. Replace "Q3 budget" with "approve the Q3 budget or list what is blocking approval". The test is whether someone in the room could say, out loud, that the item is finished.

Do recurring meetings need a new agenda every time?

They need a new one, but not from scratch. Keep the standing structure and change the content, because a recurring agenda that never changes is the clearest sign a meeting has outlived its purpose. Review the standing items quarterly and delete any that have not produced a decision in the last three sessions.

Should an agenda item say who owns it?

Yes, and it is the single cheapest improvement most agendas can make. An owner prepares the item, opens the discussion, and is accountable for landing the outcome. Unowned items produce circular conversation because everyone assumes someone else has the context, and they are the items most likely to reappear next week unchanged.