Every newsroom has a version of this story. A piece runs with a wrong job title, a misread document, or a date that turns out to be off by a year. Someone notices. The desk writes a correction, and it goes where corrections usually go: three lines at the bottom of the article, in smaller type, below the related-content module. The readers who saw the error have no reason to come back and look. The readers who arrive later never learn there was a question.

The error travels. The correction stays home. That is not a technology problem or a budget problem. It is a habit, and it is one a newsroom can break this quarter.

We treat corrections as a penalty rather than as evidence

Say the words "correction log" in a planning meeting and watch who flinches. Someone will hear "wall of shame." Someone else will point out that a public list of your mistakes is the first thing a hostile lawyer or a rival account will screenshot.

But look at what a log actually demonstrates. A newsroom that publishes forty corrections a year is not four times worse than one that publishes ten. It is checking more, catching more, and telling readers where the cracks are. The number is not a confession. It is a measure of how much scrutiny the work is under.

What we do now is worse than either option. We correct, but we correct quietly, in a place designed to be overlooked, in language designed to minimise. The story carries the note; the newsletter, the broadcast pickup, the aggregator and the screenshot do not. Nobody is lying, exactly. But the record is uneven in a way that favours the outlet's reputation over the reader's understanding, and readers can feel that even when they cannot name it.

What a correction log is, and what it is not

A correction log is one page, at one stable address, listing every substantive correction and clarification the outlet has issued. Newest first. Each entry dated, linked to the original story, and written in words a person outside the building can follow. It is indexed by search engines, so someone who finds the original error six months from now can also find the fix.

It is not a replacement for the note on the story itself. Keep doing that. It is not a standards page, and it is not a comments section. It is a log: short, factual, cumulative, and dull on purpose.

The distinction between a log and a note matters more than it sounds. The note repairs one story. The log repairs the record, and it does something else too: it makes the pattern visible to the people who write it.

For investigative desks, credibility is the whole instrument

An investigation asks a reader to accept a chain of reasoning they cannot fully inspect. Documents get quoted, not reproduced. Interviews get described, not played. Some sources cannot be named at all. The reader's decision to believe the story rests, in the end, on the outlet's record of being careful and of saying so when it wasn't.

A well-kept log is that record, in public, in a form anyone can audit. It also disciplines the desk. Writing "we reported X; in fact Y" in a sentence that strangers will read is a sharper internal conversation than typing "updated to reflect." Editors start asking different questions at the copy stage when they know the answer will one day be listed.

There is a practical benefit for sourcing, too. People who talk to investigative reporters are weighing risk, and they are often trying to work out how the outlet behaves when something goes wrong. A visible, well-maintained log answers that question better than any About page.

The objections are real, and smaller than they look

Legal risk. This is the one worth taking seriously enough to spend an hour with a lawyer rather than trusting instinct. But the general principle is not mysterious: a prompt, accurate, fair correction is usually the thing that helps you, and a system that hides errors until they are discovered does not read well to anyone. Ask counsel to review your wording template, not to veto the whole project. None of this is legal advice; get your own.

Embarrassment. The entries that sting are exactly the ones that do the work. A log containing only misspelled surnames and swapped job titles is decoration. Readers can tell the difference between a log and a brochure.

Competitors. Someone will screenshot it. Someone is already screenshotting your errors, minus the part where you fixed them.

Labour. One editor, one hour a week, once the backlog is cleared. That is the honest estimate.

How to build one that people can actually use

• One address that never changes. Link it from the footer of every page on the site, not from a dropdown in the About section.
• Date every entry, give the story headline, and link to the story.
• Say what was wrong and what is right. Two sentences is usually enough.
• Label the type: correction, clarification, update, addition. Different words, different meanings, used consistently.
• Never use "updated to reflect" to disguise a correction. If the substance changed, say so.
• Never delete an entry. If a correction itself turns out to be wrong, correct the correction, in public, in the same place.
• Write for two readers at once: the one who saw the error and the one who never read the piece.
• Keep it indexable and give it a feed. If it cannot be searched, it cannot be found; if it cannot be found, it is a note with better formatting.
• Set a threshold in writing. Errors of fact, attribution, quotation, context and captions go in. Typos and style changes stay in the CMS.
• Have a second person read each entry before it posts. Correction language is where tired people accidentally make a second error.

The wording matters more than the software

Compare "This article was updated to clarify the circumstances of the vote" with "We reported that the contract was approved in a closed session. The vote was taken in public; a different item was discussed in closed session." The second version costs eleven extra words and settles the question. It also tells the reader you know precisely what went wrong, which is the only thing that makes a correction credible.

Where to draw the line

Not every angry email is a correction. Framing, emphasis and contested interpretation are not errors, and they should go through a different channel. Keep the log for things that are demonstrably wrong.

Likewise, when a story is challenged on substance but nothing has changed, say nothing in the log rather than posting a defensive entry. The log's authority comes from being boring and factual. The first time it is used to win an argument, it stops being a record and becomes another piece of marketing.

Start with last month

Pull every correction your outlet has issued in the past twelve months. Write them out in plain language, one by one, without the usual hedging. That exercise alone will tell you more about your editing than most post-mortems.

Then publish the page, link it in the footer, and name one person who owns it. Add new entries as they happen, not in quarterly batches. Post a short note explaining what the page is, once, and then let it accumulate.

It will not be popular internally for the first month. It will be useful for years. And when a source, a reader or a sceptical editor asks why they should trust your next investigation, you will have an answer that took one page to build.

Photo: eak_kkk / Pixabay