The University of Manchester · FACULTY OF ENVIRONMENTAL SCIENCE

EART66001 Chap.9 Technical Notes and Presentations

- one subject, every graph, every model, every mark
6 Chapters5-page Bible
Our own words - no uploaded lecturer files
Updated for this semester
Chapter 9 of 9 · EART66001

Technical Notes and Presentations

Technical Notes and Presentations convert a large project record into a selective evidence route. The technical-note guidance moves through context, scope, aim, objectives, study area, method, results, limitations, conclusions and recommendations. Method identifies data inputs, modelling approach, scenarios and analysed outputs clearly enough for another reader to understand and repeat the work.

Results select comparisons that answer the aim; limitations explain uncertainty that can change the decision. The group presentation compresses the same logic for a live audience. The current assessment summary and an older guidance file disagree on duration, so the live Canvas task page controls timing.

No detailed rubric is reconstructed because the captured mark-scheme file names another module code.

Plan the note from objectives rather than from the chronology of modelling. Give each section a job and select figures that establish the necessary comparison. Background should justify the problem and boundary, method should make important choices repeatable, and results should state what changed relative to the baseline.

A visual that never affects the conclusion belongs in supporting material or should be removed.

Captions carry part of the argument. Identify scenario, location, variable and the pattern the reader should notice. Place the controlling limitation near the affected result before synthesising uncertainty in its own section.

Conclusions answer the aim without introducing new evidence, and recommendations specify an actor, action, evidence basis and next check whose strength matches the analysis.

The presentation uses the same evidence chain at a different compression. Open with the decision, show the method simply, spend time on the main comparison, state the limitation and close with action. Use readable labels and shared scenario language.

Rehearse to the current Canvas duration because the captured files conflict, and prepare every group member to explain why the representation, scenario and recommendation were selected.

In this chapter

What this chapter covers

  • 01

    Technical-note structure

  • 02

    Repeatable method

  • 03

    Selective results

  • 04

    Figure captions

  • 05

    Presentation timing

  • 06

    Proportionate recommendation

Worked example · free

Select evidence from a large project folder

Q [6 marks]. A folder contains many screenshots and time series. Build a concise report route without losing traceability. AskSia assigned these practice marks; they are not a University marking scheme.
The funnel narrows a large audit trail into selected comparisons, explicit limitations and recommendations that still trace back to evidence.The funnel narrows a large audit trail into selected comparisons, explicit limitations and recommendations that still trace back to evidence.Model files, outputs and checksSelected comparisons and limitationsConclusions and recommendations
The funnel narrows a large audit trail into selected comparisons, explicit limitations and recommendations that still trace back to evidence.
  • 2Map each objective to the smallest baseline-versus-scenario evidence set.
  • 2Use the method and model log to identify inputs, run settings and files instead of narrating routine clicks.
  • 2Link the main pattern to its limitation, affected receptor and proportionate recommendation.
The note keeps only evidence that answers the objectives while preserving the audit trail through method and model log. The original practice weighting is not an official scheme.
Sia tip — Show the comparison needed for the decision, then spend final words on its limitation and consequence.
Glossary

Key terms

Technical note
A concise professional report presenting method, evidence, limitations, conclusions and recommendations.
Figure caption
Text that identifies a visual's scenario, location, variable and decision-relevant pattern.
Recommendation
A proposed action whose strength and scope follow from the project evidence.
FAQ

Technical Notes and Presentations FAQ

How much method detail is enough?

Include data inputs, modelling approach, scenario differences, selected outputs and information needed to understand or repeat the comparison. Routine interface narration can be removed when it does not affect reproducibility or interpretation.

How should figures be selected?

Map every figure to an objective and conclusion. Keep the smallest set that establishes the comparison, preserve supporting outputs for audit and use appendices where the live instructions require material that is not central to the argument.

How should the group prepare for questions?

Every member should understand the scope, model choice, scenario control, main evidence, limitation and recommendation. If a question exceeds the analysis, state the evidence boundary and the additional run or data needed rather than inventing an answer.

What should be checked across the note and slides?

Compare scenario names, units, headline results, limitations and recommendations across the model log, technical note and presentation. A shorter spoken explanation may simplify detail but must not reverse the written meaning. Resolve any mismatch by returning to the logged model evidence, not by choosing whichever sentence sounds more confident.

How should a recommendation be written?

Name the actor, action, evidence basis, affected receptor and next check. Match the strength of the action to calibration and uncertainty evidence. Where the model supports only comparative appraisal, recommend further testing or staged action instead of presenting the scenario as a guaranteed real-world outcome.

Study strategy

Assessment move

Build the technical note as an argument map before drafting prose. Write the aim and objectives, then place one or two pieces of evidence beside each objective. Draft the figure sequence and captions early so repeated description can be removed. Use the method to identify inputs, modelling approach, scenarios and outputs, not to record every software click. In results, state the comparison and pattern before interpretation.

Attach the most important limitation to the affected claim, then explain its broader consequence in the limitations section. Make each recommendation name an actor, action, evidence basis and next check. For the presentation, compress the same route into the decision problem, a simple method visual, the main comparison, the controlling limitation and a closing action.

Rehearse transitions and shared terminology rather than treating speaker sections as independent mini-talks. Check the live Canvas duration because the captured materials conflict. Enlarge figure labels, remove interface clutter and avoid tables that need silent reading. In the final consistency pass, compare scenario names, units, headline results and recommendations across the model log, technical note and slides.

Do not invent rubric bands or marks where the captured sources do not provide usable criteria.

Working through Technical Notes and Presentations in EART66001? Sia is AskSia’s AI Environmental Science tutor — ask any EART66001 Technical Notes and Presentations question and get a clear, step-by-step explanation grounded in how EART66001 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.

A+Everything unlocked
Unlocks this Bible + all 41 of your subjects at The University of Manchester, plus 1,000+ more Bibles across the AskSia library.
Sia - your EART66001 tutor, unlimited, worked the way the exam marks it
The full 5-page Bible + practice bank with worked solutions
Chrome extension - sync your LMS so Sia knows your deadlines
Bilingual EN / Chinese on every Bible and every Sia answer
$0.99 Trial
30-day money-back · cancel in one tap · how it works