Normalized input
Original text beside the parsed and normalized legal description.
P1 · Description review
Find malformed, duplicate, overlapping, or missing land descriptions before they reach the final file.
Title examiners, abstractors, landmen, and attorneys often inherit batches of descriptions from deeds, schedules, or historical records. A thin QA workflow can normalize the inputs, plot the results, and surface records that need human review.
Built for title examiners, abstractors, attorneys, landmen, survey offices, and records teams.
Workflow
Start with the location. End with evidence your team can use.
- 1Upload or paste a batch of legal descriptions.
- 2Normalize the description and retain the original text.
- 3Resolve each record to a location or flag it for review.
- 4Compare duplicate, overlap, gap, and acreage signals where geometry supports it.
- 5Export a review queue with the original input, normalized form, result, and limitation.
Output
The useful unit is the completed research job.
Each result keeps the land identity and the source context together, so a reviewer can see what was found, where it came from, and what still needs professional judgment.
Plotted result
Resolved centroid or polygon for the records that match the grid.
Review queue
Ambiguous, malformed, duplicate, or unsupported descriptions separated for human review.
Sample response
A concrete artifact beats a layer list.
This example shows the shape of the work. Values are illustrative and should not be treated as a live result until the source records are retrieved for the requested location.
{
"input": "NE 14 32N 21W Montana Meridian",
"normalized": "NE¼ Sec 14 T32N R21W Montana Meridian",
"status": "resolved",
"qa_flags": [],
"original_preserved": true
}Questions this workflow should answer
Put one real workflow in front of the team.
Start with one tract, corridor, or assignment. Then decide which repeatable work deserves a deeper integration.
Review batch conversion