How We Define “Done Right” With Job Forms
As we added technicians, I realized “do a good job” is way too vague. What does that actually mean? For us, it means things like checking the gate, following the right yard pattern, documenting any...
Forum Discussion
Ours come down to five, and we keep them required rather than optional, or they quietly stop happening.
Gate and property left secure, with a photo of the gate closed. A before and after photo of the area actually serviced, not just the best-looking corner. A completion status on every visit, full, partial, or unable, with a reason required whenever it is not full. Anything unusual noted on the spot, access issues, damage, pets, or something left behind. And the customer notes checked before arrival, so gate instructions, pets, and access issues are read before the tech is standing at the property, not after.
The part that made it stick was not the form itself. It was reviewing every partial and unable visit at the end of the day, while it was still fresh, and keeping the form short enough to finish on site in about a minute. Once the list got longer than that, people started tapping through it without looking, and the standard we were protecting disappeared.
Keeping the form short enough to finish on site is probably one of the most important parts.
If it takes too long, people start clicking through it just to get it done and the form loses its value.
I also like the full/partial/unable status with a required reason. That gives the office something actionable to review instead of finding out later that a visit wasn’t completed the way everyone assumed.