All templates
Public Works / DOT

Snow Response Truck Readiness

Pre-storm and post-storm photo evidence for plows, spreaders, lights, tires, leaks, and body condition.

Asset class
Plow truck, salt truck, dump truck, or utility truck
Trigger
Pre-season readiness, 24 hours before deployment, after storm return, or after a repair on plow/spreader equipment.
Recipient
Public works driver, fleet technician, or shift supervisor
Decision
Release for deployment, hold for shop review, or attach evidence to a storm work order.
Duration
3-5 minutes
Policy
pol_public_fleet_readiness

Required evidence

Photo slots for this workflow

Each slot becomes a guided capture step in the no-app inspection link. Required shots must be captured before the session can be finalized.

ShotInstructionsVerifies
Asset tag, plate, or unit numberFrame the unit number or plate clearly enough to identify the asset.Asset identity
OdometerCapture the odometer and any warning lights visible on the dash.Mileage and warning context
Front view with plow mountedShow the full front of the vehicle, plow blade, mount, and headlights.Plow attachment and front condition
Driver side and tiresStep back so both driver-side tires and body panels are visible.Tires, panels, mirrors, and side condition
Rear spreader or dump bedShow spreader, chute, bed, tailgate, and rear lights.Spreader readiness and rear condition
Headlights and warning lightsCapture the vehicle with required service and warning lights on.Visible lighting readiness
Ground under engine bayPhotograph the pavement under the engine and hydraulic equipment.Visible fluid leaks

Sample report status

Hold for review

All required photos were captured. One ground-condition photo was flagged for shop review before deployment release.

Exception routing

  • - Ground-condition photo needs shop review

Integration output

Use the payload below to create a signed inspection link and route the final record by webhook.

API payload

Create this inspection link

This is the inspection-session payload shape for the template. Agencies can change labels, add metadata, or map the fields to an FMIS, work-order, reservation, or incident system.

snow-response-truck.json
{
  "policy": "pol_public_fleet_readiness",
  "recipient": {
    "name": "Avery Johnson",
    "email": "recipient@agency.gov"
  },
  "context": {
    "asset_id": "PW-2047",
    "work_order_id": "WO-91342",
    "workflow": "snow_response_predeployment",
    "department": "Public Works",
    "event_id": "storm-2026-01",
    "site_external_id": "north-yard"
  },
  "required_shots": [
    {
      "slot": "asset_tag",
      "label": "Asset tag, plate, or unit number",
      "instructions": "Frame the unit number or plate clearly enough to identify the asset.",
      "required": true
    },
    {
      "slot": "odometer",
      "label": "Odometer",
      "instructions": "Capture the odometer and any warning lights visible on the dash.",
      "required": true
    },
    {
      "slot": "front_plow",
      "label": "Front view with plow mounted",
      "instructions": "Show the full front of the vehicle, plow blade, mount, and headlights.",
      "required": true
    },
    {
      "slot": "driver_side_tires",
      "label": "Driver side and tires",
      "instructions": "Step back so both driver-side tires and body panels are visible.",
      "required": true
    },
    {
      "slot": "rear_spreader",
      "label": "Rear spreader or dump bed",
      "instructions": "Show spreader, chute, bed, tailgate, and rear lights.",
      "required": true
    },
    {
      "slot": "lights",
      "label": "Headlights and warning lights",
      "instructions": "Capture the vehicle with required service and warning lights on.",
      "required": true
    },
    {
      "slot": "leaks",
      "label": "Ground under engine bay",
      "instructions": "Photograph the pavement under the engine and hydraulic equipment.",
      "required": true
    }
  ],
  "ttl_seconds": 86400
}

Keep the decision human, keep the record inspectable

This template is designed to capture better evidence. It does not decide discipline, claims, replacement, or release by itself.

Get in Touch

Questions about pricing, integrations, or custom deployments? We'd love to hear from you.