Why English? | Writing a Technical Report Through Purpose, Audience, Scope, Methods, Results, Analysis, Recommendations, Appendices and Revision

ORIENTATION

What this guide covers

Current fact check

Checked on 8 November 2026, UNSW’s official technical-writing guide described clarity, precision, concision, audience awareness, defined jargon and careful use of abbreviations as core conventions. Its report guide distinguished experimental reports from technical design reports and listed common components while noting that purpose and audience determine the final structure.

What this guide does not cover

This article focuses on general student and early-career technical reports. It does not own laboratory-report discussions, engineering drawings, safety cases, regulatory submissions, research papers, project-closure reports or any profession-specific certification requirement.

Worked example

Every chapter returns to a fictional student engineering team comparing three low-cost classroom carbon-dioxide monitors for accuracy, usability, data export and maintenance before recommending a pilot device. It is fictional, low-stakes and educational; it does not report a real school, clinical decision or guaranteed outcome.

Warm up with eduKate’s guides to explaining scientific evidence and asking better questions in class.

CHAPTER 1 OF 16

1. Define the Report’s Decision and Deliverable

Back to contents

Why this move matters

Write what the reader must understand or decide and what form the answer must take.

Build a traceable technical claim

Write what the reader must understand or decide and what form the answer must take. Join requirement, method, observation, calculation and conclusion so a reader can inspect the path rather than trust a confident sentence.

Design for two reading speeds

For the worked report, The team must recommend one monitor for a four-classroom pilot, not declare the best monitor in the world. Give decision-makers a concise finding and recommendation, while placing enough method, units, assumptions and data detail in the body or appendices for technical review.

Audit figures, tables and units

Ask which reader question each visual answers, then verify its caption, labels, symbols, units and explanation in the prose. Confirm that rounding and conversions do not imply more precision than the measurement supports.

Keep conclusions inside scope

A technical report may inform without authorising procurement. Separate observed results, engineering judgement, recommendations and matters outside the test or design brief.

Student, parent and career transfer

Make one evidence card for “Define the Report’s Decision and Deliverable”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports engineering, science, information technology, laboratory work, environmental monitoring, facilities, quality assurance, procurement and technical project management without promising a grade, admission, funding decision or job.

CHAPTER 2 OF 16

2. Map Primary and Secondary Readers

Back to contents

Why this move matters

Identify technical reviewers, decision-makers, operators and people affected by the recommendation.

Build a traceable technical claim

Identify technical reviewers, decision-makers, operators and people affected by the recommendation. Join requirement, method, observation, calculation and conclusion so a reader can inspect the path rather than trust a confident sentence.

Design for two reading speeds

For the worked report, A lecturer checks method; facilities staff care about calibration; teachers need readable alerts. Give decision-makers a concise finding and recommendation, while placing enough method, units, assumptions and data detail in the body or appendices for technical review.

Audit figures, tables and units

Ask which reader question each visual answers, then verify its caption, labels, symbols, units and explanation in the prose. Confirm that rounding and conversions do not imply more precision than the measurement supports.

Keep conclusions inside scope

One vocabulary level will not serve every reader equally. Separate observed results, engineering judgement, recommendations and matters outside the test or design brief.

Student, parent and career transfer

Make one evidence card for “Map Primary and Secondary Readers”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports engineering, science, information technology, laboratory work, environmental monitoring, facilities, quality assurance, procurement and technical project management without promising a grade, admission, funding decision or job.

CHAPTER 3 OF 16

3. Set Scope, Constraints and Acceptance Criteria

Back to contents

Why this move matters

State tested conditions, exclusions, budget, standards, performance thresholds and deadlines.

Build a traceable technical claim

State tested conditions, exclusions, budget, standards, performance thresholds and deadlines. Join requirement, method, observation, calculation and conclusion so a reader can inspect the path rather than trust a confident sentence.

Design for two reading speeds

For the worked report, The comparison covers indoor classrooms, a fixed price band and one-month data export, not outdoor air monitoring. Give decision-makers a concise finding and recommendation, while placing enough method, units, assumptions and data detail in the body or appendices for technical review.

Audit figures, tables and units

Ask which reader question each visual answers, then verify its caption, labels, symbols, units and explanation in the prose. Confirm that rounding and conversions do not imply more precision than the measurement supports.

Keep conclusions inside scope

Scope must not be widened in the conclusion. Separate observed results, engineering judgement, recommendations and matters outside the test or design brief.

Student, parent and career transfer

