Understanding Land-Use Codes for Vacant Land

A land-use code is a short number or abbreviation a county attaches to every parcel to say what the land is — a single-family home, a farm, a commercial building, or bare dirt. For a land flipper, these codes are the single most important field in a county file, because they're how you separate the vacant parcels you actually want to mail from the 90%+ of records that have a house, a store, or a barn sitting on them. Get the codes right and your list is clean. Get them wrong and you mail houses, which burns postage and credibility.

What a land-use code actually is

Counties assess property for taxes, and to do that they classify how each parcel is used. That classification gets stored as a land-use code (sometimes called a property class, use code, DOR code, or property type). It usually looks like one of these:

• A numeric code — 0000, 00, or 100 for vacant residential in many rolls
• A short letter code — V, VAC, RV
• A free-text description — VACANT, VAC LAND, ACREAGE, or sometimes just a blank field

The code answers "what is this parcel," which is different from the owner (who to mail) and the acreage (how big it is). You need all three to build a list, but the use code is the filter that decides vacant or not. If you're new to pulling raw county data, the full county assessor data walkthrough shows where this field sits in the larger pipeline.

Why the codes vary so much by county

There is no national standard. A code that means "vacant residential lot" in one county can mean something completely different one county over, and two counties in the same state can use different coding schemes entirely. A few reasons the variation is so brutal:

• Different vintages of software. County assessor systems were built and customized over decades. Each one carries its own code table.
• State overlays vs. local codes. Some states impose a standardized use code on top of the county's own — so a single file can carry two different code columns, and they don't always agree.
• Vacant is split across many codes. "Vacant" is rarely one code. A county may have separate codes for vacant residential, vacant agricultural, vacant commercial, and undeveloped acreage. Filter on only one and you'll miss most of your inventory.
• Blank and null aren't neutral. In some rolls a blank use code means genuinely unclassified; in others it's how that county records raw land. You can't assume.

This is why a filter that worked perfectly in one county produces garbage in the next. The codes aren't portable, and neither is your logic.

How to isolate genuinely vacant parcels — honestly

The goal is a list where every parcel is vacant because the county's own data says so — not because you guessed. Here's the disciplined way to get there.

1. Get the county's code table, then verify it against real rows

Most assessors publish a data dictionary that lists each use code and its meaning. Start there — but treat it as a hint, not gospel. Documentation lies by omission: a code table may be outdated, or the delivered file may contain codes the dictionary never mentions. Pull a sample of parcels for each candidate "vacant" code and check them against the county's public parcel viewer or aerial imagery. If the code says vacant and the map shows a rooftop, the code is wrong for your purpose.

2. Build an explicit vacant / not-vacant / unclassified map

Don't filter with a single "if code = X" rule. Instead, assign every code in the file to one of three buckets:

Mail only the vacant bucket. When a code is genuinely ambiguous, it belongs in unclassified and stays off the list. "Probably vacant" is not good enough to put a stamp on.

3. Exclude exempt and non-mailable owners

Some parcels carry no improvement and will slip through a naive vacant filter even though you'd never want to mail them: government land, churches, schools, cemeteries, HOA common areas, and utility easements. These usually have their own use codes or an exemption flag. Strip them out — a state forest is technically "vacant" and completely useless to a land buyer.

4. When a county is too messy, set it aside

If a county's codes are so inconsistent you can't confidently sort vacant from improved, the right move is to skip that county, not ship a list you don't trust. One clean county beats three sloppy ones. If you'd rather not make that call county by county, you can compare counties side by side to steer toward markets with cleaner data before you sink a day into decoding.

The honesty payoff

Getting use codes right is what makes the rest of a campaign honest. When your list is truly vacant-only and absentee-filtered, a mail drop behaves predictably: roughly 1,000 well-targeted pieces typically pulls a low single-digit percentage response — think 20 to 40 calls — and out of those, one to three tend to turn into deals. A single deal in this game might look like an ~$8k buy and an ~$22k resell, which is why list quality, not volume, is the lever. Mail a list polluted with houses and those numbers quietly collapse, because half your postage never had a chance.

Use codes are also step one of a broader cleanup: once you've isolated vacant parcels you still need to separate absentee owners from local ones and dedupe by owner before anything is truly mail-ready.

The bottom line

Land-use codes are the filter that decides whether your list is dirt or houses. They vary county by county, they're often split across several values, and the documentation can't be trusted at face value — so verify against real parcels, map every code to vacant / not-vacant / unclassified, and drop anything you can't confirm.

That decoding is a genuine Saturday of work per county, and it has to be redone every time the roll updates. The names in those public files are free; the filtering is the entire value. If you'd rather skip the code-table archaeology, browse ready-made lead lists that are already decoded, vacant-filtered, and deduped — or request a custom list for a specific county and let someone else absorb the tedium.