Know which inspections are due, where and why

Every state writes its own rules, and it always rains on Friday night

If you do erosion control or site work in more than one state, you're tracking different inspection frequencies, rainfall thresholds and deadlines for every permit. A qualifying rain event on a weekend starts a clock. Miss the post-storm inspection and the SWPPP log has a gap an inspector will find.

Meanwhile the inspector in the field fills out a form for the compliance record, and someone in the office re-enters the same visit to bill it. The GC needs to sign off. The paper, or the PDF, goes to three places.

• Inspection frequencies and rain thresholds that vary by state and permit
• Rain events tracked by someone checking the weather
• The same site visit recorded twice, once for compliance and once for billing
• GC signatures chased by email after the fact

An obligation engine for field compliance

• Multi-state rule engine

  Stormwater inspection rules by state and permit type, written as rules your compliance lead can read and check. Each active site gets a list of what's owed and when.

• Rain-triggered scheduling

  Rainfall data for each site is checked against its permit threshold. When a qualifying event hits, the post-storm inspection goes on the schedule with its deadline.

• One capture, two records

  The inspector records the visit once: findings, photos, corrective actions. That single capture produces the SWPPP log entry and the billing record.

• GC signature capture

  The GC or site representative signs on site or by link. The signed record attaches to both the compliance log and the invoice backup.

From permit to signed inspection

1. 01

   Step 1: Map your obligations

   We list the states, permit types and sites you cover, and your compliance lead confirms the rules before we build them in. Your team owns the interpretation of each permit.

2. 02

   Step 2: Set up sites and triggers

   Each active site gets its permit, its inspection frequency and its rainfall threshold, plus the data source used to check for qualifying events.

3. 03

   Step 3: Put capture in the field

   Inspectors use a mobile form built to your checklist. One visit, one capture, one signature.

4. 04

   Step 4: Feed your records and your ERP

   Compliance records go to your log. Billing records go to your accounting system through a ledger layer that doesn't depend on which ERP you run.

Works with your field and billing systems

• Trimble Viewpoint Vista
• NetSuite
• QuickBooks
• Procore
• Microsoft 365 and SharePoint
• Google Workspace
• Rainfall data sources for each site location

An obligation engine prototype for an erosion-control contractor

We built an obligation engine prototype for an erosion-control contractor. It includes a multi-state stormwater rule engine, rain-triggered inspection scheduling, a single field capture that produces two records (compliance and billing) with GC signature capture, and a ledger layer that isn't tied to one ERP.

• Multi-state stormwater rule engine
• Rain-triggered inspection scheduling
• One field capture, two records, GC signature
• ERP-agnostic ledger layer
• Status: prototype

Common questions