Make one evidence card for “Set Scope, Constraints and Acceptance Criteria”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports engineering, science, information technology, laboratory work, environmental monitoring, facilities, quality assurance, procurement and technical project management without promising a grade, admission, funding decision or job.

CHAPTER 4 OF 16

4. Plan the Report Architecture

Back to contents

Why this move matters

Choose sections and numbering that follow the task, discipline and reader journey.

Build a traceable technical claim

Choose sections and numbering that follow the task, discipline and reader journey. Join requirement, method, observation, calculation and conclusion so a reader can inspect the path rather than trust a confident sentence.

Design for two reading speeds

For the worked report, The report uses executive summary, requirements, methods, results, analysis, recommendation, limitations and appendices. Give decision-makers a concise finding and recommendation, while placing enough method, units, assumptions and data detail in the body or appendices for technical review.

Audit figures, tables and units

Ask which reader question each visual answers, then verify its caption, labels, symbols, units and explanation in the prose. Confirm that rounding and conversions do not imply more precision than the measurement supports.

Keep conclusions inside scope

A familiar template can still be wrong for the commission. Separate observed results, engineering judgement, recommendations and matters outside the test or design brief.

Student, parent and career transfer

Make one evidence card for “Plan the Report Architecture”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports engineering, science, information technology, laboratory work, environmental monitoring, facilities, quality assurance, procurement and technical project management without promising a grade, admission, funding decision or job.

CHAPTER 5 OF 16

5. Write a Method Another Reader Can Inspect

Back to contents

Why this move matters

Describe equipment, settings, sampling, calibration, sequence, calculations and departures from plan.

Build a traceable technical claim

Describe equipment, settings, sampling, calibration, sequence, calculations and departures from plan. Join requirement, method, observation, calculation and conclusion so a reader can inspect the path rather than trust a confident sentence.

Design for two reading speeds

For the worked report, Each monitor is co-located with a reference instrument for defined intervals and ventilation conditions. Give decision-makers a concise finding and recommendation, while placing enough method, units, assumptions and data detail in the body or appendices for technical review.

Audit figures, tables and units

Ask which reader question each visual answers, then verify its caption, labels, symbols, units and explanation in the prose. Confirm that rounding and conversions do not imply more precision than the measurement supports.

Keep conclusions inside scope

Reproducibility may be limited by proprietary devices or unavailable data. Separate observed results, engineering judgement, recommendations and matters outside the test or design brief.

Student, parent and career transfer

Make one evidence card for “Write a Method Another Reader Can Inspect”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports engineering, science, information technology, laboratory work, environmental monitoring, facilities, quality assurance, procurement and technical project management without promising a grade, admission, funding decision or job.

CHAPTER 6 OF 16

6. Control Units, Symbols and Significant Figures

Back to contents

Why this move matters

Use consistent units, define symbols, document conversions and match precision to measurement capability.

Build a traceable technical claim

Use consistent units, define symbols, document conversions and match precision to measurement capability. Join requirement, method, observation, calculation and conclusion so a reader can inspect the path rather than trust a confident sentence.

Design for two reading speeds

For the worked report, Carbon-dioxide readings use parts per million, and averages are not reported to unsupported decimal places. Give decision-makers a concise finding and recommendation, while placing enough method, units, assumptions and data detail in the body or appendices for technical review.

Audit figures, tables and units

Ask which reader question each visual answers, then verify its caption, labels, symbols, units and explanation in the prose. Confirm that rounding and conversions do not imply more precision than the measurement supports.

Keep conclusions inside scope

Conversion does not repair poor calibration. Separate observed results, engineering judgement, recommendations and matters outside the test or design brief.

Student, parent and career transfer

Make one evidence card for “Control Units, Symbols and Significant Figures”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports engineering, science, information technology, laboratory work, environmental monitoring, facilities, quality assurance, procurement and technical project management without promising a grade, admission, funding decision or job.

CHAPTER 7 OF 16

7. Present Results Before Preference

Back to contents

Why this move matters

Report observations and calculated outputs consistently across options.

Build a traceable technical claim

Report observations and calculated outputs consistently across options. Join requirement, method, observation, calculation and conclusion so a reader can inspect the path rather than trust a confident sentence.

Design for two reading speeds

For the worked report, All three monitors receive the same table columns for bias, missing data, battery life and export success. Give decision-makers a concise finding and recommendation, while placing enough method, units, assumptions and data detail in the body or appendices for technical review.

