This technical report
is presented at your premises by a retired C.Eng, published writer and
professional trainer with a long career in the engineering industry.
Tony has presented
over 200 times so far to clients including HSE, Raytheon, Panasonic,
Southern Water, Pilkington Glass and many others.
reports are your "product". They are important in many ways and can
affect your organisation's reputation so you should make them as easy
your intended readers to understand. Writing for the reader is the
'Golden Rule' whoever they are and whatever their level of technical
understanding - and however complex the work you are reporting.
all round - Thanks".
COURSE AIM - Technical Report Writing
To help delegates to write
shorter and better technical reports and to write them faster - and
make it easier for line managers to check and approve them.
COURSE CONTENT - Technical Report
- Technical reports - their
importance and problems.
- Differences between good and poor
- Writing for readers with
different levels of technical understanding.
- Triple goals: better, faster and
- A methodical approach -
Plan, Write, Edit.
- Planning technical reports -
agreeing the purpose or terms of reference.
- Your readers - who are they, why
do they want this report, their technical understanding?
- How much
detail to include,
how much jargon?
- Who reads what?
- Formatting a
technical report, section by section.
- Conventional formats.
- Structuring complex arguments and
- Planning illustrations and tables
from the start.
- Dealing with information only a
- Using appendices.
- Planning down to paragraph level
- Going from plan to draft.
- Determining style.
- Using plain English in technical
- Verb tenses.
- When technical jargon is
and when it isn't.
- Controlling paragraph and
with SI units, bullet points, numbering systems,
citations and references, etc.
- Going from draft to finished
- Ensuring your technical report
is clear, concise and correct.
- Plain English.
- Active and passive verbs in
- 'Smothered verbs' in technical
- Eliminating waffle.
- Some troublesome points of
English grammar and style.
- Using the Microsoft grammar and
- Using the Microsoft readability
for illustrations and tables.
- Punctuation problems - reference
WHO IS IT FOR? - Technical Report
The course is mainly for engineers
and technicians who need to write reports for either internal or
external readers. It is popular with engineering consultancies.
IS THERE A TRACK RECORD? - Technical
Report Writing Course
Tony presented the course
for the first time on 7 Feb 2001 for a group of optical engineers.
Whilst writing good technical reports can be difficult, this technical
report writing course has made the task easier for around 2000
engineers. It's made checking and approving reports quicker and
easier for their managers, and made reading them easier for their
The course has been presented over
200 times including at the following organisations as well as many
Please email or phone for a
quotation. Email direct to Tony
Atherton or phone 07976-390960.
The training style is very
interactive and uses talks,
examples, discussions, group and individual work in a mix that is
appropriate as possible to the delegates. We will need to discuss your
priorities with you before your
course, which may mean your course is slightly different from the
A substantial handbook combining
course notes and reference material is given to every delegate.
Tony's engineering background has
been crucial in ensuring the success of this course. He is also a
published writer with four books and around 90 articles to his name.
He has trained thousands of
delegates from blue-chip organisations - both independently and on
behalf of large training companies including the former Institute of
Management, Reed Learning, Fielden-Cegos and Right-Coutts. He has also
inspected government-funded training on behalf of the Training
Standards Council and the Adult Learning Inspectorate (now part of
SOME DELEGATES' COMMENTS
- One of the
most enjoyable courses I have attended.
- The Managing
Partner stopped me (Training Manager) to say, "well done on the
technical report writing
course." That is high praise indeed so thank you for doing such a great
- The feedback
was all very positive and all the guys have taken something from the
course. Two of the engineers even went back and looked back at their
reports with a view to rewriting them.
- The course
was very useful and enjoyable. Very informative, good notes to take
- You'll be
pleased to know we are regularly benefitting from the (technical report
writing) training you provided (six months ago).
- We are still
seeing a good payback from the Technical Report writing training you
delivered across the business - reports continue to be generated and
the formatting, design and presentation of the reports is of an
- Thank you very
much for the technical report writing course. All the feedback I've had
so far has been very positive and there was genuine enthusiasm from
most of them which is quite unusual as they can be quite a cynical
- Very useful
and relevant to the way we write reports on the computer.
very useful and will give me confidence in technical report writing.
- Interactive -
everyone's ideas made it more enjoyable.
- The course
was well received and very quickly assimilated by all of us - a lot of
the tips and tools are now second nature.
- The trainer
came across very well, I thought, and the material he provided was very
good. It has made me realise that there is more to report writing than
- Learnt a lot,
will help when writing a technical report - definitely.
- Very useful
on all aspects of report writing.
- I'm actually
using quite a bit of the information and tips we gained from Mr
Atherton. I am now more aware of the layout of my reports when I put
them together and the effect this can have on the reader. More than
anything though I think I am planning more! Something that Mr Atherton
put across as being very important. This planning has saved me time in
the long run and has meant that I now feel more confident when handing
over my reports to QA for final approval.