Employee onboarding procedure: the steps that need a record

Most documents titled employee onboarding procedure are timelines. Before the first day, do these seven things. On the first day, do these five. In the first week, these nine. Every item is written in the imperative, which means every item has the same owner, which is nobody.

That is why the procedure works when the person who wrote it runs it, and stops working the week they are on leave. A timeline describes a sequence. A procedure has to describe a sequence plus three things a timeline leaves out: who acts at each step, what triggers them, and what is left behind afterwards to prove the step happened. The third of those is the one that turns a procedure from a nice document into something a company can rely on, and it is almost always missing.

A checklist says what. A procedure says who, when, and what remains

The difference is not pedantry, it is the difference between a document that can be handed over and one that cannot.

A checklist item reads: set up the accounts. A procedure step reads: on receipt of the signed offer, the systems administrator creates the accounts for the role template named in the offer, and records the date and the account list against the starter. The second version names the actor, names the trigger, and names the evidence. It can be audited, handed to somebody new, and checked without asking anybody.

Three questions applied to every line of an existing onboarding document will rewrite it in an afternoon.

Who does this, by role rather than by name. Names go out of date and roles do not, and a procedure that says Sarah sends the welcome pack is unusable the moment Sarah changes job.

What starts it. Offer accepted, start date confirmed, first day, end of first week, end of probation. A step with no trigger gets done when somebody remembers, which is to say it gets done late for the starters who arrive during a busy month.

What is left behind. A date, a signed document, an entry in a list, a confirmation message. If nothing is left behind, the step cannot be verified, and steps that cannot be verified are the ones that get skipped first under pressure.

The handoffs are the procedure

Onboarding is not one process. It is five short processes belonging to different people, joined by four handoffs, and the delay is nearly always in the joins rather than in the work.

Each row can only start when the row above has produced its output. That is why the procedure should be written as a chain of outputs rather than as a calendar. A calendar says accounts are created two days before the start date. A chain says accounts are created on confirmation of the role template, which may be three weeks before the start date or, for a late hire, the day before.

The two handoffs that break most often are the first and the last. Recruiting to people operations breaks because the start date is confirmed in a conversation and never written anywhere the next person looks. People operations to payroll breaks because the withholding and bank details are returnable items, and returnable items depend on somebody outside the company acting. A procedure that does not distinguish steps the company controls from steps that wait on a person will always look on schedule right up to the point where payroll is at risk.

Which steps have to leave a record

Not every step needs evidence. Three categories do, and they are worth marking on the document itself so nobody has to judge case by case.

The first is anything with a legal deadline. The employee completes their part of Form I-9 no later than their first day of employment, and the employer completes the review part within three business days of the date employment begins. New and rehired employees have to be reported to the state where they work within 20 days of hire under federal law, and some states require it sooner. The eligibility form then has to be kept for three years after the date of hire or one year after employment ends, whichever is later. Dates set by rule belong in the procedure as offsets, calculated rather than typed.

The second is anything that grants or removes access. The account list created at onboarding is the list used at offboarding, and if it was never written down, the departure is a guessing exercise. Record what was granted, by whom, and on what date, and keep it with the starter rather than in a ticket that will be closed and archived.

The third is anything the employee is later expected to have agreed to. Handbook acknowledgement, acceptable use, confidentiality, expense policy. The value of these is entirely in the record: an acknowledgement that cannot be produced is the same as one that never happened. Keep the date and the version of the document that was acknowledged, because policies get revised and an acknowledgement of an unspecified version answers nothing.

One habit is worth adding. Keep the material a government officer may ask for reachable on its own. USCIS recommends keeping the eligibility verification form separate from personnel records, and the forms have to be producible within three business days of a request, which is hard to do if they are interleaved with performance notes and salary history.

Writing it so it survives the author leaving

Four properties decide whether a procedure document is still usable in two years.

Roles, not names, throughout. One exception is worth allowing: a named escalation contact, reviewed at the same time as the rest of the document.

Offsets, not dates. Two working days before start, first day, third business day, end of first week. A procedure written in offsets works for the next hire without editing, and the offsets can be turned into calculated due dates.

One source. The most common failure is not a bad procedure but three copies of a good one, in a shared document, a wiki page and a spreadsheet, drifting apart. Pick the copy that people actually open and make the others point at it.

