Cemetery Management
Manages the complete cemetery lifecycle — plot/niche/crypt inventory with GIS mapping, interment rights sales/transfers/surrenders, burial coordination, memorial approvals, grounds maintenance, and FBCSA/BAO regulatory compliance.
Plot Accuracy
Double-Booking
GIS Map Load
FBCSA Compliance
Purpose-Built for Canadian Municipalities
Purpose & Scope
What this module owns
Clear ownership boundaries prevent duplication and ensure every capability has exactly one authoritative home.
Owns
22Delegated to
6Cemetery map rendering, plot boundaries
Rights sales, fees, instalments
Approval workflows, interment authorization
Certificates, contracts, historical records
Grave preparation, maintenance
Cemetery infrastructure tracking
These capabilities are handled by dedicated modules and consumed via stable API contracts — keeping boundaries clean and ownership unambiguous.
Core Capabilities
What it does
4 capability groups comprising 19 discrete capabilities — each with API surface, business rules, and data ownership.
Registry of cemetery properties with BAO licences, zones/sections, and denomination details.
Properties
Name, address, denomination, acreage, BAO licence #, bylaw reference. Multiple cemeteries.
Zones
Zones/sections: old, new, veterans, children, cremation garden, columbarium.
Every space tracked with type, size, status, unique ID, and GIS boundary for interactive mapping.
Space Types
Section, lot, grave, type (full burial/cremation/niche/crypt/scatter/bench). Attributes: size (single/double/family), depth, orientation, accessibility.
Status
Status (available/sold/reserved/occupied/unavailable). Unique ID. GIS boundary.
Interactive map with click-to-query, layers for status, infrastructure, and printable sections.
Interactive
Plot boundaries, pathways, roads, landmarks. Click → plot ID, status, rights holder, occupant(s), history.
Layers
Layers: available/occupied/reserved/infrastructure. Printable sections.
Individual niche position tracking with visual wall layout and occupancy status.
Positions
Individual niche positions (row × column). Status: available/sold/occupied (1 of 2 urns)/fully occupied.
Attributes
Size (single/companion/family), material, inscription plate. Visual wall layout.
Remaining capacity by type and section with depletion forecasting and development planning.
Current
Remaining by type/section/cemetery. Sold-but-unoccupied tracking.
Forecast
Depletion forecast (years at current rate). New section development planning.
Every module owns a single bounded context, exposes stable APIs, and can be composed into any Civic product — that's the architecture that scales.
Krutik Parikh
Creator of Civic
Data Model
Entity Architecture
6 entities with 7 relationships — the authoritative schema for this bounded context.
Entities
Select an entity to explore its fields and relationships
API Surface
Integration Endpoints
10 RESTful endpoints across 7 resource groups — plus 4 domain events for async integration.
/api/v1/cemeteries
Cemetery registry
/api/v1/cemeteries/{id}/map
GIS cemetery map
Ecosystem
Products that depend on this module
1 Civic products consume Cemetery Management — making it one of the most critical platform services in the ecosystem.
Technical Specifications
Performance, Compliance & Configuration
Plot Inventory Accuracy
Scheduling Double-Booking
GIS Map Load
FBCSA/BAO Compliance
Processing Time Reduction
FAQ
Frequently Asked Questions
Ready to Integrate
Build on Cemetery Management
Request an architecture brief, integration guide, or live demo environment for your team.