Operations & Compliance package
Every month, a safety inspection checklist task for each site with Pass / Fail buttons; failures raise a corrective action and are logged.
About this package
Safety inspection checklist runs your monthly workplace inspections without paper forms. On the first of each month the workflow reads the Inspection sites table and starts a Site inspection sub-workflow for every site marked Inspect monthly.
Each inspection is a checklist task form: sixteen yes/no checks grouped under fire safety, housekeeping, equipment and first aid headings with dividers, in a compact two-column grid, plus findings and a photo link. Pass records the result; Fail counts the failed checks, records them in the Inspections table, flags the site, emails the site manager and raises a corrective action task due in a week, which can be completed or sent back for re-inspection.
The main run gives the health and safety lead a sign-off task for the round, so the committee gets one summary each month. Reminders and escalation to the manager keep inspections on time. Everything is built in.
Monthly on day 1 at 07:00 (Pacific/Auckland). You can also start it any time from the Run dialog, the API or the CLI.
Runs on a schedule (daily, weekly, monthly) in your time zone.
The flow
Monthly schedule
On the 1st, every site marked Inspect monthly gets its own Site inspection run.
Checklist
The inspector ticks sixteen checks under four headings, adds findings and photos, and clicks Pass or Fail.
Record
The result, inspection date and number of failed checks go into the Inspections table and onto the site.
Corrective action
A failure emails the site manager and raises a corrective action due in seven days, with a reminder.
Sign off
The safety lead signs off the month's round with a summary for the committee.
Forms
The inputs a caller passes when it starts a run, and the forms people complete when the process needs a decision.
Start inputs
Passed by the calling system
User Task
Sign off safety inspections for {{period}} · 2-column grid · own header and theme
User Task · Site inspection
Safety inspection: {{site_name}} ({{period}}) · 2-column grid · own header and theme
User Task · Site inspection
Corrective action: {{site_name}} ({{failed_count}} failed checks) · 2-column grid · own header and theme
From your code
Every workflow can be started over REST, MCP or the CLI, whatever its trigger, with the sample input below. Runs start straight away on the published version; replace <workflow id> with the id the install created.
REST
curl -X POST "$USERTASKS_URL/api/v1/workflows/start" \
-H "Authorization: Bearer $USERTASKS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"workflow_id":"<workflow id>","variables":{"period":"2026-11","days_to_inspect":14}}'CLI
usertasks workflows inputs <workflow id> # the start form: keys, types, required
usertasks workflows run <workflow id> --input period=2026-11 --input days_to_inspect=14 --waitWhat's included
| Type | Name | Details |
|---|---|---|
| Email template | Inspection failed | Sent to the site manager when a monthly inspection fails. |
| Data table | Inspection sites | Sites inspected every month. Untick Inspect monthly to skip a site; the site manager is emailed when an inspection fails. |
| Data table | Inspections | One row per site per month: the result of the checklist, the failed checks and the corrective action. |
| Workflow | Monthly safety inspections | 11 steps — On the first of each month, schedule a checklist inspection for every site (one Site inspection run each) and give the safety lead a round sign-off task. |
| Workflow | Site inspection | 17 steps — One site's monthly inspection: a checklist task with Pass / Fail buttons; a failure is recorded, the site manager is emailed and a corrective action task follows. |
Inspection sites · 5 sample rows
Site codeSiteAddressTypeSite managerSite manager emailInspect monthlyLast inspectedLast result
Inspections · 1 sample rows
InspectionMonthSite codeSiteStatusInspected onFindingsChecks failedPhotosCorrective actionAction dueAction closed
Requirements
Credentials never travel in a package. The install wizard asks for what your environment must provide, or installs it incomplete until you finish setup.
Nothing: it installs complete.
Install
Works on UserTasks cloud and on any self-hosted instance. Installing creates the assets above; nothing runs until you complete setup and start it.
curl -fLO https://usertasks.com/gallery/safety-inspection-checklist-1.0.1.utpkg
usertasks packages inspect safety-inspection-checklist-1.0.1.utpkg # offline: checksum, hashes, signature
usertasks packages install safety-inspection-checklist-1.0.1.utpkg --dry-run
usertasks packages install safety-inspection-checklist-1.0.1.utpkg # prompts for each requirement
usertasks packages install safety-inspection-checklist-1.0.1.utpkg --keep-incomplete --yes # in CI; finish with:
usertasks packages complete safety-inspection-checklist -f values.yamlVerify the download
shasum -a 256 safety-inspection-checklist-1.0.1.utpkg should print the file SHA-256. How gallery packages are signed.
Versions
Installing a newer version upgrades in place: local credentials and requirement values are kept, and changes you made are flagged first. How packages work
More packages
Operations & Compliance Official
Monthly SOC 2 / ISO 27001 evidence run: automated controls are pulled from your systems, owners of manual controls are asked for a link, all logged for the auditor.
Needs:REST APIAssigneesEmail
Operations & Compliance Official
A daily check of your contract register: owners are reminded 60, 30 and 7 days before each notice deadline and asked to renew, renegotiate or terminate.
Needs:AssigneesEmail
Operations & Compliance Official
A daily stock check finds items at or below their reorder point, raises an Approve order / Skip task for each and emails the supplier a purchase order.
Nothing to configure: works as soon as it is installed