Once the open ground is confirmed, the claim layout is designed by hand to capture it efficiently — that judgment does not automate. Everything after it does. Location certificates written to each jurisdiction's statutory requirements, corner cards with GPS coordinates, monument positions computed from that state's own posting rules, a walking order optimized so the crew sets posts in one efficient pass, and recording maps — all generated from one source geometry. The claims are staked and monumented on the ground, then the certificates are recorded with the county recorder and filed with BLM. The package for claim 500 takes the same time to generate as the package for claim 1.

What Ships in a Staking Package

Document

Location Certificates

Complete location certificates for each claim with legal description, PLSS coordinates, claim type, locator information, and all required statutory language for county and BLM filing.

Document

Corner Cards

GPS-accurate corner cards for each claim monument with UTM and lat/long coordinates, bearing and distance ties, and monument descriptions. Ready for field posting.

Map

Claim Maps

Publication-ready maps showing claim boundaries, PLSS grid, monument locations, adjacent claims, and terrain context. Formatted for county recorder filing.

The certificates are written to the statute, not to a template

Every jurisdiction sets its own rules for what a location notice and a recorded certificate must contain, how corners must be monumented, what map has to accompany the recording, and how long you have to record it. They differ in ways that matter: recording windows run from 30 to 90 days depending on the state, some jurisdictions require six or eight monuments where others require four, some require the certificate be sworn before a notary, and several provide that a certificate missing a required element is simply void.

ClaimWatch maintains a verbatim, source-hashed library of the governing federal regulations and every western state's mining claim location and recording statute — the actual text, not a summary of it — and the certificate forms are audited line by line against it. Monument placement in the field applies each state's own posting rules automatically.

We prepare packages across the western United States. If a client needs a jurisdiction or a document the toolchain has not covered before, it gets added — that is generally how the coverage grew in the first place.

Why Automation Matters

Traditional claim staking services prepare each package by hand — drawing boundaries on a topo map, calculating corner coordinates with a ruler and protractor, and typing location certificates one at a time. For a 20-claim block, that works. For a 200-claim block, it takes weeks. For 500+ claims, it becomes a scheduling and quality-control problem.

ClaimWatch's staking processor takes the claim layout as input and generates the entire package computationally. Every coordinate is calculated from the PLSS grid. Every document is populated from the layout data. Every map is rendered from the same source geometry. The output is consistent, accurate, and fast — regardless of how many claims are in the block.

The Process

Who Needs This

How It Fits the Workflow

Staking is step four. Each step before it hands this one a finished input:

Get a Staking Package Estimate

Send us your target area, approximate claim count, and timeline. We'll scope the project and get you an estimate.

Request an Estimate

Related ClaimWatch Services