Subdivision planning guides

Research what to verify before relying on a fee, setback, design, soil, utility, or builder assumption for a specific lot.

These are independent research guides, not official association documents. Follow the source links and confirm current requirements for the exact parcel.

Desert Color

St. George, Utah 84790

Source-aware

Desert Color is a large master-planned community in south St. George. Neighborhood, lot, and product type affect the applicable design and association requirements, so buyers should confirm the current documents for the exact parcel.

Review planning questions →

Kayenta

Ivins, Utah 84738

Source-aware

Kayenta is a design-controlled desert community in Ivins. Requirements can differ by lot and change over time, so current Architectural Control Committee materials must be reviewed before design or budgeting decisions.

Review planning questions →

Why the parcel comes first

A subdivision name is not a buildable scope. Before comparing builders, identify the lot, recorded plat, title exceptions, municipality, zoning, association, design-review body, utility status, and seller representations. Rules can differ by neighborhood, phase, product type, and amendment. A number copied from a nearby home is not evidence for the parcel you may buy.

Ask for dated source documents and keep a record of who supplied each one. If a fee, setback, height, material, landscape, or approval claim cannot be tied to the exact lot and a current controlling source, carry it as unconfirmed.

Keep approvals separate

Association or architectural approval and municipal permission solve different problems. A design-review committee can evaluate community standards while a city reviews zoning, building, grading, utilities, sensitive lands, or other public requirements. Approval from one does not promise approval from the other.

Build a responsibility table naming who prepares, submits, pays for, responds to, and closes each review. Put included review rounds and redesign assumptions into the architect and builder agreements before the schedule depends on them.

Make builder proposals comparable

Give every builder the same survey, geotechnical information, program, finish expectations, and dated governing documents. Require proposals to separate fixed scope from allowances and exclusions. Site work, rock, retaining, drainage, utility extensions, engineering, permit fees, design review, landscaping, and price escalation should not disappear inside an undefined total.

These guides do not certify a builder or replace professional advice. They help a buyer assemble the same evidence for each conversation so differences in price reflect real differences in scope.

Decision gate: do not treat a lot as construction-ready until the title, survey, geotechnical information, governing design documents, municipal path, utilities, and proposal assumptions describe the same parcel. If one input is still missing, label the affected cost and schedule item as unresolved instead of converting it into a confident estimate.