Audit figures, tables and units

Ask which reader question each visual answers, then verify its caption, labels, symbols, units and explanation in the prose. Confirm that rounding and conversions do not imply more precision than the measurement supports.

Keep conclusions inside scope

A result table should not hide failed runs. Separate observed results, engineering judgement, recommendations and matters outside the test or design brief.

Student, parent and career transfer

Make one evidence card for “Present Results Before Preference”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports engineering, science, information technology, laboratory work, environmental monitoring, facilities, quality assurance, procurement and technical project management without promising a grade, admission, funding decision or job.

CHAPTER 8 OF 16

8. Design Figures and Tables for Questions

Back to contents

Why this move matters

Give each visual a purpose, label, unit, caption and prose reference.

Build a traceable technical claim

Give each visual a purpose, label, unit, caption and prose reference. Join requirement, method, observation, calculation and conclusion so a reader can inspect the path rather than trust a confident sentence.

Design for two reading speeds

For the worked report, A time-series figure shows response lag; a table compares maintenance and export requirements. Give decision-makers a concise finding and recommendation, while placing enough method, units, assumptions and data detail in the body or appendices for technical review.

Audit figures, tables and units

Ask which reader question each visual answers, then verify its caption, labels, symbols, units and explanation in the prose. Confirm that rounding and conversions do not imply more precision than the measurement supports.

Keep conclusions inside scope

Colour alone should not carry meaning. Separate observed results, engineering judgement, recommendations and matters outside the test or design brief.

Student, parent and career transfer

Make one evidence card for “Design Figures and Tables for Questions”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports engineering, science, information technology, laboratory work, environmental monitoring, facilities, quality assurance, procurement and technical project management without promising a grade, admission, funding decision or job.

CHAPTER 9 OF 16

9. State Data Quality and Uncertainty

Back to contents

Why this move matters

Report variability, missingness, resolution, calibration limits and relevant sensitivity checks.

Build a traceable technical claim

Report variability, missingness, resolution, calibration limits and relevant sensitivity checks. Join requirement, method, observation, calculation and conclusion so a reader can inspect the path rather than trust a confident sentence.

Design for two reading speeds

For the worked report, One monitor has low average bias but frequent missing values during wireless dropouts. Give decision-makers a concise finding and recommendation, while placing enough method, units, assumptions and data detail in the body or appendices for technical review.

Audit figures, tables and units

Ask which reader question each visual answers, then verify its caption, labels, symbols, units and explanation in the prose. Confirm that rounding and conversions do not imply more precision than the measurement supports.

Keep conclusions inside scope

An average cannot represent every operating condition. Separate observed results, engineering judgement, recommendations and matters outside the test or design brief.

Student, parent and career transfer

Make one evidence card for “State Data Quality and Uncertainty”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports engineering, science, information technology, laboratory work, environmental monitoring, facilities, quality assurance, procurement and technical project management without promising a grade, admission, funding decision or job.

CHAPTER 10 OF 16

10. Analyse Against Requirements

Back to contents

Why this move matters

Explain what results mean for each acceptance criterion instead of repeating numbers.

Build a traceable technical claim

Explain what results mean for each acceptance criterion instead of repeating numbers. Join requirement, method, observation, calculation and conclusion so a reader can inspect the path rather than trust a confident sentence.

Design for two reading speeds

For the worked report, A monitor meets the alert requirement but fails the required data-export workflow. Give decision-makers a concise finding and recommendation, while placing enough method, units, assumptions and data detail in the body or appendices for technical review.

Audit figures, tables and units

Ask which reader question each visual answers, then verify its caption, labels, symbols, units and explanation in the prose. Confirm that rounding and conversions do not imply more precision than the measurement supports.

Keep conclusions inside scope

Meeting one criterion does not imply overall suitability. Separate observed results, engineering judgement, recommendations and matters outside the test or design brief.

Student, parent and career transfer

Make one evidence card for “Analyse Against Requirements”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports engineering, science, information technology, laboratory work, environmental monitoring, facilities, quality assurance, procurement and technical project management without promising a grade, admission, funding decision or job.

CHAPTER 11 OF 16

11. Compare Options and Trade-Offs

Back to contents

Why this move matters

Use common criteria and explain weights, dependencies and conflicting advantages.

Build a traceable technical claim

Use common criteria and explain weights, dependencies and conflicting advantages. Join requirement, method, observation, calculation and conclusion so a reader can inspect the path rather than trust a confident sentence.

