Personnel actions
Also called personnel action request (PAR), employee status change
Started by the supervisor or HR, routed by the kind of action to every approver it needs, and recorded the moment it’s final. We build it to work the way you run personnel actions now.
Personnel action
EmployeeR. Castillo
ActionTransfer
FromLincoln Elementary
ToCentral Middle School
EffectiveJanuary 6
Next approverHR director
Submit
Video coming
Start to finish
From the request to the official record.
Here’s how it runs in Flow Forms. The steps marked on its own happen without anyone, and everyone else is notified when it’s their turn.
- 1The supervisor or HR
Fills it out on any device. They pick the kind of action, and the form only asks what applies to it, with dropdowns and required fields so the details are right the first time.
- 2The routingOn its own
Sends it down the path for that kind of action. A new hire picks up technology and building access. A pay adjustment goes to the department head and payroll. A separation puts ending access in front of the office that owns it.
- 3Each approver
Approves it from any device, or sends it back with a note. If it sits, reminders go out. If someone is out, it goes to their backup.
- 4The offices with a part
Technology, the building, or payroll is notified when it’s their turn, and marks their part done.
- ✓On fileOn its own
The record keeps who started it, who approved it, when, and what changed at each step. It’s ready for your HR and payroll systems by export, or connected directly where they allow it.
What it handles
The details, built in.
- A different path for each actionHires, transfers, pay changes, and separations each follow their own route.
- Details entered onceDropdowns and required fields catch mistakes when it’s filled out, not three systems later.
- Where it standsAnyone you authorize can see who has it and what’s next.
- When an approver is outIt goes to their backup, so an action never waits on one person.
- Every change on recordWho started it, who approved it, and what changed, step by step.
Yours needs something that isn’t here?
Bring it to the first call. We’ll build it in while you walk us through how it works.
Book a conversation →How it varies
Every organization approves personnel actions a little differently.
We don’t start from a standard personnel action form. We start from how yours runs today. And when something changes, like a new kind of action or a new approver, tell us and we change it.
We build it to yours.
- Kinds of actionHires, transfers, promotions, reclassifications, step increases, leaves of absence, and separations.
- Who approves whichA department head alone, HR review, a superintendent or city manager, or all of them.
- Board or council actionWhich actions need it, and where that step sits.
- What followsTechnology access, keys, payroll setup, onboarding, or offboarding.
- Districts and officesA district often routes by building. A city or agency often routes by department.
Questions
About personnel actions.
Does a promotion need the same approvals as a separation?
Why does a new hire need a different path than a pay adjustment?
What happens when an approver in the chain is out?
Who decides which path each kind of action follows?
Does this replace our HR or payroll system?
Bring us yours.
We’ll build it with you.
Tell us how personnel actions move now, which kinds follow which path, and who has to sign. Not a demo. A conversation about your process.
Book a conversation