AI Guides › Career & Work
The One-Page Brag Document Worth Keeping Updated
By Nigel Guy · 2 min read
The usual approach to proving your worth is reconstructive: a review or an
interview comes up, and you sit down trying to remember everything you did
over the past year. Memory is bad at this. The wins that come to mind are
the recent and dramatic ones — the quieter, compounding work that actually
built your case gets left out because you'd genuinely forgotten it happened.
The rule: capture the evidence when it happens, not when you need it — a
brag document is a running log, not a document you write from scratch under
deadline.
The mechanism: the Running Entry
- Add an entry the week something happens, while it's still specific.
Two or three lines: what happened, what you did, what changed because of
it. Not a polished sentence — a note you'll be able to expand later.
- Capture numbers and outcomes at the time, not after. "Reduced X by Y"
is far easier to write accurately in the moment than to reconstruct
months later from memory.
- Log feedback verbatim when you get it, especially unprompted praise
from a colleague or manager. It's more credible in someone else's words
than paraphrased in yours later.
- Review it monthly, not just before you need it. A five-minute skim
keeps it current and stops six months of work compressing into one vague
memory of "it was a busy quarter."
- Pull from it, don't write from it directly. When a review or interview
comes up, the document is raw material to select and shape — not a script
to paste in as-is.
Where AI genuinely helps
Turning a rough running log into a tight, quantified case for a specific
review or interview is exactly the kind of organising work AI is good at —
see "Using AI To Negotiate A Raise Without Sounding Like You Used AI" for the
same principle applied to one specific conversation. It's much less useful
for the logging step itself, which needs to happen in the moment, from you.
What to skip
Skip trying to build the whole document retroactively once you already need
it — that's the reconstruction problem this mechanism exists to avoid, not
a shortcut around it. Skip padding entries with vague achievements just to
keep the log looking full; a short accurate log beats a long inflated one.
Guardrails
- Entries need to be true and specific enough that you could defend them in
a follow-up question — don't let a later draft round anything up.
- Keep the document somewhere private and appropriate; it often contains
candid notes about colleagues or management that shouldn't circulate.
- A brag document helps you make your case — it doesn't guarantee the
outcome of any specific review, raise, or interview.
All 751 AI guides · JulieMango plans from £17/mo