“One-on-One Meeting Template: Free Download, Sections and How to Use It”

What sections belong in a one-on-one meeting template?

Seven sections, each with a job. The table below shows how they fit a 30-minute weekly meeting and a 50-minute biweekly one.

The proportions matter more than the exact minutes. In a 30-minute meeting, the employee should be talking for roughly 20 of those minutes. If the manager is talking for 20, it is not a one-on-one; it is a briefing with questions.

Notice what is not on the list: project status, ticket counts, deadline recaps. Those belong in the project tool, where they are already visible to everyone and do not consume the one hour a month you get with a person’s full attention.

How do you fill each section without it becoming a form?

The sections are prompts, not fields. Each one needs a question that opens a real answer.

Their items first. “What’s on your mind that we haven’t talked about?” is better than “any questions?” because it assumes there is something. Keep a running list between meetings so nothing depends on memory in the moment.

Progress and blockers. Ask about the obstacle, not the task: “what’s slowing you down this week?” A blocker that is named in week three is a three-day problem. The same blocker named in week six is a three-week problem with a client conversation attached.

Priorities. Force a ranking. “If only two things get done next week, which two?” is a question that reveals disagreements about priority before they become missed deadlines.

Feedback both ways. The manager goes second. If the manager opens with feedback, the employee’s feedback becomes a reaction to it. A useful prompt is “what should I do more of, and less of?” followed by silence long enough to be slightly uncomfortable.

Growth. Once a month, not every week, ask a career question with a horizon: “what do you want to be doing in 18 months, and what is missing?” Weekly career talk becomes repetitive; quarterly career talk becomes a surprise.

Team signals. “What’s the thing everyone knows and nobody says?” is the highest-yield question in the whole template, and the one most managers avoid because they are afraid of the answer.

Actions. Read them back at the end. Owner, verb, date. If an action has no date, it is a wish.

Why should the employee’s agenda come first?

Because the meeting is the employee’s, and the evidence on engagement points the same way.

Gallup’s research on managers found that managers account for about 70% of the variance in team-level engagement, and that employees whose managers hold regular meetings with them are almost three times as likely to be engaged as employees whose managers do not. That is a correlation, not a guaranteed lever, but it describes a pattern most people recognise: attention is the resource, and its absence is read as indifference.

Ordering matters for a subtler reason. A one-on-one that opens with the manager’s list trains the employee to prepare for interrogation. They arrive with status, not with problems. Six months later the manager says the team never raises issues early, and the reason is in the first five minutes of every meeting they have run.

There is a practical version of this rule that survives busy weeks: the employee’s items get the first ten minutes and the last five. If the meeting runs short, the manager’s items are the ones that get cut, not the employee’s.

What cadence actually works?

Weekly for 30 minutes is the default. Biweekly for 50 minutes works for stable, senior teams. Monthly is a performance review wearing a friendlier name.

The arithmetic is not close. Eight direct reports at 30 minutes a week is four hours, or 10% of a 40-hour week. At a $60 loaded hourly rate that is $240 a week, about $12,480 a year. Eight reports at 45 minutes biweekly is three hours a week, roughly $9,360 a year. The saving is about $3,100 a year, which is less than the cost of one avoidable resignation: replacing an employee commonly costs six to nine months of salary, so a $70,000 role carries a replacement cost of $35,000 to $52,500 before you count the team’s lost momentum.

The cadence rule that matters more than frequency is this: do not cancel, reschedule. A cancelled one-on-one teaches the team that the meeting is optional and that the first thing to go when things get busy is the conversation. Move it to Thursday at 9:15 and keep it.

There is one exception worth naming. During a genuinely intense delivery crunch, a 15-minute check-in is better than a skipped 30-minute meeting. Shorter is a compromise. Absent is a signal.

What does a filled-in template look like?

Here is a real-shaped example, with the names changed.

Priya is a backend engineer in her fourteenth week. Her manager, Tom, keeps a shared document with four headings and the date at the top of each entry.

Her items: the payments migration is behind because the staging database keeps resetting, and she has been rebuilding test data twice a week. She also wants to know whether the on-call rotation can exclude the week of her sister’s wedding.

Blockers: the staging reset has cost her roughly six hours over two weeks. She has not raised it because she assumed it was a known platform issue.

Priorities: finish the migration runbook, and pair with the new contractor for two sessions.

Feedback up: Tom’s written messages arrive after 20:00 and she reads them as an expectation to reply. Feedback down: her runbook drafts are too detailed for the audience and she should write the one-page version first.

Growth: she wants to move toward platform work in 18 months. Missing piece: one production incident she owns end to end.

Actions: Tom asks platform to add a staging reset alert by Friday; Priya writes the one-page runbook by Wednesday; Tom confirms the on-call swap by Thursday.

The visible outcomes three weeks later are modest and real. The staging issue was fixed in four days once it had an owner. The runbook shipped at one page plus an appendix. And the incident ownership was scheduled rather than hoped for.

