Guide to Effective Report Writing

Most people who write reports for a living were never actually taught how. They learned to write at school and university, where the only reader who mattered was a lecturer obliged to read every word, and then walked straight into a workplace where nobody is obliged to read anything at all. David Tuffley's Guide to Effective Report Writing exists to close that gap, in a short, dense, entirely practical handbook built for people who need to write well at work, not for people who want to write literature.

The book opens by naming the problem precisely: the habits that earned good grades at university are often the exact habits that produce unread reports in an office. Readers at work are not a captive audience. They skim. They ask, almost instantly, what is this, why am I getting it, how does it affect me, and what am I supposed to do, and if a document does not answer those questions fast, it does not get read at all. Tuffley walks through the real differences between academic and workplace writing in convincing, slightly uncomfortable detail: business writing is read by multiple audiences with different backgrounds and different stakes, it may sit in a file for years and be read by people who know nothing of the context, and it can, in the wrong circumstances, create genuine legal liability for both writer and organisation.

From there the book turns fully practical. Two alternative document structures are laid out for two different situations, one for reports where the conclusion should come first, the other for reports where the reader needs to be walked through the evidence before they will accept the conclusion. There are concrete guidelines for writing summaries, introductions and overviews, for structuring paragraphs so they can be skimmed as well as read, and for knowing when a graphic will communicate more clearly than another paragraph of text. Tuffley is particular about the small design choices that add up: a summary written last but placed first, an introduction that still makes sense to a reader encountering the document years after it was written, an overview that orients the reader before each major section rather than leaving them to work it out as they go. A chapter on style covers the practical questions that actually determine whether a document lands: how much the reader already knows, what tone is expected, what reading level to pitch at, and what your working relationship to that reader really is.

What distinguishes this guide from the many similar titles on the market is its refusal to pad. Every section answers a specific, recurring problem that working professionals actually run into, drawing on decades of Tuffley's own experience teaching technical writing at university level. There is no padding, no generic advice about finding your voice, just a clear method that can be applied the next time a report is due.

For anyone whose job depends, even partly, on being read and understood by busy people who did not ask to read your document, this is a fast, useful corrective to years of academic habit.