Puvio
Puvio
  • How it works
  • Pricing
  • Stories
Start free

Answers

How to3 min read

How do you write a brag doc for a performance review?

Updated 2026-09-14 · Written by the Puvio team · Deepam, founder · Corrections · Start free

Wins written down while they are still in memory
Log the work when it ships. Review season uses that vault.

In short

Write your brag doc when wins happen. Not the night before review season. Each entry needs what you shipped, measurable impact, and who benefited. Export a review-ready document weeks before calibration so your manager can cite metrics in the room. Puvio logs wins in under a minute and exports a brag doc from the vault you already kept. It does not write a staff-level packet for you in an afternoon. The packet is the trail you logged all year. Lena Vasquez logged twenty-three wins through Q3 2025, about forty-seven seconds each, and her manager walked into December calibration with the PDF. Promoted to Senior PM at Square in January 2026. Story: puvio.app/stories/review-without-blank-doc

Steps

How to write a brag doc for a performance review

  1. 1

    Log within days of the win

    Capture the work while numbers and names are still clear. Waiting until December is how blank docs happen.

  2. 2

    Write situation, action, result

    Situation: the problem or goal. Action: what you did, specific. Result: a number, user, revenue, latency, or stakeholder quote.

  3. 3

    Export before calibration

    Give your manager a document they can cite in the room. Puvio exports from the vault you already kept.

December panic doc versus a vault kept all year

PiecePanic doc in DecemberVault logged when it shippedWhat calibrators can use
When you writeThe night before the packet is dueWithin days of the winDates they can trust
ProofAdjectives. Great collaborator.Number, user, quote, linkA line they can read aloud
Who benefitedMissing or guessedNamed stakeholder or teamSomeone they can ping
ExportA scramble in Google DocsPuvio brag doc from the vaultA PDF your manager already has

What belongs in each brag doc entry?

Situation: what problem or goal. Action: what you did. Specific. Not "collaborated." Result: number, user, revenue, latency, or a stakeholder quote.

Skip vague lines like "great collaborator" with no proof. Calibrators cannot use those. If the line would fit anyone on the team, it is not an entry yet.

When should you write the entries?

Within days of the win. Memory decays. December panic docs are missing names, numbers, and who benefited.

Puvio is built for logging in about a minute while the work is still warm, then exporting when review season shows up. Wins is $5/month. Complete at $29 already includes it. puvio.app/pricing

What should you give your manager, and when?

A short document they can paste or print. One to two pages, not a memoir. Get it to them before they walk into the room. They argue in rooms you are not in. A PDF beats a speech they have to reconstruct.

Kenji Watanabe used a one-pager in a skip-level. The director quoted a migration metric. That is a different conversation than a raise, and it still needs receipts. Story: puvio.app/stories/skip-level-evidence

What Puvio will not do?

It will not invent a staff packet from a blank year. It will not negotiate. It stores what you logged and exports it. If you log nothing, you export nothing useful.

Promotion packets and raise talks reuse the same vault. The conversations are still separate. puvio.app/answers/how-to-document-wins-for-promotion

What does a usable entry look like?

Dead: "Collaborated with design and engineering to improve onboarding." Anyone on the team could write that. Calibrators skip it.

Usable shape: "Cut onboarding time from X to Y for [who] in [quarter]. [Teams]. [Artifact]. Cited in [meeting]." Situation, action, number, who else saw it.

Lena Vasquez averaged about forty-seven seconds per log. She did not write the PDF in those forty-seven seconds. She captured the receipt. Polish happened in November. Export happened before December calibration. Story: puvio.app/stories/review-without-blank-doc

Read the customer story

Upload the résumé you have. Save a posting. Copy the draft. You send it. 75 credits. No LinkedIn login.

Start free

Related questions

When should I write brag doc entries?
Within days of the win, while the numbers and names are still clear. Waiting until December is how blank docs happen. puvio.app/answers/how-to-write-brag-doc-performance-review
What belongs in each brag doc entry?
What you shipped, measurable impact, and who benefited. Skip vague lines like "great collaborator" with no proof.
Does Puvio write my review packet for me?
Puvio stores the wins and exports a review-ready brag doc. You still own the narrative. The quality of the packet is the quality of what you logged. puvio.app/answers/how-to-document-wins-for-promotion
How many entries do I need?
A steady trail beats a weekend rewrite. Lena Vasquez had twenty-three logged wins by calibration. Aim for proof, not a round number.

Related

  • Customer story
  • Customer story
  • Why Puvio
  • answers/how-to-document-wins-for-promotion
  • answers/how-to-ask-your-manager-for-a-raise

75 credits. You send the note.

Upload a résumé. Paste a posting or a LinkedIn URL. Copy the draft into LinkedIn yourself.

Start freeWhy Puvio

Site footer

Product

  • How it works
  • Pricing
  • Where this goes

Proof

  • Stories
  • Answers
  • Compare

Company

  • About
  • Why Puvio
  • Trust center
  • Contact
  • Privacy

Start

  • Start free
  • Log in
Puvio
© Puvio 2026
  • Sign up
  • Privacy
  • Trust
  • Log in
  • AI reference