Building a 1-on-1 Record (Karte): How Per-Employee History Pays Off in Handovers and Development
Key points - Don't write one-off notes — keep a per-employee history (karte) that accumulates over time - Separate shared notes (employee can see) from manager-only notes (private reminders) - The karte pays off most in handovers when a manager changes (no lost context, no re-explaining) - Carry action items forward so each 1on1 builds on the last - Purpose is support, not evaluation — keep records separate from evaluation to build trust
⚠️ Respect privacy and make the purpose (continuity and support) clear to employees.
1. One-off notes waste their own value
Writing 1on1 notes and never looking at them again is a missed opportunity. The value of records appears only when they accumulate per employee. When you can see what you discussed last time and what you agreed, the 1on1 shifts from a one-off meeting to a continuous conversation. For the fundamentals, see the beginner's guide to 1on1 questions; this guide is about accumulating and using records.
2. What a karte is
A karte is a per-employee history covering, for each person:
- What you discussed (topics)
- What you decided (agreements)
- Next actions until the following session
COCKPITOS 1on1s keep meeting records per employee, following a template.
3. Shared notes vs. manager-only notes
Records hold two kinds of content — what should be transparent, and what the manager keeps privately.
| Note type | Visible to | Use |
|---|---|---|
| Shared note | Employee can see | Decisions, next actions, things to keep transparent |
| Manager note | Manager only | Your own observations and reminders |
COCKPITOS supports both a shared note and a manager note, so you get transparency with the employee and a place for your own memory.
4. History pays off in handovers
The karte's real power shows when a manager transfers or changes. Without records, the new manager rebuilds the relationship from zero and the employee re-explains everything. With a per-employee karte, the new manager starts informed — aware of past topics, issues, and open actions. The more rotation your organization has, the bigger this payoff. See 1on1s for transfers and new managers where available, and pair this with AI summaries to keep records effortless (AI meeting summaries for 1on1s).
5. Action items keep the conversation going
Record the action items you agree on, and check "how did that go?" next time. That back-and-forth turns one-offs into a thread. COCKPITOS lets you keep action items in the template and carry them into the next 1on1.
6. Records as development data — with a boundary
Per-employee history is also useful for development: you can see what challenges someone faced and how they've grown, alongside skill maps (how skill visualization prevents turnover). One boundary: you cannot join individual Stress Check results with this data at the individual level (Article 66-10).
Summary
A 1on1 record becomes valuable when it accumulates as a per-employee karte. Separate shared notes from manager-only notes, carry action items forward, and you'll have history that pays off in handovers and development. Keep the purpose on support rather than evaluation, and the karte becomes a foundation of trust.