New Employee Onboarding Checklist for Small Businesses: The First Thirty Days

A new employee arrives on Monday. Nobody knows where they will sit. Their laptop is not ready. The manager is in meetings until the afternoon. By Wednesday they are quietly wondering whether they made the right choice. Small businesses often lose good people in the first month, and usually because of a first week that told them nobody was expecting them. An employee onboarding checklist costs almost nothing and changes that.

Why onboarding matters more in a small team

• Every person is a large share of the team. One slow start is felt by everyone.
• There is no training department. If the manager does not plan it, it does not happen.
• Knowledge lives in people's heads. Without a plan, the new hire learns whatever the nearest colleague happens to mention.
• First impressions stick. The first week tells a person how the company works.

Before day one

Most of what makes a first day go well happens earlier.

• Send a welcome message a few days ahead: start time, address or link, who to ask for, what to bring, what to wear.
• Prepare the paperwork. Employment agreement, forms for tax and social security registration, bank details form.
• Prepare the tools. Laptop or device, email, chat, accounts for the systems they will use, with access appropriate to the role.
• Prepare the workspace or the remote setup.
• Name a buddy. A colleague to answer everyday questions.
• Tell the team who is joining and what they will do.
• Write a first-week schedule. Even a simple one.

Day one

The goal of the first day is that the person feels expected and knows what the next few days hold.

• A proper welcome from the manager, and an introduction to each team member.
• A short conversation about the company: what it sells, to whom, and what matters here.
• A tour of the workplace or, for remote staff, the main tools and channels.
• Paperwork completed.
• Tools working: logins tested, not just handed over.
• The role explained: responsibilities, who they report to, what good work looks like.
• The practical rules: hours, breaks, leave, how to report absence, when and how pay is made.
• A first small task they can finish, so the day ends with something done.
• Lunch with the team or the buddy.

Avoid filling the day with documents to read alone.

The first week

• Tools and systems. Hands-on practice with each one, using real examples.
• The core process. Walk through the main work from start to finish. For a sales role, a real enquiry from first message to payment. For operations, a real order from receipt to delivery.
• Shadowing. Time spent watching an experienced colleague, then doing the same task while that colleague watches.
• Key people. Short conversations with people in other functions they will work with.
• Products and customers. What the company sells, common customer questions, the usual complaints.
• Standards. How messages are written, how files are named, how tasks are tracked.
• End-of-week check-in. Fifteen minutes: what is clear, what is not, what they need.

Days eight to thirty

Now the person takes over real work in stages.

• Week two. Simple tasks done independently, reviewed afterwards.
• Week three. A wider range of tasks, with review of a sample.
• Week four. The core job done without supervision, with help available.

Set three or four specific goals for the first thirty days. For example:

• Handles incoming enquiries alone, using the saved replies.
• Creates a quotation and an invoice without errors.
• Knows the top ten products and their prices.
• Has updated the pipeline every day for two weeks.

Clear goals let both sides know whether things are on track.

Hold a short weekly check-in throughout. Ask what is going well, what is confusing and what is getting in the way.

The thirty-day review

At the end of the first month, sit down for half an hour.

• Go through the goals one by one.
• Give specific feedback: what they do well and what needs to improve.
• Ask for their feedback on the onboarding itself. New people see what long-serving staff no longer notice.
• Agree the goals for the next sixty days.
• Confirm in writing.

If something is not working, say so now and agree how to fix it. A problem raised at thirty days can usually be solved. The same problem raised at ninety days tends to end badly.

What to have written down

Onboarding becomes far easier once a few documents exist:

• A one-page company overview.
• A description for each role.
• Procedures for the main tasks.
• A price list and product notes.
• Saved replies to common customer questions.
• The rules: hours, leave, expenses, conduct.
• A list of tools and how to get access.

You do not need all of them at once. Each time you explain something to a new hire, write it down. After three hires the handbook exists.

Access and security

• Give access by role, and only what the job needs.
• Use individual accounts, never a shared login.
• Explain how customer data must be handled.
• Record what was issued: devices, accounts, keys.

That record becomes the offboarding list when the person eventually leaves.

Common mistakes

• Nothing ready on day one.
• Information overload. Everything explained in a single day and forgotten by the next.
• No one responsible. Everyone assumes someone else is looking after the newcomer.
• Sink or swim. Real work with no guidance, then blame for the mistakes.
• No feedback until something goes wrong.
• Forgetting remote staff. They need more structure, not less.

The checklist in brief

Before: welcome message, paperwork, tools, workspace, buddy, team informed, week-one schedule.

Day one: welcome, introductions, company overview, paperwork, working tools, role and rules, first task.

Week one: systems practice, core process, shadowing, key people, products and customers, check-in.

Days eight to thirty: growing independence, thirty-day goals, weekly check-ins.

Day thirty: review, two-way feedback, next goals.

Polynusa keeps employee records, attendance, leave and payroll in one workspace with access by role, so a new hire's account, schedule and pay details are set up in one place. See the pricing page.

Summary

Prepare before the first day. Make day one welcoming and practical. Use the first week for tools, process and people, and the first month for a staged handover of real work with clear goals. Review at thirty days, and write down what you explain so the next hire starts faster.

FAQ

How long should onboarding last in a small business?

Plan for thirty days of structured onboarding, with a lighter check at sixty and ninety days. The first day covers the essentials, the first week covers the tools and the people, and the first month builds toward the new hire doing the core job without supervision.

Who should be responsible for onboarding when there is no HR team?

The direct manager owns it. A buddy, a colleague who does similar work, handles the daily questions. The owner or a senior person should spend some time with every new hire in the first week to explain what the business stands for.

What documents should be ready on the first day?

The employment agreement, a description of the role and its goals, company rules, the pay date and how pay is calculated, working hours and leave rules, and the forms needed for tax and social security registration. Check what your local labour regulations require.