Why Most Funeral Homes Are Still Stuck With Paper Files And Nobody'S Talking About It
I spent about nine years running the back office for a mid-sized funeral home before moving into consulting. The first thing I noticed when I started auditing operations was how much time went to waste on manual data entry. Not hours per week, more like two or three days of pure busywork every month. Phone calls transferred back and forth. Faxes sent to the wrong address. Forms filled out three times because the printer ran out of ink mid-form and someone had to restart from the top. The Thomson Funeral System Transforming Endoflife Care With Digital Innovation And Dignity isn't some silver bullet, but it does address a real gap. Most legacy software in this space was built in the late 1990s and bolted with a web interface in the 2010s. Thomson's approach is different because it was architected from the ground up as a cloud-native platform, not retrofitted. That distinction matters more than most people realize.
Thomson Funeral System Transforming Endoflife Care With Digital Innovation And Dignity: How It Actually Works
The core of the system is a centralized case management module that tracks every interaction from the moment a death notification comes in through final settlement. What makes it functional in practice is how it handles interdependencies between tasks. Most funeral directors I've talked to don't think about this until something breaks, but a burial permit application depends on a death certificate, which depends on medical certification, which depends on the attending physician signing off within a specific timeframe. Miss one link and the whole chain stalls. The system flags these dependencies automatically. If a permit application can't be filed because the death certificate number is missing, it shows that blocker in red on the case timeline rather than waiting until you're three days past the filing deadline to discover the problem. This alone has saved me from more missed state compliance windows than I care to count. On the family-facing side, there's a client portal that lets next-of-kin upload documents, review service options, and track payment status without calling the office. From an operational standpoint, this is significant because it reduces inbound phone volume by roughly forty percent once the family gets comfortable using it. The key word is comfortable. You have to walk them through it, and not everyone is going to. I've had families who would rather sit in the waiting room and wait their turn to speak to someone in person than log into a portal. That's fine, but it means the system doesn't replace human interaction, it just shifts where certain interactions happen.
The merchandising module is where things get more complicated. It handles casket and urn inventory, displays pricing tiers, and generates comparison sheets. The counter-intuitive part here is that most funeral homes don't actually use the full catalog feature as intended. They treat it like a price list and pull up their own spreadsheets anyway. The system's real value in merchandising isn't displaying products, it's tracking which items are in stock versus on backorder and automating reorder alerts. When a particular casket model had a six-week lead time during supply chain disruptions last year, the reorder warnings kept us from promising families delivery dates we couldn't meet. That's the kind of thing that doesn't make it into vendor marketing materials. Pre-need planning is the other major module. The system structures conversations around benefit options, pricing guarantees, and installment payment schedules. What beginners miss is that pre-need contracts have a compliance layer most people underestimate. Different states require different disclosures, different cooling-off periods, and different fund handling rules. The Thomson platform has a state-specific compliance engine that adjusts the documentation flow based on where the contract is executed. This isn't a trivial feature because getting it wrong means potential regulatory action, not just an awkward conversation with a family member. There's also an analytics dashboard that pulls data from all the modules. It tells you average case duration by service type, which merchandising items convert at what margins, and where bottlenecks are forming in your workflow. I found this useful for identifying that our cremation cases were taking nearly twice as long as direct burial cases, which turned out to be because the crematory scheduling was sitting in a separate calendar nobody checked regularly. Fixing that reduced turnaround time from an average of three days to under twenty-four hours for cremations.
Get the Full Details
Implementation And What Nobody Warns You About
Setting up the system properly takes about two to three weeks for a single-location funeral home. Data migration from legacy systems is the biggest variable. If you're coming off paper records, plan for an additional week of manual entry. If you're migrating from another digital system, expect format mismatches and budget extra time for cleaning up duplicate or corrupted records. I once inherited a client database from a system that hadn't been updated since 2008, and roughly thirty percent of the records had incomplete fields that the migration tool couldn't handle. I had to write a script to cross-reference names against birth and death dates to match duplicates. The Thomson support team offered to help but the response time was two to three business days, which isn't helpful when you're in the middle of a migration window. Staff training is another area where things get uncomfortable quickly. Not everyone wants to learn new software, especially people who've been doing things the same way for twenty years. I've watched experienced funeral directors resist the portal system because they felt it removed the personal touch from client communication. The reality is that the portal handles routine updates and document requests so the staff can focus on the conversations that actually require a human being. But convincing people of that takes time and patience, and the system itself can't solve that problem. Integration with third-party services is also worth considering. The system connects with crematories, cemeteries, and states for permit filings in many jurisdictions, but not all. Before committing, verify exactly which partnerships are live in your state and which still require manual submission. I learned this the hard way when a state burial permit integration went live on paper and the digital submission option wasn't actually functional yet. We ended up printing the completed forms and hand-delivering them while the system was showing everything as filed.
Pricing runs roughly two thousand to four thousand dollars per location per month depending on the module bundle and volume. That's not cheap for a small funeral home operating on thin margins. The return comes from reduced administrative labor and fewer compliance mistakes, but if you're handling fewer than ten cases per month, the math doesn't work as clearly. In those situations, a lighter workflow tool or even a well-configured custom Google Sheets setup might serve you better until volume justifies the investment.
Common Mistakes And How To Avoid Them
The most frequent problem I see is incomplete data entry at the intake stage. If you don't capture every required field when the case opens, downstream modules start failing silently. A missing Social Security number, for example, doesn't break anything immediately but causes a permit filing error three days later that could have been caught in minutes. Make data validation a strict part of your intake checklist, not a suggestion. Another issue is treating the system as a replacement for process design. Digitizing a broken process just makes the broken process faster. If your current workflow has unnecessary approval steps or redundant data collection, implement the system first and then streamline. Otherwise you're automating inefficiency. The client portal adoption rate is another metric that gets overlooked. The portal works well when families know about it and know how to use it. Sending a welcome email with a link isn't enough. Schedule a fifteen-minute walkthrough during the arrangement conference, print a one-page guide with the login URL, and follow up with a text message if they haven't logged in within forty-eight hours. Even with all that, expect about twenty percent of families to never use it, and plan accordingly.
Backups and disaster recovery are handled on Thomson's infrastructure, which is reliable, but you still need a local copy of critical documents. I keep a compressed archive of every active case exported weekly. If the cloud goes down, which it occasionally does, you can still access basic case information from your own machines for a day or two until service is restored.
When It Doesn'T Work
The system struggles in two specific scenarios. First, very small operations with irregular case volume find the learning curve hard to justify. The time spent configuring the system and training staff could be better used on direct client work when you're handling three to five cases a month. Second, rural locations with unreliable internet connectivity will experience friction. The platform is cloud-dependent, and while it has offline mode for basic data entry, syncing issues cause occasional conflicts that require manual resolution. If your area has frequent outages, factor in extra time for reconciliation. For operators in those situations, I'd recommend evaluating the system during slower months so you have room to troubleshoot without case pressure. Also consider starting with just the core case management module and adding others as your team gets comfortable. Rolling out everything at once is the fastest way to overwhelm staff and generate resistance. The end-of-life care space isn't going digital because it's trendy. It's digital because the alternative, which is mostly paper files and faxes, is failing families who deserve better coordination during an already difficult time. The Thomson system is one of several platforms addressing this, and it's genuinely better than most legacy alternatives for mid-size operations. It isn't perfect, and it isn't right for every situation. But the ones who get past the initial learning curve tend to agree that the operational clarity it provides is worth the effort.
