It is most useful for remote roles where login, hardware, or approvals can stop work before it starts.
How to use it
- Score each area below.
- Flag any hard stop.
- Add the points.
- Use the role-specific threshold before confirming the start date.
Score the hard stops first
Score four things first: access, equipment, ownership, and written process. Those are the gates that keep Day 1 from turning into Day 3 cleanup.
Use this weighting when the question is simply whether the person can start:
| Readiness area | Weight | Full credit looks like | Day 1 blocker |
|---|---|---|---|
| Access and identity | 25 | All core accounts active, MFA set, permissions assigned | Login blocked or approval missing |
| Hardware and shipping | 20 | Device and required gear are in hand before Day 1 | Laptop still in transit |
| Manager plan and ownership | 15 | First-week goals, check-ins, and owner are named | No calendar hold or unclear owner |
| Documentation and training | 15 | Role SOPs and starter guide are in one place | New hire has to hunt for instructions |
| Communication norms | 10 | Channels, response windows, and escalation path are clear | No agreed way to ask for help |
| Payroll, compliance, and policy signoff | 15 | Forms and approvals are complete | Start date is held by paperwork |
These weights are not random. Access and equipment are the hard stops. Docs and communication matter after the person can log in and get assigned work. A polished welcome packet does nothing if the new hire cannot open email.
If the role needs protected systems, raise the weight on access and compliance. If the role is mostly internal and asynchronous, manager ownership and documentation matter more than meeting volume.
What a full score actually means
The score only works if everyone uses the same bar. A 90 means little if one manager counts “docs drafted” as complete and another counts only signed-off docs.
| Readiness area | Full credit looks like | What blocks Day 1 |
|---|---|---|
| Access and identity | Core tools open on the first try | SSO, MFA, or approval still pending |
| Hardware and shipping | Required equipment arrives before the start date | Device is still shipping |
| Manager plan | First-week meetings and goals are already on the calendar | No one owns the first week |
| Documentation and training | The new hire gets one clear starter path | Instructions are scattered |
| Communication norms | Help channels and response expectations are written down | Nobody knows where to ask for help |
| Payroll, compliance, and policy | Forms and acknowledgments are finished | Paperwork is still open |
This table shows the main failure pattern: teams overrate documentation and undercount access. A tidy onboarding folder does not make up for a blocked login. In remote work, the first failure is usually mechanical, not motivational.
When to raise the bar
The same score means different things in different roles.
- Regulated or client-data roles: one unresolved access or compliance item is enough to delay Day 1, even if the rest of the score looks strong.
- Internal, low-risk roles: a score in the 70s can work if the first week is mostly asynchronous and the manager has room for check-ins.
- First remote hire in a small team: be stricter. Early remote teams have less slack, fewer backup owners, and more setup dependency on one person.
- Teams with one onboarding owner: watch concentration risk. If HR, IT, and the manager all rely on the same person, one vacation or sick day can turn a “ready” plan into a scramble.
Use this rule of thumb:
- No device or no login means no Day 1.
- Two or more soft gaps mean the first week needs a lighter workload.
- Any compliance blocker means the start is not ready.
Suggested pass lines by team setup
| Team situation | Score target | Readiness call | What to do |
|---|---|---|---|
| First remote hire | 80+ | Start only when hard stops are clear | Confirm access, device delivery, and manager schedule |
| Small team with one owner | 75+ | Start only if backup owners exist | Split HR, IT, and manager tasks before Day 1 |
| Multi-time-zone team | 70+ | Start only with written handoff and overlap | Replace live-only training with clear async docs |
| Regulated role | 90+ | Start only with zero unresolved blockers | Treat compliance and permissions as gatekeepers |
| Mature remote org | 70+ | Start if the process is repeatable | Watch for role changes that break the template |
The higher the access risk, the less forgiving the score should be. A customer-facing role with blocked tools does not get a pass because the checklist looks close. A back-office role with strong docs and one delayed form can still start if the manager has room to absorb the loose end.
Keep the checklist current
A readiness checklist gets stale fast when tools, permissions, or role expectations change. The hidden cost is not software spend. It is the coordination reset after each missed step.
Keep one owner and one backup for the checklist. Shared ownership without a single editor leads to version drift, and version drift causes small misses that compound: a missing form, a wrong start date, or a delayed account request.
Update the checklist after:
- A new HR system or IT login flow
- A policy change that adds a required acknowledgment
- A role change that adds software access
- A manager change that changes the first-week schedule
- Any onboarding miss that forced a second round of setup
The real maintenance burden is manager time, HR follow-up, and IT rework. If the team cannot update the checklist in the same place it is used, it will lag behind the process it is supposed to control.
What to confirm before Day 1
These are the items that keep the score honest. If any of them is blocked, the total needs a manual downgrade.
- Device shipping window: the laptop arrives before Day 1.
- Time-zone overlap: first-week meetings fit shared hours.
- SSO and MFA: core tools open on the first try.
- Payroll and forms: start date and tax paperwork line up.
- Security and compliance: required approvals are complete.
One blocked item here matters more than three polished soft items. If the laptop is still shipping or the account is not provisioned, the score is too generous.
Quick checklist
Use this before Day 1, not after the welcome message goes out.
- Manager has blocked time on the calendar for Day 1 and Week 1.
- HR, IT, and the hiring manager agree on one start date.
- Laptop, charger, and any required peripherals are confirmed in hand.
- Email, chat, SSO, MFA, and role-specific apps are active.
- The new hire gets one written first-week plan, not a pile of links.
- A backup contact exists for access problems.
- Payroll, tax, and policy steps are complete.
- Meeting load leaves room for actual work.
If three or more items are incomplete, the team is not ready. If access is complete but docs are weak, the first week still works only when the manager has enough time to fill the gaps live. The goal is not a perfect checklist. The goal is a start that does not waste the new hire’s first day.
Final take
Use the score to find friction, not to dress up a weak setup. The best remote onboarding plans are boring in the right way: devices arrive early, logins work on the first attempt, the manager owns the first week, and the new hire has one clear path into work.
Start only when the hard stops are gone. Everything else is a cleanup task, not a Day 1 blocker.
Frequently Asked Questions
What score counts as ready?
80 to 100 is ready for most remote roles. Below 80 needs a fix list. Below 60 is a delay signal unless the role has very low access needs and a fully async first week.
What matters most in the score?
Access and hardware matter most because they block work immediately. A strong onboarding doc does not help if the employee cannot log in or does not have a device on Day 1.
Does a strong score mean onboarding is done?
No. A strong score only means the setup is intact. The first week still depends on manager time, clear tasks, and fast responses when something breaks.
How often should the checklist be updated?
Update it after each role change, tool change, policy change, or onboarding miss. Review it again before each new hire template is reused.
Should regulated roles use the same threshold?
No. Regulated roles need a stricter threshold and zero unresolved access or paperwork. Compliance and permissions override the total score.