Commissioned Research
Top 10 Best Graveyard Mapping Software of 2026

GITNUXSOFTWARE REVIEW

Tourism & Hospitality

Top 10 Best Graveyard Mapping Software of 2026

Compare graveyard mapping software tools for research and record keeping, covering Cemify, WebCemeteries, and ArcGIS for planning workflows.

21 min readUpdated Editorially scoped research
How we ranked these tools
01Editorial Scope

Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.

02Source Research

Search agents gather the source set and the review record, including transcriptions of video reviews and podcasts.

Read our full methodology →

Framework: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy

Graveyard mapping software matters when cemetery operators need parcel-accurate plot layouts tied to burial records, maintenance history, and public-facing lookup. This comparison helps analysts and technical evaluators weigh GIS-first tools against management platforms that focus on records, publishing, and role-based access, then plan setup for automation, integrations, and reporting.

Cemify is the best pick for cemetery teams that need georeferenced plotting with ongoing record maintenance because it links headstone imagery and memorial record fields directly to map-layer features, whereas ArcGIS fits enterprise GIS groups that require API-driven automation through feature-service attribute editing.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

Cemify

Cemify ties memorial record fields and headstone imagery to geospatial plot features inside map-layer editing.

Best for: Fits when cemetery teams need georeferenced plotting with ongoing record maintenance and controlled access.

2

WebCemeteries

Editor pick

Linking headstone imaging directly to memorial records inside the cemetery mapping workflow.

Best for: Fits when cemetery staff need a maintained grave location database with map layers and linked headstone images.

3

ArcGIS

Editor pick

Editing and synchronization through ArcGIS feature services with configurable forms and domain-restricted attribute workflows.

Best for: Fits when governance-heavy cemetery GIS teams need a geospatial system with API-driven automation.

Comparison Table

1
CemifyBest overall
vertical specialist
9.3/10
Overall
2
vertical specialist
8.8/10
Overall
3
enterprise
8.7/10
Overall
4
SMB
8.4/10
Overall
5
vertical specialist
8.3/10
Overall
6
vertical specialist
7.9/10
Overall
7
vertical specialist
7.5/10
Overall
8
vertical specialist
7.3/10
Overall
9
vertical specialist
6.8/10
Overall
10
vertical specialist
6.7/10
Overall
#1

Cemify

vertical specialist

Cloud-based cemetery mapping and digitization with public gravesite lookup and plot availability.

9.3/10
Overall
Features9.3/10
Ease of Use9.5/10
Value9.1/10
Standout feature

Cemify ties memorial record fields and headstone imagery to geospatial plot features inside map-layer editing.

Cemify focuses on graveyard mapping workflows that connect field capture results to a searchable grave location database. It supports map-layer driven cemetery layout management, including section and plot visualization, so staff can reconcile interment records against geospatial features.

Cemify also emphasizes automation for ongoing data maintenance, such as keeping memorial and image-linked records tied to the correct location. Admin controls are built around managing cemetery-specific datasets and controlling access to editing and view permissions.

Pros
  • +Map-layer workflows for cemetery section and plot layout management
  • +Grave location database structure that links interment and memorial records
  • +Automation to keep image-linked records associated with locations
  • +Admin permissions for separating view and edit access by cemetery dataset
Cons
  • –Automation setup requires governance around who can edit which features
  • –Limited visibility into batch-quality issues for duplicate grave records
  • –Export formats depend on map-layer configuration rather than raw feature types
  • –Field capture integration depth can be restrictive without specific add-ons
Use scenarios
  • Cemetery mapping and planning staff

    Maintain a digital cemetery master map

    Navigable master map

  • Monument coordinators

    Coordinate headstone work with locations

    Continuity between records and tasks

Show 2 more scenarios
  • Cemetery field staff

    Lookup graves during site visits

    Faster location-based lookups

    Search map layers and related memorial details to locate specific burial sites during on-site work.

  • Cemetery data administrators

    Migrate legacy map and register data

    Consolidated legacy information

    Import existing register or map data and export layers or reports for downstream operational workflows.

Best for: Fits when cemetery teams need georeferenced plotting with ongoing record maintenance and controlled access.

#2

WebCemeteries

vertical specialist

Web-based cemetery management software for mapping plots, maintaining records, and publishing cemetery data.

8.8/10
Overall
Features8.8/10
Ease of Use8.8/10
Value8.8/10
Standout feature

