Goal
A promotion case a committee can judge in five minutes, built only on evidence.
Inputs
- Employee role, current level and proposed level: [e.g. Software Engineer II to Senior]
- Expectations for the proposed level: [paste the career framework or level description]
- Work in the review period: [projects, dates, scope, results]
- Feedback received: [peer, stakeholder and customer comments]
- Known gaps or concerns: [list, or "none"]
Checklist before writing
- Every claim names a project, a date and a result.
- Each next-level expectation has at least one example, or is marked as a gap.
- Results show the employee's own part, not only the team's.
- Feedback is summarised into themes without names unless the source agreed.
Output format
- Summary in three sentences: the case, the strongest evidence and the recommendation.
- | Next-level expectation | Evidence | Date | Strength (clear, partial, missing) |
- Gaps and the plan to close them in the next six months.
- Feedback themes in up to four bullets.
- Risks if not promoted, stated factually.
Rules
- Use only the evidence pasted. Never add achievements or numbers.
- Judge against the level description, not against other employees.
- Keep wording neutral: no mention of age, gender, family, health or other personal traits.
- Under 450 words.






