Welcome to Algorithm Taxes: Same House, New Bill

Your property tax bill is not a reflection of your hard work.

It’s a reflection of a map.

A map that decides how much land you “own” on paper, where your boundaries sit, and what the algorithm thinks your property is worth.

So when taxes rise every year, the first question shouldn’t be “why are values up?”

It should be:

Are the lines even right?

Since about 2019, it’s felt like a New Hampshire tradition: mud season, black flies , and your tax bill mysteriously “finding new ways to grow.”

And every year we get the same explanation:

• “The market went up.”

• “It’s a revaluation year.”

• “Nothing personal, it’s just math.”

Sure. But here’s the part nobody says out loud:

That “math” starts with a map. And if the map is wrong… the math is wrong.

In plain English: when your property taxes go up, blame the lines.

The Quiet Change Nobody Voted On: Mapping + Algorithms

In a lot of towns, the big shift wasn’t a new school or a new fire truck.

It was the move toward new digital mapping systems + mass appraisal algorithms (think GIS + CAMA modeling). The sales data comes in, the model runs, the map feeds the model, and poof—your “value” updates like your phone apps do:

“New features available!”

(Translation: you now pay more for the same land you were standing on last Tuesday.)

And here’s the key point:

Those systems don’t “discover truth.” They calculate based on the inputs.

If the base map has boundary errors, road placement errors, or town-line errors… then the algorithm isn’t “objective.”

It’s just confidently wrong at scale.

Which is why the bill can rise even when:

• your house didn’t change

• your land didn’t change

• your road didn’t move

  
  

  …but the paper version of reality did.

“But My Survey Says…”

(Yeah. About That.)

Surveys are supposed to be the grown-up referee of property disputes.

But what happens when:

• the survey is built from bad reference points, or

• the survey relies on records that were already clouded, or

• the “control” they’re tying into is actually based on altered mapping assumptions?

Then the survey can look official and still be wrong.

And we’re not talking about harmless mistakes like “oops, that’s a maple not an oak.”

We’re talking about town lines and road placements that don’t match what’s physically carved into the land—stone walls, original corridors, and historic patterns that don’t care what a database says.

The Extra Spicy Part: Timber Deeds Stacked Like Pancakes

We also have documentation showing how timber deeds get used like building blocks—stacked, recycled, and leaned on to “support” ownership narratives that don’t match actual original lot structure.

That matters because when the underlying record gets muddy, it creates the perfect fog for:

• boundary “interpretations”

• quiet expansions/shrinkages

• parcels that drift on paper

• and tax bills that rise because the model thinks your lot is something it isn’t

And if you’ve ever tried arguing with a tax map, you already know the town’s favorite spell:

“That’s what the system shows.”

(Yes, and my microwave clock says it’s 12:00 forever. Doesn’t make it true.)

“Okay Smart Guy—So How Do You Prove Where the Lines and Roads SHOULD Be?”

Here’s the good news:

There’s a way to prove it with one image used in three steps.

Not “made-up lines.” Not “connect-the-dots vibes.”

A real grid—because it’s already carved into the land in the form of alignment, monuments, and historic structure.

This is the method in plain language:

Step 1: Use the Original Grid Image as the “Master Template”

Think of the old survey framework like the skeleton the town was built on. It’s the starting geometry—the baseline that later deeds and maps are supposed to respect.

Step 2: Anchor It to What the Land Can’t Lie About

You don’t anchor to modern parcel sketches. You anchor to physical reality:

• long stone wall runs

• old road corridors and intersections

• water boundaries and natural constraints

• repeating angles/distances that show up consistently in multiple places

In other words: the stuff that existed before anyone could click “edit parcel.”

Step 3: Overlay That Grid Against Today’s GIS Map

Now you compare:

• what the grid says should be where

  
  

  vs.

• what the town’s GIS shows today

And that’s where the “uh oh” happens.

Because once the original grid is properly placed, it becomes painfully obvious:

• where roads were “shifted” on paper

• where boundaries got stretched/compressed

• where town lines don’t match the underlying geometry

And when you can show that visually, you’re no longer debating opinions.

You’re pointing at a mismatch.

Why This Explains the Tax Hikes Since 2019

Because the newer systems don’t just store lines.

They use lines.

They feed those lines into:

• land size calculations

• neighborhood models

• frontage assumptions

• “influence factors” (water/road proximity, access, desirability)

• assessment outputs

So if the map quietly drifts, the model quietly “corrects” you… right into a bigger bill.

And that’s why this isn’t just an Ossipee problem or a “one property” issue.

If the starting point is off, the error spreads outward—like a zipper that’s one tooth misaligned.

Bonus: If a Town Can Draft an Anti-Fraud Policy… It Can Also Follow It

It’s not “extreme” to ask for integrity in public records. Even the framework language exists for what fraud can look like in municipal settings—like alterations of records and misuse of public documents.

So the real question isn’t “Should we look?”

It’s:

Why wouldn’t we?

The Bottom Line

If your taxes keep going up every year, don’t let the conversation stop at “the market.”

Ask the question that actually matters:

Are the lines right?

Because when the map is wrong, the algorithm is wrong.

And when the algorithm is wrong…

…everyone becomes the sheep farm.

Only the sheep are paying the bills.

(And somehow the fence keeps moving.)