Linking headstone imaging directly to memorial records inside the cemetery mapping workflow.

WebCemeteries focuses on cemetery mapping workflows that convert field capture into georeferenced grave location records and section-level map layers. It centers around interactive map layer management, so staff can maintain plot inventories and synchronize updates across a cemetery dataset.

The product also supports headstone imaging capture and ties photos to memorial records for burial-site mapping and later restoration work. WebCemeteries is geared toward operational data stewardship where duplicates, missing plots, and lot and space record gaps are handled as part of ongoing maintenance.

Pros
  • +Interactive map layer management for section and plot views
  • +Grave location records tied to headstone imaging for memorial context
  • +Workflow fit for updating cemetery survey data and plot inventories
  • +Designed for ongoing maintenance across interment and memorial records
Cons
  • –Less clear integration depth for large GIS stacks and enterprise workflows
  • –Requires disciplined configuration to prevent duplicate grave records
  • –Field data synchronization can feel narrow for multi-cemetery operations
  • –Export formats for GIS interchange may limit complex parcel boundary workflows
Use scenarios
  • Cemetery mapping and GIS staff

    Represent plot inventories in maps

    Searchable cemetery locations

  • Cemetery offices serving families

    Publish grave and memorial searches

    Faster public access

Show 2 more scenarios
  • Cemetery operations managers

    Update plot occupancy and availability

    Clear burial inventory

    Track occupied, reserved, and available statuses during planning and interment activities.

  • Cemetery administrators

    Maintain consistent burial registers

    Consistent digital register

    Update interment records while keeping burial details connected to the correct plot and location.

Best for: Fits when cemetery staff need a maintained grave location database with map layers and linked headstone images.

#3

ArcGIS

enterprise

GIS software for surveying cemetery grounds, creating parcel maps, and managing spatial records.

8.7/10
Overall
Features8.7/10
Ease of Use8.8/10
Value8.6/10
Standout feature

Editing and synchronization through ArcGIS feature services with configurable forms and domain-restricted attribute workflows.

ArcGIS supports cemetery mapping by turning field-collected points and surveyed boundaries into georeferenced map layers that can be shared to staff and public viewers.

ArcGIS provides a configurable data and workflow layer via feature services, editable tables, and form-driven capture that can connect GPS collection to plot grid and memorial fields.

ArcGIS supports automation through REST endpoints for geocoding, feature updates, and geoprocessing, which can power periodic imports, duplicate detection, and bulk corrections.

Pros
  • +Feature services with attribute editing for grave plot inventory and interment records
  • +REST API access for custom cemetery search portal and map interactions
  • +Geoprocessing tools for boundary validation and bulk updates of map layers
  • +Role-based access controls with audit trails for map and data governance
Cons
  • –Cemetery-specific UX for grave lookup needs configuration beyond default templates
  • –Maintaining georeferencing accuracy requires careful control of source imagery and control points
  • –Throughput for large headstone imaging workflows depends on external storage and processing design
  • –Data model alignment between plot grid, interment records, and memorial fields takes upfront schema planning
Use scenarios
  • Cemetery operators and municipal teams

    Run internal and public grave locator maps

    Maintained plot inventories

  • Emergency management teams

    Coordinate incidents using shared maps

    Faster incident coordination

Show 2 more scenarios
  • Transportation and logistics planners

    Plan service coverage and access routes

    Location-informed decisions

    Use spatial routing and network data to evaluate access, coverage areas, and delivery decisions.

  • Infrastructure and field operations teams

    Track assets and work updates on maps

    Current map-based status

    Map assets, assignments, and operational updates against shared spatial layers for a current view.

Best for: Fits when governance-heavy cemetery GIS teams need a geospatial system with API-driven automation.

#4

QGIS

SMB

Open-source GIS software for creating cemetery maps and managing geospatial burial records.

8.4/10
Overall
Features8.4/10
Ease of Use8.3/10
Value8.5/10
Standout feature

Attribute-driven symbology and labeling with map layouts makes consistent cemetery section and lot views from the same editable dataset.

QGIS is a GIS desktop application used to build cemetery GIS workflows around georeferenced maps and editable layers. It supports importing and exporting formats like shapefile, GeoJSON, and KML, managing map-layer symbology and layouts for section and plot views.

Pros
  • +Layer-based editing supports point and polygon grave plot digitization in one project
  • +Python scripting and processing models enable repeatable cemetery map production
  • +Import and export support common GIS formats for field and survey handoffs
  • +Layout engine creates consistent section maps, keys, and legend output
