Building a Skills Checklist for the First 90 Days

Why this matters

Without a checklist, "is this new hire ready" becomes a gut feeling that different mentors answer differently, and a new hire's actual readiness depends more on who trained them than on what they actually learned. A written skills checklist turns onboarding from an informal, inconsistent apprenticeship into a repeatable process: everyone knows what "ready" means, the new hire knows exactly what they are working toward, and you have an honest, documented answer when someone asks whether this person is ready for solo work.

Step 1: List the tasks, not the traits

Start by writing down the actual, observable tasks the role requires, not vague qualities like "good communication" or "attention to detail." A trait cannot be checked off; a task can. For a field role, this looks like a list of specific job types, diagnostic routines, safety procedures, and customer-facing moments. For an office role, it looks like specific call types, software workflows, and schedule judgment calls. See related: Onboarding for Office and Support Roles, Not Just Field Techs for how this differs by role.

Pull this list from two sources: what a fully competent person in this role actually does in a normal week, and what has gone wrong in the past when someone was not yet ready for a specific task. If a callback last year traced back to someone not knowing how to properly test a repair before leaving, "verifies the fix before leaving the site" belongs on the list explicitly, not buried inside a general "completes the job" line.

Step 2: Group tasks into three tiers by risk and complexity

Not every task belongs at the same point in the ramp. Sort the full task list into three rough tiers:

• Tier 1, safe to solo almost immediately: low-risk, high-frequency tasks where a mistake is easily caught and cheap to fix. Basic tool handling, routine data entry, simple customer confirmations.
• Tier 2, needs demonstrated competence under supervision first: the bulk of the actual job. Common diagnostic routines, standard job types, typical customer interactions. This is where most of the checklist lives.
• Tier 3, needs the most repetitions and the highest bar before solo: anything touching real safety hazards, anything expensive to get wrong, anything involving a difficult judgment call with no clear right answer. Gas work, electrical work near water, a customer dispute involving money, an unusual diagnostic that does not match the common patterns.

This tiering is what lets the ramp move at different speeds for different tasks instead of one blanket "ready" or "not ready" for the whole role. A new hire can be fully solo-capable on tier 1 by week two while still shadowing on tier 3 in week ten, and that is the correct outcome, not a sign of slow progress.

Step 3: Define what "checked off" actually means for each item

A checklist item is only useful if everyone agrees on what counts as demonstrated. Vague criteria ("understands X") produce inconsistent sign-offs between mentors. For each item, write a specific, observable bar:

• Watched: the new hire observed a mentor perform this at least once and can explain the reasoning back.
• Assisted: the new hire performed this with a mentor present and correcting in real time.
• Performed independently, verified: the new hire performed this alone while a mentor observed without intervening, and the outcome was correct.
• Signed off: a mentor is willing to state, specifically, that this person can be trusted to do this task completely unsupervised.

Require the last stage before anything moves to solo status. "I've seen them do it a few times" is not the same bar as "I would sign my name to this."

Step 4: Set rough timing targets, but let competence override the calendar

Give each tier a rough expected timeframe, so both the new hire and the shop have a shared sense of pace. A common shape: tier 1 largely solo by the end of week two or three, tier 2 substantially solo by the halfway point, tier 3 approaching solo readiness by day ninety with some items still shadowed depending on frequency of exposure.

Treat these timeframes as planning targets, not hard deadlines. A new hire who reaches tier 2 competence in three weeks instead of six should not be held back purely because the calendar says week six. See related: The New Hire Is Ready Early: Promote the Timeline (Decision Tree). Equally, a new hire who needs longer on tier 3 items, especially safety-related ones, should get that time without it being treated as a failure. See related: The Cost of Rushing a New Hire Into Solo Work.

Step 5: Run a checkpoint conversation at fixed intervals

Do not let the checklist sit passively in a drawer. Schedule a short, structured conversation at regular intervals, commonly at the two-week, thirty-day, sixty-day, and ninety-day marks, where the mentor and new hire review the checklist together:

1. Go through the checklist and update the status of each item honestly.
2. Ask the new hire what has felt confusing or under-explained, not just what they have completed. See related: What a New Hire's First 90 Days Should Teach You About Your Own Systems for why this question matters beyond just tracking the individual.
3. Name what the next two to four weeks will focus on, specifically, not just "keep learning."
4. Document the conversation briefly so there is a record if a concern needs to escalate later.

Step 6: Use the completed checklist to make the actual solo decision

By day ninety, the checklist gives you something better than a gut call: an itemized, honest picture of exactly what this person can be trusted to do alone, what they can do with light backup, and what still needs direct supervision. That picture is the input to a real go or no-go conversation, and it is also the fair, defensible record if a serious concern has surfaced along the way. See related: A 90-Day Review Surfaces a Serious Concern (Decision Tree).

Step 7: Revisit and refine the checklist itself over time

Every cohort of new hires will expose gaps in the checklist: a task nobody thought to include, a criterion that turned out to be too loose or too strict, a tier that a task belonged in but was miscategorized. Treat the checklist as a living document, not a one-time project, and update it after every onboarding cycle based on what you actually observed.

References

• U.S. Department of Labor, apprenticeship competency-based training standards
• Society for Human Resource Management (SHRM), structured onboarding and 30-60-90 day plans
• See related: The Mentor Relationship That Makes Onboarding Stick
• See related: The Cost of Rushing a New Hire Into Solo Work