How to Automate Onboarding Paperwork and Employee Files

TL;DR: An onboarding document workflow is a standing instruction that runs when a new hire document arrives: read it, check whether it is complete and signed, file it under that employee, and hold anything destined for a personnel file until a person approves. In The Drive AI, an Email Attachment source watches the HR mailbox, Ask AI About the File decides whether the form is finished, and Send a Message tells you when a packet is still short one document.

You hire someone on a Tuesday. By Friday you have an offer letter in your sent mail, a tax form in a reply, a benefits confirmation from the broker, a handbook acknowledgment photographed on a phone, and an I-9 in a drawer. One of those is missing and you will not find out which until somebody asks in eight months.

If you are the HR generalist or office manager at a company of 10 to 200 people, onboarding is one of five jobs you own. The filing is not hard, it is constant, and it fails quietly. The packet is never wrong in an obvious way. It is incomplete on one page, for one person.

An onboarding document workflow is a standing instruction that runs when a new hire document arrives: read it, check whether it is complete, file it under the right employee, and pause for a person before anything lands in a personnel file.

What does a complete employee file contain?

A complete employee file is usually several files. The main personnel file holds the employment record: offer letter, signed agreement, job description, handbook acknowledgment, reviews, promotions, discipline, separation. Other categories are conventionally kept elsewhere:

• Employment eligibility verification. I-9 forms in the United States are conventionally stored apart from personnel files, in one collection covering all employees, so they can be produced without exposing the rest of the record.
• Medical and benefits information, including accommodation and leave paperwork, is generally kept apart from personnel records.

Payroll and tax records live wherever payroll lives. The boundaries, the retention periods, and who may see what vary by jurisdiction and employer size. This is not legal advice; confirm your own obligations with counsel or your labour authority.

An employee folder structure that survives your fiftieth hire

Good employee file organization is boring on purpose: one folder per employee, named the same way every time, with the same subfolders inside.

HR/Employees/Reyes, Marisol/
  Employment/      offer letter, agreement, acknowledgments
  Performance/     reviews, goals, development plans
  Separation/      resignation, final documents
HR/Eligibility/    eligibility forms, all employees, one place
HR/Medical/        benefits, leave, accommodation

Two decisions do most of the work. Pick one name format and never deviate, because "Marisol Reyes", "M. Reyes", and "Reyes_Marisol" are three people as far as search is concerned. And decide the separate locations before the first document arrives; retrofitting a split across 60 folders is a lost weekend.

Employee document retention is an obligation, not a preference

Retention has two halves and most small teams do only one. Keep records as long as you are required to, and no longer, because a record you no longer need is still a record you can be asked to produce.

Periods differ by record type, by country, by state or province, and sometimes by employer size. They also start counting from different events: date created, date of last action, or date of separation. Do not copy a schedule from a blog post, including this one; confirm each period for yourself.

What automation can do here is smaller than vendors imply. It finds records past the date you set and puts them in front of a human, which is why the retention workflow below ends at an approval step.

Why does onboarding stall on one missing form?

Onboarding rarely stalls on a hard problem. It stalls because one form never came back, and the person waiting for it is the same person who has to notice it did not.

You send six documents. Four come back in week one. One comes back unsigned on page 3. One never comes back. Your spreadsheet says "sent", which is true and useless, and the gap stays until an audit surfaces it.

Two fixes are needed. The first is a collection mechanism that tracks what is outstanding rather than what was sent, which is what file requests are for: you request the documents, people upload without an account, and what is missing stays missing in plain view. The second is a check on arrival.

How does an onboarding document workflow work?

You describe it once in plain English and the steps appear on a canvas, where each can be edited. Every step carries a cost badge: free for decisions made from details already known, ai for steps that read the file, human for steps that pause until someone decides, external for steps that contact an outside service.

• Email Attachment (free) is the source. It watches a connected Gmail or Outlook account and runs once per attachment, scoped by sender, including a domain such as @northwind.com, and by "Subject contains". The email itself is never saved. File Uploaded (free) covers documents you drop in a folder.
• Ask AI About the File (ai) reads the document and picks a path. You write what to decide, for example "Is this form complete and signed?", and you author the branches. They are not limited to yes and no: one node can have branches named offer letter, eligibility, and benefits.
• Read Details from File (ai) pulls out named values such as employee name and document type. Each field you name is available to later steps, in a filename, a folder path, an approval question, or a message.
• Move (ai) and Rename (ai) take plain English, for example "to the employee folder under HR/Employees, then Employment". They apply to files that already have a storage home.
• Save a Copy (external when it targets a connected account) is what email attachments need, because they have no storage home until you give them one.
• Ask a Person to Approve (human) pauses the workflow. You write the question, choose who decides (Admins, Specific people, Everyone), choose Always ask or Only when unsure, and set a wait of 24 hours, 3 days, or 1 week. Three exits: approved, rejected, expired.
• Send a Message (external) goes to Slack or an email address when a human has to chase something.

Files already in Google Drive, OneDrive, SharePoint, or Dropbox are renamed and moved in place. Nothing is imported unless the workflow includes Save a Copy.

Four onboarding workflows, written the way you would say them

Each is one sentence typed into the builder.

