You sit down for the 1:1. You open last week's notes. You can't remember what you agreed to do, your report can't remember what they agreed to do, and the first five minutes go to reconstructing the conversation you already had. Multiply that by six reports and you've lost half a morning to archaeology.
The fix isn't a better memory. It's a recurring agenda that carries forward what mattered, so every 1:1 starts where the last one ended. This guide is for engineering managers and first-time managers who want one repeatable structure, not a fresh blank doc every Tuesday.
- Key takeaways
- A 1:1 agenda only works if last week's action items are still visible this week.
- Use one recurring page per report, not a new doc each time, so context compounds.
- A page template gives every 1:1 the same shape: open items first, talking points, notes, next steps.
- Keep action items as the top section and roll the unfinished ones forward before each meeting.
- Turn commitments that have a real deadline into cards with an owner and a due date.
Why most 1:1 agenda templates fail
The usual template is a tidy list of headings: wins, blockers, feedback, career. It looks great the first week. By week four it's a graveyard of half-finished docs, each one missing the thread that connected it to the last.
The problem is structural. A new document every week resets context to zero. Action items from last Tuesday live in a file you have to go find, and "go find it" is exactly the friction that kills follow-through. If the commitment isn't in front of you when the meeting starts, it didn't happen.
So the goal isn't a prettier list of headings. It's continuity. One agenda that persists, where the things you both committed to last week are the first thing you see this week.
The structure: one recurring agenda page per report
Instead of a doc per meeting, keep one living agenda page per direct report. Same page, every week. New entries go on top, old ones scroll down into history. The page becomes a running record of the relationship, not a pile of disconnected snapshots.
Here's the shape that holds up over months:
1. Open action items (always at the top)
This is the section that does the real work. Before each 1:1, anything not finished from last week stays here. Anything done gets checked off and moves down into the week's notes. When you both open the page, the first thing you see is "what we said we'd do and haven't yet." No archaeology.
2. This week's talking points
A short list either of you adds to between meetings. The point is that it's collaborative and asynchronous. Your report drops in a topic on Thursday; you see it before Tuesday. Nobody walks in cold.
3. Notes from the conversation
What you actually discussed, dated. This is the history that makes quarterly reviews and promo cases write themselves. Six months of dated notes beats a frantic memory dump every time.
4. Next steps
The commitments made this week, with an owner on each. At the start of next week, the unfinished ones get promoted back up to "Open action items." That promotion step is the whole trick. It's two minutes of editing that turns a static doc into a system.
Building it as a reusable template in Zoobbe
You don't want to rebuild that structure from scratch for every report, and you definitely don't want six slightly different versions drifting apart. This is where a page template earns its keep.
Zoobbe ships page templates by category, including a meeting category. You build the agenda structure once as a template, then spin up a fresh agenda page from it for each report. Every 1:1 starts with the same four sections, so the format never drifts and a new report's first agenda looks exactly like everyone else's.
Because Zoobbe pages support a nested page hierarchy, you can keep a parent "1:1s" page with one child page per report underneath it. One place to open, everyone's agenda one click away.
The pages are real rich-text documents powered by Lexical, so headings, checklists, and formatting behave the way you'd expect. And because editing is real-time and collaborative via CRDT, your report can add a talking point or update an action item at the same time you're reading the page, without anyone refreshing or overwriting the other. You also get live presence, so you can see when someone's on the page with you.
Carrying action items forward, week to week
Here's the honest part: the page doesn't magically move last week's items for you. The continuity comes from the ritual, and the template makes the ritual cheap.
Two minutes before each 1:1, you do one pass:
- Scroll to last week's "Next steps."
- Anything done, check it off and leave it in the dated notes.
- Anything not done, move it up to "Open action items" so it's the first thing you both see.
- Add the date for this week's entry and go.
That's it. The unfinished work is now impossible to ignore, because it's at the top of the page you open together. Items stop quietly disappearing, which is the single biggest reason 1:1s feel like they repeat themselves.
When an action item deserves a card, not a checkbox
Some commitments are bigger than a checkbox. "Draft the on-call rotation proposal" has a real deadline and a real owner. For those, don't bury it in a notes page. Make it a card on your team board.
Zoobbe cards take multiple assignees, due dates with reminders, priorities, and threaded comments with @mentions. So a 1:1 commitment with weight behind it becomes a tracked card your report actually gets reminded about, while the lightweight "send me that link" stuff stays as a checkbox on the agenda page. Use the page for the conversation, the board for the work.
A first-time manager's starting template
If you're running your first 1:1s, copy this into your template and adjust later:
Open action items — unfinished commitments, rolled forward
Talking points — added by either of us during the week
Wins since last time — one line, builds the promo case
Blockers — what's in their way that I can clear
Feedback — both directions
Next steps — owner on each
Don't overthink the headings. The structure matters less than the discipline of keeping one page per person and promoting unfinished items to the top every week.
FAQ
How often should I update the 1-on-1 agenda?
Treat it as a living page. Add talking points whenever they come up during the week, and do a two-minute cleanup right before each meeting to roll unfinished action items to the top.
Should I use one agenda page per report or one per meeting?
One per report. A new page per meeting resets context every week. A single recurring page lets notes and action items accumulate, which is what makes reviews and career conversations easier later.
Can my report edit the agenda too?
Yes. Share the page with editor access and they can add talking points and update items. Editing is real-time, so you can both be on the page at once without overwriting each other.
What's the difference between an action item and a card?
Keep small, conversational follow-ups as checklist items on the agenda page. Promote commitments with a real deadline and owner into a board card so they get due-date reminders and show up in the team's workflow.
Do I need a separate template for each report?
No. Build one meeting page template and create a new page from it for each report. Same structure every time, no drift.
Want every 1:1 to start where the last one ended? Build your recurring agenda on a Zoobbe page template and stop running meetings from memory. Try Zoobbe.
Photo by Kelly Sikkema on Unsplash