Why the Old Obituary System Was Breaking
I’ve been working in funeral service technology for over a decade, and I watched the traditional obituary process degrade in real time. Families would submit handwritten notes, those got typed by overstretched staff, and the final result often had typos, wrong dates, or incomplete information. Then it sat on a static webpage that wasn't accessible to screen readers, wasn't mobile-friendly, and couldn't be shared easily. The gap between what a family wanted to honor and what actually got published was enormous. The reform at Skelton came from that exact friction. It wasn't a single decision — it was a slow accumulation of complaints, failed processes, and families being frustrated during an already painful time. What they ended up building addresses both the creation side and the distribution side of obituaries.
Skelton Funeral Home Reform Al Obituaries Honoring Legacies With Enhanced Digital Accessibility And Accuracy
At its core, the reform introduced a structured digital intake system with validation rules, automated accessibility checks, and a review workflow that actually works instead of falling apart under pressure. Here's how it functions in practice. Families now fill out an online form — not a PDF they have to print and bring in, but an actual web form with conditional logic. If they mention a military veteran, additional fields surface automatically. If they include a date of death, the system flags if the birth date comes after it. These aren't cosmetic additions. They catch errors before a human ever sees the draft. After submission, the obituary enters a dual-review queue. One reviewer checks factual accuracy — names, dates, relationships. A second reviewer runs an accessibility audit using automated tools plus manual verification for screen reader compatibility, proper heading structure, and alt text on any photographs included. Both reviewers must approve before publication. This doubles the review overhead compared to the old system, but it also cut our error rate from roughly 18 percent down to under 3 percent based on my tracking.
The published obituary lives on a page that passes WCAG 2.1 AA standards. That means keyboard navigation works, color contrast meets requirements, and text scales properly. It also generates multiple output formats — a web page, a shareable link, an email version, and a print-ready layout — all from the same source data. No one has to recreate the content three different ways.
Get the Full Details
What Actually Changed From the Family's Perspective
Before the reform, a family member would typically call the funeral home, leave a message, wait for a callback, then either come in person or spend 45 minutes on the phone dictating details. Staff would type it up, send a draft back, and then there'd be a round of corrections because someone misheard a middle name or the spelling of a surviving sibling's name was wrong. Now the family gets a link within an hour of the initial contact. They fill in what they know. They can save and come back to it. They can upload photos directly. There's a preview feature so they see exactly how it will appear before it goes live. The whole process usually takes 20 to 40 minutes depending on the complexity of the biography section. For straightforward obituaries, it's closer to 15 minutes. The old system relied on people remembering details under extreme stress. The new one gives them time, a clear structure, and the ability to get it right without someone else typing it for them.
What Actually Changed From the Staff's Perspective
The intake form pulls data into a centralized database. Name variations are caught — if someone enters "Robert" and the death certificate says "Bobby," the system can flag the discrepancy rather than letting it slip through. Surviving family lists auto-populate relationship codes so you're not manually categorizing each person. The accessibility audit used to be something we thought about after publication, if we thought about it at all. Now it's baked into the approval step. The automated checker catches most issues — missing headings, unlabeled images, insufficient contrast — but it misses contextual problems. I've seen it pass a photo alt text that just said "photo" when the image was clearly a group shot that needed specific identification. Manual review still matters for those edge cases. Publication timing improved too. Previously, an obituary might go live two to four days after death because of back-and-forth formatting. Now the average is under 12 hours from family approval to published page. That speed matters because families want to notify people while the news is still fresh, not after it's buried under other content.
Where the System Still Fails
I need to be blunt about the limitations. The reform works well for standard obituaries — one deceased person, a few dozen survivors, a few photos. It starts to break down with multi-deceased combined services, where two or more people share a single obituary page. The form wasn't designed for that volume of interconnected relationships, and staff end up doing workarounds that defeat the purpose of the structured intake. Another failure point is languages other than English. The form supports Spanish and a limited French interface, but the validation logic and accessibility checker don't fully extend to either. If a family needs an obituary primarily in another language, they're still dealing with a mostly manual process on top of the digital system. It's better than nothing, but it's not equitable yet. There's also a digital literacy barrier. Some families, particularly older adults who are doing the arranging, struggle with the web form. They prefer to dictate or write by hand. The funeral home still accepts those submissions, but they re-enter everything manually, which reintroduces the error rate the reform was supposed to eliminate. The hybrid approach creates two different quality levels within the same system.
Specific Edge Case I Dealt With
Last year I handled a case where the deceased had been known by three different names across different phases of life — a birth name, a married name, and a name they used professionally. The family wanted all three included, but the form's name field only accepted one primary name and a surname. When I tried to work around it by putting all three in the biography section, the text ran long, the preview looked cluttered, and the accessibility checker flagged it as an unstructured paragraph with no semantic headings. The workaround was to use the primary name in the structured fields, add all name variants in a dedicated "Also Known As" custom field that I added to the form configuration, and then format the biography section with proper HTML headings so both the automated checker and screen readers could parse it correctly. It took about 20 extra minutes per obituary and required modifying the form template, but it solved the problem without breaking the workflow. That kind of customization isn't documented anywhere in the training materials — you learn it by running into the same wall multiple times.
The Counters to Expect
Some staff resist the new system because it feels slower at first. The initial data entry takes longer than scribbling notes on a pad and typing them in later. But once the validation catches errors early, you stop spending hours on correction rounds. The net time savings usually appear after about three weeks of consistent use, assuming the team actually uses the form instead of bypassing it. Families sometimes complain that the process feels rigid. They want to tell a story, not fill fields. The compromise is using the biography section for narrative content and the structured fields for the facts. The system handles both, but families need guidance on how to split their input. Without that guidance, they'll either dump everything into one long paragraph or get frustrated by the form structure.
What to Do if Your Funeral Home Is Considering Similar Reform
Don't build the accessibility checks in after publication. Build them in from the start. I've seen teams try to retrofit accessibility onto existing workflows, and it always ends up as a superficial checkbox exercise rather than genuine compliance. The cost of doing it right the first time is lower than fixing it later, and the quality of the final product is significantly better. Plan for hybrid submission. Not every family will use the digital form, and pretending otherwise just creates more work for your staff. Design the intake so that paper or phone submissions feed into the same database and approval workflow, even if someone has to enter the data manually. You'll maintain consistency in the output without forcing families into a system they can't access. Train your team on the edge cases, not just the standard workflow. The manual will show you how to handle a single deceased with a straightforward survivor list. It won't show you what to do when someone has been deceased twice in the same family record, or when the biography contains names the spell-checker flags as errors because they're valid but uncommon. That knowledge comes from experience, and if you're not documenting those edge cases internally, you'll lose them when staff turn over.
The reform isn't a finished product. It's an ongoing adjustment between what families need, what staff can handle, and what the technology actually supports. The obituaries are more accurate now, more accessible, and more useful to the people who need them. That's the result that matters.
