Conversion Impact Tracking

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

Problem

Districts and the state can only see the conversions they pay for. Homeowners who follow water-wise guidelines but never apply for a rebate — the majority of organic conversions — leave no trace: "as far as the districts are concerned, they're lost." There is no mechanism today to capture that a non-program conversion happened, measure its impact, or keep that homeowner engaged after the project is done.

Concept

1. Completion check-in (outside rebate programs)

A lightweight check-in flow when a project wraps: "once your project is complete, submit it… we'll provide suggested maintenance." The check-in captures completion (with after photos) for conversions that never touch a rebate program, giving districts/state visibility into the organic conversion population for the first time.

This fills the pre-modeled Complete tab stub in the core job container — its named sections ("reviews · after photos · maintenance guide") are verbatim this feature. See the Job Container & Lifecycle Workflow spec — Scope. No re-architecture is needed; this idea builds out content the core object already reserves space for.

2. Reward: personalized maintenance guide

The check-in's reward is a personalized maintenance guide generated from the job's own plant roster — per-plant care by season, watering through establishment, pruning. This is the engagement gateway, not bait-and-switch: the homeowner gets genuine ongoing value, and the platform earns the continued relationship. The equivalent artifact is already designed as the parkstrip program's Plant Care Guide (PDF + portal, generated from the plant DB) — see parkstrip workflow research, Phase 7. Care content is supplied by the plant database (Horticulturist domain).

3. Opt-in water-usage sharing + good-citizen score

With explicit opt-in, the homeowner shares their property's water usage with their district and/or the state, and receives a good-citizen score / star rating vs the property's water budget — "virtue signaling with real substance." A possible district bill discount rides on the score (the rate-incentive hook already appears in the parkstrip handoff flow). The score consumes the water-budget number surfaced per design (see Site Planner redesign — coverage & water feedback); the district-bound usage feed is researched in turf-rebate report §A.4 Irrigation Data Monetization. Depends on the water budget engine.

4. Opt-in "great examples near me" gallery

An opt-in gallery on Slow the Flow showing completed conversions near the visitor — general-area geographic display (never exact address), participation strictly opt-in. Justification is documented: the 132-per-100 peer-effect multiplier — for every 100 rebated conversions, 132 additional nearby conversions follow without program spend (see turf-rebate report §3.5 Program Scale). Neighbor visibility is the cheapest conversion driver a district has. Surfaces on the Slow the Flow v2 Portal; extends the photo + consent plumbing designed for the parkstrip completion photo wall.

Privacy: consent model — record explicitly

The current privacy framework restricts property-level data to the homeowner + district admin (the State Program Admin reads across districts but cannot operate at property level) — see the parkstrip RBAC role matrix.

Every sharing surface in this idea deliberately INVERTS that default via opt-in consent: usage sharing, the score, and gallery participation are each individually consented, following the existing partner_consent pattern ("no partner-facing surface ever receives the user's data without consent") from Anonymous Design Save & Account Creation. The rule for implementation: extend the consent model — never weaken the defaults. A property with no opt-in behaves exactly as today.

Dependencies

• Core job container Complete tab (job-container-workflow) — the check-in's home; core ships regardless.
• Water budget engine (for the score's denominator) — placement under discussion in the Site Planner cluster.
• One-reconciled-account identity layer (anonymous-design-save-auth) — a coherent property history requires one account per customer.
• Slow the Flow v2 Portal — the gallery's display surface.

Stages

• Phase 1 — Completion Check-in + Maintenance Guide: stands alone; fills the Complete-tab stub.
• Phase 2 — Usage Sharing + Good-Citizen Score: opt-in sharing, star rating vs water budget, bill-discount hook.
• Phase 3 — Near-Me Gallery: opt-in general-area gallery on Slow the Flow.

Open Questions

1. Which districts will honor a bill discount tied to the score, and on what basis? (Program design with district/state partners.)
2. Score methodology: rating bands vs the property's water budget — needs the water budget engine's per-jurisdiction configuration.
3. Gallery geo-granularity: what "general area" resolution is both useful and safely non-identifying?

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 |