Build reusable checklist templates, run them item by item in the field, and require them before work orders close.
Checklists turn "did the crew do everything?" into a record instead of a guess. You define a checklist once as a template — a completion walkthrough, a safety check, a quality inspection — and your team runs it in the field item by item, capturing answers, ratings, photos, and notes as they go. The checklists hub has two tabs: TEMPLATES for what you have defined, INSTANCES for the runs themselves.
§Templates
The TEMPLATES tab holds your reusable checklists. Build one per situation you want standardized — a job-completion walkthrough, a pre-install inspection, a safety audit — and reuse it run after run, so every crew answers the same questions in the same order and results stay comparable across jobs.
§Runs
The INSTANCES tab lists checklist runs: the in-progress ones your team is midway through and the completed ones you can look back on. Open a run to see exactly how it was answered, item by item.
§Running a checklist
The runner walks one item at a time, and each item can capture more than a checkmark:
- ◆A
YES/NO/N/Aanswer. - ◆A 1–5 rating, for items you want scored rather than passed or failed.
- ◆Photos, so the answer carries proof.
- ◆Notes, for anything that needs words.
Answer, attach, and move to the next item — by the end you have a complete, reviewable record of the inspection instead of a verbal "all good."
§Company policy
Admins set checklist policy with the CHECKLIST SETTINGS entry — search for it from the Admin Console. Two controls matter most: requiring every checklist item to be completed before a work order can close, and auto-assigning a default template so your standard checklist is applied automatically instead of depending on someone remembering to add it.