Looking for production errors is an important part of quality assurance and proofreading.

I can’t show you real examples from my client work, so I have made some up. The scenarios below are completely fictional, but they’re also not uncommon.

A rogue AI

A chocolate teapot company uses AI to write personalised emails to customers. One email says, “The company chooses to call itself ethical.” I note that this sounds like an indirect criticism, so I query it. The phrase is removed and no harm is done to the company’s reputation.

Protecting stakeholder privacy

A document needs to explain that a woman has physical health reasons for being unable to visit Paris. It accurately describes the woman’s current problems, but it then gives details about her past substance abuse. I’m familiar with this document type and know this background information isn’t a requirement, so I query it.

A plentiful supply of loos

A reporter writes an article about new towns on the Moon. One new home is described as having three bathrooms and one bedroom. I think this sounds unusual and query whether it should be three bedrooms and one bathroom. The reporter checks their notes and makes the correction.

Unexpected content

A park authority commissions display boards to teach visitors about native plant species. I see that one board briefly mentions ancient Egypt. I wonder if this fits the theme and raise a query. It turns out that the line was left over from a previous display.

Mixed-up words

A company produces a booklet about a 1950s celebrity known for her fierce opposition to alcohol. In the foreword, she is described as “a bibulous personality.” I point out that bibulous can mean fond of drinking alcohol. The word is replaced with vivacious.

Mixed-up content

A PowerPoint presentation begins with a description of Smith’s theory of happiness and Brown’s theory of personal growth. Slide 34 talks about Brown’s theory of happiness. I’m unsure whether this is a name mix up or whether both Smith and Brown had theories of happiness. After checking online, my suspicion is that it’s a name mix up. I query the point.

I’m here to help

I often say “I’m here to support busy teams.” I genuinely mean it. I’m here to pick up problems that could frustrate and inconvenience the people who work hard to produce documents and publications.

My work allows me to make a constructive contribution. By flagging production errors, I help to prevent bigger issues popping up later.

I know that every client has unique needs for their document or publication. So when I join a team, I don’t sweep in like a whirlwind. I find out what the client wants me to check, what written instructions they have for me, and what they don’t want me to comment on.