How to report back on last week's actions
· 6 min read
Most recurring meetings end the same way: someone says "let's take that as an action", a name is attached, and everyone moves on. A week later the meeting opens with "so, what happened with…?" and you have a few seconds to report back on something you agreed to while thinking about something else.
Reporting back well is a small skill that does a lot of work. It shows the team what moved, keeps promises visible, and stops the same action drifting from meeting to meeting. This guide covers how to capture actions so they can be reported on, how to report each one in a sentence or two, and what to do about the ones you didn't do.
Write the action down properly when it's set
Most bad report-backs start a week earlier, with a vague action. "Look into the timeouts" can't be reported on, because nobody agreed what looking into them means. Before the meeting moves on, take ten seconds to pin three things down:
- Who owns it. One name. "The team" owns nothing.
- What done means. Something you could point at: a merged pull request, a number in a ticket, a decision written down.
- By when. Usually the next meeting, but say so.
"So that's mine: find out why the export times out on large accounts. Done means I can say what the cause is and whether it's a quick fix, by next Tuesday."
If you're the person writing the notes, write the actions in that form. If you're not, write your own actions down anyway. The official notes are often late, short or missing.
Mark each one before the meeting
The day before, go through your actions and give each one an honest mark: done, partly or not yet. Don't calculate percentages and don't argue with yourself about whether something counts. If done meant a merged pull request and it's still in review, it's partly.
Then look at what you actually did since the last meeting: your commits, pull requests, tickets and notes. You'll usually find three things: work that matches an action, work that matches no action, and actions with no work behind them. Each needs something slightly different in the meeting.
How to report back on each action
Lead with the mark, then the one fact that matters, then where to see it. One or two sentences per action is plenty.
Done
Say what changed for someone else, not what you did. "Done: the export no longer times out on large accounts. It was one query without an index. The fix is merged and running in production since Friday."
Partly
Say what's finished, what's left and when you expect the rest. "Partly: I know the cause, it's the missing index, and the fix is in review. I expect it merged by Thursday."
Not yet
Say why in one sentence, then say what should happen to it. "Not yet: the incident on Wednesday took most of the week. I'd still like to do it, by next Tuesday. Or if Sam has time, I'm happy to hand it over."
"Yeah, so the export thing, I had a look, there's a lot going on in there, there might be an index problem, I'm not sure, I'll keep looking at it this week."
The unclear version could mean done, partly or not yet. The team can't tell, so somebody will ask a follow-up question, and the conversation that should have taken ten seconds takes three minutes.
Report the work nobody asked for
Some of your best work won't match any action: the bug you fixed on the way, the test you made reliable, the incident you helped with. Mention it briefly, and say why you did it. "I also raised the delivery timeout, because the retries were hiding slow partners. That might come up with support."
This isn't showing off. Unplanned work is often why a planned action slipped, and saying so makes the not-yet easy to understand. It also gives the team a chance to say whether they'd have chosen the same priority.
When you didn't do it at all
The worst option is to skip it and hope nobody notices. Someone always does, usually at the moment it hurts most. A plain not-yet with a decision attached is better than silence every time.
- Renew it with a date you believe: "I'll do it by Friday."
- Hand it over if someone else is better placed: "Sam knows that code better. Sam, could you take it?"
- Drop it if it no longer matters: "Now that we've paused the migration, I don't think this is needed. Shall we drop it?"
An action that has been "not yet" for three meetings in a row is telling you something. Either it isn't important, or something is in the way that nobody has named. Name it.
Keep it short in the room
Report-backs are not the place for detail. If someone wants the full story, offer it afterwards, and put links to the pull requests or the write-up in the chat instead of describing them. Two sentences per action is a good ceiling. When everyone does this, the review of last week's actions takes a couple of minutes and the meeting can get on with this week.
A five-minute routine before the meeting
- Open last meeting's actions and find yours.
- Mark each one done, partly or not yet.
- Look at your commits, pull requests and notes since the last meeting.
- Match the work to the actions, and note the work that doesn't match.
- For each action, write one sentence: the mark, the fact, where to see it.
- Say them out loud once.
Staging Mind does most of this routine with you. The note it writes after a meeting keeps the actions with their owners and what done means. Before the next one, you mark them, see the work since in git, and practise reporting back out loud. In the meeting it notices when each action comes up.
Frequently asked questions
- How long should reporting back on an action take?
- One or two sentences: the mark, the one fact that matters and where to see it. If someone needs more, offer it after the meeting.
- What if my action depended on someone else?
- Say what you did, what you're waiting for and from whom. "Partly: the fix is ready, but it needs the platform team's sign-off. I've asked and expect an answer by Thursday."
- Should I mention work that wasn't an action?
- Yes, briefly, with the reason you did it. It explains where your time went and lets the team say whether it was the right call.
- What if nobody wrote the actions down last time?
- Write down the ones you remember being yours, check them with the person who ran the meeting, and report on those. Then, at the end of this meeting, read the new actions back out loud with their owners and what done means, so next time there's a list to start from.
- Should I report back on actions that belong to other people?
- No, leave those to their owners. If you were waiting on one of them, ask about it as a question: "Sam, did the rate limit number come back? I need it for the retry settings."
// Staging Mind
If you'd like the routine done with you, Staging Mind keeps the actions from each meeting, shows the work since in git, lets you practise reporting back, and says in the next note how many actions you reported on.
Start free: one session on us