A review date on the page. Onboarding touches payroll, access control and legal obligations, all of which change. A document with a review date gets reviewed. A document with only a creation date gets trusted for years after it stopped being accurate.

What changes when nobody is in a building

Distributed hiring does not add steps so much as it removes the assumption behind several of them, which was that the starter and their documents would be in the same room as somebody.

Document examination is the clearest example. In general the employer or their authorized representative must review the employee's documentation in the employee's physical presence. Employers who participate in E-Verify may be eligible to use an alternative procedure and examine the documents remotely, which is worth confirming against the current rules before relying on it, since eligibility depends on participation rather than on preference.

Equipment changes from an issue step into a shipping step, which means it needs a tracking number, a delivery confirmation and an asset record, and it needs to start earlier than it does for an office start. First week access becomes more consequential, because a new person who cannot reach a system cannot walk to a desk and ask. And the informal parts of onboarding, the ones a physical office provides for free, become explicit steps with owners: an introduction schedule, a named buddy, a check in at the end of the first week.

None of that changes the shape of the procedure. It changes which steps have long lead times, and lead times are what the trigger column exists to manage.

Measuring whether the procedure works

Four numbers are enough, and each one points at a different failure.

Share of starters whose returnable documents were complete before the first day. This is the number that predicts payroll problems, and it is usually far lower than the coordinator expects.

Days from start date to full access. A procedure can look perfect while a new engineer spends four days waiting for one permission that nobody owns.

Days from start to the first correct payroll run. Late by one cycle is the most damaging single onboarding failure for the person experiencing it.

Time the coordinator spends chasing. Not a precise figure, just an honest estimate. When it is most of a day per starter, the problem is not the procedure document, it is that the outstanding items are not visible in one place.

The lower rows are where the procedure stops being a document problem and becomes a tracking problem. What helps there is not a bigger document but a place where each outstanding item has an owner, a due date and a state, so that the procedure describes the work and something else shows what is outstanding. A form tool with response management covers the returnable half of onboarding this way, and the situations these tools are used for tell you more about fit than a feature list does. The parts to check are whether a submission can be assigned, whether it can be sent back with a question, and whether access can be limited per person. The stages, owners and history on each response are where to look.

What to change first

Take the existing onboarding document and add three columns to every line: owner by role, trigger, and what it leaves behind. The lines that cannot be filled in are the steps that will fail next, and they are almost always the handoffs between departments. Once the document is honest, move the returnable items somewhere each one carries its own owner and due date, whether that is Halict or any tool built on the same idea.

Q1. What is the difference between an onboarding checklist and an onboarding procedure?

A checklist lists what has to happen. A procedure adds who acts, what triggers them, and what evidence the step leaves behind. The evidence is the part that makes the procedure usable by somebody who did not write it, because a step that leaves no record cannot be verified later.

Q2. What should an employee onboarding procedure include?

Five stages with an owner named by role, a trigger, and an output for each: closing out the offer, opening the records, preparing access and equipment, running the first week, and closing payroll and statutory reporting. Write the timings as offsets from the start date rather than as fixed dates so the document works for the next hire without editing.

Q3. Which onboarding steps legally have to be documented?

In the United States, the federal employment eligibility form has to be completed by the employee no later than the first day of employment and reviewed by the employer within three business days of the date employment begins, then retained for three years after the date of hire or one year after employment ends, whichever is later. New and rehired employees must also be reported to the state within 20 days of hire, and some states require it sooner.

Q4. How long should onboarding take?

The question is easier to answer per step than overall. Returnable documents should be complete before the first day, access should be working on the first day, and the first payroll run should be correct. Programs that run for months are about integration and training, which is a separate matter from the steps that carry deadlines.

Q5. How does remote hiring change the procedure?

It lengthens lead times rather than adding steps. Equipment becomes a shipment with a tracking number and an asset record, access problems can no longer be solved by walking to a desk, and the informal introductions an office provides have to become explicit steps with owners. Document examination is normally done in the employee's physical presence, and employers participating in E-Verify may be eligible for an alternative procedure that allows remote examination.

Q6. How do you tell whether an onboarding procedure is working?

Four numbers. The share of starters whose documents were complete before the first day, the days from start to full system access, the days to the first correct payroll run, and an honest estimate of how long the coordinator spends chasing. The last one is the signal that the outstanding items need to live somewhere visible rather than in a mailbox.