This workshop used engineering assignments undertaken by early-career professionals to examine how useful review questions can be identified in routine project records and how scattered material can become a clear case with defined responsibilities.
Review method
A project review starts with facts and a timeline. Material should establish context, objectives and constraints before recording milestones, options, site adjustments and the reasons for change. It should not present only the final outcome without process evidence.
- Organise tasks, decisions, implementation, checks and corrections in chronological order.
- Distinguish individual responsibilities, team contributions and work performed by external organisations.
- Connect technical judgements to drawings, meeting records, inspections, data or site photographs.
- Record successful measures, shortcomings and practical adjustments for future projects.
Case writing
A useful sequence is problem, constraints, action, evidence, result and lesson. Titles and summaries should identify the engineering issue directly, while figures, photographs and data should carry sources, dates and explanatory captions.
Client, partner, personal or sensitive project information must be anonymised or cleared for publication. Unauthorised drawings, contract documents and internal data are excluded from public versions.
Follow-up documentation
Case outlines and revision notes developed through the workshop may support personal record improvement, team learning or preparation for an Association case call. Publication still requires content verification, rights confirmation and the relevant review process.