Writing a Brag Document Before You Leave a Job (1 Page)

A brag document before you leave a job is a one-page record of your wins, metrics, and specific projects from your time in the role. It lives in your personal cloud, not your work drive. Write it in the second week of notice, keep it to a single page, and cover five sections: role summary, top five wins with numbers, praise you got in writing, people who saw the work up close, and links to non-confidential samples.

Most people quit and lose the receipts for the last two, three, five years of work. Not the calendar. Not the projects. The specific outcomes, the metrics, the exact wording of a manager's Slack message the day you shipped the thing.

That stuff evaporates the moment your work Google account closes. You cannot get it back from HR, and you will not remember it in a year when a recruiter asks what you actually did.

A brag doc is the fix. It is the one page you write for yourself in week two of notice, before the calendar fills up with handover meetings and farewell drinks.

What a brag document actually is

Not a resume. Not a portfolio. Not a self-review for a performance cycle. A brag doc is your private record, written in plain language, of the things you did in the role that you would want to remember or point to later.

It has three future uses. First, the next time you update your resume, everything specific is already there and you are not staring at a blank page. Second, when a future recruiter or manager asks "so what did you actually do?", you can answer with numbers and specific projects instead of vague verbs. Third, if someone from your old company ever asks you for a reference or a favor, you remember the shared work with the same clarity they do.

The tension is that the version of this doc that helps you is short. One page. Ten to fifteen bullets, not fifty. Written the way you would talk about the work at a dinner table, not the way you would write a job application.

The one-page template (5 sections)

This is the structure. Keep the whole thing under a page in a normal font size. If it grows past that, cut, do not add.

1. Role summary (2 sentences)

Company name, your title, your dates in the role, and one sentence on what the job actually was, not what the job title claimed it was. "Senior product designer at [company], Feb 2023 to Sept 2026. Owned onboarding and the mobile checkout flow across three product lines."

Two sentences. If it takes more, the role was fuzzy and you should say so in the second sentence.

2. Top five wins with numbers (5 bullets)

Not everything. The five things you would still be proud of in three years. Each bullet is one sentence with a real number in it. "Rebuilt the trial signup flow; free-to-paid conversion rose from 4.1% to 6.8% over Q3." "Led migration of billing to Stripe; reduced failed charges by 34% and saved ~$180k annually in retry fees."

If you cannot put a number on a bullet, put a specific artifact instead. "Wrote the internal RFC that killed the seven-region rebuild proposal (saved ~9 months of eng time)." Specific is what makes this doc load-bearing later. Vague verbs (led, drove, spearheaded, championed) are the sound of a brag doc that will not hold up in a real conversation.

3. Praise you got in writing (3-5 quotes)

Three to five short quotes, pulled from Slack DMs, review docs, manager 1:1 notes, or customer emails. Attribute each one: name, role, month. "'This is the cleanest handoff I have ever gotten from PM.' — J. Chen, staff eng, March 2025."

You are not asking permission to save these. You wrote them down for yourself. Do not screenshot them and do not export whole message threads. A single sentence with attribution is fine and legal in every jurisdiction I have heard of. If you are unsure, err short.

The quotes matter more than people think. In two years you will still remember that you shipped the trial redesign. You will not remember the exact sentence someone said about it, and the exact sentence is what makes future you tell the story with confidence.

4. People who saw the work up close (5-8 names)

Five to eight people, with their role and one line on what you worked on together. This is not your farewell list. This is the people you would name to a future employer as "the person who saw me actually do this." A manager, a peer who partnered on the biggest project, a cross-functional lead, a client, a direct report if you had one.

Include a personal contact channel for each one where you have it (personal email, LinkedIn URL, or a note like "on WhatsApp, has my number"). If you have not asked for personal emails yet, this doc is the reminder that you should before your access ends. The one-hour method for saving your professional contacts covers the how.

5. Links to non-confidential samples (3-5 links)

