Documenting 1 on 1 meeting notes works when you keep one running log per person, not a new doc every week. Capture topics, decisions, and owned actions in the same place. Share the log. Use an AI assistant only to draft the next rows after the meeting, then confirm the words together.
Why documenting notes is the real bottleneck
The bottleneck is not the 1 on 1 itself. It is the unpaid hour after, when you try to turn talk into a record someone can trust.
You leave the call with a good feeling. Then Slack fills up. You tell yourself you will write notes tonight. Tonight you write a wall of text in a private doc. Next week you cannot find the promise about the design review. Your report wrote a different version in their notebook. You spend the first ten minutes of the next 1 on 1 reconstructing history.
That is operational drag. It steals coaching time. It also trains people to treat the meeting as theater. If nothing is written in a place both of you open, the meeting did not really finish.
According to iSilta's 2026 survey of 146 organizations, 78% cite weak 1 on 1s when manager training is late or thin. Weak 1 on 1s often have plenty of talk and almost no usable notes. According to the same survey, 81% do not measure behavior change after manager training. A running log is a simple way to see whether last week's ask actually moved.
What belongs in a running 1 on 1 log?
A running 1 on 1 log is one living page per report that grows over time, with open actions at the top and dated meeting rows below.
Do not start a fresh Google Doc for every Tuesday. You will lose the thread. Do not paste a transcript. You will never read it. Write only what next week's you will need:
- What they wanted to talk about
- What you needed to cover
- Decisions you both accepted
- Energy or blockers in one honest line
- Action items with one owner and a next date
Private thoughts can sit in a manager only box: a coaching hypothesis, a reminder to listen more. Do not mix that with the shared log. Shared rows should be facts you would both sign.
Free running 1 on 1 log template
Keep one log per person. Fill these tables in the meeting. Duplicate the meeting tables after each talk. Move unfinished work into Open items at the top.
Running 1 on 1 log: NAME
Open items
| Action item | Owner | Next date | Status |
|---|---|---|---|
| open | |||
Meeting YYYY MM DD
| Field | Notes |
|---|---|
| Their topics | |
| My topics | |
| Decisions | |
| Energy or blockers (one line) |
| Action item | Owner | Next date |
|---|---|---|
| Field | What to write | What to skip |
|---|---|---|
| Their topics | Two or three bullets in their words | Your interpretation of their motives |
| Decisions | What you both agreed to do or not do | Ideas you only floated |
| Action item | A done state a stranger could check | Vague follow up later |
| Owner | One name, you or them | We or the team |
Use the log in the last five minutes of the meeting. Read the new action row out loud. If they disagree with the wording, change it before you leave. That five minutes saves the reconstruction tax next week.
If you are tired of copy pasting this template every week, iSilta automates this entire loop for your team automatically.
How an AI assistant should help with notes
An AI assistant is useful when it turns your short notes into clean action rows. It is harmful when it pretends it sat in the room.
The operational bottleneck is typing structure, not thinking. You already know what was said. You lack time to format owners and dates for eight reports. That is the AI assistant angle: draft the table, do not invent the story.
After the meeting, paste only the bullets you wrote, or speak them into a tool that already stores your 1 on 1. Ask: turn these notes into action rows with one owner and a next date. No new facts. Then sit with your report (or send the draft in the shared log) and tick yes or no on each row.
Do not dump a recording into a public chatbot. Do not let a model add a performance verdict you did not say. According to iSilta's 2026 survey of 146 organizations, 51% plan AI for manager coaching within 24 months. The version that builds trust is coaching on structure. The version that burns trust is a secret summary your report never saw.
iSilta AI Assistant coaching sits next to the same notes and Action Points your report can see. You confirm deliverables once. The loop does not live in a personal markdown file you forget to copy.
What is the best way to follow up on 1 on 1 action items?
- Write each action in one shared list both people can see.
- Name one owner and a next date.
- Open the list at the start of the next 1 on 1.
- Mark done or still open.
- Keep notes and actions in the same log.
Follow up is not a Wednesday Slack poke. Follow up is a visible row that survives until someone marks it complete. If the action is real delivery work, link the ticket. If it is a career or wellbeing promise, it still belongs in the log. Tickets alone miss the human work. Chat alone hides the list.
Start the next 1 on 1 on the Open items table. Close what is done. Reset dates that slipped. Only then add new topics. That order is how notes become a system instead of a diary.
How do you keep the log honest over months?
Honesty means the log matches what you would both say happened, and stale rows get closed or dropped.
Once a month, scan Open items. If something has sat for three meetings, it is not an action. It is a wish. Either do it, drop it, or rewrite it so it is small enough to finish. A bloated log makes people stop reading. A short log makes people show up prepared.
Watch for pattern lines. If energy or blockers repeats, that is a topic for a deeper talk, not another empty action. If every meeting creates five new rows and closes zero, you are collecting, not leading.
When someone changes managers, the running log is the handoff. A private brain dump is not. Shared notes protect the report from starting from zero with a new lead.
How documenting methods compare
| Method | Speed | Risk |
|---|---|---|
| Memory only | Fast in the room | Both people forget different facts |
| New doc each week | Feels tidy | Open items vanish across files |
| Full recording and transcript | Low typing | Trust cost; nobody rereads it |
| Running log plus AI draft | Fast structure | Works only if humans confirm owners |
| iSilta notes and Action Points | No weekly copy paste | Still needs a five minute close in the meeting |
Implementation steps
- Create one running log file per report this week. Copy the tables above.
- Move any leftover promises from Slack or old docs into Open items.
- End the next 1 on 1 by filling the date row together.
- If you use an AI assistant, generate action rows from those notes only, then approve them in the log.
- Start the following meeting on Open items before any new agenda.
- Once a month, delete or archive rows that no longer matter.
Frequently asked questions
What should you write in 1 on 1 meeting notes?
Write their topics, your topics, decisions, mood in one line, and action items with an owner and a next date. Skip a full transcript. The log should help next week's meeting, not recreate the hour.
Should both people see the 1 on 1 notes?
Yes for topics, decisions, and actions. Private coaching thoughts can stay in a manager only field. If only you can see the log, your report cannot help keep it true.
How do you document 1 on 1s without recording the call?
Take short notes during the talk. In the last five minutes, fill the running log together. Confirm actions out loud. You do not need a bot in the room to have a usable record.
When should an AI assistant summarize 1 on 1 notes?
After you have written or spoken the facts, not instead of listening. Ask the assistant to draft action rows from your notes. You and your report still approve every owner and date.
How long should you keep a running 1 on 1 log?
Keep open items until they close. Keep a short history of recent meetings so you can see patterns. Archive old rows after a cycle so the log stays easy to scan.
Related: The Accountability Gap: how to track 1 on 1 action items, One on one meeting notes template: shared action and context, Is it OK to use AI to prepare for 1 on 1s?.
Prefer prepared conversations over memory alone? Explore iSilta features or try the product demo.