Surveys & Assessments package

Site inspection with corrective actions

A four-step inspection page with a checklist table, star rating, photos and signature; a decision table sets the outcome band and every failed item becomes a signed-off corrective action.

OfficialNo integrations neededStarts from a formIntermediate~10 min setupv1.0.0

About this package

What it does

Site inspection with corrective actions turns a safety walk-round into tracked, evidenced fixes using only UserTasks features and the official form controls. The Site safety inspection page has four numbered steps and a review step: a site lookup that fills the site manager, address and risk class from the Sites table; a Table control holding the checklist, pre-filled with eight standard items, where each row is marked Pass, Fail or N/A with an area, a severity and notes; a star Rating for the overall site condition, photo uploads and Rich text observations; and an Info card summary with the inspector's Signature.

The Site inspection workflow counts the failures with FILTER_WHERE and COUNT, works out the pass rate and the worst severity, and an outcome band decision table chooses Compliant, Minor actions, Major actions or Stop work with a close-out SLA in days. The inspection is saved to the Inspections table, the site's last result is updated, the site manager is emailed the report with the photos, and a Stop work result sends a stop-work alert straight away.

Every failed item is logged as an Open row in the Corrective actions table with a due date from a second decision table (high 2 days, medium 7, low 14), then becomes a corrective action task for the inspector with a reminder and manager escalation. The task shows the failed check on an Info card and a Progress bar of the actions closed so far, and records the fix, the root cause, photo evidence and a Signature sign-off; the site manager is emailed the evidence. When the last action is done the safety manager (the person who installed the package) gets a review task with an Info card summary, a Progress ring of the actions closed and a confidence Rating.

The Inspection overview page is the safety manager's dashboard: Chart controls of the open actions by severity and by site from the Corrective actions table, Saved report controls for failures by severity per site (workflow variables) and the open corrective action tasks, and a button that emails a digest of the open or overdue actions.

Starts from a form

Starts from a form page: inspectors open Forms → Site safety inspection (or its /f/ link on a phone or tablet) and submit it at the end of the walk-round.

Someone fills in a form to start it: the workflow start form (Run dialog in the app, or your own portal posting to the API) or a standalone form page (/f/<id>) whose Form submitted trigger starts the workflow. People complete User Task forms along the way.

How forms work

The flow

Step by step

  1. 1

    Inspect

    Pick the site (manager, address and risk class fill in), mark the eight-item checklist table Pass / Fail / N/A with severities, rate the site, add photos and observations, and sign.

  2. 2

    Score

    Failures, the pass rate and the worst severity are counted; a decision table chooses Compliant, Minor actions, Major actions or Stop work and the close-out SLA.

  3. 3

    Report

    The inspection is saved, the site manager gets the report with the photos, and a Stop work result sends a stop-work alert.

  4. 4

    Fix

    Each failed item is logged in Corrective actions and becomes a task with a due date by severity, a progress bar, photo evidence and a signature sign-off.

  5. 5

    Review

    The safety manager reviews the closed and escalated actions and closes the inspection or asks for a re-inspection; the Inspection overview page charts what is still open.

Site inspection — An inspector submits the checklist: failures are counted, a decision table sets the outcome band and close-out SLA, the inspection is saved and reported, every failed item becomes a corrective action with a signed-off fix and photo evidence, and the safety manager reviews the result. The same canvas you get in the designer after installing.

Sub-workflow: Open actions digest

From the Inspection overview page: lists the open (or overdue) corrective actions, counts them by severity and emails the digest to whoever asked.

Forms

The start form and the task forms

People start it from a form page (/f/<id>) with its own header, theme and buttons; submitting it starts the workflow. User Tasks show their fields and outcome buttons to the assignee.

Form page · /f/<id>

Inspection overview

2-column grid · own header and theme · Its own page: share the link or open it on a tablet

About this page about · ut-info-card
Open actions by severity by_severity · ut-chart
Open actions by site by_site · ut-chart
Failed checks by severity and site severity_report · ut-saved-report
Open corrective actions open_report · ut-saved-report
Email me a digest of * include · choice
All open actionsOverdue actions only
Email me the digest

Form page · /f/<id>

Site safety inspection

own header and theme · Its own page: share the link or open it on a tablet

