Getting Your Techs to Actually Follow the System

Monday morning shop meeting. The owner announces the new process: every tech sends an en-route text with their name, photo, and ETA before every job. The room goes quiet. The senior tech — the one who does the best work and knows it — leans back and says, "I've been doing this fifteen years without texting anybody my picture." The owner feels the whole initiative dying in real time. It doesn't have to.

Context: this post is part of the Leveraged Owner 8-system framework, built on four pillars — capturing every lead, turning estimates into signed jobs, the 5-star review engine, and a full, calm calendar. Every system in the framework has a tech-facing step — and every one of them lives or dies on adoption.

Why techs resist (it's not laziness)

Resistance has rational roots. Name them before you fight them:

• It feels like surveillance. "Send a text when you arrive" reads as "prove you're working." Techs who take pride in their work hear distrust.
• It feels like extra work for no extra pay. From the truck, a new step is pure cost — the benefit accrues to the office, not to them.
• The old way works fine (for them). The senior tech's way does work — for him. He doesn't see the no-shows, the bad reviews, or the lost estimates, because those happen where he isn't looking.
• They've seen initiatives die. Every shop has a graveyard of clipboards, apps, and "new processes" the owner abandoned by March. Why invest in this one?

Argue against these and you lose. Design around them and you win.

The adoption playbook: four moves

1. Involve them before you announce (the ownership trick)

Don't unveil the system at a Monday meeting. Instead, take your senior tech aside the week before: "I'm thinking about having everyone send an en-route text — customers keep calling asking where we are. What would make that not annoying for you?" He'll tell you the friction points (two apps, too many taps, customers replying with questions mid-drive). Fix the ones you can, explain the ones you can't. Now it's his input in the system — and people don't resist their own ideas.

2. Make it simpler than the old way (the simplicity test)

The new process must be easier than what it replaces, or it dies. The en-route text works when it's one tap from a template — not when it requires opening an app, finding the customer, and typing a message. Pre-fill everything: the tech taps the job, taps send. If the system adds more than 30 seconds to the tech's day, redesign it until it doesn't.

3. Show them the WIIFM (the "what's in it for me")

Techs don't care about your close rate. They care about:

• Fewer angry customers. "The en-route text means nobody's mad you were 20 minutes late — they watched you coming." Fewer confrontations at the door is a benefit they feel daily.
• Better tips and reviews with their name on them. The "meet your tech" text puts their name and photo in front of the customer before they arrive — and named techs get named in 5-star reviews. Show them one.
• Less office chaos. "When you send the job-done text, the office stops calling you for updates." Systems that reduce interruptions sell themselves to the people being interrupted.

4. Run the accountability loop (the habit engine)

Announcements create awareness. Loops create habits:

• Measure it visibly. A simple weekly scoreboard: en-route texts sent ÷ jobs completed, per tech. Post it in the shop. What gets measured gets done — especially when peers can see it.
• Review it weekly (2 minutes). "Good week, 94% on en-route texts. Mike, you were at 60% — what's getting in the way?" Curious, not accusatory. The first month is debugging, not discipline.
• Coach the gap, celebrate the win. When a tech's review mentions them by name because of the pre-arrival text, read it aloud at the meeting. Social proof beats policy memos. (Review compliance: celebrate honest reviews only — never pay for or incentivize reviews in ways that violate Google's policies, and never gate review requests to only happy customers.)
• Make it the default, not the exception. Build the step into the dispatch flow so skipping it takes more effort than doing it. Defaults beat discipline.

What to do with the refuser

After involvement, simplicity, WIIFM, and a month of coaching, one tech still won't do it. Now it's a performance conversation, not a systems conversation:

• Private, specific, documented. "The en-route text is part of the job now, like the uniform. I need you at 90%+ by end of month."
• One more month, then consequences. Systems are non-optional the way showing up on time is non-optional. An employee who won't follow documented process after fair warning is telling you something about their future at the company.
• Don't carve out exceptions for stars. The day your best tech is exempt from the system is the day the system dies for everyone. Standards are standards.

Worked example: the en-route text rollout

Example: a 4-tech electrical shop rolls out pre-arrival texts. Week 1: the owner asks the senior tech what would make it painless — he says "I don't want customers texting me back while I'm driving." Fix: replies route to the office number, not the tech's phone. Week 2: soft launch with templates pre-filled — two taps per job. Week 3: scoreboard goes up in the shop. Week 4: a customer review names a tech specifically — "Mike texted before he arrived, so professional" — read aloud at the meeting. By week 6, compliance is 96% and the senior tech is the one reminding the new guy. Total owner time invested: about 3 hours. The system that would have died in a Monday meeting is now just "how we do things."

The one-line version

Techs don't resist systems — they resist being systemized at. Involve them early, make it easier than the old way, show them what they gain, and measure it visibly. The system becomes culture when the holdouts start enforcing it themselves.

A note on texting compliance

Before you automate any customer texts: register for 10DLC business-texting registration (the carrier registration for business texting — roughly $15–$20 one-time, with 1–7 day approval), include opt-out language ("Reply STOP to opt out") in automated messages, and keep marketing texts inside TCPA (federal telemarketing law) quiet hours (8am–9pm in the recipient's local time). This is general information, not legal advice — check current carrier rules before you launch.

Related guides in this series

The four pillar guides whose tech-facing steps this playbook is built to install: How to Set Up Missed-Call Text-Back for Your Contracting Business (The Complete Guide) (Pillar A), The 5-Text Estimate Follow-Up Sequence That Turns Quotes Into Jobs (Pillar B), How to Get More Google Reviews as a Contractor (Without Begging) (Pillar C — the review ask your techs deliver), and Appointment Confirmation Texts That Cut No-Shows in Half (Pillar D). For the complete framework, read How to Automate Your Home Service Business: 8 Systems That Run It For You.

The done-for-you version

This post is part of the Leveraged Owner 8-system framework — the done-for-you version is the Starter Pack, with the full step-by-step setup guides, every script, the worksheets, and complete setup guides for all 8 systems, each designed with the simplicity test in this post already applied.

Stats sourced as labeled: none used — all scenarios in this post are worked examples for illustration.