Understanding & Writing Reports I: Incident & Progress Reports
Intended learning outcomes of this tutorial. You should be able to:
- identify and explain a possible organisational structure for an incident report
- identify and explain a possible organisational structure for a progress report
Identifying Important Features of Reports
Comparing formal and informal reports. In the following table, write down the typical audience, purpose and text type of formal and informal reports as you perceive them. What do you think are the major differences between them?
The Technical Writing Process
The Writing Process
When you are asked to produce a report and once you have finished your research, how do you start? What are your steps?
Form small groups and rearrange the following ten stages of the writing process in chronological order, justifying your decisions. You can simply select the text from the columns on the left and drag them into the boxes on the right.
The Audience and Purpose
Colour-code all the verbs/verb complexes and their respective subjects in Text A, B and C, using the buttons below. Compare and discuss the kinds of verbs in each text, e.g. with regard to their formality, expression of certainty, etc. If you make a mistake, you can clear the colour-coding (unfortunately for the whole text box) by clicking the ‘clear formatting’ button. Make sure you’re in the right text box first, though by clicking somewhere inside it.
Identify which type of text Text A, B and C are extracted from.
- Text A
- Text B
- Text C
Now that you have identified the type of text what do you think the intended purpose of these texts is?
What is the likely relationship between the writer and the audience?
Identify the language features and their function(s) in all three texts. How do the authors use some of these features to engage the audience?
An incident is any event which is not part of the standard operation in or service provided by an organisation. In general, an incident may fulfil one or more of the following conditions:
- It causes, or may cause, an interruption of the operation of the organisation or the service it provides.
- It reduces or may reduce the quality of the operation or the service.
- It causes or may cause harm or damages to the stakeholders of the organisation.
There are different types of incidents in different disciplines. Within the IT domain, incidents can vary from system failures, phishing attacks, loss of or damages to data. In an engineering project, an incident may include mechanical failures, injuries, flaws in design, delays, and so on.
Recognising Generic Structure
In general, incident reports can be organised into Summary, Background, Facts, and Outcome sections. Although the labels for these seem to be be pointing towards a relatively clear structure, the boundaries may sometimes be slightly more fluent than originally expected. The frame below allows you to select a number of different samples from the dropdown list, categorised according to subjects, to help you identify these structural elements.
Read through the samples you think are most relevant to your own subject and try to answer the following questions:
- Where do the different sections in this report begin and end? First try to identify these sections yourself by writing name of the section, followed by a colon in front of the section text in the box containing the report, and then switch on the colour coding to see whether your expectations are confirmed.
- Do you think this is an effective way of organising this report? Why?
Reading for Meaning
Read the incident reports above again and answer the following questions:
Recognising Language Features
Look at the different examples of reports above again and answer these questions:
Compiling an incident report, or, as a matter of fact, any report, involves a number of different steps/sub-tasks.
- Analysing the situation & identifying the relevant facts (discarding the rest).
- Understanding your own responsibilities in dealing with the situation.
- Demonstrating a suitable degree of initiative and resourcefulness in making suggestions as to how to deal with the situation, if your role requires this.
Analysing the Situation
Before you actually write your report, you should start by analysing the incident in detail. Below, you’ll find a diagram that shows the position of a train and its carriages after a derailment. The table below this provides the basic facts and details that you will need in order to to write an incident report about the accident.
Look at both the graphic and the table of facts below, and try to identify all the relevant facts you need to include in your report. Which details do you think may be relevant and which irrelevant? Mark the relevant ones by placing a ‘Y’ in the box next to them, and the ones to exclude by adding an ‘N’, then discuss your choices with your neighbour, justifying them.
|Type of Fact||Detail||Relevant? (Y/N)|
|Time & place of accident||15th March 2011, 6:43 pm|
|Name of driver||Peter Chan (Staff ID 529879)|
|Number of locomotives||1|
|Number of carriages||9|
|Type of train (passenger/cargo)||passenger|
|Cause of accident||Driver error. The driver was under the influence of his prescribed medication and did not pay attention to the speed limit and the warning signals in the cabin.|
|Speed of train going into the tunnel||150 km/h|
|Maximum allowed speed in tunnel||80 km/h|
|Number of derailed carriages||4|
|Number of passengers||374|
|Injuries and casualties||7 dead, 62 injured|
|Damage to track and equipment (HK$)||10 million|
|Weather conditions||Low visibility as a result of the thunderstorm|
|Events/actions following the accident||Personnel from the Dispatch and Control Centre noticed the accident immediately from the control panel. The Fire Department was notified and the rescue team arrived at the site within 10 minutes.|
Understanding Your Responsibilities
Incident reports of the type we’re discussing here aren’t usually only written to inform someone/the public of the facts concerning an incident, but their purpose is generally also to demonstrate the efficiency and sense of responsibility of the ‘reporter’ in handling the situation, and to reassure the person/people to be informed that this situation is now well under control. The former may occur throughout the report, whereas the latter happens predominantly in the outcome section.
Assuming that you are the chief engineer at the Control Centre and your task is to inform the railway company of the incident, identify your additional responsibilities in this. Which of the above actions would you already have set in motion/been responsible for, and what other steps would you still (need to) initiate in the interests of the company and to show your own initiative?
The function of a progress report is to inform your superiors or commissioning institutions about the amount of progress that has been made on a project, which problems or issues have been encountered and which phases have been completed, which phase has been reached, and what is supposed to happen next. They thus share some details with incident reports, but also exhibit distinct differences in their structure. For instance, both types of reports begin by providing a Summary and some Background information sections. The next section, entitled Progress, which may also contain some of the facts of the incident report if progress has been hampered by any incidents; otherwise it just charts the progress and details what has been accomplished so far. This is then followed by a description of the current stage of the project, called Situation Now. The final section details Future Plans and is fairly similar to the Outcome section in incident reports in that it describes future actions/initiative to be taken.
Here are some samples of progress reports. Can you divide them into different sections?
With the colour coding switched on for the above examples, look at the use of different tenses in the different sections of the report. Can you relate the use of tenses to the individual functions of the sections?