When an attachment arrives at hr@northwind.com, decide whether the form is complete and signed. If anything is missing or unsigned, save a copy to HR/Onboarding/Needs Follow-Up and email hr@northwind.com with the subject "Incomplete: {{trigger.file.name}}" from {{trigger.sender}}. If it is complete, carry on to filing.

When an attachment arrives at hr@northwind.com, decide whether it is an employment eligibility form, a benefits document, or a general HR document. If it is an eligibility form, read the employee name out of it, rename it with that name, and save a copy to HR/Eligibility, not the employee folder.

When a file is uploaded to HR/Inbox, decide whether it is a signed offer letter. If it is, read the employee name and start date, rename it with the employee name and "signed offer letter", and ask an admin "OK to file this under Employment?" before moving it to HR/Employees. Wait up to 3 days.

On the first of every month, go through every file in HR/Employees/Former, every file every run. If a file is older than 2190 days, ask an admin "Retention period reached. OK to trash this?" and trash it only if they approve. If they reject or it expires, move it to HR/Retention/Hold.

Set the day count from your own schedule. The scheduled source has a setting called "Each run goes through", and a retention sweep needs "Every file, every run" so age is re-evaluated on files already filed. That setting also reorganizes a backlog of employee folders you inherited.

Manual filing, an HRIS, a shared drive, and Workflows

To be fair to the HRIS: it owns the employee record, payroll, benefits elections, and status changes, and Workflows does none of that. Keep it. What an HRIS will not usually do is take a PDF out of your mailbox, work out that it is a half-signed acknowledgment for Marisol Reyes, and file it while telling you what is missing. More in HR document management.

What will it not do?

• There is no e-signature step inside a workflow. Signing happens in your signing tool. A workflow can check whether what came back is signed, but cannot send it out for signature.
• It is not an HRIS. No employee record, no payroll, no org chart, no benefits administration.
• It is not a compliance certification. It does not know your jurisdiction or your retention schedule. You configure that.
• ai steps can be wrong. A model reading a scanned form can misjudge a signature block. Personnel records deserve an Ask a Person to Approve step in front of them, and destructive branches always do.
• Approvals expire. After 24 hours, 3 days, or 1 week the file takes the Expired exit. Connect that exit to a holding folder and a message.
• Send a Message reaches Slack or an email address only. Never Microsoft Teams.
• Connecting a mailbox or a drive needs a plan. Workflows on files uploaded to The Drive AI work on every plan. Connecting Gmail, Outlook, a drive, Slack, or Teams needs the Max plan on a personal workspace, or any Team plan.

Setting it up

1. Decide the structure first. One name format for employee folders, and separate locations for eligibility, medical, and payroll records.
2. Connect the HR mailbox. Each member connects their own account. The Gmail and Outlook posts cover scoping the source.
3. Write one sentence. Start with the completeness check and the follow-up folder: one source, one decision, one destination, one message.
4. Add Ask a Person to Approve before anything reaches a personnel file. Set Always ask while you learn it; the approval step explains what changes under Only when unsure.
5. Run it on real documents and watch the activity feed. Every run replays on the canvas exactly as it happened, and can be retried from the step that failed.
6. Add branches one at a time. Eligibility, then benefits, then the retention sweep. For the full vocabulary, read what every workflow step does.

Frequently Asked Questions

What is an onboarding document workflow?

An onboarding document workflow handles new hire paperwork as it arrives rather than in a weekly catch up. It watches where documents land, usually the HR mailbox or a folder, reads each one, decides what it is and whether it is complete, files it under the right employee, and pauses for a person before anything enters a personnel file.

Can a workflow tell whether a new hire form is signed?

Within limits, yes. Ask AI About the File opens the document and picks a branch based on the question you wrote, for example "Is this form complete and signed?". You author the answers it may give. The step can occasionally be wrong, particularly on phone photographs of paper, so a signed offer letter should still pass an approval step before it is filed.

How do I keep certain records out of the personnel file automatically?

Give them their own branch and their own destination. One Ask AI About the File step sorts an arriving document into named categories such as eligibility, benefits, and general HR, and each branch ends at a different folder. Eligibility forms and medical information are conventionally kept apart from general personnel records. Boundaries vary by jurisdiction, so confirm yours and build the branches to match.

Does this replace our HRIS?

No. An HRIS owns the employee record, payroll, benefits elections, time off, and status changes, and none of that is here. Workflows handles the documents around the record: collecting them from a mailbox, reading them, checking completeness, naming them, filing them into an employee folder structure, and holding them for approval. Small HR teams usually run both.

Can a workflow delete records when the retention period ends?

It can find them and propose it. A scheduled workflow set to "Every file, every run" checks age on every file in a folder each month and routes anything past your threshold to an approval step. Move to Trash is a soft delete and stays recoverable. That branch should end at Ask a Person to Approve, because a date alone does not justify destroying a record.

Start with one form

Pick the form that goes missing most often and build the workflow for that one: an Email Attachment source on the HR mailbox, one Ask AI About the File step asking whether it is complete, a follow-up folder, and an email to yourself. Fifteen minutes, and the next packet stops stalling. You can start free and see how it fits together on the Workflows page.