Design for two reading speeds

For the worked report, The cheapest monitor needs manual downloads; the costlier one reduces staff time. Give decision-makers a concise finding and recommendation, while placing enough method, units, assumptions and data detail in the body or appendices for technical review.

Audit figures, tables and units

Ask which reader question each visual answers, then verify its caption, labels, symbols, units and explanation in the prose. Confirm that rounding and conversions do not imply more precision than the measurement supports.

Keep conclusions inside scope

A scoring matrix can conceal subjective weights. Separate observed results, engineering judgement, recommendations and matters outside the test or design brief.

Student, parent and career transfer

Make one evidence card for “Compare Options and Trade-Offs”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports engineering, science, information technology, laboratory work, environmental monitoring, facilities, quality assurance, procurement and technical project management without promising a grade, admission, funding decision or job.

CHAPTER 12 OF 16

12. Separate Finding, Interpretation and Recommendation

Back to contents

Why this move matters

Label what was observed, what it implies and what action is proposed.

Build a traceable technical claim

Label what was observed, what it implies and what action is proposed. Join requirement, method, observation, calculation and conclusion so a reader can inspect the path rather than trust a confident sentence.

Design for two reading speeds

For the worked report, Observed export failures support an operational-risk interpretation and a limited pilot recommendation. Give decision-makers a concise finding and recommendation, while placing enough method, units, assumptions and data detail in the body or appendices for technical review.

Audit figures, tables and units

Ask which reader question each visual answers, then verify its caption, labels, symbols, units and explanation in the prose. Confirm that rounding and conversions do not imply more precision than the measurement supports.

Keep conclusions inside scope

A recommendation adds judgement beyond the raw result. Separate observed results, engineering judgement, recommendations and matters outside the test or design brief.

Student, parent and career transfer

Make one evidence card for “Separate Finding, Interpretation and Recommendation”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports engineering, science, information technology, laboratory work, environmental monitoring, facilities, quality assurance, procurement and technical project management without promising a grade, admission, funding decision or job.

CHAPTER 13 OF 16

13. Write a Calibrated Conclusion

Back to contents

Why this move matters

Answer the purpose, state the strongest supported finding and preserve scope and uncertainty.

Build a traceable technical claim

Answer the purpose, state the strongest supported finding and preserve scope and uncertainty. Join requirement, method, observation, calculation and conclusion so a reader can inspect the path rather than trust a confident sentence.

Design for two reading speeds

For the worked report, Monitor B is recommended for the defined pilot, subject to a data-retention check. Give decision-makers a concise finding and recommendation, while placing enough method, units, assumptions and data detail in the body or appendices for technical review.

Audit figures, tables and units

Ask which reader question each visual answers, then verify its caption, labels, symbols, units and explanation in the prose. Confirm that rounding and conversions do not imply more precision than the measurement supports.

Keep conclusions inside scope

Do not claim universal superiority from a classroom comparison. Separate observed results, engineering judgement, recommendations and matters outside the test or design brief.

Student, parent and career transfer

Make one evidence card for “Write a Calibrated Conclusion”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports engineering, science, information technology, laboratory work, environmental monitoring, facilities, quality assurance, procurement and technical project management without promising a grade, admission, funding decision or job.

CHAPTER 14 OF 16

14. Build Appendices That Remain Findable

Back to contents

Why this move matters

Move detailed calculations, raw extracts, test scripts and specifications out of the main flow while linking them clearly.

Build a traceable technical claim

Move detailed calculations, raw extracts, test scripts and specifications out of the main flow while linking them clearly. Join requirement, method, observation, calculation and conclusion so a reader can inspect the path rather than trust a confident sentence.

Design for two reading speeds

For the worked report, Appendix B contains calibration records referenced in the method and limitation sections. Give decision-makers a concise finding and recommendation, while placing enough method, units, assumptions and data detail in the body or appendices for technical review.

Audit figures, tables and units

Ask which reader question each visual answers, then verify its caption, labels, symbols, units and explanation in the prose. Confirm that rounding and conversions do not imply more precision than the measurement supports.

Keep conclusions inside scope

An appendix is not a dumping ground for unexplained material. Separate observed results, engineering judgement, recommendations and matters outside the test or design brief.

Student, parent and career transfer

Make one evidence card for “Build Appendices That Remain Findable”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports engineering, science, information technology, laboratory work, environmental monitoring, facilities, quality assurance, procurement and technical project management without promising a grade, admission, funding decision or job.

