What is a flag lot, and why it slows down an acquisition pipeline
A flag lot shows up on a plat as exactly what the name says: a narrow strip of land, the "pole," running back from the street to a wider parcel behind it, the "flag." The street frontage might be twenty feet wide. The buildable part sits a hundred feet or more back from the curb, screened from the road by whatever's sitting on the lots next to it.
Some jurisdictions call it a pipe stem lot instead, same shape, same problem. Either name means the same thing to an analyst: a parcel that got carved up at some point to give an interior piece of land legal street access, usually because subdividing it any other way wasn't geometrically possible given the lot lines around it.
Why these exist in the first place
Flag lots usually come from one of two situations. A larger parcel got split and the back half needed its own access easement to qualify as a buildable lot, so the seller or a prior owner carved out a narrow access strip. Or an older subdivision predates current zoning and just drew lots that way because the road layout left no other option. Either way, by the time it lands on your screening list, the flag shape is baked into the recorded plat. It's not something a rezoning fixes.
That shape creates three things worth checking before a flag lot goes anywhere near a term sheet.
Access and the pole itself. The narrow strip has to carry a driveway, often utilities too, and sometimes it's shared with a neighboring flag lot under a recorded easement. If the pole is jointly owned or the easement language is vague about maintenance and width, that's a title problem before it's a zoning problem. Pull the easement and read who actually has rights to what before assuming the access is clean.
Setback requirements on an odd-shaped parcel. Most codes measure setbacks from the property line, and a flag lot's property lines don't look like a rectangle. The side yard that would normally face the street now faces a neighbor's back fence, and the "front" setback might apply to the narrow pole instead of the building pad. A few municipalities also apply a separate minimum lot width test at the building line, which a pole-and-flag shape can fail even when the flag portion itself is plenty wide. That's a variance conversation, and variance conversations add months to a timeline a pro forma doesn't budget for.
Frontage minimums. Some zoning codes require a minimum street frontage to even issue a building permit, separate from lot area. A flag lot with twenty feet of pole frontage against a thirty-foot code minimum doesn't qualify as-is, full stop, no matter how big the flag portion is. That number is worth pulling from the code before a site visit, not after.
Where this bites an acquisition pipeline
None of this shows up on a parcel map at a glance. The lot reads as a normal-sized, normal-shaped piece of land in the county GIS layer because most parcel viewers draw the flag shape fine but don't flag the access strip as a separate constraint. An analyst scanning fifty parcels an afternoon can easily wave one through, run the yield math on the flag portion's full square footage, and not catch the setback and frontage issues until a civil engineer looks at the site plan three weeks later.
That's the cost: not that flag lots are bad sites, plenty of them pencil fine once someone works through the access and setback math, but that they eat review time disproportionate to their size, and that time usually shows up after a parcel is already under a letter of intent instead of before. Catching the shape at the screening stage, before it's on anyone's desk as a live deal, is the cheap version of this problem.
Development Capacity's parcel lists are built to surface undeveloped and underused sites inside a built-up submarket so you're starting from a shortlist of candidates instead of eyeballing the whole GIS layer lot by lot. If flag lots and odd parcel shapes are part of what's slowing your current screening process, take a look at what a ranked list for your submarket would give you.