Cons
  • –No built-in cemetery grave location database schema for interment record modeling
  • –Shared multi-user governance requires external database and process design
  • –Large cemetery datasets can feel slow without tuned indexes and map tiling
  • –Field data sync and reconciliation require add-ons or custom scripting
Use scenarios
  • Field survey and asset-mapping teams

    Collect updates with offline reference layers

    Portable offline mapping

  • Parcel and plot mapping teams

    Digitize cemetery boundaries and connect attributes

    Editable plot maps

Show 2 more scenarios
  • Environmental consultants

    Assess constraints for site planning

    Constraint assessment maps

    Overlay habitats, buffers, and terrain layers to evaluate potential sites or development options.

  • GIS production teams

    Produce consistent cemetery map exports

    More repeatable exports

    Apply shared styles, processing models, and map-series layouts to generate repeatable multi-sheet deliverables.

Best for: Fits when teams need configurable cemetery GIS mapping with custom workflows and reporting, not a turnkey grave database portal.

#5

CemSites

vertical specialist

Cemetery management software supporting digital maps, property records, and online memorial information.

8.3/10
Overall
Features8.3/10
Ease of Use8.3/10
Value8.3/10
Standout feature

Headstone imaging can be tied directly to mapped grave identifiers for audit-friendly visual context.

CemSites supports cemetery section mapping and grave plot inventory so teams can structure burial locations and track changes per section and lot. It also supports memorial records and headstone imaging workflows so visual evidence can be attached to grave identifiers. The admin side is oriented around managing site objects and maps for ongoing maintenance rather than running a full GIS administration program. Integration and extensibility exist, but the API and automation surface appear more limited for large-scale data sync across multiple field teams.

Pros
  • +Plot-level inventory structure helps maintain consistent grave identifiers
  • +Headstone imaging attachments support evidence-based memorial updates
  • +Cemetery section mapping keeps large sites organized
  • +Search-friendly burial-site records reduce manual lookup time
Cons
  • –Limited GIS layer modeling depth compared with full GIS platforms
  • –Automation and API coverage feels narrower for high-frequency sync pipelines
  • –Complex multi-team workflows require stricter internal process discipline
Use scenarios
  • Cemetery operations teams

    Maintain plot inventory and memorial records

    Faster corrections and cleaner records

  • Field survey contractors

    Digitize survey findings into site maps

    Reduced rework between field and office

Show 1 more scenario
  • Municipal heritage program

    Publish searchable cemetery history

    More usable restoration documentation

    Use cemetery section mapping and memorial records to support public or partner search portals.

Best for: Fits when cemetery staff need plot mapping plus memorial evidence capture without heavy GIS ops.

#6

CIMS Professional

vertical specialist

Cloud-based cemetery management with GIS smart maps, drone imagery integration, and walk-to-grave navigation.

7.9/10
Overall
Features7.9/10
Ease of Use7.9/10
Value7.9/10
Standout feature

Record-linked cemetery mapping that ties plot geometry to interment and memorial fields for day-to-day corrections.

CIMS Professional is a cemetery mapping system focused on turning cemetery surveys and burial-site records into a searchable grave location inventory. It supports section and plot organization so staff can manage lot and space records alongside interment and memorial details.

Pros
  • +Plot and section structure matches real cemetery grave inventory workflows
  • +Mapped grave locations connect directly to interment and memorial records
  • +Export paths support GIS handoff for external map review
  • +Role-based access helps separate survey entry from approvals
Cons
  • –Mapping setup requires careful upfront configuration of plots and sections
  • –Advanced GIS layer management is thinner than full GIS products
  • –Bulk edits across large cemeteries take more manual step control
  • –Integration options outside the core workflow appear limited
Use scenarios
  • Cemetery operations staff

    Search mapped graves and inventory records

    Searchable grave inventory

  • Cemetery data entry teams

    Keep interments consistent with map points

    Consistent mapped records

Show 1 more scenario
  • Cemetery administrators

    Manage lot, space, and access steps

    Controlled data workflow

    Use section and plot organization alongside controlled data entry and review access for operations.

Best for: Fits when cemetery teams need a governed grave database tied to mapped plots for ongoing record maintenance.

#7

Memorial Mapper

vertical specialist

Cemetery mapping plan with interactive plot maps linked to burial records and memorial pages.

7.5/10
Overall
Features7.5/10
Ease of Use7.6/10
Value7.4/10
Standout feature