Site * site · lookup
Site name site_name · text
Address site_address · text
Site manager site_manager · text
Site manager email site_manager_email · emailname@company.com
Risk class risk_class · text
Inspection date * inspection_date · dateYYYY-MM-DD
Inspection type * inspection_type · choice
RoutineFollow-upIncidentPre-start
Checklist * checklist · ut-table
Overall site condition * site_condition · ut-rating
Photos photos · attachments
General observations observations · ut-rich-text
Summary summary_card · ut-info-card
I inspected this site in person and the checklist is accurate * declaration · boolean
Inspector signature * inspector_signature · ut-signature
Submit inspection

User Task

Corrective action

Corrective action {{action_index}}/{{fail_count}}: {{action.item}} ({{site_row.name}}) · 2-column grid · own header and theme

Site ca_site · textPrefilled: {{site_row.name}}
Checklist item ca_item · textPrefilled: {{action.item}}
Area ca_area · textPrefilled: {{action.area}}
Severity ca_severity · textPrefilled: {{action.severity}}
What the inspector found ca_found · textareaPrefilled: {{action.notes}}
Fix by ca_due · textPrefilled: {{action_due}}
The failed check ca_card · ut-info-card
Action ca_ref · textPrefilled: {{action_ref}}
Closed so far ca_closed · numberPrefilled: {{closed_count}}
Actions from this inspection ca_total · numberPrefilled: {{fail_count}}
Actions closed for this inspection ca_progress · ut-progress
What was done to fix it * fix_description · textarea
Root cause * root_cause · choice
HousekeepingMissing equipmentMaintenance overdueTrainingProcedure not followedOther
Fixed on * fixed_on · datePrefilled: {{=TODAY()}}
Photo evidence * evidence · attachments
Sign-off * signoff · ut-signature
Fixed and signed offCannot fix

User Task

Safety manager review

Review inspection {{inspection_ref}}: {{site_row.name}} ({{outcome_band}}) · 2-column grid · own header and theme

Site rv_site · textPrefilled: {{site_row.name}}
Outcome rv_band · textPrefilled: {{outcome_band}}
Pass rate rv_rate · textPrefilled: {{pass_rate}}% ({{fail_count}} failed of {{items_checked}})
Site condition rv_condition · textPrefilled: {{form.site_condition}} of 5
Inspector rv_inspector · textPrefilled: {{submitted_by_name}} on {{form.inspection_date}}
Escalated actions rv_escalated · numberPrefilled: {{=fail_count - closed_count}}
Inspection summary rv_card · ut-info-card
Actions closed rv_closed · numberPrefilled: {{closed_count}}
Actions raised rv_total · numberPrefilled: {{fail_count}}
Corrective actions closed rv_progress · ut-progress
Confidence in the site's controls * rv_confidence · ut-rating
Notes for the health and safety committee * review_notes · textarea
Close the inspectionRe-inspect

Form controls

8 official form controls, installed with it

The forms use these controls from the gallery. They come inside the package and install into Extensibility → Form controls, sandboxed and signed like every official control: nothing else to download.

From your code

Start a run over the API

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

shell
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":{"site":"AKL-DC","site_name":"Auckland distribution centre","site_address":"48 Freight Drive, Auckland","site_manager":"Jordan Sample","site_manager_email":"jordan.sample@example.com","risk_class":"High","inspection_date":"2026-10-30","inspection_type":"Routine","checklist":[{"item":"Fire exits and escape routes clear and signed","area":"Fire safety","status":"Fail","severity":"High","notes":"Pallets stacked in front of the bay 3 fire exit."},{"item":"Fire extinguishers in place, tagged and in date","area":"Fire safety","status":"Pass","severity":"","notes":""},{"item":"Walkways and stairs free of trip hazards","area":"Housekeeping","status":"Pass","severity":"","notes":""},{"item":"Electrical leads and equipment tested and tagged","area":"Electrical","status":"Fail","severity":"Medium","notes":"Extension lead at the packing bench has a cracked plug."},{"item":"Machine guards fitted and working","area":"Equipment","status":"N/A","severity":"","notes":"No machinery at this site."},{"item":"Required PPE available and worn","area":"PPE","status":"Pass","severity":"","notes":""},{"item":"Chemicals labelled, safety data sheets on hand","area":"Hazardous substances","status":"Pass","severity":"","notes":""},{"item":"First aid kit stocked, first aiders listed","area":"First aid","status":"Pass","severity":"","notes":""}],"site_condition":3,"observations":{"html":"<p>Busy dispatch day. Staff were wearing hi-vis and the new racking labels are in place.</p>","text":"Busy dispatch day. Staff were wearing hi-vis and the new racking labels are in place."},"declaration":true}}'

