How To Assess Engineering Management Through RAEng Case Studies (EG7060)

Quick answer: For EG7060 you pick two similar case studies from the Royal Academy of Engineering’s Engineering X safety-critical systems collection, then judge the engineering management behind each failure. Markers want analysis of risk management, leadership, communication, safety culture and professional responsibility, not a retelling of the accident. Compare the two cases against the same framework throughout.

This guide is for Master’s students on EG7060 Mental Wealth: Professional Life at UEL, including those studying at LSBF Singapore, who are staring at a 4,000 to 5,000-word report plus a 10-minute presentation. You can read the original task on the EG7060 coursework question page, and see a worked slice in our EG7060 case study sample (for reference only).

If you would rather have a specialist shape the whole report, our report writing help team can support you.

How do you choose two engineering case studies for EG7060?

The Engineering X collection currently lists 18 short papers. They range from rail and nuclear safety to wildfire evacuation and humanitarian supply chains. You are not meant to pick two at random.

Choose two cases that share a sector or a management setting, so the comparison tests a management idea rather than two unrelated technologies. Two rail accidents, for example, such as “Bexley train crash – a system failure” and “Revisiting the causes of the Hatfield Rail Crash”, both followed the split of British Rail into separate companies. Other natural pairs would be the THORP internal leak and another high-hazard industrial case, or two papers on systemic failure in public services.

Check three things before you commit. Does each paper give enough detail about decisions and organisations, not only engineering faults? Can you find a management theory that applies to both? And will you still have something to say after 1,000 words?

What do markers want in “Understanding of Engineering Management Principles”?

The report heading tells you the aim. Your reader is checking whether you understand management principles and can apply them to real engineering decisions. Description earns very little.

The brief’s formatting rules also matter: Calibri 11 for body text, set heading sizes, British English and Harvard referencing. Students lose easy marks here. Set up your template on day one.

Where are the marks in a case-study comparison?

The module brief does not publish a mark breakdown in the version we have seen, so check your Canvas rubric. In practice the marks sit in four places: the quality of your comparison framework, the depth of critical judgement, the link from findings to management recommendations, and presentation of the report.

The framework is the one most students skip. Without it, the report drifts into narrative. With it, every paragraph answers the same question about both cases.

Step-by-step plan for the report

1. Read the brief and your marking rubric twice. Note the word limit, the heading, the GenAI declaration and the submission items.
2. Skim all 18 case papers, then shortlist three pairs.
3. Read your chosen pair in full and highlight decisions, roles, warnings and organisational changes.
4. Build a framework with five rows: risk management, leadership, communication, safety culture, professional responsibility.
5. Fill the framework with evidence and page references from each paper.
6. Add two or three academic sources on risk, human error or team learning, and test them against your evidence.
7. Draft the critical comparison first, then the introduction and conclusions.
8. Write recommendations that a manager could act on.
9. Build the 10-minute presentation from the report’s argument, not from its headings.
10. Run the Turnitin report and check your GenAI declaration before uploading to Canvas.

Mid-way through, it helps to see how a short section is built. The sample extract mentioned above does that for risk management and leadership.

How do you critically assess risk management and leadership?

Start with ownership. Who was responsible for each hazard, and could they see the whole picture? In the Bexley paper, Elliott (n.d.) describes a derailment that needed three causes together, each sitting with a different party. In the Hatfield paper, Kemp (n.d.) shows a recognised fatigue risk that was not controlled across a split chain of responsibility.

Then ask what the organisation did with warnings, audits and reviews. Finally, test a theory. Reason’s (2000) distinction between person and system approaches gives you something to argue with, because the Hatfield author questions how well layered-defence thinking fits systems with many owners.

Opinion helps here. Most reports state that “communication was poor”. The better ones say which interface failed, who needed what information, and what a manager should have changed.

What do students struggle with on this module?

The same problems come up again and again in enquiries from students on engineering management modules.

