Hire, Onboard and Grow Crew Leaders

A construction company org chart is a drawing of who is responsible for what: the roles, who reports to whom, and the name in each box. In a growing contracting business it has one more job. Drawn with real names, it shows where the owner’s name appears three, four or five times, and that is where the next hire belongs. Many owners hire the role that feels most urgent on a bad day. The chart shows the role the business is missing.

This lesson shows the org chart of a typical 10 to 50 person contractor, how to draw yours honestly, how to decide which box to fill first, and how to write a role scorecard so the hire does the job you need rather than the job the title suggests.

Titles vary by trade and region. The roles don’t. A contractor with two to five crews usually needs these boxes filled, whether by one person each or by one person wearing several hats:

In a company of ten, the owner may be the estimator, the operations lead and half the office. That is normal at that size. The problem starts when the company reaches twenty people and the owner still holds those same boxes, now at twice the volume.

Take the table above and write the name of the person who actually does each thing today, not who is supposed to. Rules:

1. One box per outcome, even if the same person fills several. The owner’s name can appear six times. That is the point of the exercise.
2. Split a box when two people share it without a clear line. “Scheduling: Dana and Mike” usually means neither owns it and both fix it when it breaks.
3. Write “nobody” where it’s true. Collections, warranty calls and permit tracking often have no owner. Those boxes are hidden work the owner does at night.
4. Count the owner’s boxes. Then mark each one: keeps (needs the owner’s judgment, such as pricing policy or hiring) or could transfer (repeatable work someone else could do with a written standard).

If you did the first course, your interruption log already shows which boxes generate the most calls. That is the same information from the other direction.

The role you need is the one that frees the most owner hours and has the clearest standard to hand over. It is rarely the role that’s loudest.

Compare the candidate roles on four questions:

Worked example, with made-up numbers. An owner of a 14-person remodeling company feels they need a second estimator: they’re booking site visits two weeks out and losing some. A week’s time log looks like this:

The estimator box is the biggest, but it is the one the owner is best at and the one with a written standard already, because the sales course covered it. The scheduling, customer-update, materials and invoicing boxes together take 22 hours a week, are mostly repeatable, and have no owner but the owner. An office coordinator who takes those four boxes gives back roughly 22 hours. If the owner puts half of that into site visits, the estimate backlog shrinks without a second estimator, and the new hire costs less than one.

That is the general pattern: hire scheduling and customer coordination support before a second estimator or a project manager, unless you’ve already done it. The office coordinator box is the one many owners fill too late.

The titles get mixed up in job posts, and the mix-up costs hires. A quick way to tell them apart:

If you write “office manager” but need the coordinator’s work, you’ll interview people who expect to manage staff and processes you don’t have yet. If you write “project manager” but need a crew lead, you’ll pay for a role your jobs can’t fill.

A role scorecard is one page that says what the role is for and how you’ll know it’s working. Write it before the job post, because the job post is a summary of it, and the interview questions in the next lesson come from it.

Two things the scorecard forces you to do before you hire:

• Write the standards. If “scheduling rules” don’t exist on paper, the new coordinator will schedule the way they did at their last job, and you’ll be correcting it for months. The job workflow course’s office-to-field handoff is a good first standard to write.
• Decide the authority. A coordinator who must ask before every reschedule changes nothing about your day. The limits can be narrow at first and widen as trust grows, but they have to exist.

Cost the role the way you cost a job: wage plus burden, against the hours it returns. The labor burden calculator shows how to get from a wage to the real hourly cost. Then ask what the freed owner hours produce. In the example above, 22 hours a week going back into estimates and jobs is a different business from 22 hours spent on the phone and the schedule. If the honest answer is that the freed hours would not turn into estimates, jobs or collections, the role isn’t the constraint yet, and the chart should be re-read.

What this lesson does not cover: employment classification, pay rules and hiring law differ by state and trade. Check them with your accountant or an employment attorney before you post the job.

1. Draw the org chart with real names. Count the owner’s boxes and mark each one keeps or could transfer.
2. Log one week of owner hours against those boxes.
3. Pick the box, or set of boxes, with the most repeatable hours and the clearest standard.
4. Write the role scorecard for it. Write the missing standards it depends on.

