BloomBloom
    HomeToolsTemplatesArticles
    All templates·Engineering

    Promotion Packet Template

    Manager → Director Promotion Packet

    Manager → Director is a scope expansion: you'll lead managers, not just engineers, and own a meaningfully larger surface of the organization. The committee looks for sustained multi-team impact, strategic contribution beyond execution, and a track record of developing managers — not just engineers. This template structures the case around those three.

    Fill it in below. Saves to your browser automatically. Download when you're done.

    Manager → Director Promotion Packet

    What to include

    Director cases require: managing managers (or having clearly developed manager-track ICs), org-wide strategic contribution (not just team-level outcomes), credible relationships with peer functions (Product, Design, Sales), and durable talent development. Each section maps to one of these.

    Personalize

    Optional · Appears in download

    The template

    01

    Self-assessment narrative

    Your case — 5-7 paragraphs covering multi-team scope, strategic contribution, manager development, and org-level outcomes.

    • ·Lead with the org-level outcome that wouldn't have happened, or would have happened worse, without your influence.
    • ·Cite 2-3 strategic initiatives you led or substantially co-owned.
    • ·Reference managers you've developed — promoted, retained, or grew into the role.
    • ·Close with the scope you'd own as Director and the durable change you'd drive in 12 months.
    • (no entries)
    02

    Manager letter prompts

    What your VP should specifically address — Director cases lean heavily on the recommender's credibility.

    • ·Strategic moments where your judgment shaped a decision the VP could have owned alone.
    • ·Multi-team initiatives where you provided the cross-org alignment.
    • ·Manager hires or promotions you championed — and their trajectory.
    • ·Honest read on what you'd grow into as Director vs. what you already operate as.
    • (no entries)
    03

    Peer leader feedback

    Director-track committees weight feedback from peer functions and from your direct reports almost equally. Both are high-signal.

    • ·Peer VPs or Directors in Product, Design, Data — anyone who's been in your strategic conversations.
    • ·Your direct reports (especially senior ones) — their growth and retention.
    • ·Send peers: 'where has Alex's strategic input changed your team's trajectory? Where would you want them to grow?'
    • ·Send reports: 'what's the most important thing Alex has done for your career, and what's a gap you'd want closed?'
    • (no entries)
    04

    Strategic & multi-team evidence

    Artifacts that prove sustained org-level impact.

    • ·Strategy memos or planning docs you authored that leadership adopted.
    • ·Cross-org initiatives where you held the alignment.
    • ·Business outcomes tied to work you led at the multi-team level.
    • ·External evidence — talks, hires from your network, partnerships you formed.
    • (no entries)
    05

    Committee anticipation notes

    Director cases are won on durability and judgment, not heroics. Anticipate the soft spots.

    • ·Is your strategic impact distributed across multiple cycles, or concentrated in one?
    • ·Have you developed any managers (not just promoted ICs)?
    • ·Any difficult organizational moment you handled — restructure, layoff, exec departure?
    • ·Most likely committee concern: scope durability. What's the case that the impact persists in your absence?
    • (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

    I have managed multiple teams successfully over the past few years.

    Strong

    Over the last 24 months I've led 3 teams (24 engineers, 3 EMs reporting to me). Combined output: shipped the v2 platform rewrite (Series-B-scale rebuild, 14 months on-time), retained 92% of senior+ talent during a market downturn, promoted 2 EMs to senior IC manager track. The platform rewrite's $4M of avoided rework was a board-level metric this fiscal year.

    Weak

    I have strong relationships with cross-functional partners.

    Strong

    Co-authored the company's pricing-v3 memo with the VP of Product. Led the engineering side of 2 cross-functional initiatives last year (mobile rebuild + enterprise tier launch). The VP of Sales cites the partnership in her quarterly board memo.

    Weak

    If promoted, I will continue to drive team performance.

    Strong

    As Director, my first 6 months: stand up the platform group as a separate org (2 teams currently distributed across 3 EMs); hire the first dedicated Platform EM (loop drafted, candidates in pipeline); ship the deprecation plan for the v1 systems we've been carrying. Success: org chart cleaned by end of Q1, first Platform EM hired Q2, v1 sunset path committed by end of fiscal.

    Manual template vs. Bloom generated report

    Manual promotion packet

    • 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 promotion evidence

    • 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.

    The promotion case writes itself, if the daily work is captured.

    Promo packets are won on evidence — the daily moves nobody remembers six months later. Bloom captures them as they happen. By the time you sit down to submit, the scope evidence, peer-feedback prompts, and impact bullets are already in your share sheet. Ready to copy in.

    Get Bloom for iPhone

    Free 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.

    Brag document guide

    What to include and how to write stronger bullets.

    Brag doc generator

    Turn role, goals, and wins into an outline.

    Bloom career journal

    Capture the evidence that feeds your promotion packet.

    Frequently asked questions

    Can I use this Manager → Director template for a promotion packet?▾

    Yes. Use it to organize scope, impact, feedback, and next-level evidence. Promotion packets work best when the claims are supported by dated examples.

    Is Bloom a brag doc app?▾

    Yes. Bloom is a career journal and brag doc app that captures daily wins and turns them into promotion evidence, reports, and review summaries.

    What is the difference between a brag doc and a promotion packet?▾

    A brag doc is the running evidence bank. A promotion packet is the formal case. The brag doc feeds the packet.

    More engineering templates

    Mid → Senior Engineer

    Brag Doc

    Senior → Staff Engineer

    Brag Doc

    IC → Engineering Manager

    Brag Doc

    BloomBloom
    ArticlesToolsTemplatesComparePrivacy PolicyTerms of Service

    © 2026 Bloom · Last updated 2026-05-19