Making checklist fields required — possible?

Our compliance team requires that certain safety attestations be completed before a technician can close out a work order. We are evaluating FieldPulse for field operations in a regulated environment.

I have reviewed the checklist template creation interface and do not see an option to designate specific fields as mandatory. It is worth noting that from a governance perspective, we cannot rely on voluntary completion — the system must enforce this at the data entry level.

Is this capability available, or is it on the product roadmap? If not currently supported, what workarounds have other organizations implemented to ensure audit-ready documentation?

  • Hi Fatima, great question! Yes, you can make checklist fields required. Here's how:
    1. Go to Settings > Forms & Checklists > Checklist Templates
    2. Edit your template or create a new one
    3. Click the field you want to require
    4. Check the box labeled "Make this field required"
    5. Save the template

    When a technician tries to complete or close the work order, FieldPulse will block submission until all required fields are filled. This validation happens on both mobile and web.

    For your audit use case, you may also want to enable audit logging to capture when checklists are submitted and by whom.

  • Pro tip: Required fields work for most field types, but there's a gotcha with photo fields. If you mark a photo field as required, the tech must upload at least one image — no skipping it with a note. We've run into this with safety verification shots where the tech meant to add a description instead.

    Also worth noting: required fields only enforce on completion, not on status changes like "In Progress." So if your techs move jobs through multiple statuses, the validation won't trigger until they try to mark it done.

  • One more thing on enforcement: if you're using the mobile app, make sure your techs are on version 3.2.1 or later. There was a bug in 3.1.x where required field validation could be bypassed by force-closing the app mid-submission. Fixed now, but worth checking your fleet's app versions.

    Quick check: Mobile App > Profile > scroll to bottom for version number.

  • oh yeah this got us too — basically we had a checklist for CO detector testing and the required field was like "test result: pass/fail" but if you just hit the back button and then came back it would let you through without picking anything?? idk if that's the same bug sylvia mentioned but updating the app fixed it for us anyway

    what i actually wanted to add though is we started using required fields for customer signatures too which has been really good for making sure we have proof of completion on every job

  • Thank you for this clarification, Josh. The distinction regarding status changes is particularly relevant — our workflow does include intermediate stages. I will verify whether this meets our internal controls requirements or if we need to adjust our process.