You stayed up until 3 AM restoring a database that nobody backed up properly. You migrated 400 users to a new identity provider without a single ticket. You wrote the runbook that saved your team 12 hours a week.

And when your performance review rolls around in six months, you’ll remember maybe one of those things. Vaguely.

This is the quiet career killer that nobody warns you about. Not a lack of skills, not bad interviews, not even office politics. It’s forgetting your own work. The projects blur together. The wins get buried under the next fire drill. And when it’s time to make your case for a raise, a promotion, or even a new job, you’re sitting there staring at a blank self-assessment thinking, “What did I even do this year?”

The fix is embarrassingly simple: a brag document. It takes five minutes a week and it will change how you think about your career. Not in the motivational-poster sense. In the “I can now prove exactly what I’m worth” sense.

What a Brag Document Actually Is

A brag document is a running log of your professional wins. That’s it. No special format, no fancy tool, no rigid template. Just a place where you write down what you did, when you did it, and why it mattered.

The term was popularized by Julia Evans, a software engineer who wrote about the concept in a widely shared blog post. The idea is dead simple: if you don’t write it down, you’ll forget it. And if you forget it, it didn’t happen (at least as far as your career is concerned).

A brag document is not a journal. You’re not writing paragraphs about your feelings. It’s closer to a changelog for your career. Short entries. Concrete details. Enough context that future-you can reconstruct what happened.

Here’s what sets it apart from a resume or a performance review self-assessment:

  • Resume: Polished, outward-facing, stripped to bullet points. You write it once a year (maybe).
  • Self-assessment: Written under deadline pressure when you’re trying to remember six months of work in one sitting.
  • Brag document: Raw, ongoing, for your eyes only. Updated weekly. The source material that makes resumes and self-assessments actually good.

Think of it as the difference between trying to remember everything you ate last month versus checking a food log. One approach is guesswork. The other is data.

Why IT Pros Specifically Need This

Every profession benefits from tracking accomplishments. But IT has a few dynamics that make forgetting your wins almost inevitable.

Your best work is invisible

When everything is running smoothly, nobody notices. The server didn’t go down. The backup worked. The patch deployed without breaking anything. That’s not an absence of work. That’s the result of work. But it doesn’t generate tickets, praise, or paper trails.

If you’ve ever felt like your best IT work goes unnoticed, this is exactly why. A brag document creates the paper trail that your job won’t create for you.

Fire drills erase context

IT is reactive by nature. You fix the DNS issue, then immediately deal with a locked account, then troubleshoot a VPN problem, then hop on a call about the new ticketing system rollout. By Friday, Monday’s wins are ancient history.

The pace of context switching in IT roles means your short-term memory is constantly being overwritten. If you don’t capture a win within a week, the specifics are gone.

Metrics aren’t always obvious

A salesperson can point to revenue numbers. A developer can point to shipped features. What does a sysadmin point to? Uptime? Ticket counts? Those metrics exist, but they rarely tell the full story.

The brag document lets you capture the narrative behind the numbers. Not just “resolved 47 tickets” but “reduced average ticket resolution time by 30% by creating a self-service password reset portal that eliminated the most common help desk request.”

Reviews happen infrequently

Most companies do formal performance reviews once or twice a year. That’s asking you to summarize 6-12 months of work from memory. Even the most organized person loses details over that span. The people who win their performance reviews aren’t the ones with the best memory. They’re the ones with the best notes.

How to Start a Brag Document (Today)

You don’t need a system. You need a habit. Here’s how to start with minimal friction.

Pick a tool you already use

The best tool is whatever you’ll actually open on a regular basis. Some options:

  • A plain text file in your home directory or a Git repo you already maintain
  • A private note in whatever notes app lives on your phone (Apple Notes, Google Keep, whatever)
  • A Notion or Confluence page if your team already uses those
  • A Google Doc shared with nobody
  • A markdown file if you’re the type who lives in a terminal

Do not spend two hours researching brag document apps. Open a text file right now and call it brag.md. Done.

Write your first entry

Think about the last two weeks. What did you do that you were even mildly proud of? It doesn’t have to be dramatic. Here are some examples:

Good brag entries:

2026-04-14: Migrated the team from Slack Free to Slack Enterprise. Coordinated with 4 department heads, preserved channel history, set up SSO integration with Okta. Zero user-reported issues on launch day.

2026-04-10: Found and fixed a misconfigured firewall rule that was blocking intermittent connections to the print server. Had been an open ticket for 3 weeks before I traced it back to a change made during the network refresh.

2026-04-07: Built a PowerShell script that automates new user onboarding. Creates AD account, assigns license, adds to distribution groups, and sends welcome email. Saves ~45 minutes per new hire. Shared it with the team and it’s now part of our standard process.

Notice the pattern: date, what you did, context, impact. That’s the formula. You can always polish it later. Right now, just capture it.

Set a weekly reminder

Every Friday afternoon (or whenever your brain is still intact), spend five minutes adding entries from that week. That’s the whole habit. Five minutes. If nothing noteworthy happened, write “maintenance week” and move on. But you’ll be surprised how much you actually did once you start looking.

