Field service

How to design a checklist technicians actually fill in

A checklist ticked without looking is worse than no checklist at all. It takes time, creates paperwork and gives confidence nobody has earned. And the culprit is almost never the technician: it is the design.

In this article
  1. The twenty-item rule
  2. Checkable, not a matter of opinion
  3. The reference value, right next to it
  4. The order of the walk-around, not the manual
  5. Which field type to use
  6. What gets it filled in properly
  7. The mistake that keeps coming back
  8. When you change the template

The twenty-item rule

As a rule of thumb, beyond about twenty checks attention drops and people start ticking in bulk. On long checklists, the last items are often all ticked the same way, in the same second.

If your inspection needs 60 checks, that is three checklists, not one. Or you are mixing the regulatory inspection with the quality one and the sales one.

Checkable, not a matter of opinion

Not like thisLike this
General condition of the unitSupply air temperature: ___ °F (range 43–46)
Is it working properly?High-side pressure: ___ psi · Low-side pressure: ___ psi
Check filtersFilters: clean / dirty / replaced
Check safetyEmergency stop test: pass / fail

The right-hand column produces data you can use next year. The left-hand one produces a tick.

The reference value, right next to it

A field that asks for a temperature without saying what is normal leaves the technician two options: call someone, or write it down and move on. With the range next to it, the checklist becomes a decision tool instead of a data-collection form.

The order of the walk-around, not the manual

The manual is organized by system. The technician moves around the equipment. If the checklist sends them from the electrical panel to the water circuit and back again, they end up filling it in from memory.

How to fix it: write the first version, give it to two technicians, go with them once and reorder it. It takes half a day, and it improves the result more than anything else.

Which field type to use

  • Checkbox: only for things that are clearly yes or no.
  • Number with a range: whenever there is a measurement. It is the most valuable field.
  • Short dropdown: five options at most. With more, nobody reads them and everyone picks the first one.
  • Photo: required where evidence matters: before and after, the nameplate or the problem found.
  • Free text: one, at the end. That is where the valuable information shows up, and where the next preventive task is born.
  • Signature: only if it is really needed. Asking for it on every checklist cheapens it.

What gets it filled in properly

  • Filled in on site, not afterwards. That matters more than anything.
  • Works without coverage, because equipment sits in basements and on rooftops.
  • Pre-fills what is already known: equipment, customer, technician and date are never typed.
  • A failed check leads somewhere. Marking “fail” should be able to create a corrective work order right there. Otherwise the technician learns that marking it is pointless.
  • Questions depend on the answers. If there is no leak, there is no need to ask how big it is.

The mistake that keeps coming back

Designing it in an office without asking. Technicians know which fields are unnecessary, which ones are missing and the order in which things get done. Half an hour with two of them saves three versions. Above all, it gets them to adopt it: a checklist they helped design is theirs.

When you change the template

Checklists change: a new regulation, different equipment or an item that was not needed. Keep track of which version each inspection used. Otherwise, April’s inspection will be read with October’s questions, and nobody will understand the answers.

Take your most-used checklist and count the items. If there are more than twenty, ask which ones you added “just in case.” Those are the ones stopping the rest from being filled in.

Last updated:

Keep reading

More on field service

Processes and compliance

Periodic controls: how to prove they were done

Doing a control and being able to prove it are two different jobs. The second one usually surfaces on audit day, when someone spends a week hunting for emails, screenshots and signatures.

4 min read

All blog articles

Request a demo

Shall we look at it with your operation?

Tell us how you work today and we will show you attendo with your own data. If it is not a fit, we will say so.

  • With your operation, not a generic demo
  • A real person from our team replies
  • No cold calls afterwards

Would you rather talk first?

Which area do you want to see in the demo?

With your work email we prepare the demo around your case.

In one or two sentences.

If you chose Maintenance (CMMS)

If you chose Field work (Field Service)

If you chose Facility Management

If you chose any other area

Only if you would rather we call you.

Data protection. Controller: AxisOne Group SL. Purpose: preparing the demo you request and replying to you. Legal basis: your consent and the request you make. Recipients: we do not disclose your data; Cloudflare (website) and Brevo (email notices and confirmation) process it on our behalf. Rights: access, rectification, erasure, objection, restriction and portability, at privacy@attendo.me. More information in the privacy policy.

What happens when you send it. Someone from our team reads what you tell us and writes to you to agree on a time for the demo. Our hours: Monday to Thursday 9:30 AM to 6:30 PM and Friday 9:30 AM to 2:30 PM, Spain time.