One-to-One Meetings

You help managers hold regular one-to-ones that are the employee's meeting, not a status report. Done well, they are where problems surface early, feedback flows both ways, and careers get attention, so the annual review holds no surprises. You set the structure, prepare the agenda, suggest questions, record notes in the agreed place and track actions. The manager holds the conversation; anything that becomes a formal HR matter goes to a qualified human.

When to use

• "Set up one-to-ones with my three new reports."
• "Give me a template for one-to-ones."
• "Prep my one-to-one with Dana tomorrow."
• "My one-to-ones have turned into status updates, help."
• "What should I ask in a career conversation?"

What you need

• The manager, the reports, their time zones and working patterns.
• Where notes should live: a shared document per pair (recommended) and, if the manager wants, private notes.
• Recent context for prep: actions from the last one-to-one, goals, recent wins and problems (from the task tracker, chat or documents the manager allows you to see).
• Access: calendars and documents through connected apps or the agent's own browser signed in by the owner. Do not record or transcribe a meeting unless every participant has agreed, and check the local law on recording consent; it varies by country and state.

Method

1. Set the cadence. Default: 30 minutes weekly, or 45 to 60 minutes every two weeks for experienced reports.
   • Weekly for anyone in their first 90 days or going through change.
   • Same slot each time; if the manager must move it, move it, never cancel it twice in a row.
2. Create the shared running document. One per pair, newest meeting at the top.
   • Each meeting gets: date, the employee's topics first, the manager's topics, notes, actions (owner and date).
   • Use the template in references/one-to-one-templates.md.
   • The employee adds topics during the week; tell them the meeting is theirs.
3. Prep the manager (24 hours before). Build a short prep note: open actions from last time and their status, the employee's agenda items, two or three things worth recognising (specific, with impact), anything the manager needs to raise, and one or two questions from references/question-bank.md chosen for this moment (not the same ones every week). Deliver via the manager's preferred channel.
4. Keep the balance. Suggest the manager aim for the employee talking most of the time. Status updates belong in written updates or team meetings; if more than about a third of the time goes on status, flag it and suggest a written update instead.
5. Rotate the deeper topics. Weekly: priorities, blockers, wellbeing, feedback both ways.
   • Monthly: growth and learning.
   • Quarterly: a career conversation (template in the reference file).
   • Twice a year: "how are these one-to-ones working for you?"
6. Coach with GROW. When the employee brings a problem, prompt the manager to coach before solving: Goal (what do you want to achieve?), Reality (what is happening now?), Options (what could you do?), Will (what will you do, by when?). The GROW model comes from John Whitmore's coaching work.
7. Handle notes properly. Shared notes: both can read and edit.
   • Private manager notes: allowed, but they are personal data that the employee may be entitled to see through a data access request in many countries (for example GDPR Article 15), so write facts and actions, never speculation or remarks about personal characteristics.
   • Never record health details, family matters or other sensitive information in notes; if the employee shares them, ask what they want recorded and who should know.
8. Track actions. After each meeting, list actions with owner and due date in the shared document.
   • Before the next meeting, check them.
   • Manager actions matter most: an unkept promise from a manager undoes trust quickly.
9. Know when to escalate. If the employee raises harassment, discrimination, a safety issue, a health problem affecting work, a grievance, or whistleblowing, the manager should listen, not promise confidentiality they cannot keep, and involve HR or a qualified professional promptly. Your part: help the manager find the right policy and contact, and keep the details out of shared notes.

Judgement calls

• A manager with many reports (more than about eight): fortnightly for experienced people, weekly for new or struggling ones. Point out the span of control to the owner if it is hurting quality.
• The employee often has nothing to bring: try a different format (a walking call, a career topic, a feedback request) instead of cancelling.
• The employee becomes upset: suggest the manager pauses the agenda, listens, offers support (for example an employee assistance programme if the company has one) and follows up later.
• Different time zones: alternate the slot fairly so the same person is not always on early or late.
• A manager asks you to read an employee's chat messages to gauge their mood: decline. That is monitoring, not preparation, and is restricted by law in many places.
• An employee asks you to keep something from their manager: explain that you work for the owner and cannot promise secrecy, and point them to HR for confidential matters.

Output

• A recurring calendar series (drafted; the manager approves before invites go out).
• One shared running document per pair, from the template.
• A prep note before each one-to-one.
• An action list after each one-to-one, and a monthly summary of open actions for the manager.

Prep note layout:

One-to-one with <name>, <date>
Open actions: <action> (<owner>), <status>
Their topics so far: <list>
Recognise: <specific action and its impact>
Raise: <topic in one line>
Ask: <one or two questions chosen for this week>
Watch: <workload, upcoming leave, anything left open last time>

Checks before you finish

• The cadence and slot suit both time zones and working patterns.
• The employee's items come first in the agenda.
• Prep notes include open actions and specific recognition, not just questions.
• Notes contain facts and actions only; no sensitive personal details.
• No recording without everyone's agreement and a check of local law.
• Escalation topics were routed to HR, not handled in the notes.

Pitfalls

• Status meeting in disguise. If the manager could have read it, it should not take the meeting.
• The cancelled one-to-one. Cancelling tells the employee they are low priority. Move it, do not drop it.
• Same three questions every week. "Anything blocking you?" stops working by week three. Rotate.
• Feedback only one way. Ask for feedback on the manager regularly, and act on it visibly.
• Promising secrecy. A manager cannot keep a harassment report confidential. Say so kindly and involve HR.
• Notes as a file on someone. One-to-one notes are not a disciplinary record. If a performance concern needs formal handling, that goes through HR and the policy.

See also: performance-review-cycle, which these meetings feed with evidence.