Internal Promotion Offer Letter Framework

This framework is used to document a promotion for an existing employee in a formal offer letter format. It captures the new title, default compensation, effective date, revised default benefits, and the approvals needed before sending. It is meant for internal moves, not external candidate offers.

Use it when the person is already employed and you need to confirm a new role, pay change, or benefits update. It is especially useful when the promotion changes exempt status, salary basis, or reporting line. If the move is only a title change with no compensation or policy change, a lighter internal memo may be enough.

HR usually drafts the letter, with compensation or finance reviewing pay changes and the hiring manager confirming the role details. If the salary crosses the approval rules threshold, executive_approval_required should be triggered before the letter is issued. Legal or employee relations may also review cases involving state-specific carve-outs or sensitive transitions.

Yes, for US-based at-will employment contexts the letter should state at-will status where applicable and avoid language that creates a fixed-term promise. That matters even for internal promotions, because the new role should not accidentally override the existing employment relationship. State-specific carve-outs should be checked before sending.

It should use default_compensation with a salary type and a min/max range or fixed amount, depending on your workflow. For promotions, the letter should clearly state the new pay basis and effective date so there is no ambiguity about when the change starts. If the role is exempt, the salary basis test for FLSA should be reflected in the wording and approval flow.

Yes, and you should. The framework should include country and state_province fields so US letters can reflect at-will language and state-specific notice requirements, while non-US letters can be adapted for local rules. For EU-based employees, add GDPR data-handling language if the letter or workflow stores personal data.

Common mistakes include omitting the effective date, using free-text benefits instead of a structured default_benefits hash, and forgetting signature anchors for e-signature placement. Another frequent issue is failing to trigger executive_approval_required when the salary threshold is exceeded. A vague letter can also create confusion about whether the promotion is permanent or contingent on performance.

Ad hoc emails are easy to send but often miss legal and workflow details like approvals, jurisdiction, and signature placement. This template gives you a repeatable record of the new title, compensation, benefits, and acceptance terms in one place. It also makes it easier to audit who approved the change and when it became effective.