Record-to-plot linking that keeps memorial entry mappings consistent across repeated cemetery imports.

Memorial Mapper is built for grave identification workflows that require consistent linking between memorial records and spatial features. It supports map-layer management for section and plot boundaries so teams can maintain a burial plot inventory over time. Import pipelines are geared toward cemetery survey data and ongoing updates instead of one-time GIS publishing.

Pros
  • +Linking memorial records to geospatial plot features for precise lookup
  • +Map-layer management for sections and plot boundaries
  • +Repeatable import and update workflow for ongoing cemetery digitization
  • +Multi-user operations for cemetery teams and partner contributors
Cons
  • –Record-to-plot matching needs careful governance to avoid wrong placements
  • –Advanced GIS layer tuning can require map data preparation discipline
  • –Public-facing search configuration is less flexible than custom web GIS builds
Use scenarios
  • Cemetery operations teams

    Maintain burial plot inventory

    Fewer misidentifications at lookup

  • Graveyard digitization groups

    Digitize burial registers with maps

    Faster record completion cycles

Show 2 more scenarios
  • Field survey data managers

    Verify GPS survey against plots

    Reduced spatial drift in records

    Survey updates refresh spatial context while keeping memorial mappings anchored to plots.

  • Cemetery search portal operators

    Publish georeferenced map layers

    Improved location-based searching

    Operators deliver section and plot views tied to memorial details for visitor and staff search.

Best for: Fits when cemetery teams need map publishing tied to memorial records and ongoing data refreshes.

#8

GraveyardMapper

vertical specialist

Cemetery mapping tool supporting satellite imagery and SVG plans with drag-and-drop plot editing.

7.3/10
Overall
Features7.3/10
Ease of Use7.3/10
Value7.3/10
Standout feature

Georeferenced cemetery area mapping that ties each grave location record to map-layer context for fast cross-checking.

GraveyardMapper manages cemetery mapping records by linking burial locations to georeferenced cemetery areas for visual grave-site tracking. It supports data capture workflows that translate survey or field observations into map-layered points and inventory-style records.

Pros
  • +Map-first workflow that keeps grave entries tied to location geometry
  • +Supports importing and exporting cemetery data in common GIS formats
  • +Helps reduce duplicate grave records with location-based identification
  • +Works well for section and plot navigation inside a single cemetery area
Cons
  • –API surface is limited compared with GIS-first mapping stacks
  • –Data cleanup for historical interment backfills can be manual
  • –Advanced layer styling and map theming options are constrained
  • –Role separation and audit logging for multi-admin teams are basic
Use scenarios
  • Cemetery staff for field tracking

    Navigate to graves using mapped areas

    Location-based navigation

  • GIS-oriented cemetery teams

    Convert field observations into mappable records

    Mapped inventory records

Show 1 more scenario
  • Cemetery records coordinators

    Reconcile and correct grave entries

    Reconciled location lists

    Add and fix grave entries over time while keeping location lists consistent for tracking.

Best for: Fits when a cemetery or archive needs map-linked burial-site inventory with periodic reconciliation and GIS export.

#9

pg_friedhof

vertical specialist

Comprehensive cemetery management software built on QGIS with desktop, web, and mobile apps.

6.8/10
Overall
Features6.8/10
Ease of Use6.8/10
Value6.8/10
Standout feature

GeoJSON and KML export tailored to cemetery map-layer handoff for grave identification and viewer workflows.

pg_friedhof targets cemetery mapping workflows that need georeferenced grave records linked to real-world map layers. It supports working with cemetery sections, plots, and interment-related data through a GIS-style interface that can be exported into common geospatial formats like GeoJSON and KML.

Pros
  • +GIS layer workflow supports plotting section and lot geometry for burial-site mapping
  • +Exports GeoJSON and KML for exchanging cemetery map layers with other GIS tools
  • +Layer organization helps keep point and polygon features manageable during surveys
  • +Import-driven updates support digitizing burial register information into a mapped inventory
Cons
  • –Automation depth is limited for recurring bulk updates across many interment records
  • –API surface and integration options are not clearly centered on bidirectional field sync
  • –Data governance controls like RBAC and audit logs are not a primary, visible strength
  • –Complex cemetery workflows often require careful configuration of layers and attributes
Use scenarios
  • Cemetery mapping operators

    Maintain georeferenced grave features

    Organized georeferenced features

  • Cemetery office reviewers

    Review mapped points during data checks

    Faster field data review

