Run a QA process for writing metes-and-bounds legal descriptions
domain: state board of professional land surveyors (practice standards vary by state) · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Verify the description begins at a clearly tied Point of Beginning (POB) referenced to a found or established monument, with a defensible tie to record evidence (adjoiner deeds, prior plats, or PLSS corners as applicable).
Check mathematical closure: trace every bearing and distance call in sequence and confirm the final course returns exactly to the POB within your state's/firm's precision tolerance — an unclosed description is defective.
Cross-check every call against the field survey data and against adjoiner/record deeds to catch gaps, overlaps, or ambiguous monument calls (e.g., a call to a monument that no longer exists without a fallback bearing/distance).
Have a second qualified reviewer (not the original drafter) independently redraft or plot the description from scratch and compare the resulting plotted parcel to the intended boundary before it goes out under seal.
Confirm area computation, easement/exception language, and any curve data (radius, delta, chord) are internally consistent with the plat, then retain the closure calculations and review notes in the project file.
Known gotchas
A description that appears complete can still fail to close mathematically if a single bearing or distance was transposed — always run an independent closure check, don't just proofread the text.
Precision/closure tolerances for boundary descriptions are set by state statute or board rule and vary by jurisdiction and survey type — confirm your state's specific tolerance rather than using a generic rule of thumb.
Relying on a single drafter with no independent second review is the most common source of metes-and-bounds errors that surface later as boundary disputes.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?