Lot Constraint Register: One Page for Every Site Assumption

A residential lot constraint register keeps every site assumption, from setback lines to stormwater notes, on one page that travels with the project from due diligence through construction. Instead of scattering findings across emails, PDFs, and someone's memory, the register records each constraint with its source, the plan sheet it affects, who owns resolving it, its current status, when it expires or needs re-verification, any conflicts it creates with the design, and the evidence that eventually closes it out.

This article explains how such a register can be structured and used by an owner and project team. It does not replace zoning review, engineering, environmental assessment, or any determination made by a jurisdiction. York County and City of Charlotte pages are cited as examples of the kind of public information a register should point to. Requirements change, so any constraint entry tied to a code section, review process, or agency contact should be verified against the current official source and confirmed with the authority having jurisdiction before a design decision is finalized.

What Current Public Sources Establish

Local jurisdictions publish zoning and review information that forms part of the factual floor for any lot constraint register. York County, South Carolina maintains a Zoning page describing how zoning districts, permitted uses, and related standards apply within the county. That page is the starting point for understanding what a specific parcel is zoned for and what county staff expect an applicant to bring to a review, but it is not a substitute for a parcel-specific determination.

The City of Charlotte publishes a page on Individual Residential Lot Reviews, which describes a process for reviewing single lots as part of getting started on a residential project. Charlotte also maintains a Stormwater Projects page describing stormwater program activity relevant to development review. These pages illustrate that constraints are not limited to zoning district lines. They can include drainage easements, stormwater requirements, and review steps tied to a specific address or parcel, and they can change as programs and ordinances are updated.

Because these sources are maintained by the respective county and city governments, any date, fee, submittal list, or process step mentioned on them should be treated as current only as of the day it is checked. A register entry that cites one of these pages should record the date it was last confirmed and should be re-checked before it is relied upon for a submittal or a design decision.

York County Zoning: https://www.yorkcountysc.gov/377/Zoning
City of Charlotte Individual Residential Lot Reviews: https://www.charlottenc.gov/Growth-and-Development/Getting-Started-on-Your-Project/Individual-Residential-Lot-Reviews
City of Charlotte Stormwater Projects: https://www.charlottenc.gov/Services/Stormwater/Projects

Why Constraints Disappear Between Due Diligence and Construction

Due diligence often produces a burst of findings: a survey shows an easement, a zoning letter notes a setback, a stormwater review flags a detention requirement. Those findings are usually captured in a report, a set of marked-up plans, or a string of emails at a single point in time. As the project moves into design development, permitting, and eventually construction, that original documentation is frequently left behind while the design keeps evolving.

The result is that a constraint identified early can quietly vanish from later plan sets, not because it was resolved, but because nobody carried it forward. A revised site plan, a new civil engineer, or a change in scope can each create a gap where the original finding is no longer visible to the people making current decisions. By the time a footing is staked or a permit reviewer asks a question, the constraint may need to be rediscovered from scratch, sometimes after money has already been spent on a design that conflicts with it.

A setback noted in an early zoning letter may not appear on a later revised site plan.
An easement shown on a survey can be omitted from a civil grading plan if the files are not cross-referenced.
A stormwater condition raised in a preliminary review may not be repeated in the final construction documents.
Staff or reviewer turnover can mean a verbal clarification is never written down anywhere the team can find later.

What a Lot Constraint Register Should Document

A lot constraint register is a single, continuously updated page or spreadsheet that lists every known site assumption in a consistent format. Each entry should be traceable back to where it came from and forward to how it was resolved, so that anyone joining the project later can understand the current state of every constraint without having to interview the whole team.

At minimum, each entry should capture the source of the constraint, whether that is a jurisdiction's published zoning page, a recorded easement, a stormwater review comment, or a note from an owner or design professional. It should also reference the specific plan sheet or drawing where the constraint applies, name the person or firm responsible for resolving or confirming it, note the current status, record any expiration or re-verification date, flag any known conflict with the design, and store the evidence that eventually closes the item.