What to review:

• Outcomes in the chart with no owner, or with two
• Tasks the new role should take over that are still landing on the owner a month in
• Owner hours per week in the boxes marked could transfer

Next lesson: hire against the scorecard: where to find people, what to ask, and how to compare candidates fairly.

Hiring construction workers goes wrong in predictable ways: a job post that describes a title instead of the work, a first interview that’s a friendly chat, a decision made on gut feel, and a new hire who finds out in week two that the job isn’t what they pictured. The fix is the same one that works for scheduling and estimating. Write down what the job is, ask every candidate the same questions, and compare the answers against the role instead of against each other.

This lesson covers where to find people, what to put in the job post, a hiring process with a deadline on each step, interview questions for crew members, crew leads and office roles with what a good answer sounds like, and a scoring sheet that keeps the decision honest. It starts from the role scorecard in the previous lesson. If you haven’t written one, do that first; everything here comes from it.

No single source is enough. Run several at once, and track which one each hire came from, the same way you track lead sources:

For seasonal hiring with a calendar, see the spring staffing playbook.

The job post is the scorecard, shortened. The people you want read for three things first: what the work is, what it pays, and what the days look like. Put those in the first five lines.

Include, in this order:

1. The trade and the work. “Lead carpenter for residential remodels: framing, trim, cabinet installs, running a two-person crew.” Not “construction professional wanted.”
2. The pay range, hourly or salary, and how reviews work. Candidates look for it first, and some states require a range in the post; check yours.
3. The schedule. Start time, typical hours, overtime expectations, travel radius, Saturdays or not.
4. Requirements that are actually required. Driver’s license if they drive company vehicles; certifications your trade or customers demand; the physical work involved. Leave out requirements you’d waive for a good candidate.
5. What they get. The tools and vehicle policy, benefits if any, training, a path to crew lead if that’s real.
6. How to apply, and what happens next. “Text or call [number]. We reply within one working day and interview the same week.”

Leave out: a long company history, “fast-paced environment,” “must be a team player,” and anything you can’t deliver.

Good candidates are talking to other contractors the same week. A process that takes three weeks loses them. Give each step an owner and a time limit, as you do for leads:

The phone screen checks the deal-breakers so nobody’s time is wasted: can they do the hours and the travel, do they have the license or certificate the job needs, is the pay range workable, when could they start. Fifteen minutes.

The skills check. For field roles, see them work before you decide. Where you can, a short paid working session on a real task tells you more than an hour of questions. Where that’s not practical, a hands-on test at the shop (read a drawing, lay out a wall, wire a box, hang a door) does the same job. Keep it the same for every candidate for the role. Pay and local rules for working interviews vary: ask your accountant or attorney how to run one where you are.

Ask every candidate for a role the same questions, in the same order, and write down the answers. Behavioral questions (“tell me about a time when…”) work because they ask for evidence instead of opinions. A good answer has a specific job, a specific problem, what the candidate did, and what happened.

For every field role:

For a crew lead or foreman, add:

For an office coordinator or office manager, add:

Questions to leave out: anything about age, family plans, health, religion, national origin or other protected characteristics. Beyond being unfair, they’re unlawful in most places. If you’re not sure a question is allowed, ask your attorney before the interview, not after.

Each interviewer fills in a scorecard right after the interview, before talking to the others. The criteria come from the role scorecard’s capabilities and outcomes, not from a general list.

Example scorecard for a crew lead, made up:

Then compare candidates on the same rows. The decision becomes “strong on the day-to-day, needs training on documenting change orders,” which is a real conversation about whether you can provide that training, rather than “I liked him.”

Rules that keep the scores honest:

• Score before you discuss. Once the group talks, scores converge on the most confident interviewer’s opinion.
• Evidence, not impression. Every score points to something the candidate said or did.
• Mark the must-have rows, and a 2 on a must-have is a no, however charming the candidate.
• Same questions, same test, same scorecard for everyone applying to the role. It’s fairer, and it makes the comparison mean something.

