Send the three-line email after every decision

Quick answer: Within a day of any meeting that settled something, send a recap of three or four lines. Say what was decided, who owns each piece, and when it's due. End with an invitation to correct you. It reads as helpful. It also leaves a dated record of who did what.

The decision nobody wrote down

Picture a Tuesday at 4:50 p.m. The meeting has run twenty minutes long. Somebody says, "Great, so we're going with the second vendor, and you'll pull the final numbers." Everyone nods and gathers their laptops.

Six weeks later the vendor is a success. In the quarterly review, the story is that your director "drove the vendor selection." You remember doing the cost comparison over two weekends. Nobody in that review remembers it, because nothing says it happened.

Nobody lied. People remember the version that's easiest to retell, and the easiest version has the senior person in the middle. Memory fades by Friday. Email keeps the date.

The three-line version

You don't need a memo. You need something a busy person can read in fifteen seconds.

Subject: Recap: vendor decision Thanks, everyone. Confirming where we landed: we're going with the second vendor. I'll get the cost comparison to Mark by Friday, and Priya's team will send contract terms by Monday. Tell me if I've got any of that wrong.

That's it. The last sentence matters most. It makes the email a request for correction, so nobody can read it as a claim. If nobody objects, the silence counts as agreement. If someone does, you've found the disagreement on Wednesday instead of in December.

Write it as a favor, not a file

The version that backfires reads like a lawyer built it. "Per our conversation, as I stated in the meeting, it was agreed that..." That tone tells everyone you're building a case, and people stop trusting the person who's building one.

Write it the way you'd write to a neighbor about a shared fence. Plain, friendly, specific. You're doing the team a service, because most meetings end with six people holding six slightly different versions of what just happened. You're the one who gets them back to one.

Some habits that keep the tone right:

• Send it the same day if you can, the next morning at the latest. After two days it feels like a rebuttal.
• Use "we" for the decision and names for the tasks.
• Put everyone's piece in, including the small ones. Giving people credit on the record is the fastest way to make the habit welcome.
• Keep it under eight lines. If it needs more, the meeting needed a project plan, not a recap.

Where your own name goes

This is the part women tend to skip, because it feels like bragging. It isn't. It's accuracy.

Say what you did in a clause, with a fact attached: "Based on the cost comparison I ran last week, we're going with the second vendor." No adjectives. No "I worked really hard on." Just the verb and the object.

Then do the same for everybody else. "Priya's team found the second vendor." Now the record is generous and complete, and the one line about your work doesn't stick out. People who hand out credit freely are believed when they claim their own.

Over a year, those emails stack up into something useful. When review season comes, you aren't reconstructing your spring from memory. You're scrolling through a dated list of decisions you moved forward. That's also the raw material for your next raise conversation, and saying your number and then stopping lands a lot better when you can point to the work.

When the credit is already getting fuzzy

Sometimes you notice it mid-project. A manager starts saying "we" about work you did alone, or a peer presents your slide as his own.

Don't confront anybody in the moment. Start sending the recap and make sure your boss is on it. Your manager can't repeat a version of events that your own email contradicts, and most won't try. If the problem is more habit than malice, and it usually is, the recap fixes it without a single awkward conversation. There's more on that in when your boss takes credit, fix the pipeline before the person.

It also feeds the thing you can't see. Your promotion gets decided in a room you're not in, and the people in that room quote whatever is easiest to find. A clear recap with your name in the right places is easy to find.

Where the email is the wrong tool

Some things belong on a call or in person. Anything emotional, anything that would embarrass someone if it were forwarded, anything where the real issue is a strained relationship. A recap of a hard conversation can feel like an ambush even when you meant it kindly. Have the conversation first. If a written follow-up is warranted, make it short and neutral.

A few more cautions:

• Some bosses dislike it. If yours reads recaps as second-guessing, send a version to yourself and keep your own notes. A dated list of what you did and what was agreed is still worth having.
• Don't send company files to a personal account. Most employers have rules about that, and breaking them can cost you the job you're trying to protect. Check your policy. Keep your records inside the systems you're allowed to use.
• If it's turned into a real dispute over pay, a demotion or something that looks like unfair treatment, stop improvising. That's the time to talk to HR and, if needed, an employment attorney. A recap habit is for ordinary Tuesdays, not legal strategy.

The first one is the hardest

Pick one meeting this week where something actually got decided. Open a reply to the invite, write three lines, and read it once for tone. Cut any word that sounds defensive. Send it before you leave for the day.

Someone will probably reply "Thanks, this is helpful." Someone else may fix a detail you got wrong. Both are fine outcomes.

By the third or fourth time, you're just the person who sends the recap. And on a team where nobody else writes anything down, that person is the one the story keeps coming back to.