Free template
Performance 1:1 Meeting Template
A performance conversation goes badly when it’s saved up for once a year and built on impressions nobody can point to. It goes well when it happens often, stays grounded in real results, and ends with a plain statement of what’s expected next. This is a template you can copy into any doc and use in your next check-in.
The frame: look at goals against what happened, name what’s working with specific examples, be honest about where the bar isn’t being met yet, sort out what support is needed, then close with clear expectations and dated follow-ups. Every part rests on observable outcomes, not on how the work made you feel.
The template (copy this)
Performance check-in with [Your name] & [Teammate name] Date: __________ | Period covered: __________ 1. Goals vs. actual results (10 min) - Goal / commitment: - What actually happened (the observable result): - On track? Ahead? Behind? 2. What's working well (5 min) - Specific example: - What it took, and what to repeat: 3. Where the bar isn't being met yet (5 min) - The expectation: - The observed gap (what happened, when, the impact): - Not "you seem disengaged", a concrete instance: 4. Support & unblocking (5 min) - What's getting in the way: - What I can do to help: - What you'll own: 5. Expectations & follow-ups (5 min) - The bar, stated plainly: - Action items (who / what / by when): - When we'll check this again:
Fill the blanks before the check-in, and have your teammate add the results and examples they want to bring too. Performance is a shared conversation, not a verdict delivered from one side. If you want the thinking behind running it this way, read continuous performance management.
What each section is for
Goals vs. actual results
Start with the commitment and what actually happened, side by side. Naming whether something is on track, ahead, or behind keeps the rest of the conversation honest, because everything that follows hangs off a result you both agree on.
What’s working well
Recognition only counts when it’s specific. Point to a real example, say what it took, and name what you want to see repeated. Vague praise teaches nobody anything; a concrete win shows exactly what good looks like.
Where the bar isn’t being met yet
This is the part managers dodge, and dodging it is unfair to the person who never gets the chance to fix it. State the expectation, then describe the observed gap: what happened, when, and the impact. Skip labels like "you seem checked out" in favor of the instance that made you think it.
Support & unblocking
Before you assign more accountability, find out what’s in the way. Sometimes the gap is scope, tooling, or a decision that’s been stuck on your desk. Splitting what you’ll own from what they’ll own turns a critique into a plan.
Expectations & follow-ups
Close by stating the bar plainly and agreeing on who does what by when. Set the date you’ll check it again so the conversation has a next chapter instead of fading until something goes wrong.
A filled example
Here’s the same template with real entries, so you can see how grounded it gets when every line points to something that happened.
Performance check-in with Priya & Marcus
Date: Jun 9, 2026 | Period covered: last 4 weeks
1. Goals vs. actual results
- Goal: ship the billing migration by May 30.
- Actual: shipped Jun 6, one week late; rollback plan was solid.
- Status: behind on date, strong on quality.
2. What's working well
- The rollback plan caught the currency bug before any customer saw it.
- Repeat: that level of test coverage on anything touching payments.
3. Where the bar isn't being met yet
- Expectation: flag slipping deadlines at least a week out.
- Gap: the May 30 slip surfaced on May 29, so we couldn't reset
stakeholder expectations in time. This is the second time this quarter.
4. Support & unblocking
- In the way: scope kept growing after kickoff.
- I'll own: locking scope at kickoff and saying no to mid-sprint adds.
- You'll own: a Friday status note on at-risk dates.
5. Expectations & follow-ups
- Bar: deadline risk gets raised 7+ days out, every time.
- Action item: Marcus sends first Friday status note by Jun 12.
- Revisit: next check-in, Jun 16.Notice that the hard part (the second late deadline) is tied to a specific date and a specific impact, not to a feeling about the person. That’s the difference between feedback someone can act on and feedback they’ll spend the conversation defending against. For more on telling a real performance gap apart from a style or perception mismatch, see performance, preference, or perception?
Why this belongs in a regular check-in
The biggest mistake in performance management is treating it as an annual event. Wait for review season and you ask someone to absorb a year of feedback in one sitting, while you try to recall a year of detail you never wrote down. Neither job is doable, so the conversation drifts toward vague impressions. That’s where it turns unfair.
Run a version of this template inside your existing cadence and the math changes. Small corrections happen while they still matter. Wins get recognized close to when they happened. And when the annual review does come around, you’re summarizing a set of conversations you’ve already had rather than springing news on someone. If you want a broader rhythm for your meetings, the 1:1 agenda template pairs well with this one: use that for the regular weekly flow and fold the performance sections in when it’s time to go deeper.
Performance check-in FAQ
How is a performance 1:1 different from an annual review?
A performance 1:1 is a short, regular conversation that keeps results and expectations current. The annual review is a summary that should hold no surprises. If you manage performance continuously in check-ins, the review becomes a recap of conversations you've already had, not the first time someone hears hard feedback.
How often should you hold a performance check-in?
Fold performance into your regular cadence rather than scheduling a separate dreaded meeting. Touch on goals and results in your weekly or biweekly 1:1, and go deeper roughly once a month. The point is that nothing waits a full year to be said.
How do you give critical feedback fairly?
Anchor it to a specific, observable instance and its impact, not a vague impression of attitude or effort. State the expectation, describe what happened, then move to support and a concrete next step. Pairing the gap with help to close it keeps the conversation honest without making it feel like an ambush.
How do you keep a performance conversation evidence-based?
Track results as they happen so you're not reconstructing a quarter from memory. Bring the goal, the actual outcome, and at least one concrete example to each section. When feedback rests on observable outcomes instead of how someone made you feel in a meeting, it's far harder to dispute and far easier to act on.
Performance that builds over time
A template gets you through one conversation. MeetFika carries the whole story forward: goals and their progress, follow-ups that don’t fall off, starred moments, and your own private notes, all anchored to the same teammate over time. So when you sit down for a performance check-in, the evidence is already there.
And a year of those check-ins is what makes the annual review easy to write instead of terrifying. Free to start.