📋 Contents
- What a brag document is (and isn’t)
- Why you need one even if your manager is great
- Brag document vs. brag sheet vs. promo packet
- What to log: the six categories
- What to skip
- A 5-minute weekly template
- Daily lines make weekly entries easy
- Turning the document into review material
- Using it for a promotion case
- Sharing it with your manager
PART 1
What a brag document is (and isn’t)
A brag document is a private file where you record your work as it happens: projects shipped, problems solved, people helped, things you learned, and feedback you received. You add to it every week, not once a year.
The idea spread widely in tech after software engineer Julia Evans wrote about it, but it works in any job where your manager cannot see everything you do, which, in a remote or hybrid team, is most jobs.
It is not a polished resume, a list of every task, or something you send to anyone in raw form. Think of it as the raw material that later becomes your self-evaluation, your promotion case, your resume bullets and your talking points in a raise conversation.
| Brag document | Resume | To-do list |
|---|---|---|
| Private, messy, complete | Public, polished, selective | Private, forward-looking |
| Records what happened and why it mattered | Shows your best few outcomes | Tracks what still needs doing |
| Updated weekly | Updated when job hunting | Updated daily |
PART 2
Why you need one even if your manager is great
Memory fades fast. By the end of a year, most people can recall their last two months in detail and the rest only vaguely. Your manager has the same problem, multiplied by every person on the team. Work that happened in February is often missing from a December review simply because nobody wrote it down.
A brag document fixes that for you. It also helps in less obvious ways:
- On a bad week, rereading it reminds you that you do make progress.
- It shows patterns: what kind of work you are best at, and what kind keeps draining you.
- It makes one-on-ones more useful, because you arrive with specifics.
- If your manager changes, you can hand the new one a clear summary of your recent work.
- In a remote or hybrid team, it captures the work nobody saw happen: the Slack thread where you unblocked another team, the doc you rewrote at 4 p.m. on a Friday.
PART 3
Brag document vs. brag sheet vs. promo packet
These terms get mixed up in search results. They are related but used at different moments.
| Term | What it is | When you use it |
|---|---|---|
| Brag document | Your private, running log of wins, fixes, help and feedback | All year, updated weekly |
| Brag sheet | A one-page summary pulled from it, shared with someone | Before reviews, or when asking for a reference or recommendation |
| Promo packet | A structured case that you meet the next level’s criteria | When your manager puts you up for promotion; often reviewed in calibration |
| Self-review | Your answers on the company’s review form | Annual or mid-year review cycle |
The brag document feeds all the others. If you have one, a brag sheet takes twenty minutes and a promo packet starts from evidence instead of a blank page.
PART 4
What to log: the six categories
Log anything you might want to mention later. When in doubt, write it down; deleting is easy, remembering is not.
| Category | What to capture | Example entry |
|---|---|---|
| Results | What you delivered and what changed | Launched the new signup flow; drop-off on step 2 fell noticeably in the first week |
| Problems solved | Issues you fixed or prevented | Caught a duplicate-billing bug in review before release |
| Process improvements | Ways you made work easier for others | Wrote a release checklist; the team now uses it every sprint |
| Helping others | Mentoring, unblocking, covering | Walked a new hire through the data model; they finished their first report solo |
| Learning | Skills gained and where you used them | Learned basic SQL; pulled my own campaign numbers this week |
| Feedback | Praise, thanks, recognition (paste the quote) | "This doc saved me a day" — from the support lead |
Example entries are illustrative.
💡 Save the exact words
When someone thanks you in chat or email, copy the message into your document with the date and name. A direct quote is far more persuasive in a review than "people liked my work."
PART 5
What to skip
A brag document becomes useless if it is a dump of every task. Skip routine work that nobody would notice if it stopped, unless you did it in a notably better way. "Answered emails" is noise. "Cleared a 200-message shared inbox and set up filters so it stays under 20" is a result.
- Routine attendance (meetings, standups) unless you led or changed them.
- Tasks with no visible outcome yet; log them when the outcome appears.
- Confidential details you should not keep in a personal file. Describe the work in general terms instead.
⚠️ Keep it somewhere you control
If you leave the company, you may lose access to work drives. Keep the document in a place you will still be able to reach, and keep it free of confidential data, customer names and anything your employer would not want stored outside its systems.
PART 6
A 5-minute weekly template
Block five minutes at the same time every week, such as Friday afternoon. Copy this template and fill in only what applies.
✍️ Weekly brag entry
Week of: [date]
Shipped / finished: [what you delivered] → [what changed]
Solved or prevented: [problem] → [how you found it, what you did]
Made easier for others: [process, document, tool]
Helped: [who] with [what]
Learned: [skill] — used it for [task]
Feedback received: "[quote]" — [name, date]
Still open / next: [one line]
Five minutes a week is about four hours a year. Compare that with the evening (or weekend) most people lose trying to reconstruct their year from old emails.
PART 7
Daily lines make weekly entries easy
If even a weekly entry feels like a stretch, go smaller: write one line at the end of each day. "Fixed the export bug the sales team reported; they can run month-end reports again." By Friday you have five lines, and your weekly entry is mostly copy and paste.
Any notes app works for this. Apps built for it, such as PLAN2FOLIO, also sort each line into the outcomes of your role and draft the weekly summary for you, which removes the step most people skip.
✍️ A week of daily lines
Mon — Set up the test plan for the billing change with QA.
Tue — Found the root cause of slow dashboard loads (unindexed query); fix in review.
Wed — Dashboard fix live; load time down from seconds to under one.
Thu — Walked two support agents through the new refund flow.
Fri — Wrote the handoff doc for the billing change.
PART 8
Turning the document into review material
When review season arrives, do not paste the whole document. Work through it in three passes.
Group by goal or outcome
Sort entries under the goals you were given, plus one group for "beyond my goals." Entries that fit nowhere are probably routine; leave them out.
Pick the strongest two or three per group
Choose entries with the clearest result or the widest effect. Combine related entries into one story.
Rewrite as action + method + result
Turn notes into full sentences. "Dashboard fix" becomes "Diagnosed slow dashboard loads, added the missing index, and brought load times under one second for the whole sales team."
For ready-made phrasing by competency, see self-evaluation examples.
PART 9
Using it for a promotion case
Promotions at many companies are decided against a written leveling guide or career ladder: a page describing what someone at each level does. If your company has one, add a column to your brag document and tag entries with the criterion they show, such as "owns projects end to end," "influences beyond the team" or "mentors others."
✍️ Tagged entries (illustrative)
[Scope] Led the pricing page rebuild across design, engineering and sales; first project I planned from kickoff.
[Influence] My proposal for a shared intake form was adopted by two other teams.
[Mentoring] Onboarded two new hires; both now run releases without review.
When your manager asks for promo packet material, you can sort by tag and show that you have been working at the next level for months, which is usually what promotion committees look for, rather than arguing that you could.
PART 10
Sharing it with your manager
Some managers welcome a short version of your brag document before reviews; it makes their job easier. Send a one-page summary, not the raw file, two or three weeks before reviews are written. Frame it as help: "Here is a summary of my work this period, in case it is useful while you write reviews."
☐ One page or less, grouped by goal.
☐ Each line has a result or a clear before → after.
☐ Includes one or two direct quotes from colleagues or customers.
☐ Mentions anything your manager may not have seen (cross-team work, help to others).
Frequently asked questions
Q. What is a brag document?
A private, running record of your accomplishments at work: what you shipped, problems you solved, people you helped, what you learned and feedback you received, each with what changed. You use it to write self-reviews, promotion cases and resumes.
Q. What should I put in a brag document?
Results, problems solved or prevented, process improvements, help you gave others, skills learned, and direct quotes of praise. Add the date and, when possible, the goal each entry supports.
Q. Isn’t a brag document just self-promotion?
It is a record, not a broadcast. You decide what to share and when. Most of it stays private and simply makes sure accurate information is available when decisions about your work are made.
Q. What format should I use?
Whatever you will actually open every week: a Google Doc, a Notion page, a notes app, a spreadsheet, or a work-log app. A simple dated list is enough. Keep it somewhere you could still reach if you changed jobs, and keep confidential details out of it.
Q. How far back should I go if I am starting now?
Spend one session going back through the last three months of sent email, calendar and chat to seed the document. After that, just keep it current.
Q. What if I have a slow week with nothing to log?
Write one line anyway, even "mostly maintenance; prepared for next week’s launch." Gaps are fine. Keeping the habit is what matters.
Q. Should I include failures?
Yes, privately. Note what went wrong and what you changed. These entries make strong answers in interviews and honest material for the "areas to improve" part of a review.
Q. Can I use it for job applications?
Yes. It is the best source for resume bullets and interview stories. Remove confidential details and rewrite entries for an outside reader.
This article is general guidance. Review formats, rating scales and expectations vary by company — check your own company’s guidelines alongside it.
PLAN2FOLIO
Evidence for reviews, raises and job moves — starting with one line today
Write what you did today in one line. PLAN2FOLIO sorts it into the outcomes of your role, drafts your weekly report on Fridays and gathers evidence by outcome at review time. Free to start.
Start free →