Why a Memorial Archive Should Not Add a Cause-of-Death Column

Group celebrity deaths by month and the eye starts looking for a season. That instinct is useful in many fields. On a memorial archive it produces confident nonsense. This page explains what an entry should record, why a cause-of-death field does more harm than good, and where official mortality figures actually live.

No person is named here and no death is reported. Nothing on this page describes how anyone died.

What to take away

An entry records the death, the date reported, the source, and the date of entry. It records a cause only when an official finding or a family statement says so, attributed to its source.
A monthly index has no cause column because it has no cause data. It should not invent one.
Monthly grouping produces false patterns on a small, selected set. Do not publish month-by-month charts.
Questions about why and how people die belong to civil registration and national statistics offices.

Where a cause would have to come from

For a cause to appear against an entry, somebody with direct knowledge would have to have said it publicly, or an official finding would have to have been published. Neither is common.

A death is certified where it occurred, under that jurisdiction's rules, by whoever that jurisdiction authorizes. The certificate is a restricted record in most places.

In the United States, the practical route to a copy runs through the state or territory that registered the death. The CDC's National Center for Health Statistics publishes Where to Write for Vital Records, which lists the office in each state and territory that issues certificates. Eligibility is decided at that level, so the rules differ by jurisdiction. An archive that compiles entries is not an eligible applicant for anyone.

So the honest position for an entry is that it holds the fact of a death and the identity of the person, and nothing about how, unless a statement is attributed to the person who made it.

Why a blank cause field misleads

A blank field is an invitation. Someone fills it from a report, then someone else treats the filled field as the archive's finding. A field that would be empty in almost every row and wrong in some of the rest is worse than no field.

The pattern that the month invents

Here is the specific trap. An index covering a year will show uneven months, because a set that small is uneven by chance. A handful of entries either way is enough to make one month look like a spike.

Real pattern vs invented pattern

Real pattern

Cause: Tested
Sample: Sampled
Entry dates: Death dates
Explanation: Checked

Invented pattern

Cause: Guessed
Sample: Selected
Entry dates: Desk backlog
Explanation: Invented

A reader who then reaches for an explanation will find one, because explanations for a bad month are easy to invent: weather, a season, an anniversary, an age group. None of them was tested. The month with more entries has more entries because of who was written about, and because of how quickly those confirmations came through.

Two further things make the illusion worse on this kind of page.

The first is that the underlying set is selected, not sampled. An archive holds the deaths that were publicly noticed, which correlates with profession, with country, with language, and with how long a person had been out of view. Each of those correlates with time of year in some small way. Small effects on a small set produce large-looking swings.

The second is that entry dates cluster for reasons unrelated to deaths. A desk that clears a backlog in one week puts many entries into one month. That is a fact about the desk, not about the deaths.

What a reader who wants numbers should do instead

Go to the sources that count everyone, rather than the ones that write about some people.

National statistical offices and civil registration authorities compile mortality from complete registration. They code causes to a common classification, and publish the results with the definitions and caveats attached.

The WHO Mortality Database collects those national returns internationally. It is the right starting point for any question about whether deaths vary by month in a population. It also shows how much work goes into making two countries' figures comparable, which is a useful correction in itself.

What you will not find there is a name. That is the trade. Statistical sources answer questions about populations and refuse questions about individuals. Memorial archives do the reverse. Trying to get a population answer out of an archive of individuals is the mistake this page exists to head off.

How a careful monthly page handles the question

It says on its face that it records no cause, so a reader does not go looking for a column that was never there.
It resists ranking months against each other, and it does not publish a chart of monthly totals, because a chart is an argument.
Where a family has publicly stated something, it carries the statement as the family's, attributed, and does not extend it.
It keeps the date of death and the date of entry as separate fields, so that anyone who wants to understand the shape of the page can see the confirmation lag for themselves.
It points to statistical sources for statistical questions instead of trying to answer them.

Where this sits

The same argument applies to annual groupings, where the selection effects are easier to see. For what a short window can and cannot contain, the weekly and daily pages on this site make the same point at a smaller scale, and the cause of death guides set out the same position for entries.

Common questions

Do more people die in winter?

In many populations mortality does vary through the year, and statistical agencies publish that. You cannot learn it from a monthly memorial index, which is why this page sends you elsewhere for it.

A month here has twice as many entries as the month before. What happened?

Almost certainly nothing happened. On a set this size and this selective, a doubling between adjacent months is ordinary variation plus the rhythm of the desk that entered them.

Why not add a cause field and leave it blank when unknown?

Because a blank field invites someone to fill it from a report, and then the filled field looks like the archive's finding. A field that would be empty in almost every row and wrong in some of the rest is worse than no field.

If a family has said publicly how someone died, would that appear?

As a statement attributed to the family, where it is relevant, and not as a data field to be sorted or counted. What a family chooses to say is theirs, and it does not become a category by being said.

Is there any month-level question this index can answer?

Yes, but they are questions about the record rather than about mortality: how quickly entries were confirmed, how many were later amended, and how much of a month arrived after the month closed.