New employee onboarding checklist for a service business

Before the first day: prepare the basics

Choose one person to coordinate the start. In a two-person company, that may be you. In a larger crew, it might be a supervisor with office support. Put these items on a shared checklist that the responsible people can see:

• Arrival plan: start date, meeting time, exact location, parking, and the person meeting the employee.
• Role expectations: normal duties, work schedule, reporting line, and which tasks require approval or supervision.
• Administration: arrange the required hiring, payroll, employment-eligibility, and state reporting steps with the person responsible. Track their actual deadlines separately from this operational checklist.
• Equipment: prepare the tools, clothing, protective equipment, keys, and devices appropriate to the role. Record what is issued and who checks its condition.
• Accounts: create individual invitations with appropriate access, and confirm the employee has a workable way to use them.
• Training plan: reserve the trainer’s time and choose suitable first assignments. Do not assume training will happen between an already full day of jobs.

The University of Missouri’s new-employee information separates account and registration steps from broader orientation and role-related training. A small business can borrow that organizational idea without copying university-specific procedures or deadlines.

Keep identity documents, banking details, and other sensitive employee records in an appropriately secured HR or payroll process—not an ordinary job note or crew group chat. This guide is not a complete hiring-compliance checklist; confirm applicable requirements with your payroll provider or qualified HR adviser.

First-day checklist: make the work understandable

1. Introduce the people and the plan

Explain who assigns work, who handles customer changes, and whom to contact if the trainer is unavailable. Show the day’s plan and leave room for questions. Explain how schedule changes and absence notices should be communicated.

2. Show one complete job from start to finish

Walk through how to find the address, read the scope, check access instructions, record time, document completion, and flag a problem. Show what good completion looks like using an approved example. Explain who can approve extra work or a price change.

A customer asking for “one more thing” should not leave a new employee guessing. Give them a simple response: “Let me check with [responsible person] so we can confirm the scope and get it handled correctly.”

3. Cover the hazards before the task

Arrange task-specific instruction from someone qualified to provide it before assigning equipment or hazardous work. Cover the relevant protective equipment, emergency contacts, and how to report an injury, hazard, or near miss.

OSHA’s education and training guidance emphasizes understandable language, workplace-specific hazards, and opportunities to ask questions. It also calls for additional training when new tasks or changes introduce hazards. A signature on a general checklist is not a substitute for that instruction.

4. Check the setup on the employee’s device

Have the employee sign in, open a sample assignment, find the instructions, and submit a test update. Confirm the account has only appropriate access; our employee-permissions guide covers that setup. Use sample records so training does not send messages or bills to actual customers.

Explain your timekeeping process, including how to report a missed entry. Plan and record training time through the applicable payroll process; do not casually treat required training as off-the-clock work. The U.S. Department of Labor’s training-time guidance explains the conditions for excluding training from hours worked under the FLSA.

5. End with a short check-in

Ask: “What was unclear? What could you not find? Who would you contact if tomorrow’s job changed?” Record any missing access, equipment, or training and assign a person to resolve it before the next affected task.

First-week checklist: practice, observe, and follow up

Use this as a proposed sequence, not a deadline for becoming qualified. Some work takes longer to learn, and required training or authorization may determine what someone can do.

1. Observe: the trainer demonstrates an appropriate task and explains the important decisions.
2. Practice with supervision: the employee performs the task while the trainer checks understanding and provides feedback.
3. Practice an exception: use a safe scenario such as missing access instructions, a customer requesting extra work, or an app that will not load. Ask what they would do and whom they would contact.
4. Review the record: check the job notes, time entry, checklist, and any required completion photos together.
5. Decide the next step: record which tasks are ready for independent work, which still need supervision, and when the next review will happen.

Separate “shown once,” “practiced,” and “verified by the trainer.” An employee completing an onboarding form does not mean every skill has been demonstrated.

Make a familiar person available for everyday questions. Missouri State’s Bear Connection program pairs new staff with experienced employees for support while leaving position-specific training with supervisors and departments. The relevant idea for a small team is a clear support contact—not adding a university-sized program.

At the end of the week, ask the employee which instructions they had to hunt for. Correct the checklist or instructions instead of relying on the next trainer to remember to explain the same gap.

Copy this onboarding record

Use a document, spreadsheet, or operating-system record. For each task, add an owner, due date, status, and evidence of completion.

For “account tested,” evidence might be a completed sample job update. For a practical skill, it might be the qualified trainer’s observed demonstration record. Keep confidential personnel matters out of a checklist shared with the whole crew.

Example: a new window-cleaning crew member

Suppose a fictional window-cleaning business hires Sam. Before the first shift, the owner sends the meeting location, prepares the equipment, and assigns Jordan as trainer. Sam’s account shows only the jobs needed for the role.

On day one, Jordan explains the job scope and provides the appropriate safety instruction before supervised work. Sam practices finding the property notes and adding a completion update. When a customer asks about extra interior cleaning, Sam knows to contact the office rather than promise unapproved work.

During the week, Jordan notices Sam can complete the job notes but still needs help with the photo requirements. The record says “photo workflow needs another supervised practice,” not simply “onboarding complete.” The next practice has an owner and date.

This is an illustrative workflow, not a claimed customer result. It shows how a checklist can make a specific training gap visible without pretending a new employee learns every task at the same speed.

Where an operating system helps—and where it does not

Pebble Creek Media grew out of building systems around our own lawn and property-care business. We care about the handoff between the office, owner, and employee: can the person doing the work find what they need and get help when something changes?

A custom business operating system can be scoped to assign onboarding steps, show relevant instructions, track issued equipment, and remind a supervisor about unfinished training. The actual workflow should match your roles and services; every business does not need the same modules.

Software cannot replace a capable trainer, required qualifications, or a manager’s judgment about readiness. If a shared checklist works for your team, start there. If access requests, equipment records, and training follow-ups keep getting lost between tools, tell us where the handoff breaks down.