What a funeral home app should hold, and what it should never do.
A funeral home app is mostly ordinary software: one record per case, a list of who is doing what, the documents, the schedule. What is not ordinary is the screen a family sees in the first week. Patterns that are fine in client portal apps read very differently to somebody whose mother died on Tuesday, and most of the work on that screen is taking things away.
This page covers the price rules you already work under, what an app cannot do about the death certificate, what a family facing screen should never do, and where software actually helps in the days around the service.
See what to take off the family screenThe short version
The internal half is a records problem, the family half is a restraint problem.
Two different things hide inside one build. What people mean by a funeral director app is the internal half: one record per case holding the first call, the transfer, the arrangement, the documents, the tasks and the names spelled the way the family spells them. That part is ordinary and worth building carefully.
Facing the family, the job is almost entirely subtraction. No urgency, no recommendations, no prompts, no badges. A screen that shows what was chosen, what it costs and what happens next, and then stops. Nearly every mistake in this category is something that was added rather than something that was missing.
What a family facing screen must never do
Start with what to remove, because a bereaved family is the easiest group in the world to push and the worst group to push. No countdown, no limited time price, no urgency of any kind. Nothing marked most popular or recommended beside a casket or a package. No pre-ticked extras inside a bundle, because the right to decline single items is the basis of the price rules in the next section.
No account wall in front of a price. A funeral provider has to answer price questions by telephone from the price lists, and the FTC guidance is explicit that the caller cannot be required to give a name or to come in first. A funeral arrangement app that demands a login before it shows a figure is doing less than the telephone already has to do.
No review request, no marketing message, no newsletter tick box folded into an arrangement form. And no field where something a family typed at midnight becomes part of a legal record without a person reading it back to them. Collect it, then confirm it out loud.
Two quieter ones. Do not make a family log in again to see something they already gave you. Do not show a progress bar that implies they are behind. A checklist that nags is worse than a phone call, and the phone call is the thing they will remember either way.
Check the screen
What the family sees
Tick anything the family facing screen does today. Each one is worth taking out.
0 to take out
Nothing ticked. The screen shows what was chosen, what it costs and what happens next, and then it stops.
The price rules apply whether or not there is an app
In the United States the FTC Funeral Rule governs how a funeral provider discloses prices, and none of it is suspended because you built something. The provider gives a printed price list for retention to people who ask in person about funeral goods, services or prices, and for retention means the family keeps the copy. A casket price list goes to anyone who asks in person about caskets, before the caskets are shown. An outer burial container list works the same way.
By telephone, the provider tells callers any accurate information from those lists. At the end of the arrangement conference the family gets an itemised statement of the funeral goods and services selected, with the individual prices, cash advance items listed separately, and a total. One of the disclosures the price list has to carry is that embalming is not required by law except in certain cases.
As written the rule covers requests made in person, by telephone and by mail. It does not require you to publish prices on a website or in an app, and the FTC has asked publicly whether that should change, so read the current text before you rely on either half of that sentence. For a build the practical rule is simpler. If a number appears on a screen it matches the general price list exactly, it carries the same effective date, and one named person changes both. Two price lists drifting apart is the failure mode here, and it is a compliance problem long before it is a design problem.
The death certificate does not go through your app
The funeral director is responsible for filing an accurate and complete death certificate with the proper registration official, although state laws vary in the specific requirements. In practice the director completes or has completed the personal items, obtains the cause of death certification from the attending physician or from the medical examiner or coroner, secures the signature of the person pronouncing death, and files within the time limit set by that state's vital statistics laws.
Many jurisdictions have replaced paper forms with an electronic death registration system, a secure web based system that connects health care providers, medical certifiers, medical examiners or coroners, funeral directors and local registrars. Those are the jurisdiction's systems and funeral directors follow the standards and procedures in their own area. Whether an outside application can connect to a particular state's system is a question for that state's vital records office. We have not verified it for any state, so do not plan around it.
That split decides your design. The app holds the working information: the informant, their relationship to the decedent and their mailing address, the spellings checked with the family, the disposition details, the authorisations still outstanding and who is waiting on whom. The handbook guidance on names is worth copying straight into the interface, because Smith and Smyth or Gail and Gayle are exactly what gets corrected later. What the app must never do is show a record as filed when it is only sitting in the app.
CDC NCHS, Funeral Director's Handbook on Death Registration, 2019 revision
The days around the service are where software helps
Between the first call and the service the work is logistics, and logistics is what a phone is good at. Who is collecting the flowers, which celebrant confirmed, when the cars leave, how many certified copies were ordered, which cousin has the photographs. A memorial service app is mostly that: one record per case, visible to whoever is on duty, which removes the calls that exist only to ask where something got to.
On the day, the register is the classic paper object and the classic loss. A guest book gets rained on or left in a car. The mechanics are those of any event check in app: a name, a time, an optional message, an export the family can keep. The difference is tone. Nobody is scanning a code at a graveside, so the version that works lets staff add names on the family's behalf and lets anyone who wants to write in the book still write in the book.
Memorial gifts are the other thing families ask about and the thing most often tracked on a sheet of paper. Where the notice says donations in lieu of flowers, somebody has to know what arrived and tell the family, which is a small donation tracking app living inside the case record. Keep the amounts out of the family view unless they ask. The name of the person who gave is usually what they wanted.
Aftercare is the part everyone intends to build and few people do. A short list of tasks that fall due weeks later, a reminder about the copies that were promised, a note of the first anniversary. It is a small feature. It is also the one families mention by name afterwards.
What each option gives a funeral home
| Option | Family can see it on a phone | One record per case | Matches your own price list | Records who confirmed what |
|---|---|---|---|---|
| Paper file and phone calls | No | if you are holding the folder | Yes | if somebody wrote it down |
| Shared drive and spreadsheets | No | No | Yes | file history, roughly |
| Funeral home management software | varies by vendor | Yes | within the vendor fields | varies by vendor |
| A page on your website | Yes | No | a second copy to keep in step | No |
| An app you build | Yes | Yes | Yes | if you build the log |
Building one around your own firm
Funeral home management software exists and for many firms it is the right answer. It is priced per firm or per case, shaped around the vendor's fields, and it assumes you will work the way it works. The gap people describe is usually small and specific: a transfer log the platform has no field for, a form the registrar keeps sending back, a family screen you would like far plainer than the one you were given.
Newly is an AI app builder. You describe the app, including the parts of your process that do not fit a template, and it writes a real React Native project you own, then ships it: iOS through TestFlight with your own Apple Developer account, Android to Google Play internal testing and as a standalone APK. It costs $25 a month and there is no free plan. It is not funeral home management software, it does not connect to any state registration system, and it does not handle payments.
Before any of that, settle who may see a family's file and write the answer down: the arranger, the director on duty, the person covering the weekend, the contractor you sometimes use for transfers. Access is the hardest decision to retrofit and the one a family would mind most if it went wrong.
Questions people ask about funeral home apps
Software a funeral firm runs on phones and tablets: one record per case holding the first call, the transfer, the arrangement, the documents, the schedule and the tasks, plus a narrow view a family can see. It is a records and logistics tool. It is not a filing system for vital records, and it does not replace the price lists you already hand over.
Write down how your firm actually works
Start with the days around a service and the fields your registrar keeps sending back, and build around those rather than around somebody else's template.
Start building