CLI

shell
usertasks workflows inputs <workflow id>          # the start form: keys, types, required
usertasks workflows run <workflow id> --input site=AKL-DC --input site_name="Auckland distribution centre" --input site_address="48 Freight Drive, Auckland" --input site_manager="Jordan Sample" … --wait

What's included

25 assets, ready to adapt

TypeNameDetails
Email templateCorrective action closedSent to the site manager when a corrective action is signed off, with the evidence photos attached.
Email templateInspection report to the site managerSent to the site manager after every inspection, with the inspection photos attached.
Email templateOpen corrective actions digestSent to whoever asks for it from the Inspection overview page.
Email templateStop-work alertSent to the site manager and the inspector straight away when the outcome band is Stop work.
Data tableCorrective actionsEvery failed checklist item becomes a corrective action: what was found, its severity and due date, and, once fixed, what was done, who signed it off and how many evidence photos were attached.
Data tableInspectionsOne row per inspection: the checklist result (failed checks, high-severity failures, pass rate), the site condition rating, the outcome band and close-out SLA from the decision table, and the status.
Data tableSitesThe sites you inspect: the lookup on the inspection form fills the site manager, address and risk class from here, and every inspection updates the last result.
Decision tableCorrective action due date3 rules — How many days a corrective action has, by the severity of the failed item, and how soon its reminder goes out. Each corrective action task and Corrective actions row reads this.
Decision tableInspection outcome band6 rules — Turns the number of failed checks, the high-severity failures, the worst severity (0 none, 1 low, 2 medium, 3 high) and the overall site condition rating into the outcome band and how many days the site has to close out every action. Change the thresholds here.
Retention policyInspections: 7 yearsHealth and safety records are usually kept for years: purge inspection and corrective action rows 7 years after they were created. Apply it to the Inspections and Corrective actions tables after install.
ReportFailed checks by severity and siteHigh, medium and low severity failures per site, summed over the inspection runs (workflow variables).
ReportInspections by outcome bandHow many inspections ended in each outcome band, with the average pass rate and site condition (workflow variables).
ReportOpen corrective actionsCorrective action tasks from the Site inspection workflow that are not completed yet, soonest due first, with the item, area and severity.
Form controlChartBar, line, area, pie or doughnut chart of static data, another field's rows, lookup results or a saved report. Keyboard-navigable points, a data table view, and optional point selection.
Form controlInfo cardA callout or key / value card: an info, success, warning, error or neutral message that can show up to six other form values ({{field1}} … {{field6}}), formatted for the reader.
Form controlProgressProgress as a bar, a ring or named steps, from two mapped fields (current and total) or fixed values, with optional warning / good thresholds.
Form controlRatingStar, heart or circle rating from 1 to 10 with optional labels (Poor … Excellent). Mouse, touch and keyboard.
Form controlRich textA rich-text editor with bold, italic, underline, headings, lists, quotes and links, a character counter and strict sanitising of everything typed, pasted or dropped.
Form controlSaved reportShows a saved report as a sortable, paginated table or a chart, run with the permissions of the person filling in the form. Optionally pick a row as the field's value.
Form controlSignatureDraw a signature with a finger, pen or mouse, or type a name. Saved as a trimmed PNG in the form's attachments.
Form controlTableAn editable table (line items, attendees, measurements) with typed columns: text, number, currency, date, choice and tick box. Per-cell validation, totals, and spreadsheet-style keyboard editing.
FormInspection overviewThe safety manager's page: open corrective actions by severity and by site from the Corrective actions table, failures by severity per site and the open corrective action tasks as saved reports, and a button that emails a digest of the open actions.
FormSite safety inspectionThe inspector's form: pick the site (the manager, address and risk class fill in), work through the checklist table (Pass / Fail / N/A with a severity for each failure), rate the site, add photos and sign. Each submission starts the Site inspection workflow.
WorkflowOpen actions digest9 steps — From the Inspection overview page: lists the open (or overdue) corrective actions, counts them by severity and emails the digest to whoever asked.
WorkflowSite inspection46 steps — An inspector submits the checklist: failures are counted, a decision table sets the outcome band and close-out SLA, the inspection is saved and reported, every failed item becomes a corrective action with a signed-off fix and photo evidence, and the safety manager reviews the result.