Source: the document, page, or person the constraint came from, with a link or file reference where possible.
Plan reference: the specific sheet, detail, or drawing number the constraint affects.
Owner: the person or firm responsible for tracking and resolving that item.
Status: open, in review, resolved, or requires re-verification.
Expiration: any date after which the finding should be rechecked, such as a review letter with a stated validity period.
Conflict: a short note if the constraint currently contradicts the design or another constraint.
Closure evidence: the approval letter, revised plan, or written confirmation that shows the item is resolved.

Step-by-Step Owner and Project-Team Review

Building a useful register starts with collecting everything that already exists. That includes the survey, any zoning correspondence, environmental or geotechnical reports, utility locates, and any notes from preliminary conversations with a jurisdiction. Each of these documents is combed for statements that describe a limit, requirement, or condition tied to the specific lot, and each one becomes its own row in the register rather than staying buried in a report.

Once the initial list is built, the owner and project team should walk through it together at defined points, such as before finalizing a concept plan, before submitting for permits, and again before construction begins. At each checkpoint, every open item is reviewed to confirm whether it is still accurate, whether the design has changed in a way that affects it, and whether the assigned owner has made progress. Items that were resolved should have their closure evidence attached, and items that are still open should be flagged clearly so they are not lost in the next round of design changes.

Collect existing documents: survey, zoning correspondence, environmental and geotechnical reports, utility information.
Convert each documented limit or requirement into its own register entry with a source and plan reference.
Assign an owner to each entry so responsibility is clear rather than assumed.
Review the full register before finalizing a concept plan, before permit submittal, and before construction start.
Update status and attach closure evidence as items are resolved, rather than deleting the row.

Responsibilities, Dependencies, and Hold Points

A register is only useful if responsibility for each item is clear and if the team agrees on when work should pause until an item is resolved. Some constraints, such as a required setback confirmed by a jurisdiction, may need to be treated as a hold point, meaning design or construction activity that depends on that dimension should not proceed until the item's status is marked resolved with evidence attached.

Other constraints may be dependent on each other. A stormwater detention requirement, for example, may depend on a drainage easement location, which may in turn depend on a survey correction. Recording these dependencies in the register, even briefly, helps the team see which items are blocking others and helps prevent a situation where a downstream decision is made before an upstream constraint has actually been confirmed.

Identify which register items are true hold points that should pause dependent design or construction work.
Note dependencies between items, such as a drainage feature that depends on a confirmed easement location.
Assign a single owner per item, even when multiple parties are involved, so follow-up has a clear point of contact.
Revisit hold points at each project checkpoint rather than assuming they were cleared earlier.

Common Coordination Failures

Several patterns tend to repeat across projects when a constraint register is not maintained. A finding from an early site visit or zoning conversation is written down once and never transferred into the working plan set. A consultant's report sits in an inbox while the civil or architectural drawings move forward without reflecting its content. A verbal answer from a reviewer is treated as final without being confirmed in writing or logged anywhere the rest of the team can see it later.

Another common failure is treating due diligence as a one-time event rather than an ongoing check. A constraint that was accurate at the start of a project, such as a stormwater program note or a zoning interpretation, may need to be reconfirmed if enough time passes before permitting or construction begins, since public program pages and review processes can be updated. Without a register that tracks expiration or re-verification dates, these changes are easy to miss.

A finding is documented once in a report but never carried into the active plan set.
A verbal clarification from a reviewer is relied upon without written confirmation.
Due diligence is treated as a single event rather than something to reconfirm before permitting or construction.
Responsibility for an item is assumed rather than assigned, so it is not actively tracked by anyone.
A design change is made without checking whether it conflicts with an already-documented constraint.

Questions for the Responsible Authority or Qualified Professional

