QUICK ANSWER
What should a one-on-one meeting template include?
Include the meeting purpose, manager and direct-report roles, date, local time and named time zone, a shared time-boxed agenda, progress and wins, blockers and requested support, two-way feedback and development questions, priorities and tradeoffs, concise participant-visible notes, and proposed commitments with an owner role and requested date. Keep cadence, privacy, factual review, accepted tasks, performance ratings, employment decisions, and formal records in their qualified owners.
A useful one-on-one meeting gives a manager and direct report a recurring place to exchange context, surface blockers, ask for support, discuss feedback and development, clarify priorities, and propose next steps. It should invite contributions from both roles without silently becoming a performance rating, disciplinary record, transcript, or task system.
The downloadable pack includes a blank Markdown template and one blocked fictional 30-minute example. Matching Markdown, JSON, agenda and proposed-commitment CSV files, a closed Draft 2020-12 schema, a dependency-free validator, 65 positive and mutation tests, and a deterministic ZIP make its boundaries inspectable. The example contains roles rather than identities, participant-only summaries pending factual review, and proposed commitments that remain unaccepted until a separate authorized handoff.
Build the one-on-one around a shared conversation
Start with the job the two participants need the recurring conversation to do. Let both roles shape the agenda, keep notes proportionate, and route formal records and accepted work to their actual owners.
Define the local purpose and cadence
Write a purpose that fits this manager-direct-report relationship: progress, support, feedback, development, priorities, or another bounded need. Choose cadence and duration from workload, relationship, policy, and participant needs rather than treating a portable template as a universal schedule. OPM describes performance-management communication as ongoing, while Acas describes regular informal check-ins; neither source makes this exact cadence mandatory everywhere.
Sources: [one-on-one-pack], [opm-communication], [acas-performance]
Invite agenda contributions from both roles
Share the purpose and draft topics early enough for both participants to add questions. Include progress and wins, blockers and support, feedback and development, priorities and tradeoffs, and a close. OPM emphasizes employee participation and open questions, and Microsoft documents collaborative agendas and notes within its provider-specific meeting surface.
Sources: [one-on-one-pack], [opm-communication], [microsoft-notes]
Time-box prompts, not people
Give every topic a prompt and integer minutes, then make the sum equal the scheduled duration. Use timeboxes to protect the whole conversation, not to limit one role mechanically. The example gives manager, direct-report, and shared topics space in one 30-minute occurrence without claiming that this allocation fits every relationship.
Sources: [one-on-one-pack], [json-schema]
Keep notes concise, visible, and reviewable
Record short summaries linked to agenda topics rather than a word-for-word transcript. Decide who can see them, where they are retained, and how both participants can correct factual errors. Microsoft documents provider-specific access limits for collaborative meeting notes; Acas distinguishes informal check-ins from formal review records that may require an appropriate written record.
Sources: [one-on-one-pack], [microsoft-notes], [acas-performance]
Hand accepted work to the authorized task system
During the conversation, capture only a proposed description, proposed owner role, and requested date. After the owner agrees, create or update the task in the authorized tracker and preserve its real status there. Microsoft documents a separate task-list handoff from meeting notes; the pack deliberately keeps every fictional commitment proposed and every task-created flag false.
Sources: [one-on-one-pack], [microsoft-task-handoff], [opm-monitoring]
What this one-on-one meeting template owns
Use the pack for one recurring manager-direct-report development and support conversation. Keep formal employment, privacy, provider, attendance, and task-execution systems separate.
Included
- One fictional recurring series and one 30-minute occurrence with purpose, revision, exact UTC instants, reviewed local labels, named time zone, illustrative cadence, and reserved access reference
- Manager and direct-report roles without direct identifiers, five shared agenda topics totaling exactly 30 minutes, and contributions from the manager, direct report, and both roles
- Participant-only discussion summaries pending factual review and two proposed commitments with owner roles and requested dates but no acceptance or task creation
- Blank and completed Markdown, agenda and proposed-commitment CSV files, matching fictional JSON, closed Draft 2020-12 schema, fifteen-gate checklist, dated sources, validator, 65 tests, and deterministic ZIP
Not included
- A universal one-on-one cadence, mandatory question set, management style, coaching certification, employee-engagement method, or promise that meetings improve performance or retention
- Performance rating, appraisal decision, promotion, compensation, leave, accommodation, disciplinary process, grievance, investigation, termination, legal agreement, or other formal employment record
- Sensitive medical, disability, family, financial, demographic, union, complaint, or protected personal details and the systems, policies, qualified reviewers, and access controls they require
- Meeting invitation, provider configuration, identity, participant access, consent, recording, transcript, AI summary, attendance, participation, or engagement proof
- Task assignment, owner acceptance, priority, capacity commitment, status, execution, completion, evidence, or proof that a proposed action happened
- Legal, employment-policy, labor-relations, privacy, security, retention, accessibility, or regulatory advice, compliance decisions, or jurisdictional sufficiency
DOWNLOADABLE RESOURCE
Download the one-on-one meeting template pack
Inspect the blocked fictional example, adapt the blank template inside an access-controlled workspace, invite both participants to review it, and move only accepted work into your authorized task system.
One-on-one meeting template pack
A provider-neutral 30-minute manager-direct-report check-in with a shared agenda, bounded notes, and proposed-commitment handoff boundaries.
Format: Markdown, CSV, JSON, JSON Schema, checklist, dated sources, dependency-free validator, and tests in one reproducible ZIP
Locally reproduced August 1, 2026. SHA-256: 35cd44ea9691b4395d7f0f7330fffba1b67ac8a24e47789c1528f885dc5ab35f
Included
- Blank editable Markdown template and one completed fictional 30-minute one-on-one example
- Five-topic agenda CSV, two-proposed-commitment CSV, matching JSON record, closed Draft 2020-12 schema, and fifteen-item readiness checklist
- Dated source register, concurrency-safe deterministic publisher, dependency-free semantic validator, and 65 positive and mutation tests
Verification boundary
Rebuilt across UTC, Europe/Istanbul, Pacific/Auckland, and America/Los_Angeles with fixed timestamps and exact fourteen-entry archive order. Verified publisher formatting, source-to-archive byte parity, clean extraction and rebuild, recursive schema closure, role-only participants, UTC-backed local labels, exact duration and agenda sums, contributions from both roles, participant-only summary boundaries, proposed-commitment dates after the local meeting date, unresolved reviews, false authority boundaries, reserved links, no direct identifiers, no sensitive details, no provider, no tracking, and 65 passing tests.
Three one-on-one agenda patterns to adapt
Choose prompts that fit the current relationship and meeting purpose. Preserve time, privacy, factual-review, formal-record, and accepted-work boundaries when adapting a pattern.
Weekly support and blocker check-in
Use when: Work changes quickly and the direct report needs a dependable place to raise blockers, request decisions, and clarify near-term priorities.
Open with material progress, spend the largest block on constraints and requested support, clarify priority tradeoffs, and close with proposals. Keep normal status reporting elsewhere so live time focuses on context and help.
Structure
- Direct-report progress signal, shared blocker diagnosis, manager priority clarification, and proposed next steps
- A local cadence decision reviewed when workload, relationship, or participant needs change
Watch for: Do not use recurring frequency as proof of support, participation, engagement, performance, or a completed decision.
Sources: [one-on-one-pack], [opm-communication], [opm-monitoring]
Feedback and development conversation
Use when: Both participants need a bounded discussion about specific observations, learning goals, support, and future opportunities outside a formal rating event.
Invite questions from both roles, distinguish observations from conclusions, explore one development need, and record only proportionate participant-visible summaries and proposed follow-up.
Structure
- Two-way feedback question, development goal or experiment, manager support request, and later review point
- Explicit separation from appraisal ratings, compensation, promotion, disciplinary action, and formal HR records
Watch for: Follow the organization-approved employment process when the conversation becomes formal, sensitive, disputed, or consequential.
Sources: [one-on-one-pack], [opm-communication], [acas-performance]
Priority and proposed-action handoff
Use when: The participants need to clarify tradeoffs and leave with candidate next steps that still require owner acceptance in the real task system.
Name the competing priorities, the decision owner, the support needed, and each proposed commitment. After the conversation, ask each proposed owner to accept or revise the work in the authorized tracker.
Structure
- Priority question, relevant constraint, accountable decision route, proposed owner role, and requested date
- Separate task handoff with no assignment, capacity, execution, or completion claim stored in the meeting pack
Watch for: A line in meeting notes is not an accepted task. Do not report it as assigned, scheduled, in progress, or complete before the authorized owner acts.
Sources: [one-on-one-pack], [microsoft-notes], [microsoft-task-handoff], [json-schema]
Decide whether the one-on-one record is ready
The validator can expose contradictions inside the fictional record. It cannot decide whether a meeting is needed, what employment policy requires, or whether real participants have reviewed the record.
The purpose, cadence, participant roles, agenda ownership, duration, access, or participation method is unclear.
Choose: Keep the occurrence in draft. Let both participants refine the purpose and agenda, then confirm the local date, time, named time zone, access method, and total timebox.
Tradeoff: Preparation takes longer, but the meeting does not rely on a generic cadence or manager-only agenda that may not fit the relationship.
A topic contains sensitive personal details or crosses into appraisal, compensation, discipline, grievance, accommodation, investigation, or another formal process.
Choose: Move the material to the qualified employment, privacy, legal, or support owner and follow the controlled process. Keep only a safe routing note if policy permits it.
Tradeoff: The portable record contains less detail, but it avoids turning an informal template into an uncontrolled sensitive or formal file.
A note is written as a transcript, is visible beyond the intended participants, or has not been reviewed for factual accuracy and retention.
Choose: Keep publication and wider distribution blocked. Reduce the note to a concise summary, resolve access and retention, and give both participants a correction path.
Tradeoff: The record is less exhaustive, but its purpose and access boundary are clearer and factual disputes are easier to correct.
A proposed commitment is described as assigned, accepted, scheduled, in progress, or complete before the proposed owner acts in the authorized tracker.
Choose: Return it to proposed status, ask the owner to accept or revise it in the real task system, and keep status and evidence there.
Tradeoff: The meeting record cannot serve as the whole execution system, but ownership, capacity, dates, status, and evidence remain authoritative.
KEEP THE HANDOFF EXPLICIT
Download the tested one-on-one pack
Adapt the shared agenda, review notes with both participants, run the validator, and move accepted commitments to the authorized tracker.
Download the template packA validator pass does not approve access, create an employment record, accept a commitment, or prove a meeting outcome.
Open the general meeting agenda templateUse the general agenda owner for broader team, workshop, and kickoff facilitation. This page stays with the recurring manager-direct-report relationship.
What this one-on-one template cannot establish
A synchronized pack can reduce agenda and handoff drift. It cannot observe the real relationship, supply employment authority, or prove that the conversation helped.
- Cedar Vale, the series, occurrence, roles, prompts, notes, support request, and proposed commitments are fictional demonstration data.
- A role in the template does not prove identity, reporting relationship, invitation, access, preparation, consent, attendance, participation, understanding, acceptance, or accountability.
- The pack does not decide whether a one-on-one is necessary, how often it should happen, which questions are appropriate, or which employment, labor, works-council, privacy, accessibility, security, or retention rules apply.
- Concise notes are not automatically a formal or accurate employee record. Review purpose, access, correction, retention, and the qualified system before storing real discussion.
- A proposed commitment is not a task, promise, assignment, capacity reservation, deadline approval, status, completion, or evidence. Those states belong to the authorized tracker and accountable owner.
- OPM, Acas, Microsoft, and JSON Schema material supports selected communication, check-in, notes, handoff, and structural questions only. No source reviewed, certified, approved, or endorsed this original Playcode artifact.
- This ordinary informational article does not grant AI signup credits. Current eligibility, if any, belongs to separately qualified commercial entry pages.
Sources and verification record
The source register separates same-release artifact evidence from current public communication, performance-management, check-in, meeting-note, task-handoff, and schema guidance.
[one-on-one-pack] Playcode:One-on-one meeting template pack
Checked August 1, 2026. Supports: Same-release fictional record, synchronized projections, closed schema, validator, mutation tests, source parity, and deterministic archive evidence.
[opm-communication] US Office of Personnel Management:Communication skills for performance management
Checked August 1, 2026. Supports: Ongoing employee-manager planning and development conversations, open questions, employee participation, feedback, support, and future-focused discussion.
[opm-monitoring] US Office of Personnel Management:Performance management cycle: monitoring
Checked August 1, 2026. Supports: Ongoing feedback can surface progress and problems early while formal ratings and records remain separately governed.
[acas-performance] Acas:Reviews and appraisals: performance management
Checked August 1, 2026. Supports: Regular informal check-ins, feedback, coaching, support questions, fair objectives, and sharing an appropriate written record after formal reviews.
[microsoft-notes] Microsoft Support:Take meeting notes in Microsoft Teams
Checked August 1, 2026. Supports: Agenda, notes, and follow-up tasks can be collaborative and access depends on meeting participation and provider behavior.
[microsoft-task-handoff] Microsoft Support:Add a task list to meeting notes
Checked August 1, 2026. Supports: Meeting notes can hand accepted follow-up work to a separate task system with its own ownership behavior.
[json-schema] JSON Schema:JSON Schema Draft 2020-12
Checked August 1, 2026. Supports: Closed structural contract for the fictional example and nested records.
One-on-one meeting template questions
How often should managers hold one-on-one meetings?
There is no universal cadence in this template. Choose a frequency from the work, relationship, participant needs, organizational policy, and available time, then revisit it. The fictional recurring label is illustrative rather than a recommendation.
Who should own the one-on-one agenda?
Both participants should be able to contribute. The manager may maintain the meeting structure, but the direct report needs a clear way to add progress, blockers, support requests, feedback, development questions, and priority concerns before the conversation.
What should a manager ask in a one-on-one?
Use open, specific questions tied to the purpose: what moved forward, what is blocked, what support is needed, what observation deserves feedback, what development question matters, and which priorities or tradeoffs need clarification. Adapt the wording with the participant.
Should one-on-one notes be a transcript?
No for this template. Capture concise summaries linked to agenda topics, decide who can see them, and provide a factual correction path. Recording or transcription creates separate consent, access, accuracy, privacy, retention, and provider questions.
Is a one-on-one note an official performance record?
Not automatically. This pack explicitly excludes ratings, appraisals, compensation, promotion, discipline, grievance, investigation, and other formal employment decisions. Follow the organization-approved policy and qualified owners when a conversation enters a formal process.
How should action items leave the meeting?
Capture them first as proposed commitments with a proposed owner role and requested date. After the owner agrees, create or update the task in the authorized tracker. Keep acceptance, priority, status, changes, completion, and evidence in that system.
Can the validator prove the one-on-one was effective?
No. It checks the fictional record, closed keys, time-zone labels, duration and agenda sums, role contributions, note boundaries, proposed-commitment rules, blocked reviews, and false authority flags. It cannot observe attendance, trust, candor, support, learning, performance, retention, or another outcome.
Does this one-on-one meeting template grant Playcode AI credits?
No. This is an ordinary informational article with a downloadable resource pack, so it is intentionally AI-credit-ineligible. Any signup-credit eligibility is limited to separately qualified commercial entry pages under the current policy.
BUILD THE TEAM WORKFLOW
Turn accepted follow-up into a usable internal tool
Describe how your team prepares recurring conversations, controls access, reviews notes, accepts follow-up work, and tracks it in the right system. Playcode can build the internal workflow while named humans retain employment and management authority.
Build an internal toolThis informational article does not grant AI signup credits or verify participant access, employment-policy alignment, task acceptance, attendance, engagement, performance, retention, or outcomes.