Show 2 more scenarios
  • GIS data teams

    Export cemetery layers to common formats

    GIS-ready exports

    Export georeferenced cemetery mapping data into GeoJSON and KML for downstream reuse.

  • Data administrators

    Update layers through import and layer workflows

    Up-to-date map layers

    Use import, update, and layer workflows to keep mapped records aligned with changes over time.

Best for: Fits when a cemetery GIS team needs digitized grave locations tied to map layers and exportable formats.

#10

CemeteryBase

vertical specialist

Interactive digital cemetery mapping with drag-and-drop grid builder and color-coded plot status.

6.7/10
Overall
Features6.7/10
Ease of Use6.7/10
Value6.7/10
Standout feature

Location-to-record binding that preserves grave identification through imports and edits, reducing duplicates during ongoing surveys.

CemeteryBase centers on cemetery mapping as an operational grave location database, not just a static viewer. It provides tools to define sections and plots, attach interment and memorial records to specific locations, and maintain a consistent grave identification workflow across imports and edits. The integration depth is strongest when GIS outputs and field-collected coordinates need to stay aligned through repeat survey cycles. Governance features support internal administration so multiple staff can update map and record data without breaking location-to-record relationships.

Pros
  • +Maintains stable links between grave identifiers and map locations
  • +Supports import and iterative updates for cemetery record digitization
  • +Exports georeferenced map layers for GIS handoff workflows
  • +Change tracking supports correction cycles after field verification
Cons
  • –Best accuracy requires careful initial georeferencing and plot setup
  • –Dense workflows can feel technical for map editors
Use scenarios
  • Cemetery operations teams

    Map new interments by plot

    Faster on-site lookup

  • GIS analysts

    Handoff maps to GIS tooling

    Lower rework on data

Show 2 more scenarios
  • Digitization program managers

    Clean legacy burial register imports

    Cleaner grave location database

    Performs iterative corrections so duplicate grave records can be merged during digitization cycles.

  • Field survey coordinators

    Synchronize GPS findings to map

    More accurate cemetery search portal

    Ingests collected coordinates and aligns them with existing plot structures for continuous maintenance.

Best for: Fits when cemetery teams need repeatable mapping updates that keep plot, interment, and search keys consistent.

Conclusion

After evaluating 10 graveyard mapping software, Cemify stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.

Our Top Pick
Cemify

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About Graveyard Mapping Software

How does CemeteryBase keep grave identification consistent across repeated imports and edits?
CemeteryBase binds plot and interment details into a location-to-record linkage that preserves grave identification during imports and map edits. Admin review and change history help teams spot when a record would otherwise drift and produce duplicate grave records. The workflow is designed for ongoing survey updates rather than one-time digitization.
Which tool best supports headstone imaging tied directly to mapped grave identifiers?
CemSites ties headstone imaging to mapped grave identifiers for audit-friendly visual context. WebCemeteries and Cemify also connect headstone images to memorial records inside the mapping workflow. The difference is whether image capture sits inside operational map-layer editing and synchronization.
When should a cemetery team choose ArcGIS instead of a desktop GIS workflow like QGIS?
ArcGIS fits governance-heavy cemetery GIS teams that need publish-and-sync workflows and API-driven automation through REST APIs and feature services. QGIS fits mapping teams that require custom GIS layout and editing pipelines using shapefile, GeoJSON, or KML exports and Python scripting. If the main requirement is multi-department sync and attribute workflows, ArcGIS aligns better.
How do WebCemeteries and Memorial Mapper differ in the way they manage map layers and record links?
WebCemeteries emphasizes interactive map-layer management for section-level layers and keeps a maintained grave location database with linked headstone images. Memorial Mapper centers on connecting lot and memorial records to georeferenced map layers and focusing on import-to-plot assignment for publishing views. WebCemeteries is more operational for ongoing layer stewardship, while Memorial Mapper is more publishing-oriented for memorial-linked maps.
What breaks when a cemetery does not use a location-to-record binding workflow?
In Cemify, breaking the binding between memorial record fields and geospatial plot features leads to mismatches during map-layer edits and ongoing data maintenance. CemeteryBase shows the same failure mode when repeated imports do not preserve grave identification, which increases the risk of duplicate grave records. These tools are built to prevent drift between the grave-location dataset and interment or memorial entries.
How does pg_friedhof handle exporting cemetery mapping data for external viewers or GIS handoff?
pg_friedhof exports cemetery map layers as GeoJSON and KML so grave points and plot polygons can be used in external viewer workflows. Map-layer management keeps point and polygon features organized for cemetery search and field review. Automation is driven through import and update workflows rather than rules-engine bulk processing.
Which tool is better suited for multi-cemetery administration with access controls and auditing?
ArcGIS supports role-based access patterns, auditing support, and governed sharing across multi-department operations. CemeteryBase also provides admin-managed access, review controls, and change history tied to dataset edits. CemSites focuses on site administration for multiple cemeteries but keeps the automation surface narrower than GIS pipeline governance.
How do QGIS and CIMS Professional differ for teams that need a configurable mapping workflow versus a governed grave inventory?
QGIS is a configurable GIS desktop that builds cemetery GIS mapping workflows and editable layers, with exports like shapefile, GeoJSON, and KML and automation via Python scripting. CIMS Professional is built around a searchable grave location inventory that keeps section and plot organization aligned with lot and space records and interment or memorial fields. The tradeoff is tool flexibility versus operational database structure for day-to-day corrections.
What integration and data-synchronization capability expectations should be set before implementation?
ArcGIS supports automation through REST APIs, webhooks, and configurable forms with feature services for field data synchronization. CemeteryBase includes automation and data synchronization features to reduce duplicate grave records during ongoing surveys and maintenance documentation. QGIS can integrate with external services, but it does not provide a dedicated cemetery-grave database front end by itself, so integration work depends on the custom workflow.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Graveyard Mapping Software

