Death Notices Are Still Paper And Phone Calls
The funeral home industry runs on the same workflow it did in 1998. Someone dies, a family member calls the funeral director, the director types up a notice in a basic editor, and that notice gets emailed to three newspapers that charge by the line. It takes about forty-five minutes of actual work, but the friction is brutal. You're juggling phone trees, word counts, and formatting rules that vary from publication to publication. I've watched people spend two full days preparing obituaries for someone they barely had time to grieve for because the logistics were so heavy. Trn Obits is a platform built specifically for managing death notices at scale. It sits between the funeral director and the publications, handling formatting, distribution, and tracking. The core idea is simple enough, but the execution matters more than you'd expect. When a funeral home processes multiple deaths per week across different regions, the manual routing of notices becomes a genuine bottleneck. Here's how the workflow actually works in practice. You create an obituary in their editor. The system automatically formats it to each target publication's specifications, including the exact character limits and section requirements. Then it routes to every outlet simultaneously. Most funeral homes I've seen cut their average processing time from roughly two hours per notice down to about twelve minutes. That's not a marketing claim, that's what happens when you stop copy-pasting the same text into five different web forms.
One detail people consistently miss is the structured data layer. Trn Obits doesn't just store your obituary as plain text. It parses the name, date of death, service details, and surviving family members into discrete fields. This means you can generate a formatted notice, a social media snippet, and a memorial webpage from the same record without re-entering anything. Most platforms treat these as separate tasks. Trn Obits treats them as variations on one dataset. I ran into a specific problem last fall that nobody had a good answer for. A client needed to publish a death notice in both a major metropolitan newspaper and a small regional paper in a different state, but the regional paper had a strict twenty-line limit that included the family list, while the metro paper had no such restriction. The auto-formatting initially pushed both to the same layout, which meant the regional submission got cut off mid-sentence. The workaround was to set up a custom template override for that specific publication in the system settings, using their published rate card specs as the reference. I spent about twenty minutes configuring it, but after that it saved me from having to manually resize and resubmit every time that particular paper came up. The feature exists, but it's buried in the advanced settings menu and the documentation doesn't call it out explicitly.
What You Actually Save
Time is the obvious metric, but the less obvious wins matter more. First, consistency. When you're manually entering obituaries across multiple newspapers, you inevitably get versions that differ slightly from each other because of copy errors or format drift. With Trn Obits, every publication gets the same source data, reformatted but not rewritten. Second, auditability. Every submission generates a timestamped record of when it went out and to which outlet. If a family asks whether their notice was published in a specific paper on a specific date, you can pull that log immediately instead of calling three different offices and leaving voicemails. Third, the photo handling. Obituary photo submissions are where most people hit walls. Newspapers have their own requirements for resolution, file size, and format. Trn Obits compresses and converts images on the fly to match each publication's spec sheet. I had one case where a funeral director tried uploading a TIFF file to a paper that accepted nothing above two megabytes. The system caught it before submission and prompted the resize. That one check probably saved a missed deadline.
Get the Full Details
Where It Actually Falls Short
I need to be honest about the gaps because nobody else will. The platform depends entirely on having accurate publication metadata in its database. If a local paper changes its obituary format without notifying Trn Obits, the auto-formatting will produce a submission that gets rejected. I've seen this happen with at least two regional outlets where the style guide was updated mid-year and the system hadn't caught up yet. The fix is to verify every new publication format manually before running a batch, which somewhat defeats the automation you're paying for. Another limitation is the international coverage. The system works well across major US publications and a reasonable set of UK and Canadian outlets, but smaller papers outside those markets often aren't in the distribution network. If your funeral home handles cross-border cases regularly, you'll still need a fallback process for outlets Trn Obits doesn't reach. In my experience, that's about thirty percent of smaller-town papers, which is not a trivial number. The pricing model is per-notice, not per-account. For a high-volume funeral home doing twenty or more notices a week, this adds up quickly. A comparable alternative is to maintain direct relationships with regional newspapers and use their own free submission portals, but that approach requires a dedicated person managing those relationships. If you don't have staffing for that, Trn Obits pays for itself. If you do, the math flips.
Getting Started
You don't need a enterprise contract to begin. There's a standard account tier that handles up to ten notices per month, which is enough for smaller homes to evaluate the workflow. The onboarding process takes about an hour if you already have digital versions of your previous obituaries to use as reference templates. Importing from legacy systems is possible but not seamless. The platform accepts CSV exports and a few XML schemas, but the field mapping isn't automatic. You'll spend time aligning your old columns to their expected structure. The editor itself is functional, not pretty. Don't expect drag-and-drop design tools. It's a text-first interface with conditional formatting rules that apply based on your selected publications. That's intentional, because the bottleneck in obituary creation has never been the visual layout, it's been the logistics of getting the right text to the right place on time. Trn Obits optimizes for logistics. If you're already using a funeral home management system, check whether Trn Obits has an integration path for it. A couple of major platforms have one-way data sync built in, which eliminates the double-entry problem entirely. Without that integration, you're still entering data twice, just in a faster system.
The documentation covers the standard use cases thoroughly. It's less clear on edge cases like simultaneous multi-state publications with conflicting privacy requirements or cases where the family requests delays in publishing pending legal proceedings. Those scenarios exist and the platform can handle them, but you'll need to configure them manually rather than through the default workflow. That's worth knowing before you commit to using it as your primary distribution channel.