The key is consistency over quality. A rough entry every week beats a perfect entry once a quarter.

What to Track (And What to Skip)

Not everything belongs in a brag document. Here’s a filter to keep it useful.

Always track

Projects you completed or contributed to significantly. Not just “worked on the migration” but what your specific role was, what decisions you made, and what the outcome was.

Problems you solved. Especially the hard ones. The outage you diagnosed when everyone else was stuck. The troubleshooting process that found a root cause nobody expected. The workaround that kept production running while the real fix was developed.

Processes you improved or created. Automation scripts, documentation you wrote that people actually use, workflows you streamlined. Quantify the time saved if you can.

Skills you developed. Finished a certification? Completed a training? Got hands-on with a new technology through Shell Samurai or a home lab? Write it down with specifics about what you can now do that you couldn’t before.

Mentoring and collaboration. Helped a junior team member solve a problem? Led a blameless postmortem? Onboarded a new hire? These demonstrate leadership qualities that matter for promotions.

Scope increases. Got pulled into a project outside your normal responsibilities? Started handling a new system or a bigger piece of infrastructure? That’s evidence of growing trust and capability.

Positive feedback. Someone sent you a thank-you email? A manager called out your work in a meeting? Screenshot it, copy-paste it, save it. You’ll forget. They definitely will.

Skip

  • Routine tasks that are just your job description (unless you improved how they’re done)
  • Vague entries with no specifics (“did good work this week”)
  • Other people’s accomplishments (keep the focus on your contributions)
  • Stuff you started but didn’t finish (move it to a “work in progress” section if you want)

Turning Your Brag Document Into Career Fuel

A brag document sitting in a file is useful. A brag document you actively use is a career weapon. Here’s where it pays off.

Performance reviews

This is the obvious one. When self-assessment time comes around, you don’t have to remember anything. You just open the document and pick your strongest entries. You’ll have dates, details, and impact metrics ready to go.

Most of your coworkers will write vague bullets like “supported infrastructure projects.” You’ll write, “Led migration of 200+ endpoints from Windows 10 to Windows 11, completing two weeks ahead of schedule with zero critical issues.” That specificity is what gets you the higher rating.

Salary negotiations

When you’re negotiating a raise, you need evidence. “I deserve more money” is not an argument. “In the past year, I automated three manual processes saving 15 hours per week, led the disaster recovery test that identified a critical backup gap, and mentored two junior admins who are now handling tier-2 escalations independently” is an argument.

Your brag document is the source material for that argument. You’re not guessing or inflating. You’re stating facts.

Job searching

When you’re updating your resume, your brag document gives you specific accomplishments to pull from instead of generic job descriptions. “Managed Windows servers” becomes “Managed 150+ Windows Server 2022 instances across three data centers, maintaining 99.97% uptime and reducing patch compliance time from 14 days to 3.”

This is also where your document helps you beat ATS systems. You have concrete numbers and specific technologies to weave into your resume, which gives applicant tracking systems more keywords to match against.

Promotion cases

If you’re trying to move from help desk to sysadmin, or from sysadmin to DevOps, your brag document shows a pattern of growth. It demonstrates that you’ve been operating at the next level before you officially have the title.

A promotion case built on a year of documented accomplishments is almost impossible to argue against. A promotion case built on “I’ve been here three years and I think I’m ready” is easy to delay.

One-on-ones with your manager

Bring your brag document (or a curated version of it) to your regular one-on-ones. Not to brag, but to keep your manager informed. Managers have too many direct reports and too many meetings to remember what you did three weeks ago. Reminding them regularly is not self-promotion. It’s communication.

This is especially important if you’re working remotely, where your work is even less visible than it would be in an office.

The Format That Works Best for IT

After looking at dozens of approaches, here’s a format that works well for IT professionals specifically. Adapt it to your preferences.

Weekly entries

## Week of 2026-04-14

### Wins
- Completed Azure AD to Entra ID migration for 350 users (zero downtime)
- Wrote runbook for emergency failover procedure, tested successfully
- Identified memory leak in monitoring agent causing false alerts

### Impact
- Migration eliminated 3 separate identity-related tickets per week
- Runbook reduced expected failover time from 45 min to 12 min

### Skills/Learning
- Completed AZ-104 practice exams (scoring 85%+ consistently)
- Built Terraform module for standardized VM deployments

### Collaboration
- Paired with junior admin on first firewall rule change
- Led Thursday incident review for the email outage

Quarterly rollup

Every three months, review your weekly entries and write a summary. This is the version you’ll pull from for reviews and resumes.

## Q1 2026 Summary

### Biggest wins
1. Led cloud migration project (Phase 1): moved 12 workloads to Azure, 
   reducing monthly infrastructure costs by $4,200
2. Built automated onboarding pipeline saving 3 hours per new hire
3. Designed and implemented network segmentation for PCI compliance

### Growth areas
- Earned AZ-104 certification (April exam scheduled)
- Started leading weekly team standups
- Took on after-hours escalation rotation for first time

### By the numbers
- Tickets resolved: 342 (avg resolution time: 2.1 hours, down from 3.4)
- Projects completed: 4 major, 7 minor
- Documentation pages created/updated: 23
- Scripts written or improved: 11