A register organizes information, but it does not replace the judgment of the jurisdiction or licensed professionals who make binding determinations about a specific lot. Before relying on any entry for a design or construction decision, the owner and project team should confirm the current requirement directly with the authority having jurisdiction, since zoning, stormwater, and review processes can be updated after a page is published.

For South Carolina parcels, that generally means confirming current zoning district standards and any required review steps with York County. For projects within Charlotte's jurisdiction, that means confirming individual lot review requirements and any active stormwater program requirements with the City of Charlotte. Any environmental, geotechnical, surveying, or engineering question tied to a specific site condition should be directed to the licensed professional responsible for that discipline, not answered informally within the register itself.

Has the zoning district and any applicable overlay been confirmed directly with York County for this specific parcel?
Does this lot require an individual residential lot review under the City of Charlotte's current process, and what does that review currently require?
Is there an active or planned stormwater project or requirement affecting this parcel under Charlotte's stormwater program?
Which register items require a licensed surveyor, engineer, or environmental professional to confirm or resolve, rather than being resolved by the project team alone?
What is the current expiration or validity period, if any, for a specific review letter or determination already received?

Next Action and Related CDG Resource

Keeping site constraints visible from due diligence through construction is less about any single tool and more about discipline: writing every constraint down once, in one place, with a source, an owner, and a way to prove it was closed. A lot constraint register built this way gives an owner and project team a shared, current picture of the lot instead of a pile of documents that only make sense to the person who filed them.

Readers working through zoning, easement, or stormwater questions on a specific lot can review CDG Carolinas' site planning service page for Lake Wylie, SC as one example of how site planning work is framed, browse the CDG blog for related lot and zoning topics, or reach out through the CDG consultation page to discuss a specific property. Any property-specific zoning, environmental, or engineering question should still be verified with the appropriate authority having jurisdiction or a licensed professional before it is treated as settled.

Review site planning information at /site-planning-lake-wylie-sc/ for related context.
Browse /blog/ for additional articles on lot, zoning, and easement topics.
Use /consultation/ to start a conversation about a specific property with CDG Carolinas.

Questions homeowners ask

What is a residential lot constraint register?

A residential lot constraint register is a single, continuously updated document that lists every known limit, requirement, or condition affecting a specific lot, such as setbacks, easements, or stormwater notes. Each entry records where the constraint came from, which plan sheet it affects, who is responsible for resolving it, its current status, any expiration or re-verification date, any conflict with the design, and the evidence that eventually closes it out. It is a coordination tool, not a substitute for a jurisdiction's determination or a licensed professional's assessment.

Who should own and maintain the register on a project?

Ownership can be shared, but each individual line item should have a single named owner, whether that is the property owner, a design professional, or a project coordinator. The overall register itself should have one point of responsibility for keeping it updated at each project checkpoint, such as before permit submittal, so that it does not become outdated or duplicated across multiple versions held by different people.

How often should constraints be re-verified?

Constraints tied to a jurisdiction's published requirements, an active review process, or a program such as stormwater management should be re-checked whenever meaningful time passes between the original finding and a design or construction decision, and again before any permit submittal. Public sources and review processes can change, so an entry that was accurate at the start of due diligence may need to be reconfirmed with the authority having jurisdiction before it is relied upon later in the project.

Does a constraint register replace zoning or engineering review?

No. The register is meant to organize and preserve information so it is not lost between due diligence and construction, but it does not make a binding determination about zoning, stormwater, environmental conditions, or engineering requirements. Those determinations come from the authority having jurisdiction, such as York County or the City of Charlotte for the sources referenced here, or from the licensed professional responsible for that specific discipline.

Plan the next step

Use this article as a planning aid, then confirm project-specific requirements with the responsible authority and qualified professionals. Review CDG's related service, construction articles, or consultation page when you are ready to organize the next decision.

Official sources and verification

Authority pages, forms, fees, review steps, and code references can change. Verify the current path for the property and scope before relying on a planning assumption.