Brag Doc Template
Project Manager Brag Doc
A brag doc is a private running list of every project you delivered, every risk you absorbed, and every stakeholder you held together. PM work is famously invisible when it goes right — which is exactly why a running record matters. The wins disappear into 'the project shipped.' This template forces the work back into view.
Fill it in below. Saves to your browser automatically. Download when you're done.
Project Manager Brag Doc
What to include
Project Managers are graded on three things: did it ship, did it ship clean, and would they staff you again. Each of those splits into concrete signals — schedule, scope, budget, risk handling, stakeholder satisfaction, retro quality. Fill 3–5 specific bullets per section. Numbers and dates are the proof.
Personalize
Optional · Appears in downloadThe template
Delivery
Projects you owned end-to-end. Schedule, scope, and outcome — name the metric.
- ·Which projects did you deliver on schedule and in scope? What was at risk?
- ·What slipped — and what did you learn or institutionalize from the slip?
- ·Which deliverable was bigger or more complex than the team had handled before?
- ·What did you sequence smartly that the original plan got wrong?
- (no entries)
Risk Management
Risks you saw early, the ones you caught mid-flight, and the recoveries you led.
- ·Which risk did you flag early that the team initially dismissed?
- ·What mid-project recovery did you lead when something broke?
- ·Which dependency did you de-risk before it could block delivery?
- ·What 'we should have done that differently' lesson did you write up?
- (no entries)
Stakeholder Management
Cross-functional alignment, executive updates, escalation paths — the relational work.
- ·Which stakeholders did you align that previously disagreed?
- ·What executive update or steering committee did you run or improve?
- ·Where did you escalate productively — and what changed because of it?
- ·Which difficult conversation did you have that prevented a bigger problem?
- (no entries)
Process & Tooling
Templates, rituals, and infrastructure you built that the team uses on the next project too.
- ·What template, playbook, or framework did you create that others now use?
- ·Which ritual (standup, retro, planning) did you introduce or fix?
- ·What tool did you adopt or replace that changed how the team works?
- ·Which documentation did you produce that became the canonical reference?
- (no entries)
Budget & Resource Stewardship
Where applicable. Budget held, resources reallocated, vendors managed.
- ·Which budget did you steward? How did actuals compare to plan?
- ·What vendor relationship did you own — and what did you renegotiate or change?
- ·Which resource constraint did you solve through reallocation rather than asking for more?
- ·Where did you reduce cost or scope without compromising the outcome?
- (no entries)
Team Coordination & Conflict Resolution
How you kept people moving when timelines, personalities, and priorities collided.
- ·Which conflict did you mediate? What was the resolution?
- ·Who did you coach into a more effective rhythm (status updates, blockers, comms)?
- ·What did you change about how a team worked together that improved velocity?
- ·Which onboarding or knowledge transfer did you own?
- (no entries)
Your entries save automatically in your browser. Nothing is sent anywhere.
Opens your browser's print dialog · Choose "Save as PDF"
Generated via Bloom — a career journal for iPhone. Bloom writes this document for you from your daily entries; the template is the manual version. bloomjournal.cc
Weak vs. strong bullets
The format does the easy part. The bullets carry the weight. A few examples to set the bar.
Weak
Ran the platform migration project.
Strong
Owned the 6-month platform migration: 4 engineering teams, 11 services, $1.2M budget. Delivered 2 weeks ahead of plan and 6% under budget. Zero customer-impacting incidents during cutover (vs. 3 in the previous comparable migration).
Weak
Improved status reporting.
Strong
Replaced the weekly status email (averaging 4 paragraphs, opened by 30% of stakeholders) with a 6-row status table — adopted across 3 programs in Q2, exec readership now tracked at 85%+ and pulled into the COO's monthly review.
Weak
Handled a difficult stakeholder.
Strong
Mediated a 3-month disagreement between engineering and compliance on the audit log scope. Ran 4 working sessions, drafted the decision memo, and got a signed-off scope in week 5 that both sides could ship against. Project unblocked from a 6-week pause.
Weak
Mitigated a delivery risk.
Strong
Flagged the vendor dependency in week 3 of a 12-week project; team initially treated it as low-probability. Lined up a backup vendor and signed an MSA in week 7. Primary vendor missed delivery in week 9 — backup activated, project shipped on time.
Manual template vs. Bloom generated report
Manual brag doc
- Works when you already remember the right examples.
- Requires manual sorting, rewriting, and evidence cleanup.
- Best for a one-time draft or printable structure.
Bloom generated report
- Starts from the work you captured when it happened.
- Organizes entries by goals, skills, impact, and review period.
- Turns daily evidence into shareable summaries and PDF reports.
You don't fill out a Bloom report. Bloom writes it.
The template above is the manual version. Bloom is the generated version. Thirty seconds when something good happens — speak it or type it — and at review time the entire document is in your share sheet. Same shape as the template. Your numbers, your names, your dates. Already written.
Get Bloom for iPhoneFree to start · iPhone · iOS 17+
Build the evidence before you need the template
Templates help with format. A career journal helps with memory. Use these pages together: learn the structure, generate a quick outline, then keep the source material current in Bloom.
Frequently asked questions
Can I use this as a Project Manager brag doc app replacement?▾
You can use the template manually, but it will only stay useful if you update it consistently. Bloom is the app version: capture wins daily, then generate reports when you need them.
What should a brag doc include?▾
A strong brag doc includes dated wins, measurable impact, collaborators, skills, feedback, decisions, evidence links, and review-category alignment.
Is Bloom a brag doc app?▾
Yes. Bloom is a brag doc app and career journal that keeps the source material current, then turns entries into performance reports, recaps, and reusable career stories.