Skip to content
A-101

Field Inventory & Inspection

From the ditch to the engineer's desk in fifteen seconds.

THE PROBLEM

Field crews collect good data on clipboards and phones, and it dies in a spreadsheet the client never sees.

A phone form for the crew, a hosted layer as the record, an office app for QA and inspection scheduling, and a dashboard for the client.

WHAT YOU GET

  • Field Maps form with required fields, pick lists, and photos
  • Hosted asset layer with a related inspection table
  • Office web app: filters, due list, CSV export, QA flag
  • Inspection-cycle rules and a monthly due list

VARIANTS

Culverts and storm inlets · Signs and guardrail · Hydrants and valves · Street lights, sidewalk ramps, trees · Bridges under 20 ft and low-water crossings

WHO THIS IS FOR

  • Firms doing municipal asset inventories or MS4 stormwater compliance
  • County engineers who need a culvert, sign, or hydrant inventory that stays current
  • Towns that want GASB 34 asset reporting without a GIS department

THREE SIZES

Starter

2–3 weeks

Field Maps, hosted layers, and an ArcGIS Dashboards view. No custom code.

  • • Form design and domains
  • • One manual data load
  • • Dashboard
  • • Training for one crew

Standard

5 weeks

Starter plus the office web app shown here, branded for the client, with the due list and export.

  • • Everything in Starter
  • • Office web app
  • • Inspection-cycle rules
  • • Record set at handover

Full

8–10 weeks

Standard plus integration with the client's work-order system, notifications, and a 12-month retainer.

  • • Everything in Standard
  • • Work-order integration
  • • Email alerts for overdue assets
  • • 12-month support