Call two previous employers or crew leads. Ask the same questions each time: what the candidate did there, whether they showed up reliably, how they handled changes and customers, whether they’d hire them again, and what they’d want you to know. Write the answers on the scorecard. A reference who answers only dates and title is telling you something too.

Three things this lesson can’t settle for you, because they depend on your state, trade and insurer:

• Employee or subcontractor. The tests for classification are set by federal and state agencies and the penalties for getting it wrong fall on you. Decide with your accountant before the offer.
• Hiring paperwork and labor rules. Eligibility and tax forms, state new-hire reporting, workers’ compensation, overtime rules, pay-transparency requirements in job posts, and anything your license requires. Your accountant or an employment attorney can give you the checklist for your state. Don’t copy one from the internet. The workers’ comp audit post shows what your insurer will ask about new hires.
• What the hire really costs. Wage plus burden, from the labor burden calculator. Use it to set the range in the post.

1. Take the role scorecard and write the job post from it: work, pay range, schedule, real requirements, how to apply.
2. Write the interview questions for the role, with what a good answer sounds like, and the scorecard rows.
3. Decide the skills check and who runs it.
4. Set the time limit for each step and name who owns the reply.
5. Post it in at least three of the sources above, and ask your crew.

What to review after each hire:

• Did every candidate get the same questions, test and scorecard?
• Where the new hire struggles at 30 days, did the interview show it and was it ignored?
• Which source produced the hire, and how long each step took

Next lesson: a new hire’s first 30 days: an onboarding plan with a named trainer for every item.

Onboarding is everything between the signed offer and the day a new hire does the job to your standard without being watched. When it’s left to chance, it happens anyway: the new person learns from whoever is nearest, picks up that crew’s habits, good and bad, and finds out what you expected when they get it wrong. People who leave in the first two months often say the same three things: nobody told me what was expected, nobody showed me how you do it here, and nobody asked how it was going.

A written 30-day plan fixes all three, and it doesn’t have to be run by the owner. This lesson shows the plan’s structure, a filled-in example for a new office coordinator and one for a new crew member, the check-in questions at day 14 and day 30, and what to review so the plan improves with every hire.

The plan is a table with one row per thing the new hire needs to learn or get. Five columns:

Four rules make it work:

1. Every row has a name in the trainer column. Onboarding fails when it’s everyone’s job. The trainer for scheduling is whoever owns scheduling today, even if that’s you for now.
2. Shadow, then do with review, then do alone. Nobody owns a task on day one. The example below shows the sequence.
3. The standards exist before day one. If the scheduling rules, the customer update points or the job checklist aren’t written down, the new hire learns a verbal version from one person and the plan has nothing to check against.
4. The plan has two fixed conversations, at day 14 and day 30, with questions written in advance.

Most of a bad first day is decided the week before:

• Written offer accepted, start date and time confirmed, where to park and who to ask for.
• Paperwork done or scheduled for the first hour: eligibility and tax forms, state new-hire reporting, anything your insurer or license requires. The list depends on your state; your accountant has it.
• Logins created: scheduling and job software, email if they get one, the group chat if you use one.
• Gear ready: PPE, uniform, tools or tool policy, vehicle or vehicle policy, keys and codes they’re allowed.
• The 30-day plan filled in, with every trainer told their dates.
• A buddy named for field hires: a patient, reliable crew member, not necessarily the most skilled one.
• Their first week’s schedule set, so the trainer and the new hire are on the same jobs.

Made-up company, 16 people, three crews. The coordinator takes over scheduling, customer updates and invoicing from the owner. The plan shows how a responsibility moves from the owner to the new hire in four steps:

Alongside the three responsibilities, the plan has rows for the lead script (trainer: owner, checkpoint: ten calls scored), materials ordering (trainer: operations lead), and the weekly team meeting (attends from week one).

What this plan prevents: the owner “handing over scheduling” on Monday and taking it back on Wednesday after the first conflict. The conflict in week two is expected. It gets reviewed, the rule that was missing gets written, and the handover continues.

