Catch Up Template: A Copy-Ready Format for 1:1s, Status Syncs, and Team Check-Ins

A catch up template is a reusable structure for the short, recurring conversation two people or a small team have to stay aligned — a weekly sync, a manager check-in, a stakeholder update, or a quick project touchpoint. Unlike a formal meeting agenda distributed in advance, a catch-up is usually informal and short, often 15 to 30 minutes, which is exactly why it needs a template more than a longer meeting does. There's no time to figure out the structure on the fly.

The template itself is simple: a fixed sequence of sections — updates, blockers, decisions, action items, and a note for next time — that both people can run through in order without having to remember what usually gets covered. It doesn't dictate what's discussed, only the order, so a five-minute catch-up covers the same ground as a thirty-minute one, just with less detail per section.

Teams use the word "catch up" loosely — it might mean a 1:1, a project status sync, a quick stakeholder update, or an informal team huddle. The template below works for any of these because the underlying need is the same: a fast way to surface what changed, what's stuck, and what happens next.

Most catch-ups fail the same way a status meeting fails: whoever talks first sets the agenda, and the conversation ends whenever it runs out of momentum rather than when everything important has been covered. A manager asks "how's it going" and gets a project update; a blocker that's been sitting for three days never comes up because nobody asked directly.

A catch up template fixes this by reserving space for the parts that get skipped under time pressure. Blockers and decisions are the two sections most likely to disappear from an unstructured catch-up — updates are easy to give because they're front of mind, but naming a blocker out loud takes a deliberate prompt. Building a blockers line into the template means it gets asked every time, not just when someone remembers to bring it up.

A template also creates continuity across sessions. When updates, decisions, and action items are captured in the same format every week, comparing this week's catch-up to last week's takes seconds instead of scrolling through old messages or trying to recall what was said. That continuity is what turns a string of disconnected chats into an actual record of how a project or working relationship is progressing.

A working catch up template has five sections that repeat every session, each short enough to fit a 15-30 minute conversation without feeling rushed.

Below is a copy-ready catch up template you can paste into a doc, a shared notes tool, or a recurring calendar invite description.

---

CATCH UP TEMPLATE

With: _____________ | Date: _____________ | Duration: _____ min

1. QUICK UPDATES (3-5 min) What's happened since last time? _____________

2. BLOCKERS (3-5 min) What's stuck right now? _____________ What's needed to unstick it? _____________

3. DECISIONS NEEDED (5-10 min) Decision: _____________ Outcome: _____________

4. ACTION ITEMS Item: _____________ | Owner: _____________ | Due: _____________ Item: _____________ | Owner: _____________ | Due: _____________

5. CARRIED OVER FROM LAST TIME Resolved? [ ] Yes [ ] No Notes: _____________

6. NEXT CATCH-UP Date: _____________ | Anything to flag in advance: _____________

---

Keep it short enough to fill out live rather than reconstruct afterward. Section 5 — carried-over items — is the part most catch-ups skip, and it's the one that matters most once a project runs past a few weeks. For a longer-format version of the same idea aimed at recurring manager check-ins, see our 121 meeting agenda template.

The five-section structure above works the same way whether a catch-up happens live or entirely in writing — what changes is how each section gets filled in when the team isn't in the same room, or isn't even online at the same time.

For a remote but synchronous catch-up (a video call across time zones), keep the same template but timebox it more aggressively than an in-person version — video calls run long more easily than a hallway conversation does, and the structure is what keeps a 20-minute call from becoming 40. For a fully asynchronous catch-up, replace the live conversation with a shared doc or thread using the same five headings, where each person fills in their own updates and blockers by a set time, and a short comment thread handles anything that needs a decision.

The risk with async catch-ups specifically is that decisions get made in scattered comment replies instead of one place, which makes them hard to find later. Whichever format is used, the action items and decisions sections should end up in one place that both people can reference before the next catch-up — not spread across chat history, email threads, and a doc that only one person updates.

Most problems with a recurring catch-up are structural, and once a bad habit sets in it tends to repeat every session until someone fixes the format itself rather than trying to will their way through a better conversation.

Filling out a catch up template by hand during a live conversation works, but someone has to actually write down every blocker and decision in real time — which is the first thing that gets dropped when the conversation gets into something that actually matters.

Notelyn handles this by recording the catch-up and generating structured notes automatically. Record the conversation directly in Notelyn, or import a recording from Zoom, Teams, or Google Meet, and Notelyn transcribes it and produces an AI summary organized around what was discussed — close to the same shape as meeting minutes from a longer meeting, just scaled to a short catch-up.

For catch-ups specifically, this matters most for the sections that get lost when someone is focused on the conversation instead of on note-taking: a blocker mentioned in passing, a decision made verbally and never written down, an action item agreed to but not logged anywhere. Instead of relying on memory afterward, ask Notelyn's AI Q&A assistant directly — "what decisions did we make?" or "what was still blocked at the end of the call?" — and get an answer pulled from the transcript rather than a guess reconstructed from memory.

A catch up template is worth setting up once and reusing every session, whether it's a weekly 1:1, a project status sync, or a stakeholder update. The structure in this guide — quick updates, blockers, decisions needed, action items, and carried-over notes — covers what a short recurring check-in needs to stay useful across months of sessions rather than just the first few.

Copy the template above, adjust the timing to match how long your usual catch-up runs, and pick a sync or async format based on what the week actually needs. The habit that matters most is reviewing last session's carried-over items before diving into this week's updates.

If you'd rather not fill out every section by hand during a live call, Notelyn can record the conversation and turn it into a structured summary you can query afterward, so the notes from a catch up template keep pace with the conversation instead of trailing behind it. For related formats, see our guides on meeting notes with action items and meeting follow up.