CHAPTER 15 OF 16

15. Revise for Clarity, Accessibility and Consistency

Back to contents

Why this move matters

Check headings, cross-references, abbreviations, captions, link text, colour contrast, grammar and mobile or PDF reading.

Build a traceable technical claim

Check headings, cross-references, abbreviations, captions, link text, colour contrast, grammar and mobile or PDF reading. Join requirement, method, observation, calculation and conclusion so a reader can inspect the path rather than trust a confident sentence.

Design for two reading speeds

For the worked report, The team expands acronyms on first use and replaces colour-only pass/fail coding with labels. Give decision-makers a concise finding and recommendation, while placing enough method, units, assumptions and data detail in the body or appendices for technical review.

Audit figures, tables and units

Ask which reader question each visual answers, then verify its caption, labels, symbols, units and explanation in the prose. Confirm that rounding and conversions do not imply more precision than the measurement supports.

Keep conclusions inside scope

Formatting cannot correct an invalid test. Separate observed results, engineering judgement, recommendations and matters outside the test or design brief.

Student, parent and career transfer

Make one evidence card for “Revise for Clarity, Accessibility and Consistency”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports engineering, science, information technology, laboratory work, environmental monitoring, facilities, quality assurance, procurement and technical project management without promising a grade, admission, funding decision or job.

CHAPTER 16 OF 16

16. Run a Final Technical and Decision Audit

Back to contents

Why this move matters

Verify requirements, calculations, source dates, limitations, recommendations and version control with another reader.

Build a traceable technical claim

Verify requirements, calculations, source dates, limitations, recommendations and version control with another reader. Join requirement, method, observation, calculation and conclusion so a reader can inspect the path rather than trust a confident sentence.

Design for two reading speeds

For the worked report, A peer independently checks one calculation and traces the recommendation back to evidence. Give decision-makers a concise finding and recommendation, while placing enough method, units, assumptions and data detail in the body or appendices for technical review.

Audit figures, tables and units

Ask which reader question each visual answers, then verify its caption, labels, symbols, units and explanation in the prose. Confirm that rounding and conversions do not imply more precision than the measurement supports.

Keep conclusions inside scope

Review reduces error but does not certify professional compliance. Separate observed results, engineering judgement, recommendations and matters outside the test or design brief.

Student, parent and career transfer

Make one evidence card for “Run a Final Technical and Decision Audit”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports engineering, science, information technology, laboratory work, environmental monitoring, facilities, quality assurance, procurement and technical project management without promising a grade, admission, funding decision or job.

PRACTICE LAB

Build a technical report decision trail

Student route

1. Choose one original report inside this guide’s scope.
2. Copy its objective and underline actor, action, context, evidence and intended decision.
3. Draw the specific reasoning chain used in this article.
4. Mark each step reported, inferred, contested or unknown.
5. Rewrite the conclusion so it preserves the narrowest important limitation.

Parent or teacher route

Ask the learner to explain write a technical report that lets readers find, test and use the evidence behind a recommendation twice: once to a classmate and once to a method specialist. Praise a precise correction and a well-stated unknown; both show disciplined attention to evidence.

Early-career route

Create a one-page technical report audit with source link, date checked, scope, method logic, decisive wording, contrary evidence, limit and next action. A colleague should be able to continue without guessing.

Continue with eduKate’s guides to reading course and career information and giving useful feedback in group projects.

USEFUL NEXT READING

Connect this narrow owner to its neighbour

Read the laboratory-report guide for a related but different reader job. Return here when the question is specifically how to write a technical report that lets readers find, test and use the evidence behind a recommendation. Use each guide for the reader task named in its heading.

For English practice across research, school and career communication, visit the Singapore English Tuition Centre learning site.

FREQUENTLY ASKED QUESTIONS

Questions students and parents often ask

Is a technical report the same as a lab report?

Not necessarily. A lab report records an experiment; technical reports also cover designs, evaluations, failures, options and recommendations.

Should technical writing use passive voice?

Use the voice that makes the actor and action clear. Current guidance supports active voice where it improves clarity.

Can jargon be used?

Use necessary specialist terms for the intended audience and define terms that other readers may not know.

What belongs in an appendix?

Supporting detail needed for audit or reuse but too long for the main reading path, with clear references from the report.

How much uncertainty should I report?

Enough for readers to judge whether the evidence supports the conclusion and decision.

Does a polished report certify the recommendation?

No. Qualification, standards, approvals and professional judgement remain separate requirements.