Moisture / Audit-Data Import

Status: Draft (intake from 2026-07-06 Utah Water Ways funding meeting) | ClickUp: none yet

Problem

District water-efficiency teams already visit properties and capture audit data — soil conditions, moisture readings, catch-can / distribution-uniformity measurements. That data currently dies in the district's own tooling. To use it in a SimplyScapes site plan, someone would have to re-enter every value by hand. There is no import path.

Concept

The district's team exports its audit as a file; the homeowner (or district staffer) uploads it into the site plan; the plan's DU / soil / moisture values auto-populate — "no manual clicking needed."

Import mechanics — reuse the proven pattern

Reuse the CSV import/reconcile pattern designed in the rebate-compare district research: column-mapping profiles per source format, a dry-run reconcile that previews changes before applying, and a re-import key for matching later files back row-by-row. See D2 district bulk grid — CSV/Excel import-export & reconciliation. This idea applies the same ETL surface at single-plan scale.

What the data feeds

• Distribution uniformity (DU): measured DU from a real catch-can audit refines or replaces the design-computed DU — the mechanism that otherwise substitutes for the $500–2,000 field audit (see automated turf irrigation scheduling report §4, Design-Computed DU). A measured value is strictly better input to the runtime formulas.
• Soil / infiltration: populates the per-zone soil parameters the scheduling data model already specs (soil_infiltration_rate et al.).
• Moisture readings: seeds the moisture model (FAO-56 water-balance approach researched in the same report).

A no-schema-change landing zone exists: the job's site_analysis jsonb field (GeoJSON-capable) can hold the raw audit payload while typed values flow to the zone model — see the job container spec data model.

Explicitly distinct from Rachio Moisture API Integration

Do not conflate this idea with Rachio Soil Moisture API Integration:

| | Rachio Moisture API Integration | Moisture / Audit-Data Import (this idea) | |---|---|---| | Direction | PUSHES SimplyScapes-computed moisture TO smart controllers (virtual soil-moisture sensor) | IMPORTS district-captured audit data INTO the site plan | | Source of truth | The design/model computes; controller consumes | The field measurement is the input; plan consumes | | Actor | Homeowner's controller integration | District water-efficiency team |

The two are adjacent prior art for each other, not overlapping scope — cross-referenced in both directions via related links.

Strategic Fit

Districts get their field work captured somewhere it compounds (the audit improves the design, the schedule, and the water-budget math), and SimplyScapes becomes the natural landing surface for district site visits — a lightweight, data-first integration with district operations that requires no API partnership to start (file export/upload works with any tooling).

Dependencies

• Per-zone irrigation data model (from the scheduling spec) as the typed destination for DU/soil/moisture values.
• CSV import/reconcile pattern (design precedent; no shared code yet).

Stages

• Phase 1 — File Import: file parse + column-mapping profiles + dry-run preview + auto-populate DU/soil/moisture on the site plan.

Open Questions

1. Which district audit formats exist in the wild (spreadsheet templates, proprietary exports)? First column-mapping profiles should target the formats Utah districts actually use.
2. Conflict policy: when a measured value disagrees with a design-computed one, does measured always win, or is it flagged for review (the dry-run's decision surface)?
3. Who uploads — homeowner, district staffer, or both (permissions)?

Version History

| Date & Time (MT) | Author | Summary | |---|---|---| | 2026-07-09 06:19 PM MT | Dan | Initial brief from 2026-07-06 UWW funding meeting + 2026-07-09 CEO session |