I've been on the other side of the table for eight promo cycles. I'm going to tell you what actually gets said.
the first 2 minutes:
if your name is unfamiliar to anyone in the room, that's already a problem. calibration committees at most companies have 4-8 directors and senior managers from across the org. if your work hasn't crossed any of their teams, they're forming an opinion entirely from the packet and your manager's verbal pitch.
this is why cross-functional visibility matters so much. it's not politics for the sake of politics. it's that the committee literally cannot advocate for you if they don't know you.
what causes approvals: specific impact that maps to next-level criteria (not "did great work," but "drove X decision that affected Y teams") a manager who can answer follow-up questions confidently. if the committee asks "what would've happened without her?" and your manager pauses too long, that's a flag. consistency across multiple reviewers. if 2 of your 3 peer reviews say something similar about your scope, that carries a lot of weight.
what causes deferrals: packet says "influenced" a lot without evidence of what changed because of that influence scope that looks big but is actually well-defined and repeatable (executing well at scope is current-level, not next-level) a manager who comes in confident but can't answer specifics. I've seen strong packets die because the manager said "I believe in her" when asked about a specific incident. recency. if the strong work was 10+ months ago and the last two quarters look lighter, that matters.
the political part:
your manager's standing in the room affects you. a respected manager with strong promo history can advocate effectively. a manager who's known for overselling gets more pushback on their nominations. not fair but real.
there's also org headcount pressure. some companies have explicit limits on what percentage of the team can be at senior or above. if your team is at the cap, a solid promo packet can still get deferred with language like "strong but not a top priority this cycle." ask your manager about the headcount context before you commit to a cycle.
I'm not telling you this to be cynical. I'm telling you because knowing the variables lets you position better. the packet is necessary but it's not sufficient.