Same company; a carpenter joining a remodeling crew.

The unresolved gap column gets filled at each checkpoint. “Cabinet installs: level and plumb fine, scribing slow. Pair with Luis on the kitchen next week.” That line is the plan improving itself.

Two weeks in, the new-job energy has worn off and anything that’s wrong is near the surface. Twenty minutes, sitting down, with the same five questions every time:

1. Is the work what you expected? What’s different?
2. What’s been unclear, or something you had to work out on your own?
3. What’s been the hardest part so far?
4. Is there anything you need that you don’t have: tools, access, information, time with someone?
5. What’s one thing we should do differently?

Write the answers down. Then fix at least one thing they raised before the next week, and tell them you did. A new hire who sees their first piece of feedback acted on tells you the next one too.

Go through the plan row by row. For each learning objective: can they do it alone, with help, or not yet? Then:

• Give specific feedback, good and bad, tied to rows in the plan. “The schedule’s gone out on time three weeks running” and “customer updates are still going out late on Fridays” are both useful. “Doing great” isn’t.
• Set the next 60 days: which remaining rows move to “alone,” and anything new.
• Record the unresolved gaps and what you’ll do about each: more practice, a different trainer, a written standard that didn’t exist, or a conversation about fit.

If the gaps at day 30 are mostly the same as at day 14, the problem is usually the plan or the trainer’s time, not the hire. Check that before you decide anything.

In a company with crew leads and an office, the owner’s job in onboarding is to own the plan, not to run every row. The crew lead trains field work and safety. The coordinator trains the software and the office routines. The bookkeeper trains invoicing. The owner does the day-14 and day-30 conversations, or the person the new hire reports to does them.

That only works when the trainers know they’re trainers. Put the onboarding rows into their week like any other job. A crew lead who has a new person and the same production target as last week will teach nothing and resent the new hire. How crew culture wins better jobs covers what a crew’s habits do to new people, for better or worse.

1. Write the 30-day plan for your next hire, or for the person who started most recently. One row per thing to learn, a named trainer for each.
2. Write down the standards the rows depend on and don’t yet exist on paper.
3. Put the day-14 and day-30 conversations in the calendar before day one, with the questions above.
4. After the day-30 review, fix the plan before the next hire.

What to review:

• Planned onboarding steps completed on time, and which trainers ran out of time
• Unresolved gaps at day 30, and whether they repeat from hire to hire
• The last three new hires: how many are still with you, and what they said at day 14

Next lesson: develop crew leads: what to hand off, what they decide alone, and how to train them.

A crew leader, foreman or lead carpenter is the person who runs one crew’s day so the owner or project manager doesn’t have to: the crew has what it needs, the work meets the standard, the customer on site is handled, the day is documented, and the problems that need someone else reach them in time. In most growing contracting businesses the title exists and the role doesn’t. The best tradesperson gets called the lead, keeps doing the same work, and the owner still makes every decision by phone.

This lesson sets out the crew leader’s daily responsibilities, which decisions they make alone and which they escalate, how to tell who’s ready, a four-stage training path, and how to review the role so it keeps growing.

The list below is the job. Adapt the details to your trade; keep the seven areas.

Safety sits across all of it. Your trade, your state and your insurer set the training and the rules; the crew leader is the person who makes sure they’re followed on site every day.

A lead who has to call for permission on every exception is a messenger, not a leader. A lead who decides everything will eventually give away a change order or rearrange the week’s schedule without telling the office. The answer is a written list: this you decide, this you escalate, and here’s how.

Example limits. Set your own numbers:

The handoff example, made up. A kitchen lead arrives to find the cabinets delivered without two filler panels. She sends a crew member to the supplier, logs the trip and carries on with the base cabinet run: inside her limits. At ten the homeowner says the proposal “obviously included” moving the pendant lights, which it didn’t. She doesn’t argue and doesn’t move the lights. She photographs the ceiling, texts the office with the proposal page, and tells the homeowner the office will call before noon. The office handles the change order. Both were the right call, and the second one is the one that protects margin.