The “receipts” section

Keep a section for saved evidence. Screenshots of thank-you messages. Emails from stakeholders acknowledging your work. Slack messages where someone said, “That script you wrote saved my afternoon.” Copy-paste them with dates.

This isn’t vanity. When someone says “you didn’t do X” or your review feels unfairly low, you have documentation. And when you’re having a rough week and wondering if you’re any good at this job, reading through past wins is a surprisingly effective reminder.

Common Mistakes (And How to Avoid Them)

Waiting too long to start

The best time to start a brag document was your first day on the job. The second best time is right now. Don’t try to reconstruct the last six months. Start fresh from this week and build forward.

If you really want to capture past wins, spend 30 minutes brainstorming your biggest accomplishments from the past year. Check your sent emails, closed tickets, and Git history for reminders. But don’t let the desire for completeness stop you from starting.

Making entries too vague

“Helped with server migration” is useless six months from now. How many servers? What was your role? What went wrong and how did you fix it? What was the business impact?

Force yourself to include at least one number or specific detail in every entry. Not because anyone is grading you, but because specifics are what make accomplishments believable and memorable.

Only tracking big projects

The small wins add up. Automating a manual process. Writing a script that saves 20 minutes a day. Fixing a recurring issue that everyone else had been working around. These daily improvements compound, and they’re the first things you’ll forget.

The sysadmin who documents every small optimization over a year has a much more compelling story than the one who only remembers the one big migration.

Treating it as a task list

A brag document is not a to-do list. “Set up new monitoring” is a task. “Deployed Prometheus + Grafana monitoring stack for 40 production servers, catching 3 disk space issues in the first week that would have caused outages” is a brag entry. The difference is outcome and impact.

Not using it

The biggest mistake is writing a brag document and never opening it. Use it. Reference it in your one-on-ones. Pull from it for your self-assessment. Update your LinkedIn profile with entries from it. Send a curated version to your manager before your review. The document only has value if it leaves the file.

When to Start Sharing (And How)

Some people keep their brag document completely private. That’s fine, but you’re leaving value on the table.

With your manager

Share a monthly summary or bring highlights to your one-on-ones. Frame it as keeping them informed, not self-promotion: “Just wanted to make sure you had visibility into what I’ve been working on.”

Managers who know what you’ve been doing are managers who can advocate for your promotion. Managers who don’t know are managers who say “I’ll look into it” when you bring up advancement.

With your team

In team retrospectives or standups, referencing your documented work normalizes the practice. “I tracked this in my brag doc” might inspire others to start their own. Teams where everyone tracks their wins tend to have better documentation, better knowledge sharing, and less of the “who did what” confusion.

With yourself

Seriously. On days when you feel like you’re not progressing, open the document and read the last three months. If you’re dealing with imposter syndrome, your brag document is the antidote. It’s hard to feel like a fraud when you’re looking at a page of things you actually accomplished.

If you’re recovering from burnout, this can also help you see that the work you’re doing matters, even when it doesn’t feel like it in the moment.

FAQ

How long should a brag document entry be?

Two to four sentences is the sweet spot. Enough to capture what happened, your role, and the impact. You can always expand entries later when you need them for a resume or review. The goal during the week is speed, not polish.

Should I include failures or mistakes?

Yes, if you learned something significant and especially if you turned the situation around. “Led incident response for a 4-hour outage caused by a misconfigured load balancer. Identified root cause, coordinated the fix, and wrote the postmortem that led to new deployment safeguards.” Owning and resolving failures shows maturity.

What if my job is mostly reactive support work?

Even support work has wins. Track patterns you identified, recurring issues you permanently fixed, documentation you created that reduced ticket volume, process improvements, and times you went beyond the ticket. “Resolved user’s VPN issue and noticed 12 other users had the same misconfiguration. Pushed a group policy fix that eliminated the issue org-wide” is a great brag entry that started as a routine ticket.

Can I use a brag document if I’m just starting my IT career?

Absolutely. In fact, it’s even more important early on because you’re building skills quickly and it’s easy to undervalue what you’ve learned. Track certifications you earn, labs you build, skills you develop through platforms like Shell Samurai or TryHackMe, and problems you solve for the first time. When it’s time to write your first IT resume, this document will be a goldmine.

How is this different from keeping a work journal?

A work journal captures everything: tasks, thoughts, frustrations, meeting notes. A brag document is filtered for impact. Only things that demonstrate value, growth, or contribution. Think of it as the highlight reel, not the raw footage. The journal is for you to process your day. The brag document is for you to build your career.

Start This Week

You now know what a brag document is, why it matters, and how to make one that actually works. The only question is whether you’ll open that text file and write your first entry.

Here’s the play: open your notes app or your terminal right now. Create a file. Write down one thing you did this week that you’re even slightly proud of. Set a recurring Friday reminder to add more. That’s the whole system.

Six months from now, when your review comes up or a recruiter asks what you’ve been working on, you’ll have a document full of answers. Your coworkers will be staring at a blank page, trying to remember what they did in October.

You’ll have receipts.