We see the big differences come from how faithfully a tool handles grave-to-location records and how well it keeps maps, forms, and records consistent over time.

Data model for grave and plot links

Why it matters

A clear Data model for grave and plot links prevents mismatches when people move between sections, plats, and individual graves. It also determines whether you can correct errors once and have the map and record views follow.

How to check

In a demo, import a small sample set with at least one section/plot and several graves, then verify that each grave stays tied to the right plot after edits.

API access for records and map actions

Why it matters

Integration depth via API matters when your graveyard workflow spans multiple systems like records, scheduling, and reporting. With an API, you can control how updates propagate and reduce manual re-entry.

How to check

Ask for documentation or a live sandbox showing endpoints for creating/updating records and requesting map-related outputs. Try a simple workflow: pull a set of graves by location filter, then push an update and confirm the map reflects it without a manual redraw.

Automation for bulk edits and imports

Why it matters

Automation and bulk updates are what keep the database trustworthy during periodic maintenance and backfills. Good tools reduce the chance that one staff member updates the map while another updates only the record.

How to check

Request a bulk import of a CSV with section and grave fields, then verify validation rules and error reporting for bad rows. Check whether you can remap or re-link multiple graves in one workflow and see audit-like output for what changed.

Admin roles and change audit log

Why it matters

Admin and governance controls like RBAC and an audit log let you control who can change grave locations and who can view them. For death care teams, that reduces accidental edits and creates a defensible history of changes.

How to check

In the admin area, confirm whether at least two roles exist (viewer vs editor) and whether editing permissions can be limited to specific sections. Then update one grave location and check that the system records who changed it, what field changed, and when.

Map workflows tied to record updates

Why it matters

If map interactions are only visual, staff still end up typing updates elsewhere, creating drift. A graveyard mapping tool should make selection, labeling, and edits directly correspond to record changes.

How to check

Go through a workflow in the demo: select a grave on the map (or via list), edit its location fields, and save. Confirm whether the record view and map view update together and whether the system prevents edits that would break required links.

Support for field capture and offline work

Why it matters

Field capture support matters when teams confirm locations on-site and need a reliable path from capture to the main map. When offline work is handled well, you avoid transcription errors and late-night data cleanup.

How to check

Ask whether staff can capture or mark observations in a field workflow and then sync later. In the demo, simulate a delayed sync and confirm how conflicts are handled when the same grave was edited during the offline window.

Red flags

  • Edits on the map don’t reliably update the linked records
  • Bulk import errors aren’t explainable or are hard to correct
  • Roles are limited to view vs edit without audit detail

Fit by situation

  • If you’re cleaning legacy records and need corrections to stay consistent, prioritize Data model for grave and plot links.
  • If multiple teams or systems must update locations reliably, prioritize API access for records and map actions.
  • If staff confirm placements on-site and sync later, prioritize Support for field capture and offline work.
Commissioned Research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.