Writing short, accurate summary emails after meetings and calls that fix who proposed what, who decided, and who owns each risk, so the record later readers rely on is true and on file.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
A project director at a water-engineering consultancy thought the subcontractor chosen for a treatment-plant upgrade was understaffed for its schedule, and said so in a client meeting in April. The client's program manager chose to proceed. That afternoon she sent a five-line email to the client and her own division head: the decision to proceed with the subcontractor, her stated concern about staffing for the September milestone, the client's acceptance of that risk, and the agreed check-in date. She asked them to reply if anything was misstated. Nobody did. In October the milestone slipped six weeks. When the client's new director asked why the consultancy had never raised the issue, her division head forwarded the April email, and the client absorbed the delay costs.
Why it works
A written record makes your contribution look better later, because authorship of ideas and warnings is fixed in a searchable form that persists whether or not anyone replies. It also makes the alternative costlier for the other side: once a confirmed summary sits unrebutted, disowning a decision or shifting a risk back means arguing against the archive. Searchable records, colleagues who rarely correct slightly-off framings in writing, and later reviewers who lack the original meeting's context make it most valuable.
The thinking behind it
Robert B. Cialdini Robert Cialdini's Influence (1984) describes commitment and consistency: once people have taken a position, especially a written one, they feel pressure to act in line with it. A same-day summary that the client did not correct records the client's acceptance of a risk in writing. Later, disowning that acceptance means acting against one's own written position, which is much harder.
George A. Akerlof George Akerlof's The Market for "Lemons": Quality Uncertainty and the Market Mechanism (1970) showed that people who cannot verify claims discount all of them, honest ones included. Later reviewers of a dispute cannot verify what was said in a meeting months earlier. A contemporaneous written record is information they can check, which is why it settles arguments that memory cannot, and why a slanted one ruins its author's credibility once found.
When it fits
Any decision where credit or blame will be argued later qualifies: a risk you raised and someone else accepted, an idea you proposed, a commitment made out loud. It needs nothing but discipline and access to the people involved. It matters most when reviewers turn over, stakes are high, and your warnings are likely to be forgotten if they turn out right.
How to use it well
Treat the summary as the last part of the meeting.
- Send the summary the same day, while memories are fresh and a correction is easy.
- Keep it short and neutral: what was decided, who decided, which risks were raised and by whom, what was accepted, the next date.
- Send it to everyone who was in the room and to the owner of the outcome, and ask them to correct anything misstated.
- Describe other people's positions in words they would use themselves.
- File it where you can find it.
Make it routine, for decisions that went your way as well as those that didn't. A habit of accurate summaries reads as professionalism. A summary that appears only when you disagree reads as building a case.
What it costs and where it backfires
Drafting takes time and, done badly, makes you look guarded; colleagues may start writing back defensively or leave you out of informal conversations. If the other side documents too, the record becomes contested and the advantage shrinks. Accuracy is the boundary. Once a summary states agreement that wasn't reached, names someone as owner of a risk they never accepted, or claims an idea that wasn't yours, it is a falsified record, and it will be read that way when the thread is read in full.
When it is used on you
Summary emails that restate meetings in one party's favor, with phrases like 'as I proposed' or 'confirming the risk you accepted', need an answer. Reply in writing the same day, briefly and factually, to every summary that misstates what was agreed. Once both sides document, the record is contested. If you review a dispute, read the full threads.