The counterfactual is the interesting part. Without the meeting, the staging problem would likely have surfaced at the sprint review as “migration slipped”, which is a symptom rather than a cause. Six hours of lost work would have become twenty, and the manager would have spent a fortnight believing the problem was estimation.

How do you run the 30 minutes without drifting?

Four habits do most of the work.

Start with the document on screen. Both people, same page, last week’s actions at the top. Thirty seconds of reading replaces five minutes of “where were we”.

Protect the first ten minutes. No status, no logistics. If the employee opens with a status update, ask “what’s behind that?” once, and let it go if the answer is nothing.

Take notes in the meeting, not after. Notes written afterwards are a summary of what the manager remembers, which is a summary of what the manager said.

Close with the list. Read the actions aloud. “So: I chase platform by Friday, you send the runbook by Wednesday, I confirm the swap by Thursday. Anything wrong?” This single habit prevents most of the disappointment that accumulates around one-on-ones.

What should the first one-on-one cover?

Start with the working agreement, not the work. Ten minutes on four questions saves months of guessing: how do you prefer feedback, what time of day is worst for you, what should I do when you go quiet, and what does a good week look like?

Write the answers at the top of the document and leave them there. They become the reference point when something feels off, and they give the employee a legitimate way to say “this is not what we agreed” without making it personal.

Then do one round of the seven sections, short. The goal of the first meeting is not depth; it is proving that the meeting has room for the employee’s items. Depth arrives in week three, once the person believes the space is real. Managers who open with a deep career conversation in meeting one usually get a polite, rehearsed answer and no honesty until month four.

What are the common failure modes?

The status update. The meeting becomes a verbal dashboard. Fix: move status to the tool and open every meeting with “what can’t you see in the board?”

The monologue. The manager talks for 25 minutes and calls it a check-in. Fix: count. If the ratio is inverted for two meetings in a row, the next one starts with the employee’s list and nothing else.

The cancelled meeting. Two cancellations in a month and the meeting is effectively gone. Fix: reschedule within 48 hours, same week.

The feedback ambush. Six months of unspoken concerns delivered in one 30-minute session. Fix: one small piece of feedback per meeting, both directions, and never save it for the review.

“Everything’s fine.” A real answer some weeks, a defensive habit in others. Fix: ask a narrower question — “what’s the most annoying part of your week?” — and accept the first answer.

Actions without owners. “We should look into the staging issue” is not an action. Fix: verb, owner, date.

Template bloat. Someone adds engagement scores, mood check-ins, and a five-point wellbeing scale. The document grows to two pages and gets filled in for three weeks. Fix: seven sections, one page, and an annual review of whether each section still earns its minutes.

How do you adapt the template for remote teams and new hires?

For remote teams, the template stays and the medium changes. Video on, camera optional, document shared on screen. Add one line to the top of each entry: “time zone and working hours this week”, because the most common remote failure is not communication quality but availability drift.

For a new hire, the same seven sections run twice a week for the first month, with section 6 expanded into “what’s confusing, what’s missing, what did nobody tell you”. Gallup has reported that only about 12% of employees strongly agree their organisation does a great job onboarding, which is a useful reminder that the first-month one-on-ones are doing onboarding work whether or not they are designed for it.

For a manager with more than ten reports, weekly 30 minutes stops being feasible. The honest options are to reduce the span of control, delegate a layer, or move to 20-minute weekly meetings with a strict two-item agenda. What does not work is keeping 30 minutes on the calendar and spending the first ten on logistics.

Does Doitify help run one-on-ones?

Doitify is our product, so read this as disclosure. The useful part for this workflow is that meeting notes, tasks, owners, and due dates live in the same workspace as the project, which means an action agreed in a one-on-one becomes a task with an owner instead of a line in a document nobody opens again.

Concretely: a manager can keep a private project per report, with a repeating meeting note, a checklist for the seven sections, and tasks that inherit the agreed due date. Progress and workload views then answer the “is this person overloaded” question with data rather than memory, which is exactly the question a weekly 30-minute meeting is trying to answer. Teams that already run a light task tool will not switch for this alone; the argument is strongest where one-on-ones, project tasks, and workload live in different systems and the follow-through is where things leak.

Conclusion

A one-on-one meeting template is not a form to fill in. It is a promise about what the 30 minutes are for: the employee’s agenda, the blockers that would otherwise stay invisible, feedback in both directions, and a small number of actions with names on them.

Print the seven sections. Keep one document per person. Protect the first ten minutes. Read the actions aloud at the end. Do that for a quarter and the meetings stop feeling like a cost, because the alternative — finding out in a review that someone has been stuck for six weeks — costs far more.

If this post on one-on-one meeting template was helpful, you might also enjoy Project Manager vs Operations Manager: Key Differences and The Best ChatGPT Prompts for Project Managers (2026 Guide).