How to Run a Technician Performance Review That Motivates Instead of Deflates

Most contractors skip formal reviews or handle them on the fly in the parking lot. You’re busy, formal paperwork feels corporate, and nobody’s looking forward to a hard conversation. So, another year goes by, and your techs have no clue where they stand.

That’s not free. Good techs leave because nobody tells them what’s next. Underperformers drift because expectations are fuzzy. Raises go to whoever makes the most noise, not whoever earned them. You stay in reaction mode instead of building a team.

Running a technician performance review as a contractor doesn’t require an HR background or a stack of paperwork. A one-page questionnaire, a table in the break room, and about an hour is all it takes. Here’s how to conduct a review worth having.

Why Most Contractors Skip Reviews (and What It Costs Them)

If you’ve ever thought your team knows how they’re doing, you’re not alone. Owners often skip reviews for reasons like talking to them every day, not wanting to hurt feelings or cause confrontation, maybe not knowing how to measure success beyond callbacks and sales, or feeling it’s something employees never revisit.

Skipping reviews doesn’t prevent difficult conversations; it only postpones them. When expectations only come up after issues arise, techs feel blindsided. When raises get handed out without a clear standard, someone always feels shortchanged. And without a documented conversation, you and the tech will remember things very differently a year later.

A consistent employee review process fixes that. Good techs get a visible path forward, while struggling techs get a fair show to improve with support. And you have something to point back to.

What a Motivating Review Looks Like Compared to a Deflated One

Think about two different conversations. 

In the first, the owner does most of the talking. The focus is on the numbers the tech has never seen before, and specifics only come up around what went wrong. The conversation wraps up with an admonishment to step it up, but no real plan is offered. That tech walks out defensive and half-checked out.

In the second, the owner opens, “What are you most proud of this year?” The tech shares wins, and the owner adds specific observations. They work through one or two areas for improvement with real examples. Together, they set goals and agree on what support the company will provide. That tech leaves knowing exactly what a good year looks like and where they can go from here.

The difference isn’t paperwork. One conversation sounds like a verdict, while the other feels like a plan built together. That’s the one you want to have.

The 5-Question Technician Review Framework

Work through each question together and take notes as you go.

1: “What are you most proud of from this past year?”

Start with the tech talking. Ask about specific jobs, customer saves, times they helped a teammate, or skills they built this year. You’ll hear things here that won’t show up in any report.

2: “Here’s what I see you doing really well. Can I share a couple of examples?”

Now you go. Pick two or three strengths and be specific. Tie those back to your company standards so they know these things matter here.

3: “Here are one or two areas where I’d like to see growth. What do you think?”

Stay focused on observable behaviors, not personality. For example, closing out paperwork on time, following the service process on every call, or being more consistent in offering options. Then ask: what’s getting in the way, and what would help?

4: “Where do you want to be a year from now? What about the longer term?”

This shifts the conversation from past performance to future direction. Show them there’s a path in your company, not the same job year after year.

5: ”Let’s set two or three clear goals together for this year.”

Come in with draft ideas, and build the final list together.  Make them specific. Maintain an average review score of 4.8 or better, or mentor a junior tech one day a week. For each goal, decide what support you’ll provide and when you’ll check in on progress.

Set Goals Together Instead of Handing Them Down

You’ll get more follow-through when techs help shape their own goals. Walk in with a list and announce, “here’s what you’re doing,” and you’ll get quiet resistance. Ask “what do you want to work on first,” and build it together, and you’ll see actual effort.

1. Bring two or three draft goals you think make sense.
2. Ask the tech what they want to accomplish this year.
3. Adjust so goals are realistic but still push a bit.
4. Write them down, make them visible, and schedule time to check progress.

“Sell more” is too vague to act on. “Offer at least two options on every call and use the full inspection checklist” is something they can do today that will show up in the numbers later.

Connect Reviews to Raises, Certifications, and Career Paths

Running a formal review and then keeping it separate from pay, training, and advancement kills credibility fast. Techs want to know how performance connects to their paycheck and their future.

Use the review to explain your pay structure in plain terms. Show what “meets expectations” and “exceeds expectations” really look like in your shop. Tie this year’s performance to any raise, bonus, or change in their incentive structure.

Map out a simple career ladder: Technician, Senior Technician, Lead Technician, Field Supervisor. For each step, spell out the required performance level, certifications, and behaviors. Write on the form where they are now and what needs to happen to move up. That turns the review from a report card into a direction finder.

When pay comes up, be direct. “If you hit these targets and finish this training, we’ll be in a position to move you from this range to that range” is the right kind of specificity. Clear beats polished every time.

Follow Up So It Doesn’t Die in a Drawer

A solid review you never revisit won’t change much. Build in a 10- to 15-minute check-in at the 30-, 60-, and 90-day marks. Bring the form on ride-alongs. When you see them doing something you talked about, write it down. Those specific examples are what you want when you sit down again next year.

The goal isn’t a perfect review. It’s showing your technicians, consistently, that their growth matters and that there’s a fair, predictable way to move forward in your company.