Corrective actions · 8 sample rows

ActionInspectionSite codeSiteChecklist itemAreaSeverityWhat was foundDueDays to fixStatusWhat was doneClosed onSigned off byEvidence photosSummary

Inspections · 6 sample rows

InspectionInspected onSite codeSiteTypeInspectorItems checkedFailedHigh severityPass rate %Site condition (1-5)OutcomeClose out within (days)PhotosObservationsStatus

Sites · 5 sample rows

Site codeSiteAddressTypeRisk classSite managerSite manager emailLast inspectedLast outcome

Requirements

What you connect it to

Credentials never travel in a package. The install wizard asks for what your environment must provide, or installs it incomplete until you finish setup.

Needs

  • Email (optional) — Email delivery configured for the instance (EMAIL_PROVIDER), used for notifications.

After installing

  1. Nothing to configure: install it and open Forms → Site safety inspection (share its /f/ link with your inspectors) and Forms → Inspection overview.
  2. The Table, Rating, Rich text, Info card, Signature, Progress, Chart and Saved report controls install with the package (Extensibility → Form controls).
  3. Replace the sample rows in Sites with your own sites and site managers; delete the sample Inspections and Corrective actions rows when you go live.
  4. Edit the checklist's starting rows on the form (the Checklist field's Starting rows) for your site types, and the two decision tables for the outcome bands and the days to fix.
  5. Corrective actions go to the inspector who submitted the form and the review to the person who installed the package: change the assignees in the designer if your safety team works differently.
  6. Optional: apply the "Inspections: 7 years" retention policy, and set EMAIL_PROVIDER so the report, stop-work and digest emails are delivered (the console provider logs them).

Asked for on install

Nothing: it installs complete.

Install

Install it in your workspace

Works on UserTasks cloud and on any self-hosted instance. Installing creates the assets above; nothing runs until you complete setup and start it.

In the app

  1. Download site-inspection-corrective-actions-1.0.0.utpkg.
  2. Open Automations → Packages and drag the file onto the page (or choose Import package). Browse gallery there lists every gallery package without downloading by hand.
  3. Pick the file. The wizard verifies the checksum, every file hash and the signature, and shows the readme.
  4. Review the changes (what is created) and the data rows.
  5. Fill in the requirements, or tick Keep incomplete and finish later with Complete setup.
  6. Done: the workflow is published and active once setup is complete.

With the CLI

shell
curl -fLO https://usertasks.com/gallery/site-inspection-corrective-actions-1.0.0.utpkg
usertasks packages inspect site-inspection-corrective-actions-1.0.0.utpkg       # offline: checksum, hashes, signature
usertasks packages install site-inspection-corrective-actions-1.0.0.utpkg --dry-run
usertasks packages install site-inspection-corrective-actions-1.0.0.utpkg       # prompts for each requirement
usertasks packages install site-inspection-corrective-actions-1.0.0.utpkg --keep-incomplete --yes   # in CI; finish with:
usertasks packages complete site-inspection-corrective-actions -f values.yaml

Verify the download

File SHA-256
b8c38adf37464c3059eac19db36558353e08417ead094a5dd87ec0fec60fd6a9
Package checksum (what is signed)
sha256:0441195e84101dd1819b546ad7634497e21d09fc135732fa2333ce8be7555b91
Signer
UserTasks Gallery · 49:f3:04:90:47:02:4d:07:28:61:3d:dc:bb:aa:db:11

shasum -a 256 site-inspection-corrective-actions-1.0.0.utpkg should print the file SHA-256. How gallery packages are signed.

Versions

Version 1.0.0

  1. v1.0.02026-10-31First release.

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

Related

Browse the whole gallery