Promotion Nomination Packet

This template is for managers, team leads, or HR partners who need to submit a structured promotion case for review. It works best when one person owns the packet and gathers evidence from the employee’s recent work, peers, and stakeholders. If your organization uses calibration or leveling committees, this form gives them a consistent packet to review.

An ad-hoc email usually leaves out the evidence reviewers need to compare candidates fairly. This template captures the nominee’s current and proposed level, the manager’s rationale, measurable results, and mapping to the leveling framework in one place. That makes the review easier to audit, compare, and calibrate.

Use it whenever a manager is formally nominating someone for promotion, whether that is during a scheduled cycle or an off-cycle request. It is not meant for routine performance check-ins or compensation-only changes. If your company promotes on a fixed cadence, this packet can become the standard submission form for each cycle.

Include concrete outcomes such as shipped projects, process improvements, customer impact, revenue or cost effects, and examples of expanded scope. Supporting documents can include performance summaries, project artifacts, or stakeholder notes, but only attach what is needed to justify the decision. Avoid vague praise without evidence, because reviewers need facts they can compare across nominations.

That section forces the manager to connect the nominee’s work to the company’s actual criteria for the proposed level. It reduces ambiguity by showing which expectations are already met and where the evidence is strongest. If your organization uses a custom framework, the template can be adapted to match those level definitions and competencies.

The most common mistakes are writing a generic summary, overstating impact without proof, and leaving the criteria mapping too vague. Another issue is collecting unnecessary PII or attaching documents that are not needed for the review. The packet should stay focused on decision-making data, not a full personnel file.

Yes. You can swap in role-specific criteria, add department-specific evidence fields, or adjust the endorsement section for matrix organizations. For example, engineering, sales, and operations may each need different proof points, but the same packet structure still works.

The packet should go to the reviewer or calibration group for assessment, with an audit trail of who submitted it and when. Reviewers can then compare the packet against the leveling framework, request additional evidence if needed, and record the decision. A clear submission-confirmation line helps the manager know the packet was received and routed.

It can, because a structured packet supports consistent review and reduces the chance that decisions rely on undocumented impressions. The consent and data-accuracy confirmations also help set expectations for review and handling of employee information. It is still important to use the same criteria framework across similar roles to support fair, defensible decisions.