Independent Articles
Informative and thought provoking guidelines and discussions
The Review Cycle: Why the First Draft Is Not Ready for Review
A common challenge in engineering report preparation is that reports are often submitted for senior review too soon.
A report is not ready for senior review simply because the final full stop has been added. At that point, the first draft has been completed — but the report has not yet been properly reviewed, refined, or polished.
Nobody writes a perfect report the first time. The purpose of the first draft is to get the technical information, assumptions, calculations, observations, and recommendations onto paper. The real value is added through the review process that follows.
A useful way to think about report writing is to compare it to painting a house. The first coat is rarely enough. Multiple coats are needed to achieve full coverage, improve the finish, and identify areas that were missed the first time. Report writing is the same. A professional engineering report requires several focused review passes before it is ready for senior review or client issue.
It is also important to recognise that submitting a report for senior review is not a casual step. In many ways, it should be treated with the same seriousness as submitting the report to the client. The internal review process assesses not only the technical content of the report, but also the author’s judgement, attention to detail, communication ability, and progression towards becoming a senior engineer.
Before issuing a report for senior review, I recommend that the author carries out several focused review passes. Each pass should have a specific purpose. You may identify other errors during a pass, and those should be corrected, but the main objective should remain focused.
Suggested Review Process
1. Draft the Report
Prepare the first complete draft of the report. Focus on the purpose of the report, the technical brief, and the information that needs to be communicated.
The report should generally include a clear introduction, the main technical content, and a conclusion or set of recommendations. At this stage, the priority is to get the structure and content in place.
2. Review the Technical Content
Check that the engineering logic is sound. Confirm that the assumptions, interpretations, calculations, observations, and recommendations are technically appropriate.
Ask yourself whether the report answers the brief and whether the conclusions are supported by the information presented.
3. Verify the Data
Check all figures, tables, references, dates, drawing numbers, monitoring results, calculations, and quoted values.
Many report errors are not grammar errors — they are data errors. Incorrect values, inconsistent numbers, or unsupported statements can undermine the credibility of an otherwise good report.
4. Revise for Clarity
Review the report from the reader’s perspective. Simplify complex sentences where possible and remove unnecessary repetition.
The aim is not to make the report sound complicated. The aim is to communicate clearly, accurately, and professionally. A good technical report should make complex engineering information easier to understand.
5. Check Grammar, Punctuation, and Formatting
Review punctuation, spelling, grammar, headings, numbering, font styles, table formatting, figure captions, and cross-references.
Consistency matters. A report with inconsistent formatting or basic language errors can create the impression that the technical content has also not been carefully checked.
Closing Comment
A well-written engineering report is not produced in a single pass. It is developed through drafting, checking, refining, and reviewing.
Taking the time to properly review your own report before submitting it for senior review improves the quality of the document, reduces unnecessary review comments, and demonstrates professionalism.
Good report writing is not only an administrative skill. It is an engineering skill.
-Yoshlin Govender (CEO & Tailings Expert)
