Brag document template
A template gives you the structure. The only genuinely hard part is keeping it filled — which is exactly where most brag documents quietly die.
A brag document is a running record of your accomplishments and the impact they had, kept so review and promotion season starts with a year of evidence instead of a blank page. A template gives you the structure; the only genuinely hard part is keeping it filled — which is exactly where most brag documents quietly die.
Where the idea comes from
The practice was popularized by the engineer Julia Evans, who named a feeling most of us know: the review-season blank page, the "wait, what did I even do for six months?" panic. It began as a tool for people who do excellent work but undersell it — and that is still who needs it most. Your manager, however good, cannot remember everything you did, and they are the one who has to make your case to other people.
What a good template contains
Structure matters less than most people think, but a useful skeleton keeps you honest:
- Projects and their impact — what changed, for whom, how much
- Glue work — mentoring, onboarding docs, incident response, the things no ticket captures
- Skills learned, and scope you took on that you didn't have before
- Praise and recognition (screenshots count) and goals for next cycle
- Bare task logs — "attended standup," "reviewed PRs" with no outcome
- Everything, undifferentiated — a wall of entries with no impact
- Private grievances or vague notes you can't act on later
- Anything you'd be uncomfortable being reminded of months later
How to prioritize entries
- Impact first — the line a manager could repeat in a calibration room.
- Scope second — work that's bigger or more ambiguous than your level usually does.
- Glue work third — quietly essential, almost never logged anywhere else.
- Everything else only if it earns its place.
What a strong entry looks like
Every good entry answers one question: what changed, for whom, and how much? "Ran the migration" is a task. "Retired the legacy system across four teams, unblocking a year of stalled work" is an entry worth keeping. Write the impact version once, while it's fresh, so you're not rewriting it under deadline.
The reason a template alone isn't enough is upkeep. A blank document you have to remember to open loses to a busy week, every time — and by review season it's three months stale.
How Workfied helps here
Workfied is the brag-document template that fills itself. You send a ten-second voice or text note when something happens; it writes the dated, impact-framed entry for you, so the record is full the day you need it instead of empty. Built for you — never visible to your manager, your reports, or your company. Encrypted in transit and at rest.
Evidence
Why it exists
Brag docs were popularized to help people who do great work but undersell it get credit at review time.
Source: Julia Evans, jvns.ca
Why they die
The number-one reason brag docs fail is maintenance — a manual template loses to a busy week.
Practitioner consensus
Include vs cut
Cut "attended X." Keep one line of what changed. The template is the frame; impact is the point.
Workfied house view