To document a site so you can return and detect it again, you’ll need to capture GPS coordinates in decimal degrees to five decimal places, photograph every key feature with embedded timestamps, and record all measurements tied to fixed datum points. Confirm land ownership and permissions before arrival, then organize your files with consistent naming conventions, metadata tags, and backup storage. Follow a standardized protocol across every visit, and the sections ahead will show you exactly how to build one.
Key Takeaways
- Record GPS coordinates in decimal degrees to at least five decimal places using a consistent datum system like NAD83 or WGS84.
- Capture georeferenced, timestamped photographs paired with coordinate data to enable precise, independent verification of each site location.
- Anchor all measurements to fixed datum points with coordinates, recording surface elevations for accurate future spatial detection.
- Apply consistent file naming conventions, metadata tags, and organized folder structures to ensure records remain retrievable and verifiable.
- Document methodology, researcher details, date, and site limitations with each deliverable to support repeatable, future return visits.
Why Site Documentation Fails Before the Return Visit
Most site documentation failures trace back to decisions made before anyone sets foot on location. You skip the historical context, and you’ll arrive without knowing what you’re looking for. You bypass stakeholder interviews, and you’ll miss deficiencies that only occupants or landowners can identify.
Most documentation failures are decided before arrival — skip the preparation, and you’ve already lost the site.
Pre-visit planning isn’t procedural overhead — it’s your operational foundation. Without defining scope, confirming land ownership status, and compiling precise coordinates to at least five decimal places, you’re collecting data you can’t verify or relocate.
You lose the ability to detect change between visits because you never established a reliable baseline.
Freedom to work efficiently on-site depends entirely on the decisions you make before arriving. Shortcut the preparation, and you’ve already compromised the documentation’s long-term utility.
Define Your Site Documentation Scope Before You Arrive
Before you set foot on-site, define your documentation scope by identifying site boundaries, flagging known hazards, and securing the access permissions you’ll need.
Pull target coordinates in decimal degrees to at least five decimal places, and confirm land ownership status—whether private, tribal, state, or federal—so you’re not turned away on arrival.
Resolving these variables in advance keeps your field work focused and eliminates delays that compromise data quality.
Identify Site Boundaries Early
Defining your documentation scope before you set foot on-site saves time, prevents missed data, and keeps your team aligned on deliverables. Boundary clarification is your first priority. Pull property records, parcel maps, or deed descriptions to confirm legal extents before arrival. Don’t rely on visual assumptions once you’re in the field.
Use landmark referencing to anchor your boundaries to fixed, identifiable features—road intersections, utility poles, or permanent structures—so you can relocate them independently later. Mark these anchors on a base map using decimal-degree coordinates to at least five decimal places.
Confirm land ownership status early to secure access permissions without delay. Knowing exactly where your site begins and ends prevents scope creep, protects against liability, and ensures your documentation remains legally and spatially defensible.
Flag Hazards Before Arriving
Hazard identification begins at your desk, not on-site. Before you set foot on any property, pull available records—environmental reports, prior inspection notes, utility maps—and flag every known risk. You’re looking for structural instability, chemical contamination, restricted airspace, or active utility lines that could compromise your safety or your equipment.
Cross-reference your target coordinates against public hazard databases and land classification records. If the site falls under tribal, federal, or private jurisdiction, confirm access permissions before arrival—trespassing creates legal exposure, not just physical risk.
Build your safety protocols around what you discover during this pre-visit review. Brief every team member on identified hazards before departure. Arriving informed means you control the conditions of your documentation rather than reacting to surprises that could compromise the entire operation.
Secure Access Permissions First
Access permissions aren’t a formality—they’re a hard prerequisite that determines whether your documentation effort is legally defensible or wasted. Before you step foot on any site, confirm ownership verification by identifying whether the land is privately held, tribal, state, or federally managed. Each classification triggers a different permission pathway, and skipping this step exposes you to trespass liability or data invalidation.
Contact the landowner directly using confirmed name, address, and phone number. Get written authorization before arrival—verbal agreements don’t protect you in disputes.
For public or tribal lands, submit access requests to the appropriate managing agency with adequate lead time. Once access permissions are secured and documented, you control the legal foundation of your entire site record. Without it, your data has no standing.
Capture GPS Coordinates That Hold Up Under Review
GPS coordinates that don’t meet reviewers’ standards can invalidate site records, so you’ll want to capture them with consistent precision from the start. Record all coordinates in decimal degrees with a minimum of five decimal places to guarantee GPS accuracy across platforms and reviewers.
Specify your datum system — either NAD83 or WGS84 — for every coordinate entry. Mixed or unlabeled datums will fail coordinate validation and undermine your entire record. Use a calibrated GPS device or survey-grade mobile tool rather than relying on a standard smartphone’s native app.
Log coordinates at multiple fixed reference points across the site, not just a single entry location. Pair each coordinate set with a timestamped photograph to create an independently verifiable spatial record that holds up under technical or legal review.
Collect On-Site Data You Can Actually Verify Later
Once you’re on-site, capture high-resolution photographs with timestamps and georeferences tied to the same datum system you established during planning.
Use tape measures, laser scanners, or LIDAR tools to record precise dimensions, then anchor those measurements to fixed datum points that define original surface elevations.
These two practices—georeferenced imagery and datum-referenced measurements—create a verifiable record that holds up when drawings, claims, or conditions are later challenged.
Georeferenced Photos With Timestamps
When you photograph a site without embedded location and time data, you’re creating records that can’t be independently verified—a serious liability in any documentation workflow. Enable GPS tagging on every capture device before you arrive. Georeferencing accuracy depends on your device acquiring a strong satellite fix, so allow 60 seconds for lock before shooting.
Timestamp consistency requires that all devices—phones, cameras, tablets—sync to the same time source before fieldwork begins. A one-minute drift across devices corrupts your sequence.
Shoot in high resolution, confirm EXIF data is writing correctly, and cross-check coordinates against your pre-compiled target latitude/longitude values compiled to five decimal places. These embedded data points become your defensible proof of presence, condition, and sequence—records you and others can independently verify years later.
Precise Measurements and Datum Points
Georeferenced photos establish where you were and when—but they don’t tell you how things were built or how surfaces relate to one another. For that, you need precise measurements and recorded datum points.
Use tape measures, laser distance tools, or LIDAR scanners to capture structural dimensions, ceiling heights, and surface relationships. Record spot levels tied to a consistent benchmark—datum consistency guarantees every elevation reading means the same thing across return visits.
Mark datum points physically and log their coordinates in decimal degrees to at least five places. Coordinate accuracy at this level prevents drift between site visits and keeps your baseline defensible. Note grid levels defining original surface elevations, and annotate these directly onto field-marked floor plans so measurements stay tied to specific locations.
Organize Site Documentation Photos and Files for Fast Retrieval
Organizing your site documentation files from the start prevents costly retrieval delays and version confusion down the line. Use consistent photo naming that combines project name, date, and subject in under 25 characters, separating words with dashes or underscores for platform searchability.
Apply metadata tagging to every image file, embedding GPS coordinates, timestamps, and condition notes directly into the file properties. This makes filtering and locating specific records fast and precise.
Digital archiving requires a structured directory system separating photos, correspondence, field notes, and drawings into clearly labeled folders by discipline and date. Store backup copies in at least two locations — one local, one off-site or cloud-based.
You control your data when your system is deliberate, consistent, and built to scale independently.
Convert Field Notes Into Floor Plans and Elevations
Once your files are archived and accessible, the next step is converting raw field notes into usable drawings. Start with baseline floor plans derived directly from your measured sketches and LIDAR data. Transfer room dimensions, wall thicknesses, and structural elements first, then layer in door and window locations.
Convert raw field notes into baseline floor plans—transferring dimensions, wall thicknesses, and structural elements before layering in openings.
Add material annotations to identify finishes, substrates, and structural components at each surface. These notations let you verify conditions independently without returning unnecessarily.
Next, build interior and exterior elevations from your spot levels and datum points. Apply elevation annotations to mark original surface heights, soil shifts, and visible feature changes. Include scale bars, north arrows, and legends on every sheet.
These drawings become your baseline—your legal and operational record of exactly what existed before any work began.
Build a Repeatable Site Documentation Protocol for Any Project
Building a repeatable protocol means you’re not reinventing your workflow on every project—you’re executing a tested system. Start by standardizing your pre-visit checklist: scope definition, coordinate compilation, land ownership confirmation, and hazard identification. Lock in your naming conventions, datum systems, and photo coverage requirements before you arrive on-site.
During data collection, apply consistent measurement methods, georeferencing standards, and field note formats across every project. Data validation happens in the field and again at the office—cross-check measurements against photographs and flag discrepancies immediately.
For record consistency, organize all files using the same directory structure, correspondence categories, and drawing standards every time. Include a methodology section on every deliverable specifying researcher, date, and limitations. A tested protocol gives you freedom to move fast without sacrificing accuracy.
Save the Spot for Next Time
A great site is only great if you can find it again. Subterrix’s Explorer lets you save named locations with exact coordinates and QR navigation, so returning is as simple as a scan. Treasure Valley Metal Detecting Club members get Subterrix Elite for $8.99 a month instead of the standard $15.99, with 20% of every membership coming back to the club to fund hunts, raffles, and giveaways.
Join Subterrix under TVMDC for $8.99/month
Disclosure: TVMDC earns a share of membership revenue when you join through this link, at no extra cost to you.
Frequently Asked Questions
How Do You Document a Site Located on Tribal or Federal Land?
You’ll need to secure access permissions early, respecting cultural sensitivities and legal considerations tied to tribal or federal jurisdiction. Determine land ownership status, compile precise coordinates, and obtain written authorization before collecting any on-site data.
What Datum System Should You Use When Coordinates Will Cross International Borders?
Use WGS84 for cross-border projects—it’s your best choice for datum selection since it guarantees coordinate accuracy globally. You’ll maintain consistency across jurisdictions, and international teams can verify your recorded positions without conversion errors.
How Far Outside Project Boundaries Should Neighboring Property Conditions Be Documented?
You’ll want to document neighboring property conditions at least 15 feet outside your project’s boundary markers and property lines, extending your coverage up to 50 feet when you’re working in high-risk zones.
Who Should Be Listed as the Responsible Researcher in the Methodology Section?
Who’s accountable when records are questioned? You’re the responsible author — list yourself by name in the methodology section. Include your date, sources, and ethical considerations to guarantee transparent, verifiable documentation that stands independently.
How Should Daily Site Diaries Be Stored Alongside Electronic Photo Backups?
Store your daily site diaries in structured directories alongside electronic photo backups, ensuring digital archiving keeps both linked by date and project name. You’ll want photo metadata to match diary entries for seamless, independent verification later.
References
- https://layer.team/blog/5-methods-for-documenting-existing-conditions
- https://www.openspace.ai/blog/best-practices-for-construction-site-photo-documentation-what-to-capture-and-why-it-matters/
- https://www.nps.gov/subjects/heritagedocumentation/soi-standards-guidelines.htm
- https://d39d3mj7qio96p.cloudfront.net/media/documents/BU532-Site-records.pdf
- https://sitesreservoirproject.riptideweb.com/references/REF21/Appx_02D_BestManagementPractices/CWQMC_2017b_Standard Operating Procedures – Site Reconnaissance.pdf
- https://epe.lac-bac.gc.ca/100/205/301/ic/cdc/artifacts/archae/recordng.htm
- https://fiveable.me/introduction-archaeology/unit-4/site-mapping-documentation/study-guide/Zh7z0kU7pBUGnWOf
