Utah / Housing-plan and water records
For a Utah housing development, separate the proposed unit count from the water evidence needed to support it. Start with the project version being evaluated, then identify the water-right documents and service arrangement behind the concept. Keep a database summary, a pending change and a provider response distinct so a planning yield does not silently become a confirmed infrastructure capacity.
Utah Division of Water Rights query guidance informs this editorial method. No project yield, water-right status or service capacity has been independently established.
What changes the decision
Utah’s Division of Water Rights describes its online database as limited and points to scanned documentary files, noting that the documents generally control when discrepancies arise. Its query resources include right identifiers, names and location-related searches. Preserve the actual file reference and document version before summarizing the water evidence in the acquisition brief.
Source 1Ask the development team to identify the exact plan version, proposed unit types and phase sequence. Record where the count comes from and which parts remain conceptual. A land-use scenario may be useful for screening, but it should not imply that the water demand or service requirements for that scenario have already been evaluated.
Identify the planned water provider or supply arrangement and request the response tied to this project. Ask the water specialist to explain which right-file questions are relevant. Retain both workstreams so a historic document or a pending change is not misrepresented as a present commitment to serve the buyer’s proposed unit count.
Read the records together
| Evidence | What it establishes | Next decision |
|---|---|---|
| Concept or entitlement plan | A described housing layout and its stated approval status. | Fix the project version and assumptions being evaluated. |
| Water-right documentary file | The documents supporting a specialist’s right and use review. | Resolve conflicts with summary fields or missing amendments. |
| Project service response | The provider’s position for the specified proposal. | Identify conditions and infrastructure work before relying on the scenario. |
Put it to work
The kit gives the acquisition and development teams one place to connect the unit proposal with its water evidence. It records the remaining decisions without pretending to calculate an approved project yield.
Attach the current concept or approved plan and identify its status. List the proposed uses, phases and unit assumptions in plain language. Keep alternative layouts separate so a response obtained for an earlier version is not automatically attached to a larger or materially different proposal.
Record the water-right identifiers supplied by the seller or project team and use the Division’s official query resources to locate the relevant file path. Preserve document dates and references. When a database field and a supplied document disagree, flag the conflict for the specialist rather than choosing the more favorable value.
Source 1Provide the same plan version and demand assumptions to the appropriate service reviewer. Request clarification of conditions, required work and responsibilities. Keep the provider’s exact scope visible and separate a preliminary discussion from a documented response that addresses the intended development.
Have the planner, water specialist and engineer identify the conclusions each can support and the evidence still required. Export the worksheet with one task per unresolved dependency. State the housing scenario as conditional wherever its water or service assumptions remain unreviewed.
Before the next conversation
It can identify records to review, but it does not itself establish the project’s service capacity or approved yield. Trace the underlying documents and obtain the appropriate project-specific interpretations. Keep the unit plan, right-file conclusion and provider position as separately referenced parts of the acquisition case.
Record it as a pending proposal with its document reference and status date. Ask the water specialist what conclusion, if any, can presently be supported. Do not promote the requested outcome into an existing right or a committed service assumption for the buyer’s development.
AI can index scanned document dates, cross-reference right identifiers and compare plan versions with provider correspondence. Require a document location for every extracted condition and flag conflicting summaries. The planner, water specialist and engineer should approve interpretations that affect the unit scenario or infrastructure assumptions.
From the page to your next task
Build an editable right-file-to-housing-plan bridge, retain document references and open decisions, then export your team's working file.
Scope: Housing water evidence
Edition 2026-09-30.1
Evidence and scope
Utah Division of Water Rights · Checked 2026-09-30
Database-query options and the distinction between summary information and documentary files.
