Pay Increase Form Template

Use this Pay Increase Form Template when HR business partners, total rewards, and people managers need a single, reviewable intake for salary adjustment requests—whether the trigger is performance, expanded scope, internal parity, retention risk, or scheduled compensation cycles.

Structured requests reduce back-and-forth, make peer comparisons fairer inside your rubric, and leave an audit trail that finance and leadership can stand behind.

Important: This template supports workflow design and documentation. It does not replace qualified legal, labor relations, or compensation counsel where your jurisdiction or policies require it.

What to clarify before you publish fields

• Eligible populations: full-time versus part-time, regions, union coverage, probation, or freeze windows.
• Decision rights: who recommends, who approves, and budget thresholds that escalate to finance or the executive team.
• Philosophy in plain language: how market data, performance ratings, and internal equity interact—so employees know what “strong case” means in your org.

Field modules that keep reviews comparable

Tune labels to your job architecture; typical blocks include:

• Employee and role context: name, employee ID if policy allows, department, location, job title, level or grade band, manager name, hire or last-adjustment date.
• Request type: merit, promotion, market adjustment, retention, cost-of-living—use controlled lists, not open text alone.
• Scope and performance summary: structured prompts aligned to your review cycle (goals met, leadership behaviors, scope expansion)—pair with matrix questions or parallel scales where helpful.
• Business justification: why now, impact on team or customers, risk if unaddressed—keep free text questions bounded with character limits and examples of strong versus vague answers.
• Manager recommendation (if applicable): support level, proposed effective date, budget code or cost center when finance requires it.
• Attachments: offer letters for competing offers only if your policy permits and privacy rules are clear; otherwise route sensitive documents through a secure HR channel.

Use skip logic so promotion paths see different modules than simple merit bumps, and so matrixed employees route to the right approvers.

Submission timing aligned to comp cycles

• Annual or focal reviews: open the form only during published windows so finance can plan headcount and merit pools.
• Off-cycle exceptions: require an additional attestation (retention, critical skill, legal settlement) so “exceptions” stay visible to leadership.

Secure routing and confidentiality

• Send submissions to named HRBP or comp queues with e-mail notifications—not a shared mailbox no one monitors.
• Stamp organization unit, region, or business with hidden variables from each portal link for cleaner reporting.
• Push approved data to HRIS or ticketing with webhooks or your integration path only after security review—salary requests are high-sensitivity data.

Enable multilingual surveys for global teams; translate HR and finance terms with people partners, not only literal UI translation.

Manager-initiated versus employee-initiated (use case)

Manager-initiated: emphasize performance evidence, calibration readiness, and proposed band movement—employee may only confirm facts, not negotiate in the form.

Employee-initiated: add clear guidance on what reviewers need, expected timelines, and that outcomes follow policy—reduces entitlement tone and incomplete packets.

Pay increase workflow KPIs to monitor

• Time from submit to first HR or manager acknowledgment against your SLA.
• First-pass completeness rate (requests returned for missing data indicate unclear fields).
• Volume by request type and business unit—surges may signal market pressure or manager training gaps.
• Cycle time to decision and documented outcome (approved, deferred, denied with reason category where lawful).
• Repeat submissions on the same case—may signal unclear denial communication or unresolved scope issues.

Mistakes that create comp and trust problems

• Asking for current salary where pay transparency laws or policy forbid it—validate field lists with counsel.
• Letting every field be optional—reviewers get noncomparable packets.
• Mixing grievances about peers’ pay into unstructured rants—use structured criteria instead.
• No audit trail when exceptions are granted—finance and legal cannot reconstruct the decision later.
• Automated “approved” messaging when a human has not reviewed—never imply outcome from submit alone.

Helpful resources

Use create survey, make your questions required only where policy truly requires an answer, and survey data analysis for operational reporting on intake volume—restrict access to compensation roles.

Then read workplace communication, anonymous employee feedback, employee engagement survey, and survey design guide to align how you explain the process with broader listening programs and clear, fair question wording.

Build and launch in Responsly

Publish pay increase requests in Responsly with validation on critical identifiers, branching by request type, secure notifications, and integrations that create ticket or case IDs—so compensation decisions stay traceable, equitable, and finance-ready.