You Don’t Say: Fixing the blame


By John E. McIntyre 

A reader of my column on how publications deal with corrections (“Daddy, where do corrections come from?") addressed a point that regularly bedevils editors: Should corrections identify who made the error?

The issue has been described at some length in the article “Who takes the fall for errors?” by Kathy English, the public editor of the Toronto Star. Let me summarize the two main perspectives on the issue.

Point A: The impersonal correction, favored by many publications, considers a published article to be a collaborative effort for which the publication takes full responsibility without fixing blame. A given article may go through many hands, and error can occur at any point. It is the publication’s fault if such errors are not identified and corrected.

Point B: The contrary view, which received support in comments on Ms. English’s article, is that because the reporter’s byline is on the story, the reporter should not be embarrassed by being made to appear responsible for an error committed by someone else.

I am a sturdy advocate of the impersonal correction, which I justify for the following reasons.

Item: The story is the publication’s, not the author’s. Put it this way. Should the subject of an article sue for libel, the writer expects the publication to assume responsibility for the defense. No reporter wants to hear an editor say, “I see you have a problem with your story. You had better get yourself a lawyer.”

Item: The story is in fact a collective product of the publication’s staff. Publications employ originating editors and copy editors, all of whom have the authority and responsibility to make necessary changes.

Item: Bylines are more important to reporters than to readers. (That is why an eight-line brief rewritten from a press release will appear in print with a reporter’s credit at the end.) A reader may register the name of a columnist, or a reporter whose beat impinges on that reader’s particular interests, but there is little reason to think that readers take regular notice of who wrote which story.

There is thus little or no reason to think that readers care who makes mistakes of fact or that readers would benefit from reading corrections that assign such responsibility. An article in yesterday’s edition of the Blat mistakenly located the battle of Antietam as having taken place near Hagerstown, Maryland, instead of Sharpsburg. The writer’s text was correct, but the error was introduced by an intern on the copy desk. The Blat regrets the error.

The reader cares whether the publication is reliable.

Item: A typical comment on Ms. English’s article: The problem in this case is that the reporter has his or her name clearly listed as writer. If THAT writer was NOT responsible, THAT fact should be noted. The reading public will always associate the article with the writer, no matter how many people are working in the background. It is only fair to exonerate the writer from blame in these cases.

Let’s turn this one around. Should a reporter enjoy a reputation for accuracy that is the product of the editing process rather than the reporter’s own work? I have seen text from reporters, passed along by originating editors, with errors that would make your hair stand on end. (I once saw a story sent to the copy desk in which the reporter had misspelled the name of its subject sixteen times; that all sixteen were consistently misspelled was thought to mark an improvement in the reporter’s abilities.)

Anonymous copy editors, at the publications that still bother to engage copy editors, silently correct multitudes of errors. Envision this “shirttail” at the end of an article: The writer of this article identified Ougadougou as the capital of Dahomey. It is the capital of Burkina Faso. A Blat copy editor corrected the error.

Fixing responsibility is useful in-house for evaluating the performance of writers and editors. Its utility for the reading public is questionable.

Item: The exception: When a publication must acknowledge the commission of a plagiarism or a fabrication — the product of professional misconduct rather than ordinary carelessness or haste —  the miscreant should be identified.

John McIntyre, former head of the copy desk at The Baltimore Sun, is the author of You Don’t Say, a blog on language, usage and miscellaneous topics.


  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Fark
  • NewsVine
  • SphereIt
  • StumbleUpon
  • Technorati
  • FriendFeed
  • Twitter
  • While it's true that most readers don't care two hoots about bylines, sources do care, and their opinion matters for future stories. A reporter will hear about a printed correction from sources involved with that story. In fact, you'd better hear feedback about a correction: If you don't hear anything, you're out of touch with your beat.

    If the error was caused by an editor and is bone-headed enough to make your sources take you less seriously (confusing "million" and "billion", or mixing up the name of a locally prominent person), then absolutely the correction should say "Due to an editor's error ..." - otherwise you're harming the value of your reporters with the people they depend on for future stories.

    Of course, when it *is* the reporter's fault the correction should say so ("Due to a reporting error ..." ) And these days, it usually is the reporter's fault because there are so few editors any more that copy hardly gets touched between writer and reader.
  • Curiously, I have never heard a reporter suggest that a correction should begin, "Due to a reporting error." An analysis of corrections I once conducted suggested that more than three-quarters of published corrections in The Sun could carry that introductory phrase. I doubt that that would fill sources with confidence, either.
  • Charlene
    The 'Blat copy editor' needs to pull out his atlas. Benin hasn't been known as Dahomey since 1975. (Upper Volta wasn't renamed Burkina Faso until 1984, so even historically this correction would have been inaccurate.)
  • Joshua
    Charlene: No, the Blat copy editor has it right. The copy editor wrote that Ouagadougou was the capital of Burkina Faso, which it is. However, in the hypothetical example, the Blat apparently has a policy of embarrassing the reporters by identifying the errors they make which get corrected by the copy editor in the body of the article, but get called out in a tag at the end of the article.

    In the example, the reporter was apparently looking at a pre-1975 map and also failing to notice which city went with which country, thus placing Ouagadougou in a neighboring country and identifying that neighboring country by an old name.
blog comments powered by Disqus