Most people don’t come to me asking for a proofread, an edit or a rewrite. They come to me because something doesn’t feel right.

A report is about to be published and they’d like another set of eyes over it. A guide feels too complicated. A proposal isn’t landing as well as they’d hoped. A technical document needs to be turned into something more useful for its audience. Sometimes they can’t clearly articulate the exact problem. 

Perhaps they assume the document needs a proofread. But what they eventually discover is that the problem has very little to do with spelling, grammar or punctuation.

Where the review process begins

Before changing a single word, I want to understand what the document is trying to achieve. Who will read it? How will they use it? What action, decision or outcome should it support?

I’m not worried about what type of review the document needs. I ask: what’s stopping this content from doing its job?

Not all content problems are writing problems

It’s easy to assume that if a document isn’t working, the writing must be the issue. Sometimes that’s true, but it’s rarely the whole story.

Over the years, I’ve reviewed technically accurate reports that buried their key messages, long-form guides that overwhelmed readers and documents that made perfect sense to their authors but not to their readers.

A document can be beautifully written and still fail if readers can’t find what they need, understand the message or act on the information. 

This is why I believe content should be judged by its fitness for purpose rather than by writing quality alone. Writing quality matters. But content succeeds or fails based on what it helps people do.

The audience changes everything

Most content problems reveal themselves in the audience. If readers are confused, overwhelmed, disengaged or unable to act, the content fails.

One of the first things I want to understand is who will be reading the document and how they’ll use it. That’s what determines the type of support required.

The same piece of content can be perfectly acceptable in one situation and completely unsuitable in another. A detailed technical document may work well for subject matter experts who need comprehensive information. Present that same document to a time-poor audience looking for practical guidance, and it may be unusable.

I encountered this situation while reviewing a lengthy resource created for a group of busy professionals. The information itself was valuable, but the document was dense, highly detailed and difficult to work through. The audience didn’t need more information. They needed information that was easier to absorb and apply.

The solution wasn’t simply correcting grammar or tightening sentences. I simplified the language, reorganised sections, expanded areas that needed additional context and introduced a practical checklist to help readers work through the material. The information remained largely the same, but the experience of using the document changed significantly.

That’s an important distinction. Sometimes content doesn’t need more information. It needs better communication.

While audience is often the biggest factor in whether content succeeds, it isn’t the only one.

Sometimes the problem is credibility

Not every content issue relates to audience, structure or readability. Sometimes the content fails because readers lose confidence in it.

My background is in sub-editing, where accuracy was treated seriously and mistakes had consequences. That mindset has stayed with me. Even when I’m reviewing a document for broader structural or strategic issues, I’m also paying attention to the details.

Over the years, I’ve found incorrect qualifications, misspelled names, broken QR codes, outdated contact details and factual inconsistencies that could easily have made their way into published material. Some of these errors seem minor in isolation, but readers don’t assess them in isolation.

A misspelled city name in an acquisition announcement, an incorrect professional credential or a broken link can create doubt about the entire document (or worse, the company). If an organisation has overlooked something so obvious, readers naturally wonder what else might have been missed.

That’s why fact-checking remains an important part of the review process. Credibility is difficult to earn and easily undermined. It pays to check.

Different problems require different solutions

Once you’ve identified what’s preventing a document from achieving its purpose, the appropriate solution usually becomes clearer.

Some documents need a final quality-control review before publication. Others need stronger structure, clearer messaging and improved flow. Occasionally, content needs more substantial work because the format, organisation or presentation no longer serves the audience effectively.

This is where terms like proofreading, editing and rewriting become useful. They’re different solutions to different problems.

But the starting point is always the same: understanding what’s holding the content back.

Start with the purpose, not the process

When clients ask me to review a document, they’re rarely interested in editorial terminology. They want confidence that the content will achieve what it’s supposed to achieve. They want it to make sense, communicate clearly and reflect well on their organisation.

That’s why I focus less on labels and more on outcomes.

Before worrying about what level of review is needed, it’s worth asking a simpler question: can the content do its job?

Once you understand the real problem, the right solution usually reveals itself.