A good escalation has four parts: what happened, what it affects (time, cost, customer), what the lead has already done, and what they need decided. “Hey, there’s a problem at the Millers’” is not an escalation. The same structure the owner bottleneck course uses for delegated decisions applies here.

The best tradesperson is not automatically the best lead. Look for someone who already:

• shows up prepared and notices when the crew isn’t
• tells you about problems before you find them
• explains things to newer crew members without being asked
• speaks to customers comfortably and doesn’t overpromise
• keeps their photos and hours current without reminders
• follows the standard even when a shortcut would be faster

Someone with four of the six can be trained into the rest. Someone who is a superb craftsman and none of the six will be unhappy in the role and so will the crew. There’s a place for that person: the senior tradesperson who sets the quality bar, paid for skill, without the lead’s responsibilities. Say so, and keep both roles real.

Nobody becomes a lead by being told they’re one. The same shadow-then-own sequence as onboarding, stretched over a few months:

Two things that make the difference between a lead who grows and one who stalls:

• The limits widen over time. A spending limit, the courtesy list and the scheduling latitude should be larger at month six than at week one. Say when and why.
• The weekly one-to-one is for them. Fifteen minutes, their agenda first: what slowed the crew down, what decision they weren’t sure about, what they need. Then yours: one piece of coaching, not a list.

If the lead’s pay, title and expectations are the same as the week before they became lead, the role isn’t real and they’ll treat it that way. Put three things in writing: the responsibilities list above adapted to your trade, the decision limits, and the pay step that goes with them. Review all three at the 90-day mark and once a year. The same list is the job post the next time you hire a lead, and it’s what the interview questions test.

1. Write the responsibilities list for one crew leader, adapted to your trade.
2. Write the decision limits with them: what they decide, what they escalate, and how to escalate.
3. Agree what you’ll provide: the standards, your availability on call, the weekly one-to-one.
4. Start at the stage that matches where they are today, and put the move-on criteria in writing.

What to review each month:

• Routine decisions the lead handled alone, and how many came to you that shouldn’t have
• Escalations: were they the right ones, and did they arrive with the four parts
• The crew’s jobs: finished on schedule, rework, customer comments, daily status completeness

Next lesson: run a weekly team meeting that ends in owners and dates, not in another list for the owner.

A weekly team meeting is where a growing contractor’s team stops depending on the owner to carry information between people. Done badly, it’s the opposite: half an hour of status read-outs the owner already knows, no decisions, and a to-do list that’s all the owner’s. Done well, it takes 30 minutes, looks only at exceptions and what’s coming, makes the decisions that are waiting, and ends with actions that have someone else’s name on them.

This lesson gives the agenda, the action log that makes it stick, who should be in the room, the rules that keep it to 30 minutes, the one question that turns it into a feedback loop from the field, and a worked example of the same week run both ways.

• They report status. Status belongs in the job record, updated daily, read before the meeting. Reading it aloud wastes everyone’s time and tells the team the record doesn’t matter.
• They don’t decide anything. The items that need a decision get “let’s talk after,” and after never comes.
• Every action goes to the owner. The team leaves lighter; the owner leaves with nine tasks.
• Nobody checks last week’s actions. So they weren’t really actions.

The agenda below is built against those four failures.

Thirty minutes, same day, same time, every week. Standing up works for some crews. A fixed end time works for everyone.

The log is the meeting’s memory and the thing that makes actions real. One shared table, visible to everyone who attends:

Rules for the log:

• One owner per action. A person, not a crew or “the office.”
• A date, not “this week.”
• The owner isn’t the default. When an action lands and nobody’s named, the question is “who should own this,” not “I’ll handle it.”
• Decisions are logged too, with who made them and when. “Decided Thursday: rent the trailer through October, review in the November meeting.” It ends the re-debate.
• Part 1 next week reads this list. An action that moves its date twice gets discussed: is it the wrong owner, or not important?

Everyone who owns something: the owner, the office coordinator or manager, the estimator or salesperson, the operations lead if there is one, and the crew leads. Crew members don’t attend; their lead brings their items and takes back what matters to them in the morning briefing.

