Skip to content
automation

HR workflow automation: seven workflows, who approves them and what to keep

HR workflow automation for mid-size companies: seven workflows after onboarding, who approves each step and how long federal rules say to keep records.

An HR director and an HR coordinator review an HR requests screen with leave, pay change and leaver tasks at her desk

HR workflow automation is software that runs the routine steps of HR requests and changes: it sends each one to the right approver, updates the HR system, payroll and IT, and files the record the law expects you to keep. People keep the decisions; the system keeps the dates, the reminders and the trail.

This guide covers seven workflows that run after the first day, for HR, payroll and IT leads at mid-size and large companies. Onboarding has its own guide, on employee onboarding automation. For the method behind any build, see how to automate business processes.

Which HR workflows should a mid-size company automate?

The ones that repeat, follow a written policy and leave a record. Most touch HR, payroll, IT and a manager at once.

Workflow Trigger What the system runs Who approves Record kept, and for how long
Offboarding HR enters a last day Closes accounts, lists equipment, alerts payroll, dates the Form I-9 HR confirms the exit; IT confirms accounts are closed Personnel records: 1 year from an involuntary termination. Form I-9: 3 years after hire or 1 year after the last day, whichever is later
Job and pay changes A manager's request Routes it, sets the effective date, updates payroll, flags access Budget owner, then HR The change: 1 year from the record or the action, whichever is later. Payroll records: 3 years
Leave requests An employee's request Checks the balance, routes it, sends notices, records dates Manager; HR designates protected leave Family and Medical Leave Act (FMLA) records: 3 years
Policy acknowledgments A new or changed policy Sends it, collects signatures, chases, lists gaps The policy owner approves the text As a personnel record: 1 year
Form I-9 reverification An expiration date on file Reminds HR and the employee early A trained person examines the documents With the Form I-9, for as long as it is kept
Review cycles A calendar date Opens forms, reminds, collects ratings, passes pay decisions on Manager, then HR Personnel records: 1 year from the record or the action
Document requests An employee asks Checks the requester, fills the letter, logs what went out HR, beyond standard letters Your schedule; no federal period is set for the log

These are federal minimums from U.S. Citizenship and Immigration Services (USCIS), the Equal Employment Opportunity Commission (EEOC) and the Department of Labor, linked below. States can require more. This is general information, not legal advice: agree your retention schedule with employment counsel before a system deletes anything.

How should offboarding work?

Offboarding is where a slow handoff costs most: an account left open after someone has gone. In its catalog of security and privacy controls, the National Institute of Standards and Technology (NIST) asks organizations to notify account managers when users "are terminated or transferred," and to align account management "with personnel termination and transfer processes." It leaves the time limit to each organization. We suggest the same day, and NIST notes that in some cases organizations consider disabling accounts before the person is told.

One entry from HR, the last day and the type of exit, starts everything:

  • Accounts. IT gets a closing list built from what was granted, and confirms each one. For the IT side, see our guide to IT operations automation.
  • Equipment and pay. Laptops, badges and keys are listed for return, and payroll gets the last day.

For the Form I-9, the USCIS Handbook for Employers says to work out the keep-until date once someone stops working for you: keep the form "for three years after the date of hire, or one year after the date employment ends, whichever is later." After an involuntary termination, the EEOC's recordkeeping rule says personnel records are kept "for a period of one year from the date of termination."

How should job and pay changes flow?

Automated, a promotion, transfer or raise starts as a form with the new title, pay, manager and effective date:

  1. The manager asks. The system checks the pay range and the budget.
  2. The budget owner approves, then HR. Nobody approves their own request.
  3. Payroll checks the effective date before the next run.
  4. Access is reviewed. For a transfer, NIST asks organizations to "review and confirm ongoing operational need" for current access, then change it to fit the new job. Old access is removed, not just added to.

The EEOC rule covers records "having to do with hiring, promotion, demotion, transfer, lay-off or termination, rates of pay or other terms of compensation": keep them one year from the record or the action, whichever is later. The Department of Labor's wage and hour recordkeeping rules require payroll records for at least 3 years and wage rate tables for at least 2.

How should leave requests be handled?

Most leave is simple: the employee asks, the system checks the balance, the manager approves and payroll is told.

Leave that may fall under the FMLA needs more. Its recordkeeping rule says covered employers keep the records "for no less than three years," including the dates leave was taken and copies of notices. Leave must be designated as FMLA leave in the records, and medical certifications are kept as confidential medical records "in separate files/records from the usual personnel files."

When an employee picks a reason that may qualify, the request goes to HR, not the manager. HR decides the designation, the system sends the notices and records the dates, and the certification goes to a file the manager can't open.

