Building a "Brag Bank": Receipts, Metrics, and Praise You'll Actually Use

Two weeks before my 2016 review I sat down to write the self-assessment and found I could account for roughly four months of the year. October through January were vivid. February through September had evaporated — not the work, which I knew perfectly well I’d done, but the evidence: which campaign moved which number, by how much, and who had said so at the time. I filled the gap the way everyone fills it, with adjectives. I got “meets expectations” and a 2.8% increase, and I’ve never fully stopped suspecting the two were connected.

The obvious lesson is “write things down,” and the obvious lesson is why so many of these logs die by March. I’ve started four. Three were diaries — dated, chronological, prose — and diaries are useless under pressure, because the question you bring to them is never “what happened in April.” It’s “give me three examples of cross-functional influence with numbers attached, in the next twenty minutes.” A diary can’t answer that. A database can.

So build a database. Small one, designed backward from the withdrawal.

Start with the withdrawals, or you’ll build the wrong thing

There are exactly four moments this file exists to serve, and each one asks for the same raw material in a different shape:

1. The annual self-assessment, which wants your year sorted by your company’s competency language, not by month.
2. The promotion case, which wants scope evidence and results at the next level — the raw feed for the one-page doc that argues for you in a room you’re not in.
3. The interview, two or three jobs from now, which wants a story with a situation, an action, and a number — and which will ask about work performed at a company whose systems you can no longer open.
4. The pay conversation, which wants the two or three items that most directly connect your work to money, said out loud without notes.

Notice what all four have in common: none of them is chronological, all of them are keyword-driven, and three of them happen months to years after the work. That’s your spec. Every design choice below falls out of it.

The five fields

One row per entry. Anywhere you like — a spreadsheet, a plain text file, a notes app — as long as it’s searchable and it’s yours. The fields are non-negotiable; the tooling isn’t.

The same win, logged twice

Here’s an actual entry of mine from a Tuesday, in the form I’d have written it in 2016:

4/12 — big week, finally got the nurture sequence live after all the back and forth with product, Dana was great about it, results looking good

And the version that survives contact with a review cycle:

Claim: Rebuilt and shipped the six-email nurture sequence after a two-month cross-team stall. Number: Open rate 19% → 31%; demo requests from nurture 40/mo → 96/mo (Q2 vs. Q1 baseline). Proof pointer: “Nurture v2 — Q2 results” deck, 6/30; Marketo dashboard “Nurture Performance.” Witness: Dana R. (product) ran QA; Marcus T. (sales ops) confirmed the demo attribution. Tags: revenue, cross-functional, process.

Same Tuesday, roughly the same four minutes of typing. The second is a promotion bullet, an interview answer, and a line in a raise conversation, already assembled. The first is a feeling with a date on it.

The deposit: ten minutes, monthly, on a calendar hold

1. Sent mail, not inbox. Scan your own sent folder for the month. It’s a near-perfect record of what you actually did, in your own words, with dates — and unlike your calendar, it captures the work rather than the meetings about the work.
2. The praise sweep. Search your mail for thank you, nice work, saved us, appreciate. Copy the sender’s exact sentence in. Their words, not your summary — a quoted line from a director carries weight in a calibration room that “positive feedback from leadership” never will.
3. Two or three entries, maximum. If you’re writing eight, you’re logging tasks. The bar: would this be worth thirty seconds of a stranger’s attention?
4. One number check. Take the entry with the shakiest metric and confirm it while the dashboard still says what it said.

Twelve sessions a year, two hours total, feeding every item on that withdrawal list — including the six-week performance review prep sequence, which gets vastly easier when the raw material already exists.

Metric archaeology: getting numbers you never wrote down

The most common state of affairs is not “I have no log.” It’s “I have a log with holes where the numbers should be.” Four ways to backfill, roughly in order of yield:

• Your own sent mail is a dated primary source. Any figure you emailed to someone is a figure you can cite, with a date and a recipient. Search for %, $, and increase in your sent folder and you’ll be startled what falls out.
• Ask the owner, not the system. The analyst or ops person who owns the dashboard can usually pull a historical number in two minutes and is generally pleased to be asked. Ask in writing so the answer arrives in writing.
• Bracket honestly when you can’t confirm. “Roughly a third” and “somewhere between 40 and 50 accounts” are legitimate, credible, and survive scrutiny. A precise-sounding number you can’t source is the single most expensive thing you can put in a promotion packet — one audited-and-inflated figure doesn’t cost you the cycle, it costs you the benefit of the doubt permanently.
• Reconstruct from artifacts. Old decks, invoices, ticket exports and status reports carry numbers you forgot you’d already computed.

And do this on a clock, because your evidence has a shelf life that nobody warns you about:

Keep it portable — and know where the line is

This is the part that separates a brag bank from a folder of screenshots, and it’s the piece almost nobody gets right until they’ve been laid off once.

Your access ends the hour your employment does. Not “shortly after” — the hour. Median tenure with a single employer was 3.9 years in January 2024 (3.6 for women), per the BLS Employee Tenure release, which means a normal career involves doing this handoff eight or ten times. So the working copy of your brag bank does not live on a company laptop, a company drive, or a work email account. Personal file, personal device, updated in the same ten minutes.

Two more things worth knowing, both neutral facts rather than advice:

• Your formal file may be legally available to you. Roughly two dozen states give private-sector employees some right to inspect their own personnel records, and the details vary a great deal. California’s is among the most specific: under Labor Code §1198.5, explained by the state’s Labor Commissioner, an employer generally has 30 calendar days to respond to a written request to inspect or copy, must keep the records at least three years after separation, and a former employee may make one such request a year. Your state may give you more, less, or nothing — check your own labor department before assuming.
• Contemporaneous records are the record — and there are clocks. The EEOC’s filing deadlines are generally 180 calendar days from the discriminatory act, extended to 300 where a state or local agency enforces a corresponding law, with different rules under the Equal Pay Act. I hope you never need this. Dated notes written at the time are worth far more than a reconstruction written later — true whether the eventual use is a promotion case or something less pleasant.

What this is worth, in the only units that count

Here’s the honest case for two hours a year. U.S. employers project average salary-increase budgets of 3.4% for 2027, essentially flat against 3.5% in 2026, in WTW’s Salary Budget Planning Report (surveyed March–May 2026; 1,650 U.S. organizations responding). WTW’s framing of the trend matters more than the headline: employers are shifting away from broad-based increases toward pay targeted and differentiated by performance.

Read that as a sentence about evidence. A flat pool divided unevenly is a pool allocated to whoever makes the most defensible case — and defensibility is exactly what your five fields manufacture.

Where this fails

Three failure modes, all of which I’ve either committed or watched:

You log activity instead of impact. Forty entries a year describing tasks you were paid to do is a to-do list with better formatting. If an entry has no number and no witness, it isn’t an entry — it’s a Tuesday.

You build the bank and never withdraw. The file gets meticulous and the self-assessment still gets written from memory the night before, because opening it feels like homework. The fix is scheduling the withdrawal, not the deposit: a hold six weeks before review season that says read the bank, and a second one each year for the annual audit I run on my own career.

You write it for yourself. The entries sit in your shorthand, tagged with your categories, phrased in your team’s jargon. Then you go to write a LinkedIn profile a recruiter will actually read and discover none of it translates. Write the claim field the way you’d say it to a smart person at another company, and portability comes free.

The first month feels absurd — you’ll write two entries and wonder if that’s the whole point. It is. The value isn’t in any single row; it’s that in three years you’ll have sixty of them, tagged and sourced, on a device nobody can revoke, at the exact moment somebody asks you to justify a number.