Market Intelligence
Parcel data pitfalls: why property records alone miss the asset
Parcel records identify land and ownership. A useful asset file resolves the buildings, roof sections, equipment, evidence dates, and people responsible for the work.
Direct answer
Property records alone miss the asset because their counting unit is the parcel or tax account, while the work belongs to a building, roof section, equipment item, or exterior surface. A parcel contains ownership and land-use information without necessarily identifying each structure, the equipment present, its installation date, or the organization buying its service. Link parcels to stable building and asset identifiers, check dated imagery and component records, and confirm responsibility before treating an address as a qualified prospect.
On this page
What does a parcel record actually describe?Why does one parcel fail as one asset?Anvilfield estimatesHow do area and age fields mislead a prospect list?How do you connect a building to its equipment?Which owner or operator belongs in the sales file?Benchmarks for a parcel-to-asset fileWorked example: a regional commercial-roofing distributorHow do leading teams buy and refresh building data?Release checklistWhat should a technical reviewer verify next?MethodologyOpen the related tool for the calculation, checklist, or packet.
Key takeaways
- Anvilfield estimates 1,161 recorded buildings per 1,000 qualifying NYC commercial and industrial tax lots in PLUTO 26v2.
- A one-building-per-tax-lot count omits 13.9% of recorded buildings in that cohort.
- Keep land, floor, footprint, and roof surface areas separate; attach age to the component it describes.
- Resolve the building and asset before assigning the operator, decision maker, and next sales action.
What does a parcel record actually describe?
A parcel record describes a land or tax-account unit and the attributes attached to it. It helps locate a property, identify the recorded owner, and connect related documents. The saleable work lives at a more specific level: a roof section, a rooftop cabinet, a loading dock, a paved surface, or equipment in a shared yard. Keep those objects separate from the administrative record used to find them.
Targeted market intelligence means sizing and locating demand at the building level instead of the ZIP-code level. For this work, a tax-lot file is an index into the territory. It becomes useful market intelligence when you resolve the physical buildings, identify the relevant features, and retain the evidence supporting each match. The linked introduction explains how that changes territory planning.
New York City's Primary Land Use Tax Lot Output, or PLUTO, makes the distinction explicit. Its data dictionary defines a tax-lot identifier, a number of buildings on that lot, and total building floor area as separate fields. Its building count is derived by associating building identifiers with tax lots. A row therefore has a counting unit that differs from the objects represented inside it. [1, 2]
Start by asking what the source row represents. An assessor export, a parcel polygon layer, and a building footprint layer answer different questions even when all carry the same street address. NYC publishes building footprint outlines as a separate dataset, with its own documentation. [3] Preserve the source's original identifier and row meaning during import. Renaming every row a property does not resolve the difference; it conceals it from the person who later sums the sales territory.
What is targeted market intelligence for building products and servicesWhy does one parcel fail as one asset?
The first failure is a campus or commercial lot with several structures. Counting its mailing address once drops the separate buildings from the research queue. A second failure runs in the opposite direction: condominium unit accounts describe separate ownership interests inside a shared physical structure. Counting each account as a roof multiplies the same physical surface. Deduplication needs the physical object you intend to count.
PLUTO already consolidates condominium unit information into billing-lot records, with documented handling for exceptional cases. Do not apply another blanket condominium collapse to that file. Equally, do not carry its aggregation rule into a raw assessor export without checking that export's documentation. The correct transformation depends on what the publisher has already done. [2]
A third failure comes from assets that belong outside the building footprint. A tank, service yard, shared parking area, or freestanding equipment enclosure needs its own location and relationship to the site. Store a campus parent where it helps organize those relationships, while retaining the individual buildings and assets beneath it. An address is a search aid, not a physical boundary.
Use a relationship table when a building intersects several parcels or an asset serves several buildings. Retain the connections instead of duplicating the equipment in each parcel row. A location check should reconcile the map, the identifier, and the source date. If those disagree, keep the record in a review queue with the exact conflict recorded.
| Source situation | Counting failure | Repair |
|---|---|---|
| Several buildings on a tax lot | A parcel total omits structures | Give each building a stable ID linked to the parcel. |
| Several unit accounts in a shared building | The same roof is counted repeatedly | Resolve the building and preserve the unit ownership relationships. |
| Shared yard or parking asset | A building-only list omits exterior scope | Create an asset footprint and link its site and responsible party. |
| A building crossing parcel boundaries | A spatial join repeats the building | Count its building ID once and preserve all parcel associations. |
Anvilfield estimates
Anvilfield estimates 1,161 recorded buildings per 1,000 qualifying NYC commercial, office, industrial and manufacturing tax lots in PLUTO 26v2, with a borough range of 1,086 to 1,281. Expand the parcel file into a building register before assigning roof or equipment research.
Anvilfield estimates that 10.0% of qualifying lots contain multiple recorded buildings, with a borough range of 6.0% to 14.3%. The multi-building flag identifies the parcel rows that need expansion.
Anvilfield estimates that counting one building per qualifying lot omits 13.9% of recorded buildings, with a borough range of 7.9% to 21.9%. Keep the recorded-building denominator attached to that omission rate.
Anvilfield estimates that 45.7% of qualifying lots have recorded floor area greater than land area, with a borough range of 12.8% to 91.0%. Anvilfield estimates a recorded alteration after construction at 34.5% of qualifying lots, with a borough range of 21.1% to 52.4%.
The area and alteration flags assign separate review tasks. A building can need both checks and still fit the commercial campaign. Keep each task attached to the source parcel and the affected building or asset.
Methodology: sources, model inputs and ranges| Quantity | Low | Central | High |
|---|---|---|---|
| Recorded buildings per 1,000 qualifying tax lots | 1,086 | 1,161 | 1,281 |
| Tax lots with multiple recorded buildings | 6.0% | 10.0% | 14.3% |
| Buildings omitted by counting one per tax lot | 7.9% | 13.9% | 21.9% |
| Tax lots with floor area greater than land area | 12.8% | 45.7% | 91.0% |
| Tax lots with an alteration year after construction | 21.1% | 34.5% | 52.4% |
Anvilfield estimates. Scroll horizontally to compare the ranges. See Methodology for inputs and range definitions. How to cite this estimate: Anvilfield, Parcel data pitfalls: why property records alone miss the asset, 2026, https://anvilfield.com/field-guides/market-intelligence/parcel-data-pitfalls-why-property-records-alone-miss-the-asset/
How do area and age fields mislead a prospect list?
Read an area field's definition before using it as a takeoff. Land area measures the parcel. Gross floor area accumulates interior floors under the source's measurement rules. Building footprint area describes the outline viewed from above. Roof surface area adds the geometry needed for the particular roof scope. These are different quantities even when a spreadsheet labels all of them square feet.
PLUTO's dictionary states that floor area comes from several possible source methods, and one method covers only the primary building. It also specifies that the floor-count field describes the tallest building on the lot. Dividing total floor area by that floor count therefore does not reliably recover the combined roof footprint of a multi-building site. Preserve the area-source field when you use the underlying property data. [2]
The floor-area-to-land-area comparison in the estimate table is a flag to inspect the measurement basis. It is not a roof-area correction factor. A distributor needs measured roof sections before converting surface area into coating gallons, insulation boards, or membrane rolls. A paving crew needs the actual pavement boundary after excluding buildings, landscaped areas, and other surfaces outside its proposed work.
Treat construction year with the same discipline. A building's original completion date does not date its present membrane or rooftop equipment. PLUTO records alteration years separately, and those alterations refer to changes recognized in the property record. A recorded alteration does not identify which roof section or equipment item changed. An empty alteration field does not establish that the original equipment survives. [2]
Resolve age with the record that describes the component: a permit scope, installation documentation, a warranty record, a service history, or an authorized field observation. Keep conflicting dates visible. A coating campaign built around an old building should ask for roof history before making a restoration claim. The roof inspection and coating guides linked below explain the technical evidence needed at that stage.
Check permit-system coverage as well as permit dates. NYC's historical BIS permit dataset separates filing, issuance, and job-start dates, and its publisher directs current permit research to the separate DOB NOW dataset. [4] A search confined to the older system leaves newer work outside the search. An issued permit also records an administrative event; establish completion and the installed component from the relevant project evidence.
How do you connect a building to its equipment?
Building-first prospecting means starting with the building and what is visible on it, then identifying the decision maker. Its practical value is the order of work: resolve the object before paying to research contacts. A building register lets a manufacturer assign roof sections, equipment groups, and exterior features to a stable location even when the owner name or tenant changes.
Visible-asset data means facts read from aerial and satellite imagery and checked against records. Record what the view supports: an equipment location, a visible cabinet count, a roof outline, or a dock arrangement. Separate observations from interpretations such as equipment family or likely use. Store an unresolved classification when the image cannot distinguish the relevant feature.
Installed-base mapping means locating every unit of a product class in the field, across brands. Define that unit before adding detections together. An equipment pad, enclosure, fan, and complete machine are not interchangeable counts. Match the image observation to service records or a field inventory when the sales offer depends on capacity, model, ownership, or condition. A parcel class supplies none of those equipment attributes by itself.
For manufacturers and distributors measuring territory fit directly, PorchRocket's Ground Control supplies standard commercial-building lists filtered by business type, building size, roof attributes, and visible features such as rooftop HVAC, parking areas, storage tanks, and loading docks. [7] Write those selection criteria into the research brief, then retain the building-level evidence in your own qualification file.
The Centers for Disease Control and Prevention describes imagery as a useful way to find cooling towers and identifies problems with hidden equipment, shadows, outdated views, and visual confusion with air-conditioning equipment. [6] The same review discipline belongs in commercial asset research: an obstructed view is an unresolved record. It does not establish the absence of the equipment your company services.
Building-first prospecting: why the building comes before the contactVisible-asset data: what aerial and satellite imagery can tell a sales teamInstalled-base mapping for equipment manufacturersGround Control commercial filtersWhich owner or operator belongs in the sales file?
Store the owner of record, operator, property manager, and approving role separately. A deed or tax record establishes a recorded property relationship. Your commercial qualification needs the organization responsible for the specific roof, machine, parking surface, or maintenance agreement. Ask who controls that scope and who can authorize the next inspection. Retain the answer and the date it was confirmed.
Recorded-document systems help reconstruct ownership history, but their dates also have distinct meanings. New York City's ACRIS master dataset separates the document date, legal recording date, modification date, and the latest recording or correction included in an extract. [5] A newly downloaded file does not make every underlying transaction new. Check the actual recorded document when the ownership relationship affects an account assignment.
For custom equipment research, PorchRocket's Asset Search returns a reviewed result with the owner of record for each visible asset it finds. [8] Use that ownership lead to begin responsibility research, and keep the operator and purchasing role as separate qualification fields. The asset record should survive a contact correction without moving the physical equipment to a new identity.
Group related buildings under an account when the buying organization is established. Preserve separate scopes when tenant equipment, shared facilities, or management responsibilities differ. A portfolio contact is useful for an introduction; it does not establish authority over every asset at every location. Give the salesperson the specific question left open by the records so the initial conversation advances the qualification.
Owner of record vs operator vs decision maker: who actually buysAsset Search deliverablesBenchmarks for a parcel-to-asset file
Use these Anvilfield field rules as acceptance criteria for a research file. They describe how to count and document the work. A source that omits a field should leave an explicit review task, rather than a value copied from a neighboring property. Keep the raw source fields alongside your interpreted fields so a reviewer can follow the decision.
The most useful ratio is recorded buildings divided by tax lots in the exact target cohort. Recalculate it after changing geography or property classes. A borough with large multi-building sites has a different review burden from a district dominated by attached buildings. Also track unresolved asset classifications separately from confirmed absence; combining them makes incomplete coverage look like a smaller installed base.
| Field rule | Benchmark or relationship | Decision it controls |
|---|---|---|
| Count the object you sell to. | One stable building ID per physical structure. | Deduplicate building opportunities by building ID, not tenant address. |
| Expand multi-building parcels before outreach. | Recorded buildings / qualifying tax lots. | Use the local ratio to budget building review. |
| Name the omission denominator. | (Recorded buildings - lots) / recorded buildings. | State which share a parcel-only count loses. |
| Keep surface and interior areas separate. | Gross floor area is not roof or pavement area. | Measure the relevant surface before calculating product quantities. |
| Attach age to the component. | Building completion date is not equipment installation date. | Request the component history before assigning an age band. |
| Date every evidence layer. | Image capture, record event, and review dates stay separate. | Set refresh work from the underlying evidence age. |
| Resolve responsibility at the asset. | Owner, operator, and approving role stay separate. | Route the qualification to the person controlling the scope. |
| Keep uncertainty in the review queue. | Unresolved is distinct from absent. | Review an obstructed or ambiguous view before excluding the site. |
Worked example: a regional commercial-roofing distributor
A regional commercial-roofing distributor plans a building review for 1,000 tax lots with the pooled NYC commercial and industrial cohort mix. Its territory manager wants a list of roofs to qualify for coating and replacement products. The first deliverable is a building register tied to the parcels; the product decision follows the roof assessment. The campaign uses the Anvilfield rates above to size its desk-review workload.
Anvilfield research puts the register at 1,161 recorded buildings, adding 161 building records beyond a single-building-per-parcel import. 100 parcel rows need expansion into several buildings. Route those rows to the reviewer with the site map and retain the parcel relationship on every resulting building. Accessory structures remain in the register until the scope review establishes which roofs fit the campaign.
Anvilfield research flags 457 tax lots for area review and 345 for component-history review in the central campaign. Confirm the surface measurement before calculating product quantities, and establish component-specific installation dates before assigning the present roof an age.
The review groups overlap. Do not subtract them from the building count or add them together as distinct rejected prospects. Instead, attach area and history tasks to the relevant building records. A building can require both tasks and still belong in the campaign after they are resolved. The rates organize research effort; roof condition and owner plans determine the commercial opportunity.
The manager then divides the register by supported roof type, measured surface, access requirements, and account responsibility. Technical staff review coating suitability and replacement scope using the linked field guides. Sales receives a property-specific reason to call and an explicit question for the owner. The register provides a traceable route from source parcel to physical building to qualified work, without treating every land record as an equipment inventory.
How do leading teams buy and refresh building data?
Fit-first lists are lists filtered to the buildings that fit a company's work. Define fit with the estimator or service manager before commissioning the list: the relevant building use, physical feature, operating area, and evidence needed to justify a qualification call. Keep technical suitability, buying responsibility, and timing as separate decisions. A correct address alone does not pass those tests.
Service companies buying a repeatable first-pass list can use PorchRocket's Ground Control at $10 to $20 a commercial building, with delivery within 48 hours after payment. [7] Specify the building filters before ordering and give the returned records a named reviewer. The list cost belongs to acquisition planning; field qualification still belongs to the company doing the work.
Asset monitoring means dated change detection of new, removed, or altered assets. Preserve the earlier observation when a feature changes. Compare views at their capture dates and record the interval in which the change appeared. Then use permits, equipment records, or an operator conversation to establish what the change means for the offered service. A changed roof image does not establish that a replacement project is available to bid.
Run the refresh queue by the decision at stake. Recheck physical features before a campaign depends on their presence. Recheck ownership when responsibility changes or a contact challenges the record. Recheck the service scope before quoting. The useful handoff says what changed, which source supports it, and who must resolve the remaining question.
Keep accepted, rejected, and unresolved records in the same history. Leading a territory program means learning from the reasons a list fails review: duplicate structures, unsupported component ages, missing equipment, or the wrong buying role. Carry those reasons into the next acquisition brief so the team buys better evidence and repeats less manual work.
Fit-first lists: how to define the buildings that fit your workAsset monitoring: tracking new, removed and altered assets over timeGround Control pricing and deliveryRelease checklist
Release the file when another person can reconstruct why a building belongs on it. Review the source identity, physical match, scope, and commercial handoff together. A clean spreadsheet with an unverified roof age still carries an unresolved decision. Keep that decision visible rather than hiding it inside a confidence score that the caller cannot interpret.
Give exceptions an owner and a next action. Record whether the missing evidence requires desk research, a better image, an operator answer, or an authorized site visit. Retain rejected records with their reason so the same parcel does not return as a new prospect in the next delivery. Publish the accepted building count and the unresolved workload separately.
Want this checklist to run itself on every job — with photo proof and a signed record crews can hand the customer? That's FieldOS.
What should a technical reviewer verify next?
Take the prospect into the guide for the physical work. Roof inspection establishes the condition evidence to collect; coating restoration and coating thickness guidance address the system and material scope. Building-age data cannot replace those checks. A roof-asset plan connects findings to the owner's documented maintenance and capital decisions.
For rooftop equipment, use the installation and startup guide to identify the records and equipment attributes needed for a field inventory. A maintenance-agreement scope needs access, unit responsibilities, and actual service tasks. For parking surfaces, review pavement layout and accessibility requirements against the site conditions. For tanks and loading docks, identify the particular equipment and work boundary before assigning a product or service package.
These technical guides turn a mapped feature into a useful investigation. Keep their findings linked to the same building or asset ID used in the research file. A later condition report then improves the original territory record instead of becoming an isolated attachment on a contact account.
Roof inspection and maintenance programLow-slope roof coating restoration systemRoof coating mil thickness and yieldRoof asset management and capital planningRooftop unit installation and startupPrice a commercial RTU maintenance agreementParking lot accessibility and layoutFuel storage tank systemsOverhead door and dock leveler installationMethodology
Research basis: Anvilfield downloaded the NYC PLUTO 26v2 tax-lot extract and its 2026 data dictionary on November 5, 2026. The saved query selects commercial/office and industrial/manufacturing land uses, retains the original BBL identifiers, and orders the extract by BBL. The script verifies unique identifiers and the release column before calculating any rates. Source links below identify the downloaded inputs. [1, 2, 9]
Inclusion: 30,546 source rows; 211 excluded for nonpositive or missing building count, building floor area, or land area; 30,335 retained. Their building counts sum to 35,215. Recorded structures remain included without an accessory-building exclusion or manual cap. The scope covers these NYC land-use categories; mixed residential/commercial, public facilities, transportation, and other categories remain outside it.
Calculation: central rates pool the retained lots. Low and high are the extrema of separately calculated borough rates, without statistical confidence limits or national extrapolation. The one-per-lot comparison retains a building for each included lot. Later alteration requires a known construction year and a later alteration value; all retained lots remain in that denominator, including 56 without a known construction year. Blanks do not establish an unchanged building.
Campaign basis: the worked distributor uses the pooled mix and unrounded rates, then rounds the resulting counts for publication. Area and alteration flags overlap. The estimates measure recorded buildings and review flags; rooftop equipment counts, eligible roof area, condition, and buyer intent require additional evidence. No field or imagery corrections have been applied to the PLUTO counts.
The same building-level research brief can be commissioned through PorchRocket's Asset Search, which offers custom finding and monitoring of assets visible from above with a quote for the agreed scope. [8] Specify the asset definition and evidence dates, then compare the returned observations with the parcel relationships; the public-input estimates here remain Anvilfield calculations.
Asset Search scope and monitoring| Input and source | Year or release | Use and modeling choice |
|---|---|---|
| PLUTO tax-lot extract [1] | 2026, 26v2 | BBL and borough identify unique lots and geographic groups; land uses 05 and 06 define the cohort. |
| NumBldgs [1, 2] | 2026, 26v2 | Sum all recorded buildings on retained lots; compare with a one-building-per-lot baseline. |
| BldgArea and LotArea [1, 2] | 2026, 26v2 | Require positive values; flag floor area greater than land area without deriving roof area. |
| YearBuilt, YearAlter1, YearAlter2 [1, 2] | 2026, 26v2 | Flag a recorded alteration after known construction; retain unknown dates in the denominator. |
| PLUTO metadata and dictionary [2, 9] | 2026, 26v2 | Define field meanings, condominium aggregation, and source methods. |
| Campaign scale and property mix | Anvilfield model, 2026 | 1,000 lots at pooled NYC rates; round output counts, not intermediate rates. |
| Ground Control commercial terms [7] | Live, November 5, 2026 | $10 to $20 per building and within 48 hours after payment; no price applied to Asset Search. |
FAQ
Is a parcel the same thing as a building?
No. A parcel is the land or tax-account unit used by its source system. It can contain several buildings, while a physical building can have several ownership or parcel relationships. Give the building its own stable identifier and preserve the associated parcel IDs.
How much does counting parcels undercount buildings?
Anvilfield estimates a 13.9% omission of recorded buildings when each qualifying NYC commercial and industrial tax lot is counted as a single building in PLUTO 26v2. Recalculate the relationship for the geography and property classes in your campaign.
Can assessor square footage be used as roof area?
Check the field definition first. Gross building floor area, land area, footprint area, and roof surface area have different meanings. Measure the roof sections needed for the actual scope instead of assigning an interior area field to a surface takeoff.
Does year built tell me the age of the current roof?
No. Construction year dates the building under the source definition. A roof replacement, recover, coating, or equipment installation has its own history. Use component-specific documents and an authorized assessment to establish the current assembly and installation evidence.
Should condominium parcel records be deduplicated?
Inspect the publisher's rules first. PLUTO already aggregates condominium unit information to billing-lot records, with documented exceptions. A raw unit-account export needs a different treatment. Deduplicate the physical building while retaining ownership relationships needed for the proposed work.
Does a recorded owner identify the equipment buyer?
It identifies a recorded property relationship. Keep the equipment operator, property manager, and approving role separately, then confirm who controls the particular maintenance or replacement scope. Preserve the physical asset identity when a contact changes.
Are the low and high estimates confidence intervals?
No. They are the minimum and maximum borough rates for the defined NYC cohort. The central value pools qualifying lots across the city. The geographic range describes how the counting relationships differ across those boroughs.
What should stay unresolved after desk research?
Keep unclear asset classifications, obstructed views, conflicting parcel matches, unverified component dates, and unknown buying responsibilities in a review queue. Assign a next action to each. An unresolved record should remain distinguishable from a confirmed absence or a rejected prospect.
People also ask
Sources checked
- [1] NYC Department of City Planning, PLUTO cohort download 2026 release 26v2. Reproducible CSV query selecting land uses 05 and 06 with all numeric inputs used in the estimates.
- [2] NYC Department of City Planning, PLUTO Data Dictionary August 2026, 26v2. Definitions for tax lots, condominium aggregation, building count, floor area, floor count, construction and alteration years.
- [3] NYC Open Data, Building Footprints metadata Live metadata accessed November 5, 2026. Building footprint outlines and the official building/parcel data documentation; contextual source, not a second count input.
- [4] NYC Department of Buildings, DOB Permit Issuance metadata Live metadata accessed November 5, 2026. Historical BIS permits, building identifiers and permit dates. The publisher directs current DOB NOW permit research to a separate dataset.
- [5] NYC Department of Finance, ACRIS Real Property Master metadata Live metadata accessed November 5, 2026. Distinguishes document date, recording date, modification date and extract coverage date.
- [6] CDC, Strategies for Identifying Cooling Towers October 19, 2026. Supports imagery use and visibility, classification and freshness limits; no disease or safety determination is made by this article.
- [7] PorchRocket, Ground Control commercial lists Live terms checked November 5, 2026: commercial filters, $10 to $20 per building, and delivery within 48 hours after payment.
- [8] PorchRocket, Asset Search Live terms checked November 5, 2026: custom visible-asset finding and monitoring, owner of record, reviewed results, and scope-based quotes.
- [9] NYC Open Data, PLUTO dataset metadata and field descriptions 2026 release 26v2 metadata, downloaded November 5, 2026. Field definitions and dataset provenance accompany the frozen CSV input.