Brag Document Template: A Simple Structure for Any Role

If you've looked into brag documents at all, you've probably noticed there's no shortage of templates. Notion has dozens. There are Google Docs versions, GitHub repos, blog posts with suggested structures. The concept has been around since Julia Evans wrote about it in 2019, and the number of variations has grown every year since.

That's actually part of the problem. When every template looks a little different, it's hard to know which sections matter, which are optional, and what you should actually write down. Most people stall out on that question before they get past the first entry. For what a brag document is and where the practice comes from, see our full guide. This page is about the structure itself.

We reviewed over 25 brag document templates, from Evans' original to Notion marketplace templates to structured frameworks from career coaches and engineering leaders. Most trace back to the same foundation, but they make different trade-offs between simplicity and detail, and many were built with a specific role in mind.

This is the one we'd recommend to any working professional. Five sections that apply across every knowledge-work role, designed to work from day one without requiring a specific tool or format. The simplest version is the one you'll actually keep up with, and this template is built around that principle. Copy it into your tool of choice and start filling it in.

What actually goes in a brag document

Goals and focus areas

This section frames everything that follows. When you list your goals at the top, every accomplishment below gets read in the context of what you were trying to achieve. That makes the whole document more persuasive, whether you're re-reading it yourself or sharing it with your manager.

These don't need to come from a formal goal-setting process. “Get better at stakeholder communication” or “Ship the redesigned onboarding flow” count.

Example entries:

• Lead the migration to the new CRM and get adoption above 80% by end of quarter
• Improve the team's turnaround time on customer escalations
• Develop enough SQL proficiency to run my own reports without waiting on the data team

Projects and accomplishments

This is the section most people think of when they hear “brag document” — and it's the one that does the most work during performance reviews, promotion conversations, and interviews.

Focus on outcomes, not tasks. Not “worked on the product launch.” What you specifically contributed, what changed because of your work, and any numbers you can attach.

Example entries:

• Redesigned the onboarding email sequence, reducing time-to-first-value from 14 days to 6 days
• Led the vendor contract renegotiation that saved the team $180K annually
• Built the internal dashboard that the sales team now uses for every quarterly forecast
• Managed the cross-functional launch for the new pricing tier, coordinating across product, engineering, marketing, and legal

Collaboration and leadership

The work that shapes how a team functions rarely shows up in a sprint report. Mentoring a junior teammate, unblocking another team, mediating a disagreement about technical direction, facilitating a cross-functional decision. This is high-impact work that disappears without a record.

Example entries:

• Onboarded two new team members and built a 30-day ramp-up guide that the team now uses for all new hires
• Identified a miscommunication between product and engineering on the feature spec, then facilitated a working session that resolved it before it became a sprint blocker
• Mentored a teammate through their first client presentation. They've now led three on their own

Skills and growth

This section is easy to neglect because it doesn't feel like an “accomplishment.” But it's what makes a brag document compound over time. A year from now, when you're making a promotion case or updating your resume, the skills you built will matter as much as the projects you shipped.

Example entries:

• Learned Figma well enough to create my own wireframes for stakeholder reviews, which reduced back-and-forth with the design team by roughly two rounds per project
• Completed a data analytics course and applied it to build the team's first self-service reporting setup
• Took on the team's first customer-facing presentation in a language other than English. Now comfortable leading bilingual client calls

Feedback and recognition

Positive feedback fades fast. A Slack message saying “your presentation was the best I've seen this quarter” gets buried in a week. A performance review noting that you “consistently raise the quality bar” is forgotten by the next cycle.

Capture it when it happens. Copy the exact words, note who said it and when. This section gives you evidence in someone else's voice — which is often more convincing than your own.

Example entries:

• Manager in Q2 review: “You've become the go-to person for cross-team coordination. Multiple team leads have told me they come to you first.”
• VP of Sales in Slack after the QBR: “The dashboard you built has changed how we prep for quarterly reviews. The team references it in every forecast meeting.”
• Peer review: “They have a talent for translating between technical and non-technical stakeholders. Our last three planning cycles went smoother because of it.”

How to write a single entry

A good brag document entry captures three things: what you did, why it mattered, and what changed as a result. That's it.

You don't need paragraphs. You don't need perfect grammar. You need enough context that when you read this entry six months from now, you remember the situation and can articulate the impact.

Weak entry: “Worked on the analytics dashboard.”

Strong entry: “Built the analytics dashboard that the ops team now uses for weekly capacity planning — replaced a manual spreadsheet process that took 3 hours per week.”

