Land assemblage: check the parcels behind a proposed housing site

For a homebuilder evaluating a land assemblage, start with a record of the individual parcels and what each contributes to the proposed site. Identify the parcels needed for the current concept, the evidence supporting each owner's involvement, and the questions that remain open. Keep that record when the proposed boundary changes.

This guide uses land assemblage to mean considering neighboring parcels together for a proposed acquisition or development. It describes a research method. The method does not combine legal lots, establish title or seller authority, or determine a housing yield.

The useful deliverable is a parcel register linked to named site configurations. The downloadable research register provides a manual template. A map showing one outline can accompany the register, but each parcel should remain traceable to its own sources and follow-up.

Give every source parcel its own record

Choose a site reference such as Research Site A. Under it, list every parcel being considered with its jurisdiction and source identifier. Include the source URL or recording reference, observation date and any identifier changes that need reconciliation. For each observation, state what the source supports and what remains unverified. Preserve any later professional finding with its author, date and scope. An address can help someone recognize the location; use the parcel identifiers to distinguish the records.

Keep each source's acreage beside its definition. If the parcel export, deed and survey disagree, record the disagreement instead of selecting a convenient total. The acreage reconciliation guide explains how to preserve those distinctions. Adding rows from mixed sources does not produce a verified site area.

Use one row per distinct source parcel. If the same parcel appears in two sourcing exports, attach both source references to that row. If a record appears to contain several underlying lots, preserve that question for the title and survey reviewers.

Connect owner evidence to the parcels it actually covers

Give each reported owner or entity a separate reference and connect it to the relevant parcels. Preserve the name exactly as it appears in the source, together with the document and date. Similar names, a common mailing address or a shared business contact can suggest a research task; they do not finish the ownership review.

Keep contact history separate from evidence of authority or control. A broker's description, a conversation with a business representative and a reviewed acquisition document answer different questions. Record what was actually received and ask the appropriate professional to establish its scope. Do not mark all parcels as controlled because one contact discusses the whole site.

For an entity-owned parcel, the LLC owner research guide provides a way to connect property and business records without treating a registry contact as a verified owner.

Record which parcels the current concept needs

Create a configuration identifier, such as A1, for an exact proposed set of parcels. For each included parcel, write its intended role and the reason it is needed. Possible roles include a main site area or a possible route being investigated. These are proposed roles, not findings that the parcels can legally or physically perform them.

Then ask what changes if one parcel is unavailable. The answer may be that the current concept needs to stop, or that a separate configuration deserves investigation. Write the changed assumption explicitly. Avoid carrying an old map or review forward under the same label after its parcel set changes.

For each dependency, assign the evidence that could resolve it and the person responsible for obtaining that evidence. If a parcel is included because a possible entrance crosses it, link the corresponding access evidence record. A neighboring boundary alone does not answer that route question.

Keep local combination review separate from the research group

Ask the responsible jurisdiction how the existing lots and proposed configuration would be reviewed. Supply the parcel identifiers, available recorded descriptions, current boundary drawing and proposed use. Ask which records and professional work it needs before treating any internal boundary as removed.

Raleigh provides a specific example. Its UDO section 10.2.6 describes recombination review and distinguishes recorded maps from recorded instruments. For recombination by instrument, the requirements include a metes-and-bounds description or recorded-plat reference and signatures from all property owners. The section also addresses access, utilities and other conditions. These are Raleigh requirements, not a national application checklist.

Use the applicable authority's response to define the next work. Keep the actual response and its stated conditions with the configuration it covers. If the parcel set or proposed use changes, ask which parts need another review. A sourcing record called “assemblage” does not establish that this process is complete.

Worked example: one opportunity with two configurations

Everything in this example is fictional. It illustrates record keeping, with no measured property, customer result or approved housing plan.

An analyst groups four neighboring parcels into Research Site A. The source records report the following:

• P1: 8 reported acres, owner reference O1, proposed main site area. Title and boundary records need reconciliation.
• P2: 6 reported acres, owner reference O1, proposed main site area. Confirm which documents cover this parcel.
• P3: 2 reported acres, owner reference O2, possible entrance route. Obtain route documents and a scoped access review.
• P4: 1 reported acre, owner reference O3, optional additional area. Establish whether owner involvement is supported.

The source acreage sums to 17 acres. This is a sum of reported figures, not surveyed or developable area. Configuration A1 includes all four parcels. No acquisition control or entrance suitability has been established.

If P4 is excluded from further investigation, create A2 containing P1, P2 and P3. Its reported-acreage sum is 16. A2 still depends on the unresolved P3 route. Carry that same open question into A2, with its evidence request and responsible reviewer; changing the parcel set has not answered it. Removing the optional parcel has not resolved access.

If P3 becomes unavailable, mark A2's assumed route unavailable. Do not keep that configuration marked ready because P1 and P2 remain in the sourcing list. Any alternative connection needs its own investigation, with the changed parcel set and assumptions recorded.

Hand off a configuration someone else can reconstruct

The review packet should identify the configuration, its included and excluded parcels, and the sources behind each row. Attach the owner-to-parcel relationships, dependency questions and current follow-up assignments. A colleague should be able to see why an optional parcel was removed and which unresolved parcel still prevents a decision.

Use the manual parcel-register worksheet to prepare that packet. Assign each unanswered question to a named person and the appropriate reviewer or authority, with the scope of the requested response. Keep overlapping legal, survey and design questions separate when they need different reviews. Before a configuration advances, carry its unresolved questions into the land feasibility review. Preserve earlier configurations so later reviewers can distinguish a changed proposal from newly established evidence.