How Heraldandreview Obituaries Actually Work in Practice
I spent three years maintaining archives for a regional newspaper that merged with Heraldandreview's obituary system. What I learned is that most people treat this platform like a simple submission form, which is a fundamental misunderstanding of how it operates. The system is built around a heritage index that cross-references names, dates, and family connections across decades of published content. When you submit an obituary through Heraldandreview, you're not just posting a notice. You're creating a node in a database that other researchers, genealogists, and distant relatives will eventually find. The core workflow starts at the submission page, but here's what nobody tells you: the standard template will reject certain formats automatically. Names with diacritical marks, non-Western naming conventions, and hyphenated surnames often get stripped or malformed in the initial parse. I learned this the hard way when a client submitted an obituary for a Vietnamese decedent whose family name came first. The system reordered it during ingestion, making the record essentially unsearchable by the family's preferred name format. The workaround is straightforward if you know it exists. Before you fill out any fields, you download the legacy template file from the Heraldandreview developer resources. It's not advertised prominently. Look under the "Archival Standards" section of their contributor guidelines, not the public-facing help page. This template includes hidden columns for alternate name spellings, phonetic transliterations, and family relationship mappings that the standard UI doesn't expose. Populating those columns preserves data that would otherwise vanish.
Another counter-intuitive detail is the character limit behavior. The public interface shows a 500-word ceiling, but the archival backend accepts up to 2,400 characters in the body field before triggering a second-pass review flag. Most contributors hit the UI limit and cut meaningful biographical content. The trick is to draft everything in a plain text editor first, then paste it in. The system counts differently than a word processor does. What looks like 520 words in Google Docs might be 1,800 characters and still pass automated validation. I've also seen people waste hours trying to attach photos through the standard media upload. The platform accepts JPEG and PNG only, and anything over 3.5 megabytes gets auto-compressed to a quality level that makes facial recognition impossible. For genealogical purposes, that's worthless. The solution is to compress images yourself using a tool like Squoosh or ImageMagick down to around 1.2 megabytes with 75 percent quality before uploading. The archive stores the lower-resolution version anyway because the display layer applies its own compression. You're saving yourself a rejection step. Here's the part that trips up experienced users: the family verification process. Heraldandreview runs a basic cross-check against previously published records to prevent duplicate listings. If the deceased has been mentioned in any prior obituary or anniversary notice within the archive, the system flags the new submission for manual review. This review queue moves slowly. In my experience, typical wait times range from 48 to 120 hours during non-peak periods and can extend to five business days during holiday seasons when staffing drops. I've had cases where families needed urgent publication for a service and the review delay caused real problems. The workaround is to contact the Heraldandreview editorial desk directly with a proof of death document and request expedited processing. They have a separate queue for time-sensitive submissions that processes within six to eight hours.
The heritage search function deserves more attention than it gets. Most people use the basic name search and stop there. But the advanced filter includes a date range slider, a relationship field, and a publication type selector. If you're researching a family line, switching to the advanced view and filtering by "family notice" type alongside obituary type will surface anniversary memorials that reference the same individuals. These secondary records often contain genealogical details not present in the original obituary, such as surviving sibling names or predeceased relatives. One limitation worth noting bluntly: Heraldandreview's archival retention policy has changed several times over the past decade. Records older than a certain threshold get migrated to a read-only repository that doesn't support community corrections or update submissions. If you find an error in a legacy record from 2012 or earlier, you cannot edit it directly. The only path is to submit a correction request through their archival review form, which goes to a different team than the standard editorial desk. Response times for archival corrections average three to four weeks, and approval is not guaranteed. They require documented proof, usually a certified copy of the relevant public record. For people building a research workflow around these obituaries, the most efficient approach is to export records in CSV format rather than relying on screenshots or manual transcription. The export function lives under the search results toolbar and includes fields for the full obituary text, publication date, submitter relationship, and linked family members. I typically run exports monthly for active research projects. The CSV structure maps directly to standard genealogical databases, which saves hours of manual data entry compared to copy-pasting individual entries.
Get the Full Details
The metadata attached to each record is also underutilized. Every obituary in the system carries a normalized date object, geolocation tags for the funeral home or church listed, and a citation key that links back to the original print edition if one exists. Researchers who ignore these fields miss the ability to sort obituaries by geographic cluster or to trace how a single family's notices evolved across multiple publications. I've used the geolocation tag to map migration patterns for immigrant families, which turned out to be more reliable than census data for certain time periods. If you're just getting started, here's what I recommend without any padding. Create your account first and verify your email. Download the legacy template before writing anything. Draft your obituary in a plain text editor and count characters, not words. Compress any images yourself before uploading. Use the advanced search filters when looking up existing records. Export your results to CSV rather than transcribing manually. And if you need something published quickly, skip the automated queue and call the editorial desk directly with documentation ready.
