Job checklists and standard operating procedures for field crews

A good field SOP is short, specific and lives where the work happens: on the technician's phone, attached to the job. Write one checklist per job type covering arrival, the work, photos and close-out, keep each item to one action you can check, and make the few critical items required before the job can be marked complete.

Most small companies have SOPs. They just live in the owner's head. That works until you hire your third technician and start getting callbacks for things you would never have missed.

What's the difference between an SOP and a checklist?

They're related but not the same:

• An SOP explains how and why. "How we do a furnace tune-up," written once, used for training.
• A checklist is the short version used on every job. "Filter checked, flame sensor cleaned, photos taken, customer walked through."

New hires learn from the SOP. Everyone, including your best tech, uses the checklist. Pilots and surgeons use checklists not because they don't know the job, but because skipping one step on a busy day is human.

Which jobs need a checklist first?

Don't try to write fifty checklists in a weekend. Start where the payoff is biggest:

1. Your most common job type. Small improvements here repeat every day.
2. Jobs that cause the most callbacks. Look at your last few months of return visits and find the pattern. A free return trip quietly wipes out the profit on the original job, as our guide to job costing shows.
3. Jobs with safety or code risk. Gas, electrical, roof work, anything where a missed step can hurt someone.
4. Jobs new hires do alone. Maintenance visits and simple repairs.

Two or three good checklists in use beat twenty that nobody opens.

How do you write a checklist techs will actually use?

A few rules make the difference between a checklist that gets used and one that gets ignored:

• One action per line. "Check and clean condensate drain" is fine. "Inspect system" is not.
• Start with a verb. Check, measure, photograph, tighten, ask.
• Record values when they matter. If a reading matters later (a pressure, a temperature, a voltage), make it a number field, not a checkbox.
• Keep it under one screen where possible. If it scrolls forever, split it.
• Use the words your techs use. Not manufacturer jargon, not office language.
• Write it with your best technician. They know which steps really matter and which ones are padding.

What should a typical service visit checklist include?

Here's a starting template you can adapt. It works for most residential repair and maintenance visits.

Arrival

• Confirm the work with the customer in their words.
• Note pets, access issues or hazards.
• Put on shoe covers if entering the home.
• Take "before" photos of the equipment or area.

The work

• Steps specific to the job type, one action per line.
• Readings recorded as numbers with units.
• Parts used added to the job as you go.
• "Issue" photos of anything the customer should know about.

Close-out

• Test that the original problem is resolved.
• Clean the work area and remove debris.
• Take "after" photos.
• Walk the customer through what was done and any recommendations.
• Get the customer's signature when your process needs it.
• Collect payment or confirm how they'll pay.

How do photos fit into your SOPs?

Photos protect you, help the office and help the next technician. Make them part of the checklist, not optional:

• Before and after for every job, from the same angle when possible.
• Model and serial plates for any equipment you service.
• Issues found that you didn't fix, so a recommendation isn't just your word.
• Hidden work before it gets covered up, like wiring inside a wall or a pipe repair under a floor.

A clear photo of a rusted heat exchanger does more to sell a replacement than any explanation.

Which items should be required?

If everything is required, techs will tap through without reading. Pick only the items where a miss really costs you:

• Safety checks (gas leak test, breaker off, fall protection)
• Measurements you need later for warranty or compliance
• Customer signature on approved extra work
• Before and after photos

Everything else can be a reminder. Software that refuses to complete a job until required answers are filled in is useful exactly because it's selective.

How do you get crews to follow SOPs?

Writing the checklist is the easy part. Adoption takes a few weeks of attention:

1. Explain why. Tie each important step to a real callback, complaint or injury.
2. Train with it. Walk through the checklist on a ride-along.
3. Review completed checklists weekly. Look for blank fields, identical readings on every job, or missing photos.
4. Praise good examples. Share a well-documented job in the team chat.
5. Revise often. If techs keep skipping a step, ask why. Sometimes the step is wrong.

How do SOPs help when hiring?

Written SOPs shorten training dramatically. A new hire who can read how you do a job, then follow the checklist on site, needs less shadowing and makes fewer early mistakes. They also make it easier to bring on people who are skilled in the trade but new to your way of working.

If your crew includes Spanish speakers, translate the checklists rather than relying on them to read English quickly on site.

A checklist for writing checklists

• Start with your most common job and your biggest callback source.
• One action per line, starting with a verb.
• Numbers for readings, not checkboxes.
• Photos built in: before, after, plates, issues.
• Only critical items required.
• Written with your best tech, reviewed weekly at first.

FAQ

Paper or digital checklists? Paper works, but it gets lost, is hard to review and can't hold photos. Digital checklists attached to the job are easier to check and stay with the customer's history.

How long should an SOP document be? As short as possible while still teaching the job. A page or two per job type, with photos, is usually enough. The checklist itself should fit on a phone screen or close to it.

Won't experienced techs resent checklists? Some will at first. Involve them in writing the checklists and keep them short. Most come around when they see fewer callbacks and fewer calls from the office asking what happened.

How often should SOPs be updated? Whenever something changes: new equipment, a recurring callback, a new code requirement in your area. A quick review once or twice a year catches the rest.

How ServFlo helps

ServFlo has two tools for this. Every job has a simple checklist that techs tick off in the technician app. Job forms go further: you build templates with headings, checkboxes, text, number fields with units, dropdowns, dates, photo fields and signatures, and attach them to service types so the right form appears on each job automatically. Fields marked required must be filled in before the job can be completed, and the app warns about an unchecked checklist or missing sign-off. Photos can be tagged before, after or issue, and the app works in English and Spanish. Job forms are on every plan; see pricing.

Photo by Ali Mkumbwa on Unsplash.