The office needs to answer several questions separately: where is the niche, what is its documented status, who holds rights, what use is permitted and what has actually occurred? Combining all of these into one “sold/unsold” field makes later decisions harder to explain.
What is the unit you are tracking?
Start with the physical unit. Give the niche a stable identifier and record the cemetery, structure, face or panel, row and position used by the office. Retain the manufacturer's or construction reference where it helps staff identify the correct unit.
Decide how the identifier appears to families and staff. A readable label can accompany an internal ID, but both should lead to the same physical location. If a structure is renamed or a panel numbering convention changes, preserve the earlier reference as an alias.
Avoid using a holder's name as the niche identifier. Rights can change, and a family may hold more than one niche. A stable physical reference survives those changes.
How are availability and physical use different?
Use separate fields for inventory and use. A niche may have no recorded inurnment but be held under an existing rights arrangement. Another may be temporarily unavailable for maintenance. A record imported from old files may not yet be reviewed at all.
Our recommended status model is:
| Dimension | Suggested states | Question it answers |
|---|---|---|
| Record review | Reviewed, unreviewed, exception | How confident is the office in this record? |
| Inventory | Available, held, committed, unavailable | May the office offer this unit under its process? |
| Rights | No recorded holder, recorded holder, review pending | What supporting rights record exists? |
| Physical use | No recorded inurnment, one or more recorded events, unknown | What has been documented as occurring? |
| Operational task | None, work planned, work completed, follow-up | What does the team need to do? |
These are proposed operating labels, not legal classifications. Agree on definitions and who may change each status. In particular, unknown should not automatically become available when an import leaves a field blank.
What should staff know about capacity and fit?
Keep the documented dimensions and configuration information needed for the cemetery's review. Where capacity is described in a contract or rule, retain that source instead of relying on a general label such as “double niche.”
Check the actual proposed urn or container against the relevant dimensions and approved use. A sales category should not be treated as a guarantee that every container will fit. Record the review and any unresolved question before promising a service arrangement.
Do not infer a universal number of containers permitted in a niche. Cemetery rules, structure design and rights documents can differ. Savannah's published rules illustrate that a municipality can specify particular inurnment and scheduling requirements. They are a local example, not a national specification.
For families asking what a niche is, explain the term and then refer to the actual cemetery's offered arrangement. Technical inventory language should not force a family to interpret internal dimensions or status codes unaided.
How should a reservation be recorded?
Distinguish an inquiry, a temporary hold and a completed rights transaction. Record the person who requested the hold, the relevant unit, the approving staff member and the agreed terms. Where a hold has an expiry, make it visible to staff and define who reviews it before the niche becomes available again.
A quotation should not silently reserve inventory forever. An expired hold should not silently cancel a completed agreement. Those are different events, and the office needs a review process that reflects the actual terms and applicable requirements.
Record the supporting document rather than reproducing a partial description of the agreement in a status note. Staff should be able to retrieve what was agreed and identify whether a later change was authorized.
How do rights records connect to an inurnment?
Link the niche to the reviewed rights record and the specific planned inurnment. Keep the person providing information, the payer and the person whose authority is reviewed as separate roles where appropriate.
The New York cemetery FAQ is a state-specific example of why rights history and records matter. It should not be used to decide an inheritance question in another jurisdiction. The software's job is to make the supporting history available to the cemetery's qualified reviewer.
After the service, record the actual event and link its completion evidence. A scheduled inurnment is not yet a completed one. If the arrangement changes, preserve the earlier instruction and the approved revision rather than overwriting the history.
A worked example: a reserved unit with no inurnment
In a fictional example, a family reserved a niche several years ago and nobody has been inurned there. A new employee searches for empty niches and sees the unit on a list generated only from interment records.
If the office treats “no interment” as “available,” it may offer a unit already committed under the rights record. The inventory should instead evaluate both the physical-use history and the recorded agreement, with any uncertainty sent for review.
A second family may request two urns in a different niche. Staff should check the relevant unit's dimensions, rules and agreement rather than assuming that every niche in the structure has the same capacity. Both examples belong in a software demonstration.
What should a niche inventory worksheet include?
Use one worksheet or table for physical units and linked records for people, rights and events. Suggested physical-unit fields are stable ID, public label, cemetery/structure, row/position, documented configuration, source reference, review status and inventory status.
The reservation record adds inquiry reference, agreed hold terms, approval and review date. The rights record adds holder and supporting document. The event record adds planned/actual date, person interred and completion reference. Keeping these linked avoids duplicating the same rights history across several flat spreadsheets.
If the office needs a simple printable list, generate it from the reviewed working record and show its issue date. Do not let an undated printed availability sheet become a competing master.
How do you verify an existing inventory?
Pilot the review with several different records: an available unit, a reservation, a recorded rights transaction with no inurnment, a completed inurnment and a historical exception. Compare the system with the supporting documents and approved location reference.
Ask a second employee to find the unit from a family inquiry and explain why it is or is not available. Check that the employee can retrieve the agreement without relying on the original salesperson's memory.
FuneralHQ offers cemetery mapping, plot inventory and deeds as part of the wider platform. Bring niche-specific records to the demonstration and confirm how your structure and agreements are represented. Use the cemetery accounting guide for the financial handoff and cremation follow-up guide for the family's separate return and memorial commitments.
Blank working template
Open the accompanying blank CSV worksheet. This editorial template contains headings only. Adapt it to the firm’s reviewed process before use and keep completed records in approved storage.
The FuneralHQ advantage
Preneed, custody, and cemetery work in one system
FuneralHQ connects preneed, at-need case work, documents, payments, and QuickBooks Online. Chain of custody runs on signed, timestamped forms with QR and barcode scan checkpoints. Cemetery mapping, plot inventory, and deeds are included.
We will work through a real example with you, from the first details to the finished record.
See it on one of your casesAbout the FuneralHQ Editorial Team
This guide was written by the FuneralHQ Editorial Team, the in-house team behind funeral home software used by independent firms to run cases, documents, payments, and QuickBooks sync in one record. Our editorial standards explain how we review product claims, outside sources, automation, updates, and corrections.