Nevada / Southern Nevada service inquiry
Nearby infrastructure becomes useful acquisition evidence when someone can explain how it would serve the proposed project. For Nevada development land, separate the location of a water source from provider responsibility, connection design and a documented service position. This guide uses Southern Nevada Water Authority’s engineering inquiry route to build a better first request, then keeps the unanswered project questions visible.
Southern Nevada is the worked example. SNWA’s inquiry route is not a statewide utility service map or confirmation for an individual parcel.
What changes the decision
SNWA’s contact page directs developers seeking the nearest available water source to Engineering Services. It also describes an engineering record-drawing request route for licensed Nevada professional engineers. These are different information requests. Frame the project and location clearly, and record the response as source information unless it expressly addresses a broader service question.
Source 1Ask the project engineer to identify what remains between the described source and the proposed buildings: connection point, route, potential third-party crossings and site distribution. Keep each item attributed to the person or document that supports it. A line shown near the property does not establish the cost or responsibility for completing those connections.
A warehouse, commercial kitchen and irrigated recreation use can prompt different service questions. Give the engineer the actual proposed activity, phasing and fire-protection assumptions. A useful acquisition memo records the specific scenario discussed, so an early response about one concept is not recycled as confirmation for a materially different development.
Read the records together
| Evidence | What it establishes | Next decision |
|---|---|---|
| Nearest-source inquiry | Information supplied about a water source relative to the proposal. | Identify the provider and project questions still unanswered. |
| Engineering drawings | A referenced infrastructure description with its own date and scope. | Review route, connection and design assumptions with the engineer. |
| Project-specific service response | The provider’s stated position for a described project. | Check conditions, scope and validity before using it in underwriting. |
Put it to work
Use this worksheet before paying for a detailed feasibility narrative that rests on an undefined water assumption. It assembles the project description and questions needed for a meaningful technical review.
Provide a location plan, proposed uses, construction phases and the demand assumptions currently available. Mark estimates as estimates. Ask the project engineer to identify missing inputs before making a capacity inquiry so the response can be tied to a recognizable version of the project.
Use SNWA’s engineering contact route for the nearest-source question in its Southern Nevada context. Have a properly qualified requester use the record-drawing route when needed. Save the question and answer together; record who must confirm retail service and project-specific conditions.
Source 1Ask for an annotated route from the proposed connection to the operating areas. Track off-site work, third-party crossings, fire-service questions and design responsibilities separately. Request the documents behind each assumption rather than treating a conceptual utility line as a construction-ready solution.
Write the service assumption in plain language and list what could change it. Keep preliminary engineering information separate from the provider’s actual commitments. Export the request and review sheet so the buyer can decide which questions must be resolved before relying on the development scenario.
Before the next conversation
The research method travels; the authority does not. Outside the Southern Nevada example, identify the provider and official engineering inquiry process for that location. Do not route a statewide property list through SNWA or describe its response as evidence of service in another jurisdiction.
Ask for the inquiry correspondence, the project description it addressed, relevant drawings and the current responsibility schedule for connection work. An answer without its original question is easy to misread. A changed use, phase or demand assumption should remain visible in the review.
AI can compare project versions, extract explicit conditions and build a document-linked question list. It should not convert words such as nearby or preliminary into a capacity commitment. Have the engineer and provider clarify ambiguous language before it enters the investment committee’s approved assumptions.
From the page to your next task
Build an editable engineering-inquiry-to-service register, retain document references and open decisions, then export your team's working file.
Scope: Development service
Edition 2026-09-30.1
Evidence and scope
Southern Nevada Water Authority · Checked 2026-09-30
Developer water-source inquiries and engineering record-drawing request routes in Southern Nevada.
