One-on-One Meeting Template for Managers
- What should a manager's one-on-one template include?
- How is this different from the weekly team meeting?
- Who prepares the agenda?
- Can I copy a ready-to-use template?
- How could a 30-minute version work?
- What does a completed example look like?
- What should stay out of the shared working note?
- When does a performance concern need another conversation?
- Sources
What should a manager's one-on-one template include?
A one-on-one meeting template should give the employee space to raise priorities, blockers, development questions, and feedback, then capture agreed actions for both people. Keep routine status in the work tracker. Use limited-access notes, not a general team document, and explain their handling. This is general management education: employment, privacy, grievance, accommodation, or formal performance matters require the appropriate organizational process and qualified guidance for the relevant jurisdiction.
For an owner who manages every employee directly, the template's value is consistency without forcing identical conversations. The same fields can support different needs. An experienced employee may want a decision about conflicting priorities; someone learning a responsibility may need feedback on their approach.
How is this different from the weekly team meeting?
The weekly team meeting resolves shared dependencies and decisions. A one-on-one focuses on the working relationship between a manager and direct report: support, development, expectations, and feedback that does not belong in a group discussion.
Do not copy the project tracker into this agenda. Turn a status item into a question when discussion is needed. “The draft is in review” is status. “Two reviewers gave conflicting instructions; who decides which requirement takes precedence?” gives the manager something to help resolve.
The operating-cadence guide explains where this conversation fits among other routines. Here, the task is narrower: prepare and use one meeting record.
Who prepares the agenda?
Invite the employee to choose the first substantive topic and add items as they arise. The manager also prepares: read the agenda, revisit previous commitments, and add any questions openly.
GitLab's public one-on-one handbook describes a consistent agenda with contributions from both people, preferably mostly from the team member. That is a documented company practice, not evidence that a particular split works everywhere. The practical adaptation here is employee-led priorities with shared preparation.
Before the first meeting, explain the purpose, where notes live, who can access them under business policy, and how urgent matters should be raised between meetings. Do not promise absolute confidentiality. A shared document's name does not establish its access permissions or override reporting obligations.
Can I copy a ready-to-use template?
Copy the following fields into an approved, appropriately restricted document. This is Plainwork Operations' original working template, not a validated HR form.
Meeting frame
- Employee and manager:
- Date and next meeting:
- Agreed note location and access arrangements:
- Employee's most important topic today:
- What would make this conversation useful?
Discussion record
| Topic | Prompt to use | Short note to capture |
|---|---|---|
| Previous commitments | What happened to the support or action we agreed? | Completed, changed, or still blocked; next step |
| Employee priority | What needs attention that the normal work record does not explain? | Issue and help requested |
| Blocker or workload | Which decision, input, or priority conflict needs resolving? | Decision needed and person responsible |
| Development | What part of the work would you like to understand or practice better? | Learning opportunity and support to explore |
| Feedback both ways | What should I continue or change in how I support your work? | Specific observation and agreed response |
Closing record
For each commitment, record the next action, one owner, an agreed date or review point, and how completion will be checked. Add a separate line for an unresolved question and its destination. Confirm that both people understand the record; do not convert a suggestion into a commitment without agreement.
MIT Human Resources' agenda guidance distinguishes the topic from its desired outcome and identifies who is responsible. That distinction informs the template: “development” is a topic; “identify a suitable supported practice opportunity” is a possible outcome.
How could a 30-minute version work?
This is an editable planning allowance, not a recommended minimum or a research benchmark:
| Minutes | Use |
|---|---|
| 0–3 | Confirm the employee's priority and any changed circumstances |
| 3–13 | Discuss that priority and the support needed |
| 13–20 | Explore a blocker or development question |
| 20–25 | Exchange feedback or return to an unfinished topic |
| 25–30 | Confirm actions, unresolved questions, and the next meeting |
The blocks total 30 minutes. Change the distribution together when the important conversation needs more room. Do not rush a consequential issue to fit a template; identify the proper separate process where needed.
A quiet agenda is not proof that everything is resolved. Ask one concrete, open question, such as “Which part of your current work needs a clearer decision from me?” Allow thinking time. Do not require disclosure of personal circumstances to fill the slot.
What does a completed example look like?
The following is fictional and illustrates wording only. It describes no real employee, business, intervention, or measured result.
Employee priority: “I receive different instructions about who approves the project outline.”
Help requested: “Confirm the decision owner before I revise it again.”
Development question: “I would like practice presenting the outline, with feedback before the customer meeting.”
Manager response to explore: Confirm the approval route and arrange an appropriate rehearsal opportunity; do not promise authority or access that has not been approved.
| Agreed illustrative action | Owner | Review point | Completion check |
|---|---|---|---|
| Confirm the project-outline decision owner with the relevant lead | Manager | Thursday | Decision route recorded in the project record |
| Bring a draft presentation structure for discussion | Employee | Next one-on-one | Draft available for review |
| Check whether a supported rehearsal can be arranged | Manager | Next one-on-one | Opportunity confirmed or alternative discussed |
The operational decision route can enter the appropriate project record. The whole one-on-one note need not follow it. A development request is also not a promotion promise, a performance rating, or evidence that the learning activity happened.
What should stay out of the shared working note?
Record enough factual context to understand an agreement, not a transcript of everything said. Distinguish an observation from an interpretation. “Approval route unclear” is more useful here than a speculative judgment about motivation.
Do not put diagnoses, unnecessary personal details, passwords, or confidential third-party material into this routine template. If sensitive information is raised, use the organization's designated handling process and obtain qualified HR, privacy, or legal guidance as appropriate. Follow applicable retention requirements; this guide does not tell you to delete records or avoid required documentation.
Urgent safety or safeguarding concerns should use the appropriate reporting or emergency channel without waiting for the next one-on-one. The routine agenda is not an investigation form.
When does a performance concern need another conversation?
Routine feedback can be part of a one-on-one; the meeting should not become an undisclosed disciplinary process. Acas's Great Britain performance-management guidance, updated June 23, 2026, distinguishes regular informal feedback, coaching, and check-ins from more formal reviews. Its employment-law context is not a universal rule for every reader.
When a concern requires formal assessment, warnings, investigation, or another consequential employment decision, identify the proper process with a qualified professional. A business without an HR department still needs appropriate advice. Do not use this template to decide legal rights, accommodations, grievances, or disciplinary outcomes.
Close ordinary meetings by checking the manager's commitments as carefully as the employee's. At the next conversation, return to the agreed support and ask whether the record still reflects what is needed. More team-rhythm resources can help coordinate the surrounding work without replacing this individual conversation.
Sources
- GitLab Handbook: 1-1 agendas and conversations.
- MIT Human Resources: How and Why to Use a Meeting Agenda.
- Acas: Reviews and appraisals, updated June 23, 2026; Great Britain context.