• Picking cases that are too different. A flood case and a ferry case leave no common thread to compare.
• Not knowing how critical to be. Students often fear criticising published work. You are allowed to question an author’s interpretation if your evidence supports it.
• Treating the paper as the only source. The brief expects wider reading.
• Stretching 5,000 words. Many run short because they describe rather than evaluate.
• Handling GenAI rules. The submission asks for a declaration, so students want to know what is acceptable under UEL’s policy. Read the policy on Canvas and declare honestly.
• Splitting time with the presentation. It is a separate deliverable, so plan it early.

Our experience is that the report improves fastest once the comparison table exists. After that, writing is mostly filling in judgement.

Common mistakes that lose marks

• Opening with 600 words of accident narrative.
• Using headings that repeat the brief instead of answering it.
• Citing case papers without author or year. Where the paper shows no year, use “n.d.” and give the access date.
• Treating “safety culture” as a buzzword with no evidence.
• Recommendations that are only “improve communication”.
• Presentation slides crowded with report paragraphs.
• Ignoring the font and heading specifications.

Mark-maximising checklist

• Two cases justified in a short paragraph.
• One framework applied to both cases in every section.
• At least one academic theory tested, not just quoted.
• Every claim tied to a case paper or other cited source.
• Recommendations linked to named management principles.
• Word count between 4,000 and 5,000, excluding references and appendices.
• Harvard list matches in-text citations.
• GenAI declaration and Turnitin report included.

If the timeline is tight, our case study assignment help page explains how we support analysis and structure. Our warranty policy sets out what we do and do not promise.

Frequently asked questions

Can I choose any two case studies from the Engineering X collection?

Yes, provided they are genuinely similar and come from the safety-critical systems collection named in the brief. Similar means a shared sector, hazard type or management setting. Confirm your choice with your module team if you are unsure.

How many words should I spend on each case?

Aim for balance, but organise by theme rather than by case. A comparison section on risk management might give each case about 300 words and a further 200 for the verdict. That keeps the report analytical instead of two summaries.

Do I need sources beyond the case study papers?

You should use them. The papers are your evidence, but your analysis needs concepts from the engineering management and safety literature. Peer-reviewed articles and official regulator reports are the safest choices.

What does n.d. mean in Harvard referencing?

It stands for “no date” and is used when a source shows no publication year. Some Engineering X papers show no year on the page, so cite the author as (Surname, n.d.) and add the access date in the reference list.

Can I use GenAI for the EG7060 report?

Only as far as the UEL GenAI policy and your module rules allow, and you must complete the declaration in the submission. Do not paste AI text into the report. Use any permitted tool for planning and always check facts against the source papers.

What should the 10-minute presentation include?

Present your argument: why these cases, your framework, three or four key findings and your recommendations. About one slide per minute is a sensible guide. Practise timing, because 10 minutes passes quickly.

Next step

Build your five-row framework before you write a single paragraph. If you want a specialist to check your structure or show you how a full answer reads, send your brief through our engineering assignment help service or look at our coursework writing help page.

About the expert

Guidance for this article comes from Han Lee, who holds a PhD in Mechanical Engineering from Nanyang Technological University and has worked as an academic writer for six years and as a design engineer for two years.

References

• Elliott, C. (n.d.) Bexley train crash – a system failure. Engineering X, Royal Academy of Engineering. Available at: https://engineeringx.raeng.org.uk/media/m3kbpmdm/engx-bexley-train-crash-a-system-failure.pdf (Accessed: 27 October 2026).
• Engineering X (n.d.) Safety critical systems case studies. Royal Academy of Engineering. Available at: https://engineeringx.raeng.org.uk/scs-case-studies (Accessed: 27 October 2026).
• Kemp, R. (n.d.) Revisiting the causes of the Hatfield Rail Crash. Engineering X, Royal Academy of Engineering. Available at: https://engineeringx.raeng.org.uk/media/sogkgnhl/engx-revisiting-the-causes-of-the-hatfield-rail-crash.pdf (Accessed: 27 October 2026).
• Reason, J. (2000) ‘Human error: models and management’, BMJ, 320(7237), pp. 768–770. Available at: https://pmc.ncbi.nlm.nih.gov/articles/PMC1117770/ (Accessed: 27 October 2026).