Three to five links or file paths to work you can point to later without violating any agreement. Public case studies, published talks, patents, blog posts under your byline, open-source commits, dashboards or product pages that are external-facing.

Do not include: client lists, source code, pitch decks marked internal, proprietary metrics, anything from a "confidential" folder. If the artifact is behind a login, it does not belong here; describe it in section 2 instead and move on.

For non-linkable samples where you own the underlying craft (a slide deck you wrote, a template you built), email a copy to your personal address if the employment agreement allows. Most agreements do; a few do not. Read yours.

The pivot: the doc holds your work, but not your relationships

A brag doc is a record of what you did. It is not a record of who you did it with. Those are related, but they are different lists, and section 4 above only holds five to eight people. The full working relationships of your last three years are ten to fifty people, and your brain will drop half of them in the ninety days after you leave.

The honest record of who worked closely with you does not live in your head or in a brag doc. It lives in the last twelve months of your calendar. That is the list of people who saw the work day to day, and it is the list to run alongside this doc before you write the farewell emails.

When to write it

Not the final Friday afternoon. Not the morning of your last day. The right window is Tuesday or Wednesday of week two of notice, in a single ninety-minute block. Early enough that you still have access to Slack, Google Drive, your review docs, and your calendar. Late enough that your notice is out and the first wave of handover conversations has already happened, so you know which projects the successor is actually inheriting.

Split the ninety minutes: first thirty on sections 1 and 5 (the shortest and the most link-hunting), next thirty on section 2 (the wins, which need you to pull numbers from dashboards you may lose access to), last thirty on sections 3 and 4 (the quotes and the people, which need you to scroll through Slack and 1:1 notes). Save the file to a personal cloud folder, not the work drive. Not "brag-doc-final.docx" on your desktop. A real folder in a personal account you will still have in three years.

What to leave out

Five things that make a brag doc worse, not better.

• Confidential numbers. If revenue or headcount or churn figures are not public, use ratios or ranges instead of the raw number. "Reduced churn by ~30%" is fine. Exact ARR is not.
• Blame. The project failed, the reorg went sideways, the launch got pulled. Note what you did and what you learned. Do not name the person you think caused it. Future-you will read it, and possibly a future manager will read it over your shoulder.
• Job-application language. Do not translate a bullet into "spearheaded strategic initiatives to optimize customer experience." Write it the way you would explain it to a friend over coffee. You will thank yourself in a year.
• The whole email thread. The praise section is one sentence with attribution. Not a forwarded thread, not a screenshot. One sentence is enough to trigger the whole memory later.
• Fifty bullets. The single hardest edit is cutting from fifteen good bullets to five great ones. Do it anyway. A one-page doc gets reread; a five-page doc gets ignored.

Three edge cases

You were laid off with same-day access cut. You cannot pull dashboards or scroll old Slack messages. Write the doc from memory in the first weekend after the layoff. It will be shorter and rougher; that is fine. Fill in details over the next month as they surface, and reach out to two or three former coworkers to sanity-check your numbers. A rough brag doc is worth a hundred times a perfect one you never wrote.

You are on gardening leave. You still have laptop access but no active work. Perfect conditions for this doc. Use the first three days of the leave to write it, then close the laptop and let the rest of the leave be what it is.

You were at the job less than a year. Skip section 2's "top five" and write "top two or three" honestly. Do not stretch. A short brag doc for a short tenure is credible; a padded one is not.

What it pairs with

The brag doc is one of three private records worth writing in the final two weeks of notice. The other two are practical, not reflective: a list of the files worth saving from your work laptop (work samples, review docs, personal templates) and a one-page handover document for your successor. The brag doc is for you. The handover doc is for them. The laptop-save list is the boring plumbing. All three fit inside a single week if you block the time.

Write the brag doc. Save it somewhere you will find it again. And then close the laptop and go say goodbye to the people who made the work worth doing in the first place. If you need help with the list of who those people actually were, It Was Great Working With You reads your calendar and hands it back to you.

Further reading: The people you'll forget to say goodbye to when you leave your job.