The weak version tells you what you touched. The strong version tells you what you delivered and what it meant. The difference takes about 30 seconds more to write, and it's the difference between a useful entry and one you'll stare at blankly during your next review.

For a deeper guide on what counts as an accomplishment and how to capture the right details, we've written a full framework.

One important note: use “I” and “my,” not “we.” If your team shipped something, write down your specific contribution. Did you design it? Scope it? Coordinate across teams? Fix the critical bug at the end? Your brag document is the one place where your individual contribution gets documented without the group attribution that shows up everywhere else.

Start simple, level up later

There's a tension in most brag document advice that nobody addresses directly. On one side, people recommend simple bullet lists (low friction, quick to maintain). On the other, people recommend structured templates with fields for context, impact, metrics, and collaborators (richer detail, more useful at review time).

Both camps are right. They're just describing different stages.

Think of it like learning a language. On day one, you learn basic vocabulary and simple phrases. You don't start by writing essays or holding debates. The practice matters more than the sophistication. You build fluency through consistency, and the complexity comes naturally once the foundation is solid.

Running works the same way. Nobody trains for a marathon on their first week. You start by just getting out the door regularly. Once the routine is second nature, you add distance, pace work, structured training. Starting at the advanced level doesn't make you better — it makes you quit.

A brag document follows the same pattern. If you've never maintained one before, start with one section — Projects and Accomplishments — and write simple bullets. No metrics required. No STAR format. Just “here's what I did and why it mattered,” in your own words.

Once the habit sticks and you're consistently adding entries, start layering in detail. Add metrics where you have them. Start filling in the Collaboration section. Capture feedback when it arrives. The brag document template above is the full version, but you don't have to use all five sections from day one.

The sophisticated version of a brag document pays off when a forcing function arrives: a performance review, a promotion case, a job interview. That's when rich detail and specific metrics matter most. But you won't have that detail if you abandoned the practice in week three because it felt like too much work. A bulleted list you actually maintain is worth more than a structured template you gave up on.

Pick a cadence that works for you

A brag document template is only useful if you actually use it. We recommend updating weekly. Find the moment that fits naturally into your routine — end of day Friday, Monday morning over coffee, the ten minutes before your weekly standup. The specific time doesn't matter. What matters is that it's a recurring moment you can build around.

Weekly works well because the details are still fresh. You can still remember who was in the meeting, what the pushback was, and why the decision mattered. Wait a month, and most of that context evaporates. You'll end up with “launched the new feature” instead of “drove the technical decision to use progressive rollout, which caught two critical edge cases before full launch.”

That said, if monthly is what you can commit to — do it. A monthly update with less detail beats no updates at all. You're trading some richness and freshness of memory, and that's a real cost. But it's a cost you can live with, and you can always move to weekly once the habit feels easier.

Some people update daily. Julia Evans, who popularized the brag document concept in 2019, has said she personally prefers a marathon session every six months, though she notes most people do better with biweekly or weekly updates.

The common thread across every approach: set a reminder. Don't rely on motivation or memory to prompt you. A recurring calendar event, a phone notification, whatever works. Treat it like any other recurring task, not something you get to when you feel like it.

This template works in any tool

This brag document template is designed to live wherever you already work. Paste it into a Google Doc, a Notion page, a plain text file, an Apple Note, a Word document, a spreadsheet — whatever you'll actually open when it's time to add an entry.

People use all kinds of setups. Some keep a private Slack channel with themselves. Some use a running note on their phone. Some maintain a dedicated Notion database. The structure matters more than the tool.

If you want this to happen with less effort (capturing entries by voice, automatic organization, skills surfaced for you), that's what Volio does. But the template above works regardless of what tool you put it in.

What comes next

Two paths forward, depending on where you are:

Start using the brag document template today. Copy it, paste it into your tool of choice, and fill in this week's entries. Don't overthink it. Three bullet points in the Projects section is a better start than spending an hour perfecting your setup.

Level up as you go. As you get comfortable with the habit, you'll notice areas where you want more detail or more tailored sections for your specific role. An engineer might add a section for technical decisions and architecture work. A marketer might track campaign performance data. A customer success manager might log client health signals and renewal conversations. We'll be covering role-specific additions in future guides.

A brag document is a snapshot — a record of what you've done over a period of time. A career journal is the ongoing practice that makes every snapshot easy. If you want a system that builds your brag document as a byproduct of weekly reflection, that's the next step.

Related reading

• What Is a Brag Sheet? The Working Professional's Guide
• How to Track Accomplishments at Work: A Practical Framework
• What Is a Career Journal?