How to Capture Decisions After a Team Meeting

The chamber met on Monday and agreed to seek an adjournment, brief senior counsel, and hold off on the counter-claim until the client confirmed the figures. By Thursday, one associate has briefed counsel, another has drafted the counter-claim anyway, and nobody sent the adjournment application because each assumed the other would. The meeting produced decisions; the notes recorded discussion. The gap between the two is where matters slip. Capturing decisions well is a distinct skill from taking minutes, and it is the one that actually moves work forward.

Record the decision, not the debate

Discussion notes tell you what was said; a decision log tells you what was resolved. Nobody needs a transcript of who argued which way. They need the settled outcome, stated plainly enough that a colleague who missed the meeting knows exactly what to do. For each item, write the decision as an instruction: "File the adjournment application by Wednesday," not "We discussed whether to seek an adjournment." If the meeting reached no decision on a point, say that too, and note who owns getting to one.

Capture the reason alongside the choice

A decision without its reasoning invites reopening. Three weeks on, someone questions why the counter-claim was deferred, and without the reason on record the whole discussion happens again. A single line, why this was decided, prevents it: "Counter-claim deferred until the client confirms the disputed invoice amounts." The reason also protects the decision if circumstances change, because the team can see whether the original basis still holds rather than arguing from memory.

Give every action an owner and a date

The fastest way to guarantee a task falls through is to assign it to "the team." Every action item needs one named person and one deadline. Shared responsibility is no responsibility. Structure each item the same way:

• What is to be done, in concrete terms.
• Who owns it, by name, one person.
• By when, an actual date.
• What it depends on, if anything, and the source of that deadline.

When the owner and date are explicit, the log doubles as a task list, and nothing hides in the collective.

Note the source of every commitment

Where a decision rests on a fact, a date, a figure, a document, a client instruction, record where that fact came from. A hearing date driven by a court order should cite the order; a step contingent on a client's confirmation should say so. This turns the log into something checkable, and it prevents a meeting-room assumption from hardening into an acted-upon fact that nobody verified.

Circulate while it is fresh, and keep it with the matter

A decision log is worth most in the first day, while people still remember the meeting well enough to correct it. Send it out promptly, invite corrections, and treat a disputed entry as a signal to resolve the ambiguity before work proceeds on it. Then attach the log to the matter itself rather than leaving it in an inbox, so that anyone picking up the file, including a colleague who was never in the room, sees the current state of decisions. Keeping the log in the shared matter workspace, as tools like Juniorlawyer allow, means the record travels with the case instead of living in one person's notes.

Update it when a decision changes

Decisions get revisited; that is normal. What causes damage is a stale log that still shows the old decision while people act on the new one. When a choice is reversed or refined, update the entry, note the change, and tell anyone who may be working from the earlier version. A decision log is only trustworthy if it reflects the present, and its whole value is that people can rely on it without asking.