# 1:1 Meeting Notes & Action Tracker

> A cumulative 1:1 log built so commitments carry forward from one meeting to the next instead of resetting every week: with a rolling table, status codes, and a quarterly rollup.

Free template for sales managers. Topic: [Coaching, 1:1s & Feedback](https://www.peerlab.ai/library/topic/coaching-1-1s-feedback/). Published by PeerLab in the [Sales Enablement Resource Library](https://www.peerlab.ai/library/). Source: https://www.peerlab.ai/library/1-1-meeting-notes-action-tracker/

## How to use it

Copy the per-1:1 block for every meeting, always complete Step 1 (checking last time's commitment) before adding anything new, and keep the Rolling Commitment Log as one continuous table per rep so nothing quietly resets.

## What's inside

- A reusable per-1:1 template built around checking prior commitments first
- A rolling commitment log table designed to be added to, never reset
- A five-code status system (Done / On track / At risk / Missed-carried / Missed-dropped)
- SMART-commitment fields for every new action item
- A quarterly rollup worksheet to catch repeat-missed patterns

Most 1:1 notes die in a notebook and reset every week: commitments get made, then quietly forgotten because nothing carries them forward. This tracker is built to be cumulative: every entry starts by checking the last one.

## Setup (fill in once per rep)

```
Rep name:
Manager:
Role / territory:
Current skill focus (updates as needed, not every week):
Cadence: [ ] Weekly [ ] Bi-weekly Day/time:
```

## Per-1:1 Template (copy this block for every meeting)

```
──────────────────────────────────────────
1:1 #___ Date:
Skill focus this period:

STEP 1: Check last time's commitment FIRST, before anything new
 Commitment from last 1:1:
 Status: [ ] Done [ ] On track [ ] At risk [ ] Missed
 If not done: why, and does it carry forward or get replaced?

STEP 2: Wins since last 1:1 (specific, skill-tagged, not "good month")


STEP 3: New observation (call review, deal, pipeline, behavior)


STEP 4: New or continued commitment (SMART: specific, measurable,
 timebound)
 Commitment:
 How we'll know it's done:
 Due by (next 1:1 or specific date):

STEP 5, Anything the rep needs from me (manager) to unblock this?


Next 1:1 date:
──────────────────────────────────────────
```

## Rolling Commitment Log (the part that prevents the reset)
Keep this as a single running table per rep: add one row per 1:1, never delete old rows.

| # | Date | Skill focus | Commitment made | Status at NEXT 1:1 | Carried forward? |
|---|------|------------|------------------|---------------------|-------------------|
| 1 | | | | | |
| 2 | | | | | |
| 3 | | | | | |
| 4 | | | | | |

Status codes: **D** = Done · **T** = On track, not due yet · **A** = At risk · **M** = Missed, carried forward · **X** = Missed, dropped (record why)

## Status Code Key (pin this to the inside cover)
- **Done (D):** commitment met, verified with evidence (a call, a number, an observed behavior), not self-reported alone.
- **On track (T):** in progress, due date hasn't passed, no red flags.
- **At risk (A):** due date approaching, insufficient progress: flag it explicitly in the 1:1, don't let it slide silently.
- **Missed, carried forward (M):** didn't happen, still the right commitment: re-set the date, don't quietly re-write history.
- **Missed, dropped (X):** didn't happen and isn't the right commitment anymore, write down why it was dropped so the pattern is visible later.

## Quarterly Rollup (every 3 months per rep)

```
Rep: Quarter:

Commitments made this quarter: ___
Marked Done: ___
Carried forward more than twice: ___ <- watch this number
Skill focus changes this quarter: ___
Net skill trend (baseline vs. latest observation, 1–4 scale):

Pattern noticed across the quarter (e.g., always at-risk on the same
type of commitment):
```