Your First 30 Days as a New Crew Lead: A Field-Tested Playbook (With AI Prompts)
You got the call. You're running the crew now.
It feels good for about ten minutes. Then it hits you. Yesterday you were one of the guys. Today you decide who's on the shovel, you answer when the PM calls, and your name is on the report if something goes wrong.
Nobody hands you a manual. Most of us learned by messing up: doing all the work ourselves, dodging the hard talk, or turning into "the boss" overnight. Here's a simple plan for your first 30 days, week by week, with a few AI prompts to handle the prep so you can focus on people.
Your job just changed
As a tradesman, you were judged on your own work. As a lead, you're judged on the crew's work. Did everybody stay safe? Did the crew hit the plan? Did the PM have to babysit?
So most of your day is now planning, talking to the PM and the crew, clearing things that slow the crew down, watching safety, and teaching. You'll still turn wrenches. But if you're on the tools all day and nobody's planning, the crew has no leader. That's the trap most new leads fall into.
Week 1: Listen and don't change much
The biggest mistake in week one is showing up with a list of changes. The crew is watching to see if the title went to your head. Earn their trust first.
Take ten minutes with each person, at the truck or over lunch. Ask what's working, what's slowing them down, and what they want to get better at. Then ask your PM what a great week looks like to them and what they need from you. Write it all down, but don't fix anything yet.
I just became crew lead on a construction/trades crew of [number] people, some of whom were my peers last week.
Help me prepare for short, informal one-on-one conversations with each of them.
Give me: a 2-sentence casual opener that acknowledges the change without making it awkward, 5 open-ended questions (no corporate language), and 3 things I should avoid saying.
Keep it natural, like how people actually talk on a jobsite.
At the end of the week, you can paste your notes in (use "Tech 1, Tech 2," not names) and ask AI to group what you heard into themes. That makes it easier to see what keeps coming up.
Week 2: Set expectations and fix one thing
Now you know the crew and what the PM wants. Time to tell everyone how you'll run things.
Hold a quick huddle, ten minutes max. Tell them most things aren't changing. Give them your two or three must-dos. Safety is always one. Others might be "tell me early when something's wrong" or "clean up before we leave." Tell them how you'll keep them in the loop, and that you want to hear it when they disagree.
Then fix one small thing from your week one notes. Maybe it's the tool trailer, where material gets staged, or confusion about start time. Pick something people complained about. It shows you listened.
Start a morning plan too: who's doing what, where, and the safety focus for the day. Same time every day.
Write talking points for a 10-minute huddle where I, the new crew lead, set expectations with my crew.
Include: a short opener, what isn't changing, my non-negotiables [list yours], how we'll communicate day to day, and an invite for pushback.
Tone: confident but not bossy, like a respected foreman. Bullet points I can glance at, not a speech.
Week 3: Handle the first hard talk
It usually shows up around week three. Somebody's late again, skips a safety step, or tests you to see if you'll say anything. How you handle that first one sets the tone for the whole job.
Do it early, in private, and talk about what they did, not who they are. Say what you saw: "You were 20 minutes late Tuesday and Thursday." Say what it caused: "We started the lift short a man, and everybody else picked up the slack." Then ask what's going on, and really listen, because sometimes there's a real reason. Finish with what you need: "Be here by start time, or text me before 6 if something comes up." Afterward, notice when they get it right.
Safety is different. If somebody's doing something unsafe, stop the work right then and talk later. Follow your company's stop-work and reporting process every time, even if it's your buddy.
I'm a new crew lead and need to have a conversation with a crew member about [behavior, e.g., "repeatedly skipping the pre-task hazard review"]. They were my peer until recently.
1) Write a short, respectful script using: what I saw, the impact, an open question, the clear expectation, and next steps.
2) Then role-play as the crew member. Push back the way a real person might (defensive, joking it off, or "you used to do it too"), and let me practice responding. Stop after 4 exchanges and give me feedback on how I did.
That role-play part is one of the best ways to use AI as a leader, and hardly anyone does it. Practicing in your truck beats winging it.
Week 4: Get organized and show the PM
By now you've earned some trust. Week four is about habits that keep the crew running and let the PM see you've got it handled.
Send your daily report the same way, at the same time, every day. Our daily report guide shows you how. Every Friday, send the PM a short update: what got done, what went wrong and what you did, next week's plan, and what you need. Most PMs never get that from their leads, so it stands out.
Pick one person and teach them a task you used to do. It frees you up and makes the crew stronger.
Turn my notes into a short end-of-week update email for my project manager.
Sections: Progress This Week, Issues & What I Did About Them, Plan for Next Week, What I Need From You.
Under 175 words, bullet points, no fluff. Don't add numbers, dates, or names I didn't give you. Flag anything that looks like a schedule risk at the top.
Notes: [paste]
Five traps to watch for
Doing all the work yourself. It feels productive, but the crew has no leader. Plan first, then help.
Trying to stay one of the guys. Be friendly, but don't skip hard talks to stay liked.
Acting like a dictator. A title doesn't earn respect. Being fair and steady does.
Hiding problems from the PM. Bad news doesn't get better with time. Tell them early, with a plan.
Letting safety slide for the schedule. One injury outweighs a hundred on-time days. Your crew will copy whatever you let slide.
What to paste into AI, and what not to
Your own notes, general task descriptions, and fake names like "Tech 1" are fine. Never paste client or site names, drawings, pricing, or anything personal about your crew, like health, discipline, or home life. And only use the AI tools your company approves.
The bottom line
Your first 30 days aren't about proving you know everything. They're about showing the crew and the PM that you listen, keep people safe, and follow through. Do that, and the next promotion talk starts on its own.
The Tech-to-Lead Playbook is coming soon: a 30-60-90 day plan, 75 prompts, scripts for the 10 hardest conversations, and ready-to-use templates.
And join The Tailgate, our free weekly newsletter for techs moving up. Join here