A new hire starts on Monday. The checklist for onboarding is open, and it has thirty two rows. Twenty of them are things the company does to itself: order the laptop, create the accounts, book the first week, tell the team, assign a buddy. Twelve of them are things that have to come back from a person: a signed offer letter, tax withholding details, bank details, proof of eligibility to work, emergency contacts, a signed acknowledgement that the handbook was read.
By Wednesday the twenty are finished. The twelve are the reason payroll is at risk, the reason a laptop is sitting in a cupboard waiting on an asset form, and the reason somebody is about to send a fourth reminder email that starts with an apology. Every published onboarding checklist covers the twenty. Almost none of them treat the twelve as a different kind of work, which is why the checklist keeps passing inspection while the process keeps failing.
The checklist is two lists wearing one name
An internal task has one actor and two states. Somebody orders the laptop or they do not. The deadline is negotiable, the consequence of slipping it is mild, and nothing outside the building cares when it happened.
A returnable item is not like that at all. It has a counterparty who does not report to the person chasing it. Its deadline is often set by a rule rather than by a manager. What comes back can be wrong, in which case the row goes backwards. And after it arrives it has a retention tail, sometimes measured in years, that no internal task has.
Putting both kinds of row in one column of checkboxes hides the twelve rows that can actually cause damage among the twenty that cannot. Worse, the checkbox itself is the wrong instrument. A tick says a task is finished. It does not say who is waiting, since when, whether the last message was sent by the recruiter or the manager, or whether the file that arrived was a photograph of a screen at an angle that nobody can read.
The first fix is free and takes ten minutes. Split the list in two and give the returnable half its own columns. One list stays a checklist, because that is what it is. The other becomes a small register with an owner, a due date and a state on every row. The language changes with it: the second list is not about what has been done, it is about what is outstanding and who it is outstanding from.
The deadlines that are not yours to move
Some rows on the returnable list carry dates that a manager cannot push. Employers in the United States work to the following, and the pattern holds elsewhere even where the specific rules differ.
| What | What starts the clock | The deadline |
|---|---|---|
| Employee part of the federal employment eligibility form | The job offer, accepted | Completed no later than the first day of employment |
| Employer review of that same form | The date employment begins | Within three business days of that date |
| New hire report to the state | Date of hire | Within 20 days under federal law, sooner in some states |
| Producing the eligibility forms for inspection | The request from a government officer | Within 3 business days of the request |
| Keeping the eligibility form on file | The end of employment | Three years after the date of hire, or one year after employment ends, whichever is later |
Those are not house rules. The employee must complete the first part of Form I-9 no later than their first day of employment, and the employer has to complete the review part within three business days of the date employment begins, with the exception that a hire of less than three business days has to be reviewed on the first day itself. Federal law also requires employers to report basic information on new and rehired employees within 20 days of hire to the state where they work, and some states require it sooner. The federal withholding form collects the data elements that report needs, including the date of hire, which is why a late withholding form delays two obligations rather than one.
Retention runs in the other direction. The form has to be kept for three years after the date of hire or one year after employment ends, whichever is later. A checklist that gets ticked and then deleted at the end of the quarter is a compliance problem dressed as tidiness.
The practical consequence for the returnable list is that due dates should be calculated from the start date rather than typed in by hand. Anything typed by hand drifts, and the rows that drift are the ones with rules attached.
What a returnable row needs that a checkbox cannot hold
Five fields carry almost all of the value.
One named owner on the company side. Not a team, not a shared mailbox. If the row is owed by the new hire and owned by nobody, it will sit. A shared mailbox is where accountability goes to be diluted: three people see the same unread message and each assumes another has it.
The person it is owed by. Obvious with one starter, not obvious with six. Cohorts are where a checklist quietly stops working, because a single tick has to stand for six separate answers.
A due date derived from the start date. Two days before the start, first day, third business day, end of the first week. Written as an offset rather than a date, the same template works for the next hire without editing.
A state from a short defined list. Not requested, requested, received, returned as unusable, accepted, filed. Six states rather than two, and the two that matter most are received and accepted. A photograph of a document that cannot be read has been received. It has not been accepted. Most onboarding backlogs live in exactly that gap, invisible because the tick went in when the attachment arrived.
The artifact itself, or a link to it. Not in a cell, not in a thread. One place per person, reachable by the next person who needs it.
Two fields are worth leaving out. Free text notes fill with fragments that mean nothing three weeks later, and a percentage complete column invites somebody to report progress upward instead of chasing the two rows that are stuck.
Three places the returnable list leaks
The leaks are structural, so they do not close by adding reminders.
Attachments in a personal inbox. The signed form exists, but only one person can see it, and only they know what was already chased. When they take a week off during a cohort start, the state of every row becomes unknowable without asking them. A forwarded copy makes a second version rather than a shared one.
The shared folder. Files arrive with the names the sender chose, sit next to files from a hire who joined in March, and carry no state at all. A folder can tell you a document exists. It cannot tell you that the document was rejected for being illegible, or that the same document is still missing for the other four starters.
The spreadsheet. Better than both, and still short in three ways. A cell has no owner, so two people can chase the same person within the same minute and the later edit silently wins. The reply lives elsewhere, so what was actually said to the new hire is not in the tracker. And read access is close to all or nothing: a manager who needs to see the two starters on their own team gets the bank details and salary context of everyone else on the sheet.
Keep the record narrow, then keep it long enough
Onboarding is the moment a company collects more sensitive material about a person than at any other point in the relationship. Identity documents, bank details, home address, dependants, sometimes health information. The volume arrives in a week and then sits for years.
Two habits make the difference. The first is separation. USCIS recommends keeping the eligibility verification form separate from personnel records, precisely so that an inspection request can be answered without handing over everything else in the file. The same logic applies more broadly: the documents a government officer may ask for should be reachable on their own, and the material nobody outside the company will ever ask for should not travel with them.
The second is an expiry date on everything that is not a record. Copies of identity documents for a candidate who accepted and then withdrew, duplicate scans, a photograph somebody sent because the first one failed. None of that has a retention requirement and all of it has a risk. Decide the period once, write it next to the state definitions, and put a date in the calendar. Business records more broadly have their own floors: tax records generally run to the period of limitations, and employment tax records should be kept for at least four years after the date the tax becomes due or is paid, whichever is later. Archive rather than delete, and keep the decision in writing so the next person does not have to guess.
Shapes that hold, by how many people start at once
The trigger for changing the shape is not the size of the company. It is the number of people who have to act on the same list.
| Situation | What holds | What breaks first |
|---|---|---|
| One start a quarter, one coordinator | A document pack by email and a folder per person | Nothing, until the coordinator is away |
| One start a month, two people involved | A spreadsheet with owner, due date and state | Knowing what was chased, when, and by whom |
| A cohort starting on the same day | Per person rows, not per task rows | The single tick that has to stand for six answers |
| Managers who should see only their own starters | Not a shared sheet or folder | Confidentiality, immediately |
| Documents arriving through a form every week | A tool where each submission carries its own owner and state | Manual copying, and the errors it creates |
The middle rows are where most teams sit, and the choice there is usually framed too dramatically. The alternative to a spreadsheet is not a human resources platform with an implementation project attached. It is any arrangement where the submission itself carries a state, an owner and the history of what was said, so the record and the chasing happen in the same place. A form builder with response management does this, and so do several other categories of tool. Reading how other teams route incoming submissions is a faster way to judge fit than comparing feature lists, and the detail that matters is narrow: whether a response can be assigned, whether it can be rejected and sent back, and whether a manager can be given sight of some rows and not others. The access levels and per response history are the parts to check first.
What to change first
Split the checklist into internal tasks and returnable items, then put three columns on the returnable half: owner, due date as an offset from the start date, and a state that distinguishes received from accepted. Do that before buying anything, because it will tell you within one cohort whether a spreadsheet is still enough. When it is not, move the returnable half somewhere each document carries its own owner and state, whether that is Halict or any tool built on the same idea.
Q1. What should be on a checklist for onboarding before the first day?
Two separate lists. Internal tasks such as equipment, accounts and calendar invitations, and returnable items such as the signed offer, withholding details, bank details, eligibility documents and emergency contacts. The returnable list needs a named owner and a due date on every row, because those rows depend on somebody outside the team acting.
Q2. When does new hire paperwork actually have to be finished?
In the United States, the employee completes their part of the federal employment eligibility form no later than the first day of employment, and the employer completes the review part within three business days of the date employment begins. Federal law also requires new and rehired employees to be reported to the state within 20 days of hire, and some states require it sooner. Those dates are set by rule, not by the hiring manager.
Q3. How long do onboarding documents have to be kept?
The federal employment eligibility form must be kept for three years after the date of hire or one year after employment ends, whichever is later. Employment tax records should be kept for at least four years after the tax becomes due or is paid, whichever is later. Material that is not a record, such as duplicate scans of identity documents, needs an expiry date decided in advance rather than being kept by default.
Q4. Is it a problem to collect onboarding documents by email?
It works for one starter and fails quietly after that. The attachment sits in one person's mailbox, so nobody else can see what arrived or what was already chased, and there is no way to mark a document as received but unusable. The gap between received and accepted is where most delays sit.
Q5. How do you track paperwork for several people starting on the same day?
Make the rows per person rather than per task. A checklist organized by document type forces one tick to stand for six separate answers, so a missing item for one starter disappears into a row that looks half done. Filtering by person and by state is what makes a cohort manageable.
Q6. Where should copies of identity documents be stored?
Somewhere separate from the general personnel file, with access limited to the people who need it. USCIS recommends keeping the eligibility verification form apart from personnel records so an inspection request can be answered on its own, and the forms have to be producible within three business days of a request. Files that only one person can reach fail that test as surely as files everyone can reach fail the privacy one.