Describe the employee changes your HR team needs to document. Makeform turns the request into a structured personnel action form with employee details, current and proposed status, compensation changes, effective dates, reasons, supporting files, and approval routing—so payroll, HR, managers, and IT can act from the same record.
Send approved personnel actions to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt the details, or send it into the Makeform builder. Each example shows a practical structure rather than a live AI result.
Prompt ready4 formats
Audience
Hiring managers initiating an employee record
Format
New-hire action with start details and routing
Prompt size
493 chars
Brief qualitySends to builder
Example form structure
New-hire action with start details and routing
Prompt exampleEditable in builder
Employee identity and contact details
Short answerFirst ask
2
Role, department, manager, and location
Dropdown
3
Start date and employment classification
Date & time
4
Pay type, rate, and cost center
Number
5
Offer details and setup documents
File upload
Suggested routing tags
Suggested
Pending manager approval
HR review
Payroll ready
Keep current values beside proposed values. Payroll and HR reviewers should never have to infer what changed from a manager's notes.
Step 1
Request
manager selects an action and enters the change
Step 2
Review
HR checks dates, fields, and supporting details
Step 3
Approve
required reviewers record decisions in sequence
Step 4
Implement
payroll and operations complete dated tasks
Why personnel actions need structure
A manager's email is not a change record.
A personnel action affects several systems and owners. A structured request puts the old value, new value, reason, effective date, and approvals together before downstream teams begin work.
Current and proposed values side by side
Record the title, manager, department, location, status, and compensation before and after the action. Reviewers can see the precise delta instead of reconstructing it across an email thread.
Questions change with the action
Conditional sections ask for a start date on a hire, return date on a leave, and last day on a separation. Managers see relevant questions while HR receives consistent data.
One handoff across departments
Capture which approvals and operational tasks are needed for HR, payroll, IT, facilities, and the manager. The submission remains the shared reference as each owner completes work.
Built for common employee changes
One form can branch into the right personnel workflow.
Start with an action-type question and reveal only the fields that HR and downstream owners need for that change.
Hire and rehire
Collect identity, role, classification, reporting line, start date, compensation, cost center, and setup needs before the employee arrives.
Promotion and transfer
Compare the current job with the proposed job, including manager, department, location, title, compensation, effective date, and business reason.
Pay and schedule adjustment
Document current and proposed rates, pay type, scheduled hours, full-time equivalency, effective date, and whether an adjustment is recurring or one-time.
Leave, return, and separation
Coordinate status dates, reason categories, return expectations, access changes, equipment tasks, final handoffs, and internal review fields.
Personnel action workflow
Turn a requested change into an implementable record.
Build the form around the real approval path and downstream work, then give every reviewer enough context to decide without chasing the requester.
Tell Makeform which employee changes you process, who may submit them, which fields are required, and which approvals vary by department, compensation amount, or action type.
02
Separate current, proposed, and internal data
Edit the generated fields so requesters enter current and proposed values distinctly. Keep sensitive reviewer notes and internal decisions in sections intended for the appropriate HR workflow.
03
Add conditional branches and validation
Show compensation questions only when pay changes, return dates only for leave, and equipment tasks only when assets are assigned. Require employee IDs, effective dates, and reasons before submission.
04
Route the record and track completion
Send notifications to the right reviewers, then pass approved details to payroll and operational owners. Use the submission identifier to reconcile acknowledgments, implementation notes, and completed tasks.
Form vs email vs document
Choose a record that can move with the work.
A static document can describe a change, but a generated online form captures structured values, branches by action type, and starts the handoff without rekeying the same employee details.
Approach
What happens
Best read
ApproachEmail or chat request
What happensThe reason may be clear, but effective dates, old values, cost centers, and approvals are easy to omit or scatter across replies.
Best readUseful for an initial conversation, weak as the operating record.
ApproachDownloaded PDF or Word document
What happensThe request has a repeatable layout, but staff may still type the same values into routing messages, trackers, and downstream systems.
Best readUseful where a printable copy is needed, with manual handoffs.
Approach
Generated online personnel action form
What happensAction-specific questions produce structured submissions with dates, attachments, reviewer context, and routing tags from one entry point.
Best readBest for repeatable intake and coordinated implementation.
Field guide
What a personnel action form should include.
The strongest form distinguishes facts about the employee, the requested change, timing, justification, approvals, and implementation. Use these six sections as a practical starting point, then match them to your internal policies.
Employee identity
Match the action to the correct employee.
Names alone can be ambiguous. Capture the employee identifier and organizational context needed to locate the right record, while avoiding unrelated personal data. For a new hire without an ID, make the temporary identifier or recruiting reference optional and record who initiated the action.
Employee legal or record name, preferred name when useful, and employee ID.
Current title, department, manager, work location, and cost center.
Requester name, role, contact, and date submitted.
Action and change set
State exactly what is changing.
Begin with a controlled action-type list: hire, rehire, promotion, transfer, job change, compensation change, schedule change, leave, return, or separation. Then place each current value beside its proposed value. This makes a multi-part action visible, such as a promotion that also changes manager, department, pay, and work location.
Action type and requested employment status.
Current and proposed title, manager, department, location, and classification.
Current and proposed scheduled hours or full-time equivalency when applicable.
Compensation details
Give payroll unambiguous values.
Compensation changes need structured numbers and labels, not a sentence such as give a ten-percent increase. Record the current and proposed pay basis and frequency, the effective date, and whether the request is recurring or one-time. A reviewer can then confirm the requested values before payroll performs its own processing.
Current and proposed hourly rate, salary, stipend, or other defined pay value.
Pay frequency, recurring or one-time indicator, currency where relevant, and cost center.
Effective date and the pay period the requester expects the change to affect.
Reason and support
Capture decision context without writing an essay.
Use a reason-category dropdown for reporting and a concise explanation for reviewers. Ask for attachments only when they support the internal process, such as approved compensation details or a role-change summary. Avoid turning the form into a repository for sensitive information that is not required for the action.
Standard reason category plus a plain-language business explanation.
Budget owner, position or requisition reference, and backfill impact when relevant.
Supporting attachment field with clear instructions about appropriate documents.
Dates and approvals
Separate requested timing from decisions.
The effective date drives payroll, access, reporting lines, and employee communication. Collect it as a date field rather than burying it in notes. Give each required reviewer a distinct decision, reviewer identity, date, and comment area so a later reader can follow the sequence without assuming that submission equals approval.
Requested effective date, employee communication date, and last day or return date when relevant.
Manager, department head, HR, compensation, finance, or payroll decisions as your process requires.
Decision status, reviewer, review date, and explanation for returned requests.
Implementation and closeout
Translate the approved action into owned tasks.
Approval is not the final operational step. Identify which teams must update systems, pay, access, equipment, directories, schedules, benefits administration, or reporting structures. Record target timing and completion notes against the same submission so HR can reconcile the request with what was implemented.
Payroll, HR system, IT access, facilities, equipment, and manager task flags.
Named owner, target date, completion status, and implementation note for each handoff.
Shared personnel action identifier for matching related records without duplicating sensitive details.
Related tools
Connect the rest of the employee lifecycle.
Use focused Makeform tools for the employee information, onboarding, review, timekeeping, requisition, and separation workflows that sit around a personnel action.
Practical answers for HR teams replacing scattered emails, paper requests, and manually routed change documents.
What is a personnel action form?
A personnel action form records a requested change to an employee's work status or job record. Common actions include hires, rehires, promotions, transfers, manager or department changes, pay adjustments, schedule changes, leave, return from leave, and separation. The form usually captures the current state, proposed state, reason, effective date, supporting context, approvals, and downstream tasks. It is an internal coordination record; your organization decides which fields and reviews its process requires.
What fields should a personnel action form include?
Start with employee name and ID, requester, action type, current title, department, manager, location, classification, and compensation fields relevant to the change. Add the proposed values, effective date, reason category, explanation, cost center, attachments when appropriate, and separate reviewer decisions. Leave and separation actions may also need last-day, return-date, access, equipment, and handoff questions. Conditional logic keeps this broad list from appearing on every request.
Can one form handle hires, promotions, pay changes, and separations?
Yes. Make the first question the personnel action type, then create a conditional section for each pathway. A hire branch can request start and setup details; a promotion branch can compare current and proposed roles; a pay branch can request current and proposed compensation; a leave or separation branch can request status dates and operational tasks. Keep a small shared section for employee identity, requester details, reason, and effective date so reports remain consistent.
How should a personnel action form show salary or hourly-rate changes?
Use separate numeric fields for the current and proposed values, plus fields for pay type, pay frequency, currency if needed, recurring or one-time status, cost center, and requested effective date. Do not rely only on a percentage or a note because reviewers may interpret the base differently. Limit access to sensitive submissions according to your internal practices, and have the appropriate HR and payroll reviewers confirm values before implementation.
How do we prevent incomplete personnel action requests?
Require the employee identifier, action type, proposed change, effective date, and reason before submission. Use dropdowns for departments, managers, locations, classifications, and reason categories where a maintained list exists. Conditional logic should require branch-specific details without burdening other requesters. Include concise instructions beside compensation, date, and attachment fields, and give reviewers a return-for-information path rather than forcing them to resolve gaps outside the record.
Can the form route different actions to different reviewers?
Build the intake so its action type, department, location, or other selected values produce useful routing tags and notifications. A title-only update may follow a simpler path than a compensation change, while a separation may notify HR, payroll, IT, facilities, and the manager. Keep each reviewer decision distinct, and avoid presenting a submitted request as approved. If your desired routing behavior is not available in the builder, the precise branching and notification requirement is a useful feature request.
Is this personnel action form generator free?
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and use your personnel action form without a response cap. The paid tier removes the Makeform badge. Review the generated structure, replace sample choices with your organization's real departments and action rules, and test every conditional path before sharing it with managers.
What should happen after a personnel action is approved?
Turn the approved change into named implementation tasks with owners and dates. Depending on the action, this may include updates to the HR record, payroll instructions, reporting lines, directories, schedules, system access, facilities, or assigned equipment. Reference the same personnel action identifier in downstream work, record completion notes, and reconcile the implemented values with the approved request. Keep unrelated sensitive detail out of broad operational notifications.
Replace scattered change requests with one clear record.
Generate a personnel action form built around your employee changes.
Unlimited free forms and responsesCurrent and proposed valuesConditional approval handoffs
