reph

Templates · People

1:1 notes template

Recurring 1:1 agenda: wins, blockers, growth, action items

Start with this template →Sign in

Opens on reph with the template ready to start. No account needed; sign in to keep your document.

Use it when

You meet a direct report regularly and want one running doc for their agenda, feedback and the actions you both owe

Who it's for

ManagerEngineering managerTech lead

Part of a kit

Team rituals, step 2 of 5. The recurring meetings a team runs on: weekly team meeting, 1:1s, retros, all-hands and offsites.

Filled example

The template filled in for a made-up company, so you can see what good looks like.

1:1 notes: Sam and Leo

Manager: Sam Whitfield · Date: 7 October 2026

Date

  • With: Leo Marchetti, Backend Engineer, Fernhill Platform team
  • Cadence: Weekly · 30 min

Last time

Check-in

  • Back from a long weekend and feeling rested. Said the previous sprint was "a lot of context switching" with three interrupts from the Sales team.

Their topics

  • Wants clearer rules on who handles Sales escalations, since he picked up all three last sprint.
  • Asked whether the conference talk proposal for NorthDev is something the team would support.

My topics

  • Context on the Q4 plan: the queue migration moves up two weeks because the vendor contract ends in December.
  • Feedback on the incident review he led last Tuesday (see below).

Wins

  • The incident review for the 2 October outage: clear timeline, no blame, and the two follow-up actions were already filed with owners before the meeting ended. Anika in Support said it was the first review she fully understood.

Blockers

  • The load test environment has been down for six days, which blocks the retry proposal. Needs me to escalate to Infra, not just airtime.

Growth & feedback

  • Landing well: Writing. The incident review and his design notes are being linked from other teams' docs.
  • To work on: Saying no to interrupts. He took all three Sales escalations without flagging the cost to the sprint. Next time, post in the team channel and let the on-call engineer take it.

Action items

The template

Show the blank template

1:1 notes

Manager: [your name] · Date: [date]

Date

Cadence and who's in the room. Most 1:1s drift without this line pinned at the top.

  • With:
  • Cadence: Weekly · 30 min

Last time

Unchecked action items from the previous session. If the same item shows up three weeks running, talk about why.

Check-in

Ask this before the agenda. How they actually are usually reshapes what matters today.

Their topics

Their agenda goes first. If you run out of time, cut yours, not theirs.

My topics

Things you need to raise (context, feedback, asks), kept short enough to not eat their half.

Wins

Name the specific thing, not "great work." Specificity is what makes recognition land.

Blockers

What's actually stuck, and whether it needs you to unblock it or just needs airtime.

Growth & feedback

One thing landing well, one thing to work on, said directly, not softened into mush.

  • Landing well:
  • To work on:

Action items

Owner in bold on every line. An action item with no owner never happens.

Questions

Who owns the agenda?
The report does, their topics go first and yours get cut if time runs out
Should I keep one doc or one per session?
One running doc per person, newest session at the top, so history stays in one place
Who can see these notes?
Only the two of you, so keep the doc private and share nothing without asking

Fill it with your agent

Connect Claude to reph over MCP, then paste this. The draft arrives as suggestions you accept or reject section by section. How to connect Claude.

Find my reph doc "1:1 notes" with search_docs, then read it with read_doc. Carry forward last session's unchecked action items and draft My topics from the project updates and notes I paste. Leave Check-in, Their topics and Growth & feedback empty, and keep anything personal or health related out. File it with suggest_edit, one replace_section op per section (heading line kept) so each can be accepted alone. Ask each open question (topics you were unsure belong in a 1:1) with add_comment quoting that section's heading line, then call request_review with a one-line summary.

Related templates

Weekly team meeting

Running agenda for the weekly team meeting: wins, metrics, priorities, blockers, decisions and action items with owners

ManagerEngineering managerTech leadProduct managerOperations

Retrospective

What went well, what didn't, and what we'll change

ManagerOperationsEngineerProduct manager

All-hands agenda

Run of show for a company all-hands: timed segments with presenters, Q&A collection, and follow-ups owed afterwards

ExecutiveFounderOperationsCommunicationsManager

Offsite agenda

Team or leadership offsite plan: goals, pre-reads, day-by-day schedule, sessions with owners, decisions to make, logistics and outcomes

ExecutiveFounderManagerEngineering managerOperations

Hiring debrief

Structured hiring debrief: independent panel scores recorded before discussion, evidence by competency, concerns, a bias check and the hire or no hire decision

RecruiterManagerEngineering managerTech lead

Interview scorecard

Structured evaluation against role competencies

RecruiterManagerEngineering managerTech lead

Start with this template →Sign in