Employee onboarding checklist

Checklist

First day, first week — who does what, by when, and whether it actually happened.

What this deliberately cannot hold

There is no field for a Social Security number, a tax form, bank details, a date of birth, immigration or I-9 data, medical or disability information, benefits enrollment, or a background-check result. Not hidden, not optional — absent. This product is a set of operational tools that runs on your own device, and holding a personnel file would be a promise it is not built to keep.

The tool says so at the notes box, where somebody with a folder in their hand is about to type, rather than only in a line at the bottom of the page.

People, not names

Everybody here is a contact with a stable internal id, and the checklist belongs to that id. Two people with the same name are two people. Renaming somebody moves nothing. That is the same rule this product applies to buildings, equipment, customers and contracts, and it is the reason it can be trusted with a second person’s record at all.

The rest of the first week

What you require somebody to be trained in belongs on the training matrix. The hard hat, the laptop and the keys go on the PPE & equipment issue register, which knows what is owed back. And when somebody leaves, the offboarding checklist is the same list run backwards.

An operational checklist. It is not an HRIS and not a personnel file: it holds no Social Security number, tax form, bank detail, date of birth, immigration or I-9 data, medical or disability information, benefits enrollment or background-check result — there is no field for any of them. CompliMaint gives no employment-law advice and makes no compliance determination. Everything runs on your device.

Questions people ask

What should an onboarding checklist include?
The operational things that have to happen and that somebody forgets: orientation booked, policies acknowledged, training assigned, equipment issued, systems and building access set up, introductions made, and whatever the first week specifically needs. Each with an owner and a date, because a checklist where everything belongs to 'HR' is a checklist nobody does.
Can I store an employee's personal information here?
No, and there is deliberately nowhere to put it. There is no field for a Social Security number, a tax form, bank details, a date of birth, immigration or I-9 data, medical or disability information, benefits enrollment or a background check. This is an operational checklist, not a personnel file, and the tool says so at the notes box rather than four screens down.
How does it handle two people with the same name?
As two people. Everybody is a contact with a stable internal id, and a checklist is attached to that id rather than to a name — so two people called Chris Nguyen have two separate checklists, and renaming either of them changes nothing about whose tasks are whose.
What happens to a task that does not apply to somebody?
Mark it Not applicable. It is a finished state and it is deliberately not the same as Done: a vehicle handover for somebody who will never drive is settled business, but counting it as completed would inflate every figure the checklist shows.