How do you track policy acknowledgments?

A new code of conduct or the yearly security rules need a signature from everyone covered.

The policy owner approves the final text. The system sends it to the right groups, collects electronic signatures, chases anyone who hasn't signed and gives HR a list of gaps. NIST's control for access agreements, such as acceptable use and conflict-of-interest agreements, works the same way: people sign before they get access, re-sign when the agreement is updated, and may sign electronically unless company policy says otherwise.

Keep the exact text, who signed and when. Kept as a personnel record, it falls under the EEOC's one-year minimum. Our guide to document automation covers retention schedules.

When does Form I-9 need reverification?

When an employee's work authorization, or in most cases the document showing it, expires. USCIS guidance on Supplement B says to reverify "by the earlier date" when Sections 1 and 2 show different dates, and suggests giving employees "at least 90 days advance warning."

A system can read the dates on file, start reminders 90 days out and escalate if nothing comes back. Two limits matter:

  • Remind only where reverification applies. USCIS lists cases where employers should not reverify, including U.S. citizens and noncitizen nationals, permanent residents who presented a Permanent Resident Card, and List B identity documents.
  • People handle the documents. The employee presents an unexpired List A or List C document, and a trained person examines it, then signs and dates Supplement B.

The USCIS handbook says to keep the supplement with the original Form I-9, so it follows the form's retention period.

What about review cycles and document requests?

Review cycles run on dates. The system opens self-reviews, reminds managers, collects ratings and sends approved pay or promotion decisions into the job and pay change workflow, with the same approvals. Reviews are personnel records, so the EEOC's one-year minimum applies.

Document requests are the quiet volume: employment verification letters, copies of pay statements, a signed policy. The system checks who is asking, fills the standard letter and logs what went out. Anything unusual, such as a request from an outside party, goes to HR first.

Who approves what, and what goes in the record?

Four rules keep HR workflow automation safe:

  1. People decide. Pay, terminations, leave designation and I-9 document checks stay with named roles.
  2. Nobody approves their own request, and approval limits live in the rules, not in someone's memory.
  3. Every step is logged: who asked, who approved, what changed and when.
  4. Deletion waits for a person. The system flags records past their keep-until date, and a person approves each removal. If a charge of discrimination is filed, the EEOC rule says to keep the relevant personnel records "until final disposition," so the system needs a hold that stops deletion.

Managers see their own team's requests; medical files stay with HR.

How does Raileon build HR workflow automation?

We map how each HR process really runs, automate the steps that follow rules, and run it for you as part of our business process automation work. We build around the HR system, payroll and IT tools you already run.

It starts with a free 20-minute call with the founder, then a written proposal: what each automation does, what needs approval and what it costs. Every action is logged, so you can check what ran, and when something fails, your Raileon team fixes it.

Builds are priced by scope. Monthly care starts from $1,999 a month and covers monitoring, fixes, updates and a monthly review. Cancel any time. Your plan runs to the end of the month you've paid for. No exit fee.

Every client's data is kept separate, encrypted in transit and at rest, and backed up daily. We never use your data to train AI models, unless you hire us to train your own model.

FAQ

What is HR workflow automation?

It is software that runs the routine steps of HR requests and changes, such as offboarding, pay changes, leave and policy sign-offs. It sends each request to the right approver, updates the connected systems and records every step.

Which automated HR workflows should we build first?

Start with offboarding, because an account left open after someone leaves is a security risk, then job and pay changes and leave requests. Policy sign-offs, I-9 reminders, reviews and document requests can follow.

How long do we have to keep HR records?

Federal rules set at least one year for most personnel records, three years for payroll and FMLA records, and for Form I-9 the later of three years after hire or one year after the last day. States can require longer, so agree a retention schedule with employment counsel.

Can a system remove a leaver's access on its own?

Yes, once HR confirms the last day. It can disable each account on the list and log it, while IT checks for anything the list missed.

Which HR request waits longest at your company?

Bring the HR process that takes the most emails today. On a free 20-minute call, we'll tell you what to automate first and what should stay with your HR team.

Book a free 20-minute call

About the author

Konstantin, Founder & CEO of Raileon

Konstantin

Founder & CEO, Raileon

Konstantin has spent more than 15 years in systems, processes, automation and development. He has built businesses from scratch, from early crypto to tech ventures that led to acquisitions, and founded Raileon to build the software and automation he wished he'd had.

  • 15+ years in IT, automation and development
  • Founder & CEO of Raileon
  • Based in North Miami, Florida

Let's put your operations on rails

Book a 20-minute call with our team in Miami, Florida, and we'll show you exactly what Raileon would automate for your business.

Book a 20-minute call

No commitment. No credit card. Just a conversation.