The short answer: most new hires decide in their first week whether they are staying. Have their access, gear and paperwork ready before day one, cover safety and expectations first, and make sure they finish a real day of work they can point at. Being useful on day one is what makes someone come back on day two.
His first day started in a parking lot. Nobody had told him which site to go to, so he went to the shop, where nobody was. Two phone calls later he found the crew, forty minutes away, already an hour into the pour. No one knew his name. The foreman pointed at a shovel. At lunch, everyone sat in their own trucks. He worked hard all day, drove home, and told his girlfriend he would give it two weeks.
Nothing about that day was hostile. It was just nothing: no plan, no introduction, no signal that anyone had thought about his arrival for even five minutes. And it is how most small crews onboard, because the owner is slammed, hiring took months, and the quiet assumption is that a good hand will figure it out.
They will figure it out. What you do not get to choose is what they figure out. In the first week, a new hire is answering one question with everything they see: "Is this place organized, and do they care?" You spent months finding this person. The first week decides whether you get to keep them, and it is cheap to run well.
Before day one: the ten-minute setup
Most first-day chaos is solvable the afternoon before, in about ten minutes:
- Send the logistics message. Where to be, what time, who to ask for, what to bring, what is provided, when lunch happens, when and how they get paid. Half of new-job anxiety is these seven facts; put them in writing so nobody has to ask.
- Tell your crew. Name, start date, background, what they will be doing. A crew that is expecting someone greets them; a crew that is surprised sizes them up. If one of your guys wondered whether the new hire is a threat to his hours, answer that before day one, not during it.
- Have their stuff ready. PPE in their size, a locker or a shelf, timesheet or app access set up. Handing someone their own kit on arrival is a tiny thing that says: we knew you were coming; you have a place here.
If your crew runs on an app, do the invite the day before too. In Zeus you add them to the team and hand over their login from your own phone, by email or text, and they sign in on theirs. Tomorrow's schedule, the site address and the job details are there before they have met anyone. Day one starts with them walking onto the right site at the right time knowing what the job is, which is a very different first impression than the parking lot. You pick their access level when you add them, so giving them the app on day one does not mean giving them everything; a Field Tech captures job data and photos and cannot send or delete documents.
The drive cost calculator shows what the drive to a job costs you, per job and across a year.
Day one: safety, expectations, and one good day of work
Resist the urge to make day one a firehose. It has three jobs only.
Safety, done like you mean it. Walk the site together: hazards, exclusion zones, where the first-aid kit lives, who is first-aid trained, what to do if something happens, and the two or three non-negotiable rules of your crew (nobody under a suspended load, glasses on the saw, whatever yours are). Ten serious minutes. This is legally your responsibility almost everywhere, but it is also your first credibility test: crews that shortcut the safety talk are telling the new hire what else they shortcut.
Expectations, said out loud. Every crew has an invisible rulebook: start time means boots-on-at-7 or rolling-in-at-7, phones are fine at break or fine never, how tools get put away, how mistakes get reported. New hires break invisible rules constantly and get silently judged for it, which is corrosive and entirely your fault. Say the rules. It takes five minutes and it is the difference between a culture and a hazing.
"Here's how we run. Boots on at 7, not arriving at 7. If you break something or cut something wrong, tell me the same hour, and I promise you it's fine; what's not fine is me finding it Thursday. Ask anything twice, no one cares. And if something looks unsafe, you stop, even if it's me doing it."
One real task, finished. Give them actual work with a visible result on day one: not sweeping alone in a corner, and not the hardest thing on the job either. Something they can complete and quietly look at during cleanup. People decide how they feel about a job by how they feel driving home, and "I built that today" is the feeling you want in the truck.
Then eat lunch with them. It sounds trivial. It is the single most reported difference between "I knew I'd stay" and "I felt like a spare part."
Pair them with your best habits, not your fastest worker
The default move is to put the new hire with your most productive person. It is usually a mistake. Your fastest worker is often fast because of twenty years of shortcuts, some of which you would rather not propagate, and speed rarely comes bundled with patience for questions.
Pair them instead with the person whose habits you would clone: the methodical one who measures, sets up properly, keeps a clean area, and does not mind explaining why. For the first weeks, the new hire is not learning tasks so much as absorbing a standard: what this crew considers finished, tidy, straight, safe. They will imprint on whoever they stand next to. Pick that person on purpose.
Give the mentor a real brief, not just proximity: "You've got Marcus this week. Teach him our setup routine, let him run the easy cuts by Wednesday, and tell me Friday what he is ready for." Being chosen to train someone is a quiet promotion; say it that way, and it improves your mentor too, because nothing tightens your own habits like explaining them.
The first week: widen the work, watch the patterns
Across days two through five, rotate them through the crew's ordinary work: material handling, site setup and teardown, the basic tool operations of your trade, riding along on a supplier run. The goal is not mastery but a map: by Friday they should understand how a normal job flows and where they currently fit in it.
While they learn your crew, you are learning them. A paid first week tells you things no interview can, if you watch the right signals.
Green flags, week one: asks questions before acting, then remembers the answers. Owns small mistakes without being caught first. Notices what needs doing next (the person who grabs the broom unasked at 3:55 is telling you who they are). Treats the apprentice and the laborer the same as they treat you. Shows up a little early, consistently.
Early red flags, honestly weighted: slowness is not one; week-one speed means almost nothing, and pushing new people to be fast is how fingers get lost. The real ones: safety corners cut after being told once. Blaming (the tape, the lumber, the other guy) as a first reflex. Phone in hand every time your back turns. Big talk about how their old crew did everything better. A different excuse each day. None of these improve with tenure; they compound.
One structural tip: end each of the first five days with two minutes of feedback, specific and mostly positive. "Your cuts were clean today. Tomorrow I want you watching how Sam sequences the room, that's your next thing." New hires in silence assume the worst, and the good ones, the ones with options, are the quickest to leave over it.
The 30-day check-in, and what it is actually for
Put it in the calendar on day one, and tell them it is coming: "Thirty days in, we sit down for coffee and half an hour." Announcing it changes the first month; both of you are collecting things to say.
The check-in is two conversations in one, and both directions matter:
- Yours to them. What they are doing well, said concretely. What to work on next, limited to two things at most. What comes after this: the next skill, the next responsibility, and if things are going well, the wage or role step you see ahead. People stay in jobs where someone has said, out loud, what the future looks like.
- Theirs to you. Ask real questions and let the silences sit: "What's confusing that everyone assumes you know? What does your last outfit do better than us? Anything about how we run feel off to you?" A thirty-day-old employee sees your operation with fresh eyes you will never get back, and their answers routinely surface things your veterans stopped noticing years ago.
If it is not working out, the check-in is where you say that too, plainly and kindly, while it is still a one-month experiment for both sides rather than a two-year resentment. Letting a bad fit drift because the conversation is awkward costs you the person you should have hired instead.
The 30-day meeting is also where onboarding hands over to just managing well: a fair wage, real training, visible respect, and a schedule they can plan a life around. Keeping people is its own subject. But be clear that retention does not begin at the exit interview or the counteroffer; it begins in the parking lot on the first morning, with whether anyone knew their name.
Where Zeus fits
A new hire spends the first week deciding whether this place is organized, and that verdict is built out of what they can see without asking. They get their own seat and their own login, and you set what it reaches before they arrive. Tomorrow's job, the site address and the scope are on their phone the night before, so the morning starts at the right gate. Through week one you widen it: the checklist for the work they are doing, the photos going onto the job, the day log. They clock in and out against the job they are standing on, so the 30-day conversation opens with their real hours on real work rather than two people remembering. And when you pair them with your best hand, the planner shows you both on the same job instead of accidentally on two. That whole side of the app is laid out on the crew and supply pages, and the features page has the rest. Quoting, invoicing and the record for every address cost nothing to start and do not run out, and the pricing page shows what the paid sizes add. Download it the afternoon before your next hire starts.
He gave it two weeks because his first day was nothing: no plan, no introduction, no sign that anyone had thought about his arrival for five minutes. The afternoon before costs ten minutes, and most of those ten minutes is just deciding what he needs to be able to see. Then he sees it, and the parking lot never happens.
Frequently asked questions
I run a two-person operation. Does any of this apply?
More, not less: on a two-person crew, you are the logistics message, the mentor, the safety officer and the culture, and the new hire is half your workforce. The pieces shrink but keep their shape: the day-before message, the said-out-loud rules, one finished task on day one, lunch together, feedback daily, the 30-day coffee. It costs you maybe an hour of talking across a month for the person you will rely on most.
How long until a new hire should be productive?
Contributing usefully within days; paying for themselves, typically somewhere between a few weeks and a few months depending on the trade and their starting point; genuinely running work solo, months to a year. Decide privately what your budget is and judge them against that curve, not against the veteran they are standing next to. The costly error is not slow progress but no progress: someone in week six still needing the same instruction as day three.
Should the first week be a formal probation period?
A probationary period (typically 30 to 90 days, and check the employment rules for your province or state, because notice and termination rules vary) is standard and sensible, and you should be upfront about it. But treat it as a mutual trial, and say so: "First month, we're both deciding." Framing it as something you hold over them poisons the week you are trying to use to win them.
What paperwork has to happen on day one?
At minimum: their legal details for payroll and tax forms, emergency contact, any workers' compensation registration your jurisdiction requires, and documented safety orientation, which in most places you are required to provide and wise to record. Have it ready in one folder so it takes twenty minutes, not a scattered week. It is also the first process of yours they ever see; a shambles here undermines everything the tidy trailer said.
ZEUS