Pressconnects Obituaries Today Honoring Lives Guiding Community Grief With Dignified Reporting

Navigating the Pressconnects Obituary Section

I spent years working local news, and one of the more tedious parts of that job was dealing with the obituary desk. Not because the content was hard — it was usually just plain text sent over by funeral homes or family members — but because figuring out how to present it properly on the website, keeping everything accurate and dignified while also meeting deadlines, took a fair amount of attention to detail. The Pressconnects has built something reasonable around this. Their obituary section today is called Pressconnects Obituaries Today Honoring Lives Guiding Community Grief With Dignified Reporting, and it's not some automated feed. Someone at least reads these before they go live. Here's what that actually looks like from the inside. When a death is reported, the standard flow starts with a phone call or an email to the funeral home. They submit a draft — sometimes typed up, sometimes pasted from a Word doc, sometimes handwritten on a form. The editor reviews it for accuracy, checks the name against a local directory if possible, verifies dates, makes sure the service information is clear. Then it gets posted. Simple on paper. Not always simple in practice. The first thing people get wrong is assuming obituary content is static. It isn't. Families will call back three days later asking to change the time of the visitation. Someone will realize they forgot to mention a surviving grandchild. A correction needs to go out. The Pressconnects system handles this through an edit log, which means every change is trackable. That's useful. It's also a pain when you're working a graveyard shift and the copy comes in at 11:45 PM on a Friday.

I ran into a specific problem a couple years ago that took me about forty-five minutes to sort out. A family submitted an obituary for a man who had recently moved from New Haven to Manchester. The address listed was his old one, and the funeral home had the new address. The service details were contradictory — one line said the visitation was at St. Mary's Church in New Haven, another said it was at St. Mary's in Manchester. Two different churches with the same name, ten miles apart. The family hadn't caught it because they were grief-stricken, which is completely understandable. But printing the wrong church location would have been a real mess for people showing up. I called the funeral director, got clarification, updated both the print version and the web listing, and added a note in the internal log so no one else would have to re-investigate it if someone else picked up the file later. That's the kind of thing that doesn't show up in any training manual but happens regularly.

How Pressconnects Obituaries Today Honoring Lives Guiding Community Grief With Dignified Reporting Actually Works

Let me break down the workflow without making it sound more complicated than it is. The Pressconnects uses a content management system — I believe it's a customized WordPress installation with a custom plugin for obituary management — that lets staff pull submitted obituaries into a queue. Each entry has fields for the full text, photo, service details, survivor list, and a couple of metadata tags like cause of death (optional), veteran status, and whether a donation in lieu of flowers is requested. The photo part is where things can go sideways. Funeral homes will send a JPEG that's either too small to print at the standard column width or way too large and takes forever to load on mobile. I usually resize incoming images to about 600 pixels wide, which works for both the print layout and the web. If the family sends a scanned photo that's grainy or dark, I leave it as-is rather than trying to enhance it. These are memorial photos. People get upset if you "fix" a picture of their mother and it doesn't look like the version they remember. There's also a premium component. The Pressconnects offers expanded obituaries — longer formats, multiple photos, embedded video tributes — that families pay for through the funeral home. This is how newspapers still make money on obits when print circulation is in freefall. The basic obituary runs for free in print and online. The paid version gets pushed to the front of the queue, gets a larger photo, and appears on the homepage rotation. It's transparent if you look at it long enough. I've seen younger editors squirm about this. They shouldn't. It subsidizes the free content everyone else gets.

One counter-intuitive thing about this work: the most detailed obituaries aren't always the ones people read. The ones that get shared, forwarded, and commented on are usually the shorter, sharper ones — the five-hundred-word pieces that capture a person in a few paragraphs instead of listing every accomplishment like a resume. I once edited a ninety-word obituary for a guy who'd been a sheet metal worker for thirty years. It mentioned he liked fishing, his dog's name, and that he could fix anything with a wrench. That piece got more engagement than a two-thousand-word biography of the local mayor published the same week. There's no formula for it, but it's worth knowing if you're writing these things for a living. Another nuance that trips people up: the difference between an obituary and a death notice. An obituary is a narrative — it tells a story about the person. A death notice is essentially a factual announcement with names, dates, and service information. The Pressconnects accepts both. Death notices are cheaper and faster to process. Obituaries require more editorial oversight. Some families don't know the difference and submit a death notice wanting it to read like an obituary. That's when the conversation happens about length, tone, and what can realistically fit in the space available.

The Reality of Managing This Section Day to Day

If you're considering submitting an obituary to the Pressconnects, there are a few practical things to know. First, submit as early as possible. The daily deadline for online obituaries is typically around noon, but print deadlines can be earlier depending on the edition. Miss the window and your loved one's notice might not appear for a day or two. Second, double-check every date. Month of birth, month of death, age — these are the most common errors and the hardest to catch in a quick read-through. Third, if you're including a photo, make sure it's something the family is comfortable with publicly. I've had to pull photos after publication because a relative saw them and didn't want them online. It's awkward but it happens. There are limitations to what this system can handle. It can't verify every claim in an obituary. If a family says the deceased served in the Vietnam War, the Pressconnects typically takes their word for it unless there's an obvious red flag. They don't cross-reference military records or pull draft files. That's not their job. It also can't accommodate every request — religious specificity, non-English text, complex family structures that don't fit standard templates. When something falls outside the normal format, it usually gets flagged for manual review, which slows things down. For anyone who needs this content quickly or in a format the Pressconnects doesn't support, the alternative is usually a paid placement through a dedicated obituary service like Legacy.com or a local funeral home's own publishing platform. Those can be faster but lack the editorial review process. Whether that's a trade-off worth making depends on what you're prioritizing.

The bottom line is that Pressconnects Obituaries Today Honoring Lives Guiding Community Grief With Dignified Reporting isn't perfect. It's a newsroom operation doing its best with limited staffing, tight deadlines, and families who are often exhausted and grieving. The people who work this beat care about getting it right. They make mistakes occasionally — names spelled wrong, times listed incorrectly, photos that don't match the text. But they also fix those mistakes quickly when they're pointed out. That's the honest version of how this works.