Archive | June, 2014

Due to a reading error …

19 Jun

Imagine how crushing it must have been for the Guardian corrections editor to post this:

Picture 48

No one likes having to print a correction to a correction. Sometimes, it’s just a trivial matter – a typo in a clarification that has to be pointed out the following day. Sometimes a correction will even introduce a new error in its preamble.  But this isn’t, it appears, one of those occasions. This is something much stranger.

The column links, dutifully, to the original correction the day before:

Screen Shot 2014-06-10 at 12.37.12

Just business as usual, it seems: a writer’s slip, an editor’s inattention, all put right in the corrections desk’s breezy fashion. So what happened to cause a complete reversal of position the following day?

The article, it emerges from the amendment notice at the bottom, has been returned to its original wording following the correction that wasn’t:

Screen Shot 2014-06-10 at 12.46.08

And when you read the paragraph that caused all the stir, you wonder how on earth any of it could have happened:

Screen Shot 2014-06-10 at 12.49.10

It couldn’t be clearer: a colon introducing three complete-sentence clauses, separated by semicolons, as a list. It’s textbook. No punctuation errors, no unclear antecedents. It seems impossible to misread. And yet someone seems to have read right past the word “Hinterland”, attached “Happy Valley” to the content of the clause that follows the semicolon, perceived a mistake, and rushed in on Monday morning to get it changed (before, presumably, belated – and one imagines heated – objections from someone who actually worked on the piece).

How did it happen? Uncomfortable scenarios present themselves to the imagination. Did the corrections desk’s natural inclination to take the reader’s side – the “customer is always right” mentality – lead them to change the article on the say-so of a complaint without adequate consultation? Did someone on the corrections desk read the paper inattentively and act on their own authority to “put something right”?

One possible explanation is that the writer got confused about what she had written, called a foul on herself (something many conscientious reporters do if they perceive a mistake) and spoke straight to the ombudsman. Speaking from a fleeting fortnight’s experience as the Tribune’s Sunday corrections editor, when writers turn themselves in it’s very easy for the investigative process to get short-circuited. A letter from a reader is like a tip in an investigation; a confession from a writer is, usually, like closing the case.

But still, not many people appear to have read the sentence correctly (or at all), apart from the editor who passed it for press. And this time it sounds like that editor, whoever he or she was, has overcome the sub’s natural reticence and felt the need to explain, in quite short terms, how syntax works.



Please show working

10 Jun

The chief revise sub isn’t quite sure about this paragraph:

Picture 42

He immediately saw what we all see when he calls us round to look at it: that doesn’t sound like 18% less. That sounds like a lot more than that. And he’s right: £250 is almost 40% less than £415, not 18%. And in the second calculation, £204, compared with what men with no qualifications earn per week (£354), is 42.3% less, not 14.3% less.

The nervousness that descends upon all journalists when numbers appear in a story starts to cloud the collective mind as we stare at it. The percentage figures are per hour, but the amounts in pounds are per week. Is that what the problem is? Does the hourly rate difference accumulate to create a larger gap at the end of the week? But a simple thought experiment rules that out. If one worker is paid £8 an hour and other is paid £10, the difference in hourly rate is 25%. After a six-hour shift, one has earned £48 and the other £60 – still a 25% difference. At the end of a five-day week, one has earned £240 and the other £300 – still a 25% difference. No: if a woman earns 18% less in the course of an hour, she should earn 18% less in the course of a week. Something’s wrong.

The chief revise sub goes over to the reporter and ask to see the data on which the story is based. (The appearance at one’s desk of a member of production staff asking to see source documents is never a good sign for a reporter, of course, but they always seem to take it with remarkable stoicism.) He returns with this (click the image to magnify):


Pay data main NEW

As usual, some of the highlighting and circling seems to have been done with a completely different story in mind, but the data is there. Take a look at the last column, four rows down. There’s the 18% median pay gap figure (well, 17.9% – close enough for newspaper work). Read left, back along that row, and there are the gross weekly pay figures for men and women: £415 and £250. And the second-bottom row, for unqualified men and women, is also just like the reporter wrote it: 14.3%, £204, £354. What’s on earth’s going on? Is the table just completely innumerate?

And then someone has a bright thought. The problem women face in the workplace is not just lower pro-rata pay: it’s also less opportunity to work, whatever the rate. What if the gross pay figure reflects not only a lower hourly rate, but also a lower number of hours overall? It doesn’t explicitly say so anywhere in the table or the story, but what if the women’s working week in the study is shorter than the men’s?

The figures are there to work it out quickly: divide the gross weekly pay by the median hourly rate to get number of hours. For the men, that’s £415 divided by £10.02, or 41.4 hours per week – a full-time job. For the women, though, it’s £250 divided by £8.23, or 30.4 hours a week – a full 11 hours less. That’s why it doesn’t add up. No wonder it struck everyone as strange.

It’s fairly easy fix in the article, too. There’s no space to explore the issue of unequal hours – it’s only a 250-word downpage slot– so you have to lose the easy-to-grasp pound figures and go with the percentages. But at least it’s right now, and at least it was fixed before publication.

Thank goodness for multi-stage editing. The common cry when a mistake gets into print, from readers or readers’ editors, is “didn’t any of you notice?” Well, this time, somebody did. Maybe the chart shouldn’t have been taken out of context, or divorced from its explanatory notes. Maybe it didn’t have any notes at all, and silently included undeclared data that would have thrown anyone off track. Maybe it shouldn’t have got all the way through to the revise desk before it was spotted.

But that’s editing. That’s how it works. It’s not a discrete, finite task: it’s a process. There will always be mistakes on first proof. There will always be mistakes on second proof. More often than not, you’ll find something horrible on a final read even after hours of work on a story. That’s why the Tribune’s production editor insists on press-reading every page of the paper: even if it’s right on deadline, even if that means tearing the proof up and hurriedly handing individual stories round the room. Nothing beats multiple revisions and multiple pairs of eyes. It doesn’t matter how good you are: you won’t spot everything. But maybe someone else will see what you missed.