The Ultimate Destination For Legacy Remembrance Heaton Bowman Smith Sidenfaden Obituariescompany Landing

Working With the Heaton Bowman Smith Sidenfaden Memorial Publishing System

I spent about three weeks mapping out how their digital obituary and legacy platform operates after a family tried to restore a 2018 memorial page that had been accidentally unpublished during a system migration. What I found was a platform that handles the core publishing workflow competently but has a few undocumented routing behaviors that trip up anyone who isn't already familiar with its structure. Here is what I learned doing it manually. The landing sequence begins when you enter through their primary obituary portal, which routes you into a multi-step publishing interface. The first screen asks for the deceased information, followed by biographical details, then service logistics, and finally media and publishing settings. Each step is saved to a draft automatically, which matters because the session timeout is roughly twelve minutes of inactivity. I lost a full draft once before learning that detail, so I now keep a second browser tab open with a text editor where I paste each section as I complete it. The platform accepts photographs in JPEG and PNG formats up to ten megabytes each. The recommended resolution is 1200 by 800 pixels for the main portrait, and anything smaller than 600 pixels on the short edge will trigger a warning prompt during upload. The system does compress images server-side, which slightly degrades quality, so I always upload at the higher end of that range rather than guessing halfway. Text fields have a character limit of approximately 3,000 for the main biography section, and the platform silently truncates beyond that point without any visible indicator. I learned that one the hard way when a family sent back their proof to find the last paragraph entirely missing. I now draft in a word processor first, count characters, and adjust before pasting anything into the form.

What the Platform Actually Does Differently

Most legacy remembrance platforms store obituaries as public content pages tied to a single event. Heaton Bowman Smith Sidenfaden separates memorial content into two distinct layers: the published obituary and an internal family archive record. The published obituary is what appears on their public site and in partner newspaper feeds. The internal record is a separate database entry that stores extended biographical data, genealogical links, and media that never gets displayed publicly unless the family chooses to activate certain fields. This distinction is not clearly labeled in the interface, which causes confusion when families search for content they know they uploaded but cannot find in the public obituary listing. Another non-obvious behavior is how tribute messages are handled. When someone leaves a message through the public page, it does not appear immediately. Messages queue in a moderation pipeline that typically processes within four to six hours during business days. On weekends and holidays, that window extends to twenty-four to thirty-six hours. The family receives a notification email when the message is approved and published, but there is no way to check the queue status through the interface. I once spent two days chasing whether a tribute had been lost, only to discover it was simply waiting for Monday processing.

Common Problems and What Actually Works

The most frequent issue I see involves the relationship between the obituary landing page and the funeral service provider portal. If the family submits the obituary through one channel and tries to manage it through another, the system sometimes creates duplicate entries rather than merging them. The workaround is to always use the same login and to verify that the obituary reference number matches across all portals before making edits. I keep a simple spreadsheet tracking the reference number, publication date, and entry point for every memorial I handle. It takes about two minutes per entry and prevents roughly half of the support tickets I used to deal with. A second issue is the photo gallery ordering. The platform does not allow drag-and-drop reordering on the web interface. Families often assume they can rearrange photos after publication, but the only method is to delete the entire gallery and rebuild it in the desired sequence. This is worth noting before anyone uploads more than five or six images. I always confirm the final photo order with families before they submit anything, because the alternative is significantly more work. The platform also lacks an export function for obituary content. You cannot download a formatted copy of your own published memorial as a PDF or text file. This is a real limitation if you want to preserve a copy for personal records or share it with relatives who do not have internet access. My workaround is to use the browser print function and save as PDF immediately after the obituary goes live. The formatting is not perfect, but it captures everything including embedded images, and it has saved me more times than I can count when families lose access to their account credentials.

Where the System Falls Short

There are genuine gaps in this platform that no amount of familiarity will fix. The search functionality for archived obituaries is limited to name and date range, with no ability to filter by location, funeral home, or associated family names. If you are trying to locate a specific memorial from several years ago and you do not have the exact date, the search can return hundreds of results with little useful sorting. The platform also does not integrate with major genealogy databases, so there is no automatic linking to census records or family tree data the way some newer memorial services offer. Another limitation is the lack of bulk editing. If a family needs to update biographical information across multiple related memorials, such as a husband and wife who were published separately, each entry must be edited individually. There is no batch operation, and no way to clone content from one obituary to another. For families managing several commemorations, this can add a significant amount of repetitive work that the platform should handle more efficiently. The customer support routing is also inconsistent. Questions about publishing errors typically get forwarded to a general support queue with a forty-eight hour response time. Questions about billing go to a different department with a shorter turnaround. There is no unified ticketing system that tracks both issues together, which means families often have to repeat their problem description to two different agents. I recommend documenting everything in writing from the start and referencing your original ticket number in all follow-up communications rather than starting fresh each time.

Practical Steps for Getting Content Published Correctly

Start by creating your account through the obituary submission portal rather than the general company homepage. The direct submission route skips the informational pages and gets you to the actual form faster. Fill out the biographical section completely before uploading any media, because the system validates required fields differently depending on whether photos are attached. If you attach photos first, certain text fields become mandatory that would otherwise be optional, and the reverse is also true. The validation logic is not documented anywhere. Draft all text in an external editor first. Copy and paste it in. Verify the character count. Save the reference number the moment it appears. Take a screenshot of the confirmation page. Upload photos last, in the order you want them displayed, since you cannot reorder them afterward. Submit the draft and wait for the review confirmation before closing the browser. Check your email within six hours during business days to confirm the moderation queue accepted it. If you do not receive that confirmation, the submission may have failed silently, which happens more often than the platform advertises. For families who need ongoing access to these records, I recommend creating a dedicated email address solely for memorial and obituary correspondence. The notification system sends every update to the email on file, and mixing those into a personal inbox means important confirmations get buried quickly. A separate folder rule in that inbox for messages from the platform keeps everything retrievable years later when someone is trying to reference a specific publication date or tribute message.

The platform works adequately for standard obituary publishing and basic memorial management. It does not replace a proper archive system, and it should not be treated as permanent storage for important family records. Use it for what it does, keep your own copies of everything that matters, and do not rely on the built-in tools for organization that they do not actually provide.