Setting Expectations a Tech Can Actually Be Held To

Why this matters

You cannot hold anyone to a standard you never made concrete. "Be professional," "hustle," "take pride in your work" feel like expectations, but they are wishes wearing a work shirt. When it comes time to correct a tech, a vague expectation hands them a place to stand ("I thought I was doing fine") and hands you nothing to point at. The expectation that survives a correction conversation, a review, and sometimes a termination is the one that was specific, observable, and stated the same way to everyone. This is how you build that kind, so accountability is even possible.

The clarity test: could two people agree it was met?

Here is the single filter that separates a real standard from a wish. Read your expectation and ask: if the tech and I each judged whether it was met, using only what we can both see, would we land in the same place?

• "Keep the truck clean" fails. Clean to you and clean to a second-year are different pictures.
• "Truck cab clear of trash and the bin restocked to the checklist at end of shift" passes. Two people looking at it agree.

If an expectation would spark an honest argument about whether it was met, it is not yet holdable. Rewrite it until the argument disappears.

Describe behavior you can see, not character you infer

Most unenforceable expectations are secretly about character. "Have a good attitude" is a judgment about who someone is. You cannot coach it, cannot measure it, and cannot defend it later. Convert every character expectation into the observable behavior that made you write it in the first place.

• "Be a team player" becomes "answer a crewmate's call for a hand within the shift, and flag a job you cannot finish before you leave it."
• "Be reliable" becomes "on site by the start time, and a call to dispatch if you will be more than the agreed window late."

Behavior is visible, teachable, and correctable. Character is none of those. Always aim the expectation at the thing you could point to on a camera.

Attach a number or a bar wherever one honestly exists

An expectation gets sharper the moment you attach a measure to it, as long as you frame the measure as a target you coach toward, not a wire you fire someone for touching once. A callback rate has a healthy range for your trade; state it as the range you expect a tech to trend inside over a stretch, not a single-job verdict. A maintenance call has a rough time it should run; state the expected pace and the note that a hard job or a real find is a fair reason to blow past it.

Where no clean number exists, anchor to a visible example instead: "finished work looks like this reference job." A photo of a done-right install teaches a standard faster than a paragraph.

Sort the black-and-white from the graded

Not every expectation is a range. A few are absolute, and mixing the two categories is how techs learn to treat all of them as soft.

• Black and white (zero tolerance, stated as absolute): lockout before working hot, no working impaired, honest time and honest paperwork, the safety non-negotiables of your trade. These are not targets to trend toward. They are lines.
• Graded (a bar you coach toward): pace, callback rate, cleanliness, communication frequency, upsell conversion. These live on a slope, and a single miss is a coaching cue, not a violation.

State which category each one is in when you set it. A tech who does not know which rules are lines and which are slopes will guess, and they will guess generously.

Write down the load-bearing ones

Verbal standards fade and get remembered differently by each side within a month. You do not need a binder. You need the handful you would actually cite in a correction to exist somewhere the tech can look back at: a one-page standard, a note in their file, the checklist itself. The test is simple. If "I told you that" has to be true and checkable later, it needs to be written now, not reconstructed from memory during an argument.

The two-way half most owners skip

An expectation the tech had no realistic way to meet is not an expectation, it is a trap, and everyone on the crew can smell one. Before you hold someone to a standard, confirm three things were true: they were told it plainly, they had the tools and training to hit it, and nothing in your own scheduling or dispatch made it impossible. If you booked a tech so tight that the arrival-window standard could not be met, the miss is yours, not theirs. Holding people to standards you undercut is the fastest way to teach a crew that the standards are theater.

The bar to hold yourself to: if a correction would genuinely surprise the tech, the expectation was never really set. Fix that before you judge anyone against it.

References

• Society for Human Resource Management (SHRM), setting measurable performance expectations
• U.S. Small Business Administration (SBA), employee performance standards guidance
• See related: Setting Expectations in the First Week, Not the First Review
• See related: The Performance Conversation That Changes Behavior