What should a manager write down after a 1:1?

Before each 1:1, write down the date, the points you want to raise, any areas of concern and anything you need to follow up from the previous meeting.

You do not need to over-engineer this. The key thing is to understand what you need to get out of the meeting. If there was an action last week, do not rely on memory. If there is a concern you need to raise, write it down before the meeting so you can be clear rather than vague.

What should be written down during or after the meeting?

You should write down what was discussed, particularly any issues that the team member raises or that you raise. Capture areas of concern, performance points, agreed support and any actions.

I would not share everything you write. You may need your own manager notes where you are more direct about concerns you want to raise, the agenda you want to cover, or patterns you are starting to see.

What should the action tracker include?

In simple terms, it should include what the action is, who owns it, and what the expectation is on delivery date. That is enough for most 1:1s.

The important thing is that you actually come back to it. Failing to follow up is worse than not asking in the first place. The person raised something, you wrote it down, and then nothing happened. That devalues the concern and the meeting.

How should recurring concerns be recorded?

Keep a separate section in your personal notes for recurring concerns. Add specific examples over time. This helps you build a clear narrative if you later need a performance conversation.

Do not use this as a secret dossier. Use it as a way to be fair and specific. If you ever need to say someone is falling below expectations, you should be able to explain what happened, when it happened and how you have already tried to address it.

How should career or development notes be captured?

It is reasonable to have a shared section for skills they want to improve, areas they would like to move into and potential learning opportunities.

Just keep that balanced with ongoing work and expectations. Development conversations are useful, but they still need to sit inside the reality of the role, the work and any cost or capacity constraints.