Employee personal data change form

When to use an employee change form

Use it whenever something in an employee's record changes after hire. That covers two kinds of change that many companies split into separate forms: personal data changes the employee starts (a new surname, address or phone number) and personnel actions the manager starts (a raise, promotion, transfer or move from part-time to full-time). The second kind is often called a personnel action form or employee status change form. One form with two parts is simpler for small HR teams; larger organizations often run them as separate workflows in the HRIS.

The form is the audit trail. When an employee later asks why their pay changed or a regulator asks when someone was reclassified, the signed form with an effective date and reason answers it.

What to include and why

Old and new values side by side. Writing only the new value makes errors hard to spot. Showing $17.50 to $18.25 lets the approver check the math and the percentage.

Effective date tied to payroll. Mid-period changes create retro pay and split calculations. Most teams set changes to the start of a pay period unless there is a reason not to.

Reason codes. A fixed list (promotion, merit, market adjustment, transfer) lets you report on pay decisions later, which matters for pay equity reviews.

FLSA status. A title change that moves someone from non-exempt to exempt is a significant decision with overtime consequences. Making it an explicit field forces someone to check the salary basis and duties tests.

Links to other forms. An address change in another state can change state income tax withholding. A name change needs to match Social Security records or W-2s will not reconcile. A marriage can open a benefits window. The checkboxes in Part 2 prompt for each.

Legal and record-keeping notes

Several states require employers to give written notice of pay rate changes before or when they take effect, for example under New York's Wage Theft Prevention Act and California's Labor Code. Check the rules for each state you operate in, since they vary in timing and content.

For a name change, employers are not required to complete a new Form I-9, but may record the new name in Supplement B. Do not ask the employee for new identity documents just because they changed their name.

Keep the completed form in the personnel file. Anything that includes bank details or Social Security numbers should be stored with restricted access. Our personnel file checklist sets out what goes where, and the glossary entry on the personnel file explains employee access rights.

Making changes simple at volume

In a large hourly workforce, change requests arrive daily: shift moves, pay step increases after training, transfers between programs. Paper forms passed between three approvers get lost. Use a digital form with routing so each approver is notified in turn, the employee gets confirmation, and payroll sees only approved changes. Let employees update their own address and phone number through self-service, and keep the approval workflow for job and pay changes.

Batch predictable changes. If every agent gets a pay step after graduating from nesting, process the whole class on one form with a list of names rather than 40 separate forms.

Common mistakes

• Updating the HRIS but not payroll, or the other way round, so the two systems disagree.
• Backdating effective dates without calculating retro pay.
• Changing someone to exempt because their title now says manager without checking the duties test.
• Accepting an address change by text message with no record of who asked for it, which is also a common route for fraud.
• Forgetting the knock-on updates: tax forms, benefits, system access and the new manager's team list. Compare with the details collected at hire on the new hire information form.