Deaths this week list: verified names and source notes

The rule behind every serious weekly compilation is short enough to put on a wall: it is always better to be late than to be wrong. A name added a day after everyone else costs a publisher nothing. A name added wrongly reaches someone's family, or the person themselves, and cannot be taken back.

That single asymmetry is the reason verification procedures exist, and it explains most of what looks like slowness in a well-run list.

No person is named here and no death is reported. This page is about the procedure, not about any entry.

What to take away

• Being late costs a publisher nothing. Being wrong reaches a family, or a living person, and cannot be taken back.
• Confirmation means a source with direct knowledge and accountability. Repetition, at any volume, is not a second source.
• Every line should record how it got there: the source, the date checked, and any field that could not be confirmed.

Why the standard is so high

A mistaken death report does specific damage. Relatives are contacted by people offering condolences. Employers, banks and insurers act on what they read. A living person finds their own death circulating and has to prove otherwise, which is harder and more humiliating than it sounds. Search engines and aggregators pick the claim up within minutes and keep serving it long after a correction has run.

None of that is repaired by an apology. So the procedure is not defensive paperwork; it is the only part of the process that can prevent the harm rather than respond to it.

Who counts as confirmation

Not all sources are the same kind of thing, and the useful distinction is whether the source has direct knowledge and accountability for the claim.

Source	Standing
The funeral home or crematorium handling arrangements	Direct, and usually willing to confirm that a service is being arranged
The immediate family, or a representative speaking for them	Direct
An official statement from the employer, club, agency or institution	Direct, where the institution would know
A published death or funeral notice placed through a recognized channel	Direct, though check who placed it
An entry in the civil register, where accessible	Definitive, but usually slower than publication
Social media accounts belonging to family or the institution	Usable with care; accounts get compromised and impersonated
Aggregators, fan pages, encyclopedic entries, unattributed posts	Not confirmation, at any volume

The last row is where the trouble is. A claim repeated in a thousand places is one claim with a thousand copies. Volume feels like corroboration and is not.

Where the register row is the route you need, the National Archives guidance on vital records sets out what exists and who holds it for one country. Access is decided by the registering jurisdiction rather than centrally, and a compiler is rarely an eligible applicant.

A working sequence

1. Write down the claim and where you first saw it. Every later step depends on knowing your entry point.
2. Trace it upstream. Follow each report to the source it cites, and keep going until you reach something that is not citing anyone. Very often the whole cloud collapses into a single unsourced post. This is the ordinary method of fact-checking rather than anything special to death reports.
3. Find one direct source. Funeral home, family, or an official statement from a body that would know.
4. Find a second that is genuinely independent. Independent means it could not have come from the first. Two outlets running the same agency copy are one source.
5. Check the identity, not just the name. Confirm a date of birth, a place, an affiliation: something that distinguishes this person from everyone else with the same name. Name-only matching is how a death gets attached to the wrong person.
6. Check the date. Announcement dates and death dates differ, sometimes by days. Record which one you have.
7. If it does not hold up, hold it. Keep the note, keep the sources, and wait. A claim held back for a day is a non-event.

Warning signs worth stopping for

• The earliest version of the report is an account created recently, or one with no history of covering this subject.
• Every source traces back to the same single post.
• The report is unusually detailed about circumstances but vague about who confirmed anything.
• The wording is copied verbatim across outlets, which suggests one origin rather than many.
• The person shares a name with someone more prominent, or with someone in the same field.
• The claim arrives on an anniversary, which is when old reports resurface as new ones.
• A photograph is being reused from an unrelated context.

What goes in the entry

A list is more useful, and much easier to correct, when each line records how it got there. At minimum: the name as the primary source gives it, with variants noted; the date of death and separately the date of announcement; the source that confirmed it and the date you checked; and any field you could not confirm, marked as unconfirmed rather than left blank or filled with a guess.

That last habit matters more than it looks. A blank field invites the next editor to complete it from memory. A field marked unknown tells them what work is still outstanding.

What a weekly list is, and what it is not

It is a record of deaths that were reported and confirmed during a given week. It is not a record of who died that week. Notices lag: by days, often by longer where a family waited, an investigation was pending, or a death happened somewhere with slower registration. Some deaths are never publicly announced at all, which is a choice families are entitled to make.

So the boundary should be stated on the page: what period the list covers, whether it is ordered by date of death or date of confirmation, and what kinds of death it includes. A reader who knows the boundary can use the list. A reader who assumes it is complete will draw conclusions it cannot support.

And when something does get through wrong, it happens to careful publishers too, the correction should be as prominent as the entry, dated, and left visible rather than quietly deleted. The people most affected by the error deserve to see that it was acknowledged.

Where this sits

How a single notice moves from a death to publication in the first hours is set out in the first-day timeline. The parent index is deaths this week. For why almost nothing can be confirmed on the day itself, see deaths today, and for the name collisions that cause the worst errors, actors who died.

Common questions

How many sources does an entry need?

One with direct knowledge, and ideally a second that could not have come from the first. Counting outlets is not counting sources.

Can a funeral home confirm a death?

Usually only that a service is being arranged, and only where the family has agreed it can be said. That is often enough, and it should not be asked out of curiosity.

What if a report is everywhere and I still cannot source it?

Hold it. A held item costs nothing, and a wrong entry costs a family a day they cannot get back.

Should an unconfirmed field be left blank?

No. Mark it unknown. A blank invites the next editor to fill it from memory; an unknown tells them what work is outstanding.

What makes a correction adequate?

That it is as prominent as the entry, dated, names what was wrong, and stays visible rather than being quietly deleted.