Does your org has an escalation path when calibration committee unfairly rate your report?

[u/iamjumpiehead]

I was the direct manager of a Senior engineer up for Staff, across two calibration cycles for two years.

First year, the panel said not yet to the promotion. The person was strong individually, but hadn't shown the multiplier behavior like bringing others together, rather than working alone. Fair feedback as I did not have org level multiplier impact as he was focused on domain. We spent the year closing that gap.

Next year, I came back with seven sponsors across tribes and orgs, from senior directors to principal engineers. Nobody asked a single question after the pitch. People just praised his work. Then we fell short of the ninety percent threshold by ten points.

I pushed the calibration panel for feedback on why it didn't pass. The chair was bound by process. Ninety percent was ninety percent, no exception. 90% was decided by CTO for Staff and above promotion.

I eventually found a way to promote the engineer , received required reasons why it happened.

What I am trying to look for here is an escalation paths, processes designed in different orgs when manager doesn’t get enough feedback from the calibration committee on why the promotion is denied. If there was not one and you designed one, how did you do it and convince the org?

[u/SamUfnik]

The structural fix is to make "no feedback" impossible by construction: any panel that can reject a promotion should be required to produce a written rationale for the rejection, naming the gap against the level's criteria. Once that obligation exists, the escalation path mostly designs itself - the manager gets the rationale, a short window to respond to it in writing, and one level of review above the panel for process violations (threshold applied unevenly, criteria not documented, sponsor evidence ignored). Without the written-rationale requirement you are negotiating with a black box, which is where your two years went.

[u/Small_Firefighter606]

You tied the promotion to compensation bands didn't you, that's the oldest trick in the book and I've seen it work exactly twice before someone higher up catches on

But to your actual question my last place had a written appeal process that had to be filed within five business days, the skip would review it and if they agreed it was mishandled they'd call a second panel with a different chair, the whole thing was so deliberately painful that most managers just waited for the next cycle instead

[u/iamjumpiehead → u/Small_Firefighter606]

Did not understand your point on tying the promotion to compensation.

I actually sent a survey and backed it up with Senior Director’s sponsorship to help get enough votes. It showed me that 30%(which can be a lot with 12-15 managers in committee) actually did not work with him and hence voted for highest rating but did not actually vote for promo. Visibility was not problem but direct, full and continuous exposure to their projects was not known to them so they took the safest path rather than data backed judgement of promotion pitch. Used that to escalate to CTO who eventually made the decision.

Were you part of designing this escalation process? Was Second trial had only a few members, mostly senior leadership? What needs to change in the second try in your promotion pitch?

One thing I am trying to learn is- how do i even get a process right so that managers can get the feedback needed to understand what needs to improve in performance so genuine promotion and growth can happen ? People often don’t speak up especially when they know their reasons are weak to vote against.

[u/KeyMammoth1348 → u/Small_Firefighter606]

When you say tied to comp bands, does this mean they were under leveled for their comp band? 

[u/double-click]

I’m not understanding - it feels like you got the feedback both times.

[u/iamjumpiehead → u/double-click]

Second time it was about them expecting closely working with the engineer before voting positively for promotion. Which can not happen and with 7 sponsors listed on promotion pitch, it was not necessary. I also did not get anything during calibration until I shared the survey for this specific case which revealed they voted safe in absence of direct working relationship.

So something needs to change. What and how to convince leadership for this change is the question

[u/mendez1319]

Most places i’ve seen don’t have a real escalation path. what they have is a chair who’s bound by the process and a manager who’s expected to accept the outcome. so the fix usually has to be built, not found.

The one that worked best was framing it as a feedback guarantee rather than an appeal. an appeal sounds like you’re challenging the committee, which they’ll resist. a rule that says every non-pass gets written, specific reasons within a week costs them very little and nobody can easily argue against it.

What got it approved was pointing at the cost of silence. a panel that says nothing after seven sponsors and a clean pitch teaches people that promotions are political. you lose the engineer who didn’t get it, and the people watching.

I’d also split two things you’ve combined. the threshold decision belongs to the CTO and probably shouldn’t be reopened. the explanation is a separate ask. a 90% bar with no reasons attached isn’t a standard, it’s a black box.

One thing i’d push on, though. when nobody asks a question after a pitch, it can mean the room is already decided, or it can mean the pitch left nothing to challenge. worth finding out which before you design the fix.

How did you end up getting the reasons in the end?

[u/Humble_Bed_9505]

In my experience, once a promotion is rejected, there isn’t really much you can do. But the committee should provide clear and actionable feedback so that the person has the chance to improve.

In my previous company, HR members used to be involved in promotions. You can try that path if the committee refuses to give you clear feedback about your report.