Promotion Case Documentation: Build the File Before the Meeting

You are doing director work at manager pay. Your manager agrees "in spirit." Calibration kills the packet because impact lives in Slack threads, not a file. Promotions are capital allocations — they need documentation that survives people who were not in your 1:1s. Committees compare packets side by side with limited time. Yours must read as proof, not persuasion.

This guide covers level criteria mapping, initiative pages, pre-wiring calibration, customer and cross-functional proof, sponsorship, and what to do after denial — the full promotion file before the room decides.

#Start from level criteria

Pull official level definitions: scope, problem complexity, interaction breadth, business impact. Map your last eighteen months to each bullet with evidence — not adjectives.

If the rubric says "influences cross-functional strategy," your packet needs named initiatives, stakeholders, and outcomes — not "strong collaborator." If it says "owns ambiguous problems," show one problem that was undefined when you arrived and measurable when you left.

Compare at level+1: show work already performed at the next level — not work you promise if promoted. Committees fund evidence, not potential alone. Timeline transparency helps: ask when committee meets and what happens if deferred. Ambiguity breeds rumor.

Tip. Share the draft packet with your manager early. Ask: What would make this an easy yes in committee? Incorporate feedback before the room, not during it.

#One page per major initiative

For each initiative, one page:

• Situation — What was broken or missing
• Mandate — What you were asked to own (or stepped up to own)
• Actions — Decisions you made, coalitions you built
• Measurable outcome — What changed, for whom
• Persistence — Does the result still hold?

Link artifacts where allowed — dashboards, launch notes, postmortems, anonymized customer proof. Committee members trust files they can open — not only your summary. Artifacts appendix: attach or link anonymized dashboards, launch briefs, or customer emails where policy allows.

External validation — NPS movement, renewal saves, partner quotes — carries weight internal adjectives do not. Customer and partner proof belongs in the appendix when policy allows. Even anonymized metrics beat "stakeholders were happy."

"Internal adjectives do not travel — artifacts and cross-functional endorsements do."

#Pre-wire calibration and sponsorship

Cross-functional endorsements from peer leaders in other functions beat solo manager advocacy. You need a sponsor willing to spend political capital in the room. Mentors advise; sponsors advocate. Know which you have before you walk into committee.

Align language with capital allocation reviews. If your company runs input-driven reviews, quarterly inputs should feed the promotion file continuously — not a last-minute scramble before calibration locks. Promotion case and review case should tell the same delta story.

If you are building the process on the HR/ops side: require promotion packets before calibration agendas lock. No packet, no slot. That rule protects committees from narrative-only debates and protects high performers from "we ran out of time."

#Rejection post-mortem and next cycle

If denied, request written gaps to close. Silent denial wastes another year. If gaps shift next cycle, document the pattern for skip-level visibility. Rejection post-mortem is data for the next packet — not venting. After denial, written gaps become next quarter's goals.

Internal mobility angle: if promotion path is blocked, parallel transfer with expanded scope may achieve comp and growth; present as option, not threat. Compare at level+1 in the packet makes internal transfer conversations easier — you already have proof of next-level work.

#What to do this week

Pull level criteria tonight. Draft one initiative page before Friday. Send manager one question: What evidence would make approval easy? One page, one conversation.

If you are building promotion process on HR/ops side: require packets before calibration agendas lock. No packet, no slot — protects committees from narrative-only debates and protects high performers from "we ran out of time." Customer proof, cross-functional endorsements, and artifacts appendix turn internal adjectives into evidence committees can compare side by side.

Timeline transparency with your manager — when committee meets, deferral rules, budget cycle — prevents rumor-driven quarters. Sponsorship question — who advocates when you are not in the room — should be answered before you finalize the packet, not after denial.