Will-serve letters for land development: what does the response cover?

Read a utility will-serve letter against the project it addresses. Check the provider, service, housing proposal, conditions and any stated capacity reservation before using it in a land acquisition decision. A response about water for one concept leaves different questions open from a wastewater approval for a revised community.

The document's title alone cannot settle those questions. Charlotte Water, for example, renamed its Willingness To Serve review to Preliminary CAP Review; that preliminary approval does not reserve wastewater capacity. Its Full CAP approval has a different scope and a two-year reservation. Those are provisions of Charlotte's Capacity Assurance Program, not a national definition of a will-serve letter.

This guide, written by the Pillar team, offers a manual way to record what a response supports and what still needs an answer. Use the utility service response worksheet alongside the broader land feasibility study record.

Identify the service and the actual document

Create separate entries for water and wastewater, even when one organization handles both. Record whether the file is a submitted request, an acknowledgment, a preliminary response, or an issued approval. Keep the document and its date with the entry.

Tri-County Joint Municipal Authority's will-serve request form explicitly identifies water service and asks for the property, APN, project description and a layout with connection details. The form is an application for a response. Completing it does not supply an issued commitment or an answer about sewer service.

If the service, provider or document stage is unclear, write the unresolved question beside the file. A generic “utilities confirmed” field would conceal which answer the team actually has.

Match the response to a named housing scenario

Give each proposal a version and date. In the worksheet, record its parcel identifiers, housing type, proposed unit count and phasing. Retain the plan or exhibit supplied to the provider and identify any connection location under discussion.

For demand figures, keep the quantity, units, calculation basis and preparer together. Ask the responsible utility reviewer or engineer which inputs the provider requires. Leave an unavailable demand figure marked unknown; do not calculate one from an assumed national allowance.

Raleigh's water and sewer review guidance asks availability inquiries to include the address, intended utilities and size/type of service. Its page also routes subdivision, site-plan and main-extension work through applicable review processes. That is a Raleigh example of why an initial availability inquiry and later project reviews need their own records.

When a layout, unit count, phase or demand assumption changes, flag the earlier response for a scope check. Ask whether it remains applicable and save the answer with the revised proposal. Do not silently carry its status into the new scenario.

Read the reservation terms separately from the remaining work

Extract what the provider actually says about capacity reservation. If the document is silent, record “not stated” and assign a follow-up question. Keep any approval date, expiry, renewal requirement or project milestone with the source clause. A calendar reminder helps the team follow a stated term; it does not create or extend a reservation.

Then record the infrastructure and review questions still open. Charlotte's Full CAP description illustrates the distinction: its approval does not ensure that additional infrastructure conveying flows to the public system will be built or adequate, and its analysis does not verify low-pressure sanitary sewer capacity. The same program says changes in development flows can require notification or reapplication. Check the current Charlotte requirements for projects there; obtain the actual provider's requirements elsewhere.

For the acquisition record, give each unresolved item an owner and the evidence needed to close it. Possible questions include the proposed connection route, work needed to reach it, separate reviews, responsibility for that work and the scope of any cost input. These are prompts for project-specific follow-up, not a universal approval checklist.

Worked example: a response for an earlier concept

Consider a fictional acquisition team comparing Concept A, with 42 homes, and a revised Concept B, with 56 homes. The counts and documents below are invented to demonstrate the worksheet. No site or customer result was studied.

The team's file contains a preliminary water response addressed to Concept A. In this example, it asks for a later demand submission and says nothing about a capacity reservation. The file contains no wastewater response.

The team records water for A as “preliminary response received; demand submission outstanding; reservation not stated.” Wastewater remains “response missing.” For B, the team asks whether the water response applies to the changed proposal and what additional inputs are needed. It does not label either concept fully served.

The next reviewer receives both concept versions, the water response, the open wastewater inquiry and named follow-ups. A preliminary cost note that excludes unresolved utility work stays labeled with that exclusion; the missing cost is not entered as zero.

Use the response in the next decision

Complete one worksheet entry per service, response and scenario. Carry its supported conclusion and unresolved conditions into the feasibility review. Keep the issued file available so a colleague can trace the summary back to the provider's words.

For the earlier parcel and map checks, use the desktop screening checklist. For the broader planning, site and commercial dependencies, return to the feasibility handoff. The utility worksheet supplies the service evidence within that review.