If the crews start at seven and the meeting is at seven, the crews stand idle. Hold it the afternoon before, or first thing on the one day the crews start later, or do it by video with the leads on site at the end of a day. Pick what costs the least production and keep it fixed.

1. Status is updated before the meeting, in the job record. Whoever runs part 2 reads the records first and lists the exceptions. The office-to-field workflow describes the update points.
2. Exceptions only. A job that’s on plan gets no airtime. People learn quickly that the way to be left alone is to keep the job on plan and the record current.
3. Two-minute rule. Anything that takes longer than two minutes to resolve becomes an action: “Luis and Mike, sort out the Henderson schedule after this; decision by Wednesday.” The meeting moves on.
4. No deal strategy, no design, no pricing in the room. Those happen between the two or three people involved, afterwards.
5. The log is written during the meeting, by the coordinator, on a screen everyone sees. Not reconstructed later from memory.

Add one question to part 4 every week, asked of each lead in turn: “What slowed your crew down last week?” One sentence each. Write every answer down, even the small ones.

After a month, patterns show. Materials arriving the morning of instead of the day before. Instructions missing the gate code. The same customer calling the crew directly. Each pattern is a process fix the owner never sees from the office, and each one that’s fixed and reported back in the meeting makes the next answer more honest. Why field feedback matters covers how to get techs to speak up in the first place.

Two more loops sit around the weekly meeting:

• Weekly one-to-ones with crew leads, 15 minutes, their agenda first. The crew leader lesson describes them. Problems that belong to one person don’t belong in the team meeting.
• A monthly numbers review, 60 minutes, with the KPI scorecard: margin by job type, estimate accuracy, schedule performance, cash. The weekly meeting runs the week; the monthly one steers the business.

Made-up company: 18 people, three crews, an office coordinator, an estimator.

Before. The Monday meeting runs 55 minutes. Each lead describes their jobs, most of them fine. A countertop delay comes up; the owner says he’ll call the fabricator. The office mentions a customer who hasn’t signed a change order; the owner says he’ll call her. Luis says exterior jobs keep starting late because the materials come in the morning; everyone agrees it’s annoying. The owner leaves with nine calls to make and makes five of them. The countertop slips another week.

After. Part 1: last week’s six actions, five done, one re-dated with a reason. Part 2: two exceptions out of eleven jobs: the countertop (fabricator hasn’t confirmed the template date) and a bathroom over on plumbing hours. Part 3: a crew member out Thursday and Friday; the coordinator will move the Carter start to Monday and tell the customer today. Part 4: the dump trailer question, buy or rent, gets a decision date of Thursday; Mike brings the bookkeeper’s numbers Wednesday. New actions: Dana owns the fabricator call and tells the Reyes crew by Tuesday; Sam owns the unsigned change order by Monday; Luis writes the exterior readiness checklist by Friday so materials are confirmed the day before. “What slowed you down”: the gate code missing from two jobs’ instructions; Dana adds it to the handoff checklist. Twenty-eight minutes. Six actions across four people; the owner has one.

Neither week had fewer problems. The second one has owners for them.

1. Pick the day and time, and put a 30-minute recurring meeting in everyone’s calendar.
2. Set up the action log where everyone can see it.
3. Before the first meeting, have every job’s status updated in the record and list the exceptions.
4. Run the agenda. End on time. Read the log first thing next week.

Free tool: the Weekly Team Meeting Agenda and Action Log spreadsheet has the 30-minute agenda and an action log that shows what’s overdue and how much sits with the owner.

What to review each month:

• Open actions closed on time, and how many are owned by the owner
• Recurring blockers from “what slowed you down” that have been fixed, and those still repeating
• Meeting length, and how many jobs were discussed that were on plan

Next course: plan your next stage of growth: find the one constraint that’s holding the business back, compare your options, and build a 90-day plan.

You’ve reached the end of Hire, Onboard and Grow Crew Leaders. The course toolkit (PDF) has a worksheet for each of its five lessons in one file, in lesson order, ready to print or fill in on your phone. It comes with one spreadsheet: the Weekly Team Meeting Agenda and Action Log.