The term is the problem. Brag document, brag sheet, brag folder, whichever name you've met it under, it sounds like a place to write flattering things about yourself. For a lot of capable people that's enough to make the whole practice feel distasteful.
It helps to notice that the useful version isn't a brag at all. It's a source record: plain notes about what happened, kept because human memory is unreliable over a twelve-month cycle. Keeping an accurate record isn't the same thing as praising yourself.
Most advice on the subject is about sharing one: what to put in front of your manager, and when. This guide is about the half that comes first, the private record you draw it from.
Write down what happened first. Decide what it means later.
Two documents, not one
The record you keep and the version you eventually show someone are doing different jobs.
The source record is for you. It holds what happened while the details are still available: what you did, what changed, what was difficult, who was involved, and anything you may want to remember later. It can be rough. It can be incomplete. It doesn't need to make you sound good.
The version you present comes later. You make it for a particular purpose: a self-review, promotion conversation, resume, interview, or something else that asks you to explain your work.
That version should be selective. The source record shouldn't have to be.
Once you separate the two, keeping track of your work becomes much less loaded. You're not making a case for yourself on a Tuesday afternoon. You're writing down that the migration finished, what you did to get it there, and what changed because of it.
The case can wait until you need one.
Write for the person who will have forgotten
Imagine yourself eleven months from now with a review form open and only a vague memory of what happened last spring.
That's who you're writing for. They don't need to be impressed. They need the details you've lost.
A sentence can be enough. So can a number, a decision, a piece of feedback you're permitted to keep, or a note about something that was harder than it looked.
You'll probably remember the big launch. You may not remember the problem you caught before it became one, the process you quietly made easier, or the afternoon you helped someone else get unstuck.
Those are often the details worth preserving.
A template that doesn't require confidence
You don't need to know why something matters before you write it down. These six prompts are enough to give your future self something useful to work with:
Six prompts, none of them compulsory
- What happened. The event, in plain words, with a date.
- What I did. Your specific part, separate from the team's.
- What changed. What was different afterward.
- Who was involved. The people you worked with or who benefited.
- Evidence. A number, link, piece of feedback, or decision that followed.
- What I learned. Something you understood differently afterward.
Fill in one or fill in all six.
An entry that only says what happened is still useful. It's much more useful than the entry you never made because documenting it felt like another assignment.
Two worked examples
Say this is what you wrote at the time:
In the record
What happened. March 14. Month-end reporting broke again, third month running. Spent two days on it.
What I did. Traced it to the reconciliation step. Rewrote it and made the runbook that didn't exist.
What changed. Takes about half a day now instead of two. Three people can run it, not just me.
Who was involved. P. from finance tested it. Said it was the first month-end they hadn't dreaded.
What I learned. Should have written the runbook the first time it broke.
Eight months later, you need an example of a process you improved.
In the version you use
"Month-end reporting had failed three months running and was taking two days each cycle, with the process understood by only one person. I traced the failure to the reconciliation step, rewrote it, and documented the process. It now takes around half a day and can be run by three people instead of one."
You didn't have to invent a better story eight months later. You already had the facts. All you did was choose the ones that mattered for that conversation.
Keep the work that disappears easily
Some contributions come with an obvious artifact: the launch, the signed deal, the finished presentation, the project everyone remembers.
A lot of useful work doesn't. It might be the meeting you got unstuck. The risk you raised early. The person you helped through a difficult stretch. The customer situation you steadied. The decision you made that prevented more work later. The process you improved without anyone calling it a project.
Because these moments don't always look like accomplishments, they're easy to leave out.
The answer isn't to make them sound grander. Make them more specific.
"I'm good at supporting the team."
"The two newest people were both stuck on the same setup step. I rewrote that page of the guide, and the next person through didn't need to ask."
Specifics make the contribution visible without turning it into a boast. If you're struggling to name what yours were, 50+ work accomplishment examples may jog a few loose.
Keep it yours, and keep it clean
A personal work record should capture your contribution, not become a copy of your employer's information.
Keep the details you need to remember what you did, but leave out confidential material, customer data, proprietary documents, internal information you aren't permitted to retain, and anything else covered by an agreement you've signed.
Often you don't need any of it. "Reworked the reporting process and cut the monthly close from two days to half a day" may tell your future self everything they need to know without carrying the underlying files with it.
The goal is to preserve your history, not your employer's.
Let confidence follow evidence
There's a lot of career advice about advocating for yourself. That advice tends to assume the hard part is being willing to speak up.
Sometimes the harder part is remembering what there is to speak about.
A year is long enough for steady, useful work to become ordinary. Problems you solved stop being problems. Things you made easier become the new normal. Someone thanks you, you move on, and six months later the moment is gone.
Memory has a way of keeping the mistake and losing the Tuesday when you quietly handled something well.
A record gives you something better to work from. It doesn't have to tell you that you were brilliant. It just has to tell you what happened.
Confidence doesn't have to come first. Evidence can.
If you'd rather keep the record than the brag document
That's what Worth Noting is for.
It gives you a private place to keep the source material while it's still fresh: what happened, what you did, what changed, who was involved, the evidence, and what you learned.
There's no feed or profile, and nothing you write is published for other people to see. Your record stays on your device by default and isn't tied to an employer, so it can follow you from one role to the next.
Then, when you do need the polished version, you aren't starting with a blank page. You're starting with what actually happened.
Next: how to prepare before review season, or what a done list keeps that a to-do list can't.
Keep the record before you need the case. Start your record.
