Every operator has had both: the tech who clears twelve yards without a complaint, and the tech whose route generates review mentions by name. The difference is rarely effort and almost never speed. It is a short list of habits, and most of them can be trained if you know what to look for.
Good techs finish yards. Great techs close gates.
The single most expensive mistake in this trade is a gate left open. One escaped dog can end a client relationship, and the story travels through a neighborhood faster than any referral program. Great techs treat the gate like a pilot treats a checklist: photographed shut, every visit, no exceptions, even when the yard has no dog in it that day.
This is a habit you can enforce structurally instead of by nagging. Requiring completion photos, the before and after kind, builds the documentation reflex, and a gate photo rides along with it naturally. It is why the HoundStack field app makes photo capture required at completion rather than optional.
Good techs read the work order. Great techs read the yard.
The work order says two dogs, weekly, back gate code 4482. The yard says one of the dogs has been sick this week, the back fence board is loose again, and there is a wasp nest starting under the deck rail.
Great techs report what the yard tells them. That loose board is an escape risk next week. The wasp nest is a hazard for whoever comes next, which might be them. A tech who logs an issue photo and a one line note is doing sales and safety at the same time, because the client hears about the fence from you before they notice it themselves. That is the moment a service becomes worth referring.
Good techs know their route. Great techs know their dogs.
Clients in this business are dog people. The tech who knows Bruno charges the gate but settles if you let him sniff the bucket, who knows Pepper is deaf and startles, is safer and faster, and clients can tell. Hazard notes are where that knowledge should live, not in one tech’s head. When it is written down, structured, and shown before the gate opens, a substitute tech on a sick day is nearly as smooth as the regular, and nobody gets bitten learning what the regular already knew.
Good techs handle the visit. Great techs handle the exception.
Locked gate. Dog in the yard that should not be there. A client standing on the porch wanting to talk about a missed spot from last week. The visit that goes sideways is where reputations are made.
The trainable core is simple: never guess, always log, communicate before leaving the curb. A skipped visit with a reason, a photo, and an automatic client notification is a professional interaction. The same skip, silent, becomes a “did they even come?” complaint by dinner.
What to do with this as an owner
Three practical moves:
- Make the habits structural. Required photos, structured hazard fields, and skip reasons turn great tech behavior into the default behavior. Tools matter here because memory does not scale.
- Ride along quarterly. Not to inspect, but to watch for the yard reading skill. It shows within three stops.
- Praise specifics in front of the team. “Marcus caught a loose fence board at the Hartleys and the client called about it” teaches more than any handbook page.
Hiring matters, but most great techs are made, and the making is mostly repetition with the right defaults. Give a conscientious person a system where the professional move is also the easy move, and the review mentions follow.