How to Write a Brag Document (With Template)

What Goes in a Brag Document

A brag document is a private, dated record of the work you actually did, written in your own words while you still remember it. You keep one because reviews, promotion cases, and resume updates all demand specifics, and specifics are exactly what memory drops first.

Five kinds of entries cover most careers:

• Shipped work. Projects, deliverables, launches, and reports that went out the door with your name on them.
• Fixes. Problems you found or resolved, especially the ones that were quietly costing people time.
• Work that made others faster. Documentation, tooling, process changes, unblocking a teammate. Chronically underreported, because it never has a launch date.
• Learning. Skills, tools, and domain knowledge you picked up, and where you applied them.
• Feedback received. Praise from a client, thanks from another team, a manager’s comment. Capture the words, the person, and the date, because paraphrases decay into nothing.

The Template

Copy this into wherever you actually write: a doc, a notes app, a text file. One block per entry. Skip fields that don’t apply.

ENTRY: date CATEGORY: shipped / fixed / made others faster / learned / feedback WHAT HAPPENED: One or two sentences. Name the project, the system, or the person involved. Write it so that you-in-ten-months knows what this was. MY PART: What you specifically did. Use the verb that matches the facts: led, built, ran, reviewed, proposed, tested. OUTCOME: What changed because of it. Numbers if you have them. If not, a name, a date, a link, or a before-and-after state. Most outcomes land after the entry date. Add them when they land and date the addition.

Three Filled Examples

Two of these are deliberately not from software, because brag documents are not an engineering habit. They are a working-adult habit. Notice the dates on the OUTCOME fields: you write the entry when the work happens, then come back for the result once there is one.

An IT Administrator, After a Fix

ENTRY: 2026-03-12 CATEGORY: fixed WHAT HAPPENED: Recurring VPN drops for the Denver office. Eleven reports over two weeks, all filed as "the network is flaky." MY PART: Traced it to an MTU mismatch on the new firewall, reproduced it, tested the fix after hours, wrote the change record, rolled it out. OUTCOME (added 2026-04-09): No drop reports in the four weeks since the change. Denver helpdesk tickets went from about eight a week to one.

A Consultant, After a Delivery

ENTRY: 2026-04-30 CATEGORY: shipped WHAT HAPPENED: Vendor-selection report for the Meridian engagement: three weeks of stakeholder interviews, a weighted scoring model, and a final recommendation. MY PART: Ran nine of the twelve interviews, built the scoring model, wrote the recommendation section end to end. OUTCOME (added 2026-07-15): Client signed with the recommended vendor in May. The partner has reused the scoring model on two engagements since.

A Developer, After a Speedup

ENTRY: 2026-05-08 CATEGORY: made others faster WHAT HAPPENED: CI pipeline had crept up to 40 minutes and people had started batching pull requests to avoid it. MY PART: Profiled the build, split the test suite across four runners, cached dependency installs. OUTCOME (added 2026-06-02): Pipeline runs in 12 minutes now. Batching stopped, and merges happen about twice as often as they did in April.

Write It Strong and True

The entries above follow four rules, and the rules matter more than the format.

Use precise verbs when the facts support them. “Led the migration” only if you led it. If someone else led it and you wrote the runbook and ran the cutover, say that. It is specific, verifiable, and still impressive; vague credit-taking reads as exactly what it is.

Surface the outcomes you buried. Reread your entries a week later. People routinely hide their best result in a subordinate clause, as in “while updating the onboarding doc, which new hires now finish in one day instead of three.” That number is the entry. Promote it.

Cut hedges the evidence doesn’t require. “Helped out a bit with the rollout” is the right phrasing only when it is true. If the ticket history shows you did the rollout, write that you did the rollout. Hedging accurate claims is not modesty; it is bad data.

Never add what didn’t happen. This is the hard line. No invented numbers, no outcomes written as landed when they haven’t, no characterization you couldn’t defend with the person involved in the room. The document’s entire value is that you can stand behind every line when someone asks a follow-up question. One inflated entry taxes the credibility of all the others.

Keeping It Up When You Keep Forgetting

Be honest about why you’re reading this: review season is close and you can’t remember March. That is the normal case. Memory fails at precisely the moment reviews demand specifics, which is the reason this document exists, and also the reason most attempts at keeping one die within a few weeks.

Three maintenance patterns work, for different kinds of people:

• The Friday ritual. Fifteen minutes, blocked on your calendar, last thing before the weekend. Scan the week and write two or three entries. If you already send a weekly update to your manager, the same scan produces both. This produces the best records and fails most often, because the block is the first thing sacrificed in a busy week.
• The monthly reminder. A recurring calendar event with a lower bar: thirty minutes to reconstruct the month from sent email, closed tickets, and your calendar. Lower fidelity, much harder to fall off.
• The daily one-liner. One sentence about the day, somewhere you already write. This is keeping a work journal at its most minimal. No structure required in the moment; structure gets added at rollup. Lowest friction, easiest to keep alive.

Pick the pattern that matches habits you actually have, not habits you want. If you keep the one-liner as free text, Journaled turns those descriptions into structured, searchable entries with a written summary you can edit before saving, which makes the quarterly rollup a reading job instead of an archaeology job.

The Quarterly Rollup

Whatever running record you keep, review it once a quarter and pull the entries that mattered into the brag document proper, in the template format above. A quarter is the right interval: short enough that you still recognize your own notes, long enough that outcomes have landed. The fix from January has its four quiet weeks of evidence by March. The rollup pass is also when you revisit entries with an empty or stale OUTCOME field and add, with a date, whatever has landed since.

Four quarterly rollups, stacked and trimmed, are the annual version. You assemble that yourself at review time; do not try to write a year from raw daily notes in one sitting, because that is the exact task you were avoiding when you stopped updating the document. If your review includes a written self-assessment, the quarterly rollups are most of the draft.

Common Questions

How Long Should a Brag Document Be?

A quarterly rollup usually lands between half a page and a page. The annual version gets trimmed for its audience; a promotion packet and a resume update pull different lines from the same record.

Who Actually Sees It?

By default, only you. Excerpts feed your self-assessment, your promotion case, and your one-on-ones. The raw document stays private, which is what lets you keep it honest instead of performative.

What If My Work Has No Measurable Outcomes?

Numbers are one kind of evidence, not the only kind. A name, a date, a quote, or a before-and-after state all count. “The team stopped rebuilding the report by hand” is an outcome even though nothing in it is a number.

Isn’t This Just Bragging?

It is a record, not a broadcast. Nothing gets announced; the document sits there so that accurate claims are available when someone asks for them. The accuracy rules above are what separate it from bragging.

Should Failures Go In?

Include what you can defend. A project that failed but where you caught the problem early, salvaged the timeline, or documented the lessons is a legitimate entry, usually under learning. Leaving a whole quarter silent will read strangely to you later.

I Missed Most of the Year. Where Do I Start?

Start today with a reconstruction pass: sent email, closed tickets, your calendar, anything you shipped. Write what you can verify and let the rest go. An honest partial record beats a padded complete one, and next quarter the record will be running.