Purpose of the report

The report is not a description of projects. It is an assessment of you as a professional engineer.

Reviewers are looking for evidence that you can:

• take responsibility for engineering work

• make and justify decisions

• understand the implications of those decisions

• learn from challenges and outcomes

In simple terms, they are assessing whether you are ready to operate at the level required for EngTech, IEng, or CEng.

How the report is assessed

Your report should read as a clear, structured account of your work, not a list of tasks.

The ICE does not expect a rigid “attribute by attribute” structure. A stronger approach is to describe your role and responsibilities, and demonstrate the attributes through that narrative.

This allows reviewers to understand:

• what you did

• why you did it

• how you approached decisions

• what you learned

Key requirements

• Word limit
  5000 words for IEng and CEng
  3000 words for CPRP

• Project focus
  You may focus on one major project, a number of smaller projects, or your general role, provided it demonstrates your competence clearly

• Appendices
  Supporting information can be included, but should be relevant and used to support your narrative, not replace it

What strong reports do well

Clear ownership

Strong reports are explicit about your role.

They explain:

• what you were responsible for

• what decisions you made

• how you contributed to outcomes

Vague wording is a common weakness.

Evidence of judgement

You need to show how you think as an engineer.

That includes:

• explaining why decisions were made

• considering alternatives

• recognising constraints and risks

• reflecting on outcomes

This is where many reports fall short.

Focus on your contribution

The report is about you, not the project.

Avoid long sections describing the project in detail unless they directly support your role and decisions.

Lessons learned

Reviewers are interested in how you respond to challenges.

This includes:

• what went wrong

• how you addressed it

• what you would do differently

This demonstrates maturity and professional development.

Common mistakes

• describing the project instead of your role

• using passive language

• underplaying your contribution

• not explaining decisions

• trying to cover too much without enough depth

Structuring your report

A simple structure works well:

Introduction
Set out your role and the projects or responsibilities being discussed.

Main body
Explain your work, responsibilities, and decisions in a logical sequence.

Reflection
Highlight key challenges and lessons learned.

Conclusion
Summarise your level of responsibility and readiness.

Presentation and clarity

Your report should be easy to read and follow.

• use clear sections

• keep language concise

• avoid unnecessary jargon

• define acronyms where needed

• use visuals where they genuinely support your explanation

Final checks

Before submission:

• check grammar and clarity

• ensure your role is clear throughout

• confirm consistency between report and appendices

• consider whether a non-specialist could follow your explanation

The role of feedback

Most candidates improve their report significantly after external review.

A second perspective can highlight:

• where your role is unclear

• where decisions are not explained

• where attributes are not being demonstrated strongly enough

Why the report matters

The report is usually the first detailed view reviewers have of your experience.

It shapes how they approach your interview and the areas they choose to explore.

A clear, well-structured report makes it easier for reviewers to understand your competence and assess you at the appropriate level.

Preparing your report

If you are working on your submission, the key question is not whether you have enough experience, but whether it is being presented clearly and at the right level.

If you are:

• unsure whether your report meets the expected standard

• struggling to show your role and decisions clearly

• or preparing for submission in the near future

it is worth getting this reviewed before you submit.

How to write a strong ICE Professional Review Report (PRR)
A strong PRR clearly explains your role, your decisions, and your level of responsibility. It should show how your experience meets the ICE attributes through real examples.

To write an effective report:

• focus on your personal contribution, not the project

• explain why decisions were made

• demonstrate judgement and awareness of constraints

• include reflection on challenges and outcomes

Most candidates have enough experience. The difference is how clearly it is presented.

Next step

If you want structured feedback on your report:

Book submission report review

You will receive:

• detailed feedback aligned with ICE expectations

• clear identification of gaps and weaker areas

• practical steps to improve your submission before review