Creating required safety checklist before job close

We're evaluating FieldPulse for our industrial maintenance division and have a critical compliance requirement. We need to ensure technicians cannot mark a work order as "Complete" until they have submitted a specific safety checklist.

Is this currently supported? If so, what is the recommended configuration approach to enforce this at the work order level rather than relying on technician discipline?

Our auditors will need to verify that the checklist was completed before closure, so any gaps in enforcement would be problematic.

Parents
  • Pro tip: Even with "required" enabled, train your techs to hit Submit Checklist before they start the final job tasks. I've seen situations where they're almost done, try to close the job, get blocked, and then have to backtrack through the checklist while standing in front of the customer.

    Also if you have multiple checklist templates assigned to a job type, all of them must be submitted before closure. We learned that the hard way with a pre-job safety check AND a post-job equipment check both set to required.

  • Seconding Josh's point about sequencing — we actually renamed our checklists to include "STEP 1" and "STEP 2" in the titles so techs know the order. Small UX win that saves a lot of confusion.

    Also worth noting: the required checklist block only applies to status changes to Completed. If your techs are using "Pending Parts" or "Needs Follow-Up" as workarounds, those don't trigger the validation. You may want to audit your status usage if compliance is critical.

Reply
  • Seconding Josh's point about sequencing — we actually renamed our checklists to include "STEP 1" and "STEP 2" in the titles so techs know the order. Small UX win that saves a lot of confusion.

    Also worth noting: the required checklist block only applies to status changes to Completed. If your techs are using "Pending Parts" or "Needs Follow-Up" as workarounds, those don't trigger the validation. You may want to audit your status usage if compliance is critical.

Children
No Data