Build the promotion record that can survive a 'we chose someone else' decision

When a promotion goes to someone else, the painful part is the gap between what you believe you did and what the employer can defend. The file that matters is the one that can be checked against the org chart, the posting, and the written reason for the choice. A manager who has written promotion cases and lost some knows the difference.

The record is the case, not the conversation

The employer's written rationale is the starting point. The posting window, the alternate role, and documented relevant experience let you check it. Self-assessment helps you organize the file, but it does not carry the proof. A challenged decision asks whether the employer can point to a defensible reason and whether the record can be checked against it.

The org chart matters because the role you want has a reporting line, a budget, a set of duties, and a manager who must defend the choice. A file that cannot be mapped to those facts reads like a self-review, not a case.

In Richard Highbaugh v. Exelead, Inc., No. 25-2638, the Seventh Circuit affirmed Exelead's summary judgment, a decision without a trial, because Highbaugh did not establish that the company's stated reason for not promoting him was pretextual, or not the real reason. The appeal arose from the U.S. District Court for the Southern District of Indiana, Indianapolis Division, where Judge Richard L. Young was the district judge. Highbaugh claimed that Exelead discriminated against him based on race and age when it passed him over for a management position. The court found that he did not supply enough evidence to challenge Exelead's rationale that it selected a candidate with more relevant experience.

Start the file before the decision, not after the disappointment.

Build the file before the decision

The file works because each part tests a different part of the employer's story. A dispute often turns on whether the stated reason can be checked against the posting, the window, and the actual choice. A good file is boring: dates, documents, and short descriptions of work. It should let a skeptical reader follow the logic without asking you to explain your value.

• Written rationale: keep the job posting, the stated selection standard, and the close date, because the decision is judged by the reason the employer gives.
• Posting window: save the dates the role was open, who was told, and whether the window was long enough for qualified candidates to apply.
• Alternate role: document the other position the company filled, its requirements, and the person chosen, so you can compare the actual choice against the stated standard.
• Relevant-experience proof: collect project records, scope, duration, and outcomes that match the role's requirements, not just titles or years.
• Contemporaneous feedback and metrics: save dated performance notes, customer or manager feedback, and measurable results that show the work was recognized when it happened.

A missing part shows where the case is weak. A file is useful when it lets you ask a concrete question and get a concrete answer. The test is simple. Can you open the file and answer the question without memory, emotion, or a long narrative? A story answer means the file is not ready.

After a pass-over, test the employer's reason

After a pass-over, do not start with a grievance. Start with the file. Request the written rationale if it was not given. Ask for the posting window and who else applied. Compare the alternate role's requirements with the chosen candidate's fit. Those requests are the same ones a reviewer will make. Make the tone factual. You are asking for the record that will show whether the decision was made on the stated standard, not for sympathy. A fair request makes the next step clearer.

Relevant-experience claims need a comparison between the requirement and the work you did. A short posting window needs dates that show whether the time was enough. Metrics claims need the metrics you had and the dates they were recorded. The review usually begins with the same ask: what did the employer write down, and can the record test it?

In California, an appellate opinion is citable once ordered for publication in the Official Reports, and other courts and parties can cite or rely on it. The written record must survive review. If the employer cannot produce the rationale, window, or comparison material, the file has done its job. If the employer can, it shows where your case needs more proof.