June 20, 2026

A brag document template you'll actually keep (copy and paste)

Most brag-doc templates are too elaborate to maintain. Here's a minimal one built around a single 30-second-a-day habit — and how to turn it into a review.

Most brag-document templates fail for the same reason most journals fail: they ask for too much. A template with ten columns and a tagging taxonomy feels productive to set up and is abandoned within two weeks. The only template that survives contact with a busy work week is one you can fill in thirty seconds, on the worst day, without thinking. This is that template.

The capture format is one line per entry, four fields, nothing optional. Date. What you did, in plain language. Why it mattered (the "so what"). And a link or reference if one exists. That's it. Example: "2026-05-22 — Caught a race condition in the payments retry logic during review. Would have double-charged customers in prod. (PR #4821)". You are not writing for an audience today; you're leaving enough detail that your future self can reconstruct the story months from now.

Group entries into a handful of buckets so review season is a selection problem, not a search. Five buckets cover almost everyone: Shipped (what you built or delivered), Fixed (problems you caught or solved), Led (decisions, direction, influence), Grew (mentoring, unblocking, helping others), and Learned (skills and scope you took on). When something happens, drop it in the right bucket in one line. Don't overthink which bucket — the point is capture, not taxonomy.

The single habit that makes the template work is an end-of-day trigger. Before you close the laptop, ask one question: did anything today take real effort or involve a real decision? If yes, one line goes in. Most days that's thirty seconds; many days it's nothing, and that's fine. The cost of the habit is trivial; the cost of reconstructing a year from memory the night before your review is an hour and a worse result.

When review season arrives, you don't write — you select and translate. Read through the buckets, pick the strongest two or three entries for each behavior your company's rubric cares about, and rewrite each from "what I did" into "what it changed": scope, effect, and what would have gone wrong otherwise. Mark anything you're estimating rather than measuring. The review writes itself because the raw material is already sitting in the template.

A few rules keep the template honest. Capture the invisible work, not just shipped features — the mentoring and judgment calls are what separate levels and they never land in a ticket. Be specific enough to tell a story ("fixed bug" is useless; "caught the data-loss bug in the migration review before it shipped" is evidence). And never backdate or inflate — a brag doc is only useful if you trust it, and the first time you pad it, you stop believing your own record.

You can keep this in a text file, a Notes app, a spreadsheet, or a private journal — anywhere you'll actually return to daily. Meritbook is the structured version of exactly this template: the same five buckets and one-line habit, but with tamper-evident timestamps so nothing looks backdated, and a generate step that turns the entries into a review with every claim traceable back to what you wrote. The tool is optional. The habit is not. Start the file today; your next review depends on a record you haven't written yet.