Eminent domain software

Most software sold to land teams manages parcels. Very little of it knows what a statute requires. Here is the difference, who needs which, and what to ask a vendor before you buy.

What the term actually covers

Three different products get sold under adjacent names, and buyers routinely end up in a demo for the wrong one. The distinction is not marketing. It decides whether the thing you buy can answer the question you bought it for.

Right-of-way permitting software

Manages encroachment permits inside the public right-of-way: applications, review, inspection, closeout. It is a municipal function and it has nothing to do with acquiring land rights. If you are a city processing permit applications, this is the category you want, and we are not in it.

Land management and ROW tracking

Handles parcels, agents, documents, and payments across a corridor. Good at status and at keeping a large team pointed the same direction. Generally agnostic about what any particular state's statute requires, because it is built to work everywhere.

Eminent domain and condemnation software

Adds the procedural layer on top of tracking: the offer sequence, notice requirements, deadlines derived from the statute, the approval chain, and a record that holds up when the file is examined years later.

Who needs the procedural layer

Not everybody. If your acquisitions are few, mostly voluntary, and rarely go near condemnation, a tracker and a good paralegal will serve you better than anything in this category. Buy the cheaper thing.

The procedural layer starts paying for itself when all three are true:

The parcel count is past the point where one person can hold the calendar in their head, so the answer to “what is late?” has to come from a system rather than a meeting.
The work spans internal agents, engineering firms, and outside counsel, who each see a different slice of the file and none of whom see all of it.
Some parcels will end up in front of commissioners or a court, and the record you built along the way is the record you will have to stand on.

What to ask any vendor

Ask us these too. We would rather answer them on the first call than in a procurement review.

Which states do you actually encode, and what happens in the others?

A system that quietly supplies a generic deadline for a state it does not know is worse than one that refuses, because it looks authoritative. Ask to see the refusal.

Show me the citation behind a derived date.

On screen, on the parcel, without a support ticket. If a deadline cannot be traced to a statute, you have bought a calendar with opinions in it.

How do you version the rules, and can you tell me which version a parcel was worked under?

Statutes change mid-project. Ask what happened at the last amendment in a state you operate in, and what the product did about parcels already in flight.

Who reviews the legal content, and how often?

Ask for the review process and the date each pack was last checked. Encoded law with nobody accountable for it is the failure mode this whole category has.

Business days, calendar days, or working days?

Ask about Texas specifically. Chapter 21 uses several different time units inside one procedure, and a tracker that counts them all the same way will be wrong on some of them.

Can counsel approve inside the system, and does the approval become part of the record?

Approval by email, reconstructed later from an inbox, is the thing you are trying to stop doing.

Can you produce a complete parcel file, and would my litigators call it usable?

Ask for a sample against a real parcel, then hand it to the attorney who would actually have to use it.

Can the audit history be altered, and how would you prove it was not?

A log that an administrator can quietly edit is not a record. Ask what verification looks like.

Where LandGrantIQ fits, and where it does not

We do the procedural layer for two states. Texas and Indiana ship with full statutory rule packs: every requirement carries its citation, every pack is versioned, deadlines are derived per parcel, counsel approves inside the system, and the record is built while the work happens rather than reconstructed afterwards.

We do not do national coverage. Two states encoded properly is a product. Fifty states approximated is a liability, and it is a liability that surfaces on the one parcel that ends up in front of a judge.

So if you need broad coverage more than you need accuracy, we are the wrong vendor. We would rather say that on the first call than three months into an evaluation.

Texas rule pack →Indiana rule pack →Free deadline references →

This page is not legal advice. It describes a category of software and summarizes published statutory requirements with their sources attached. It does not tell you what the law requires of your project, it is no substitute for your own counsel's judgment, and nothing in it creates an attorney-client relationship.

Bring us the route.

Tell us the project, the states, and the constraint you are actually up against. The first conversation is about fit, including whether there is any.

Scope a pilot