In this guide
Use this material to examine your own work. Confirm current requirements, forms and dates with ICE before applying.
Explain how you plan and run engineering work. Include how you use people and resources and help others improve their practice.
What the area requires
That you can plan and run work, use people and resources well, and help others get better at what they do.
Additional Chartered requirements
The IEng statements are about managing work well. The CEng extensions add direction and development: leading or influencing rather than managing within a set structure, developing people rather than assisting them, promoting best practice rather than contributing to it. Note the word influence. Leading a team you have no line authority over is squarely within this, and for many engineers it is the more honest description of what they do.
What strong and weak evidence look like
Look for
- A programme you built, what you got wrong in it, and how you recovered.
- A resourcing decision with a real constraint behind it: someone you could not have, a skill you did not have.
- A time you changed a colleague's approach by persuasion, and what argument worked.
- Concrete development of someone else: what they could not do before, what they could do after, and your part in that.
- A quality process you changed because it was not catching what it was meant to catch.
Watch for
- A job title offered as evidence of leadership.
- "I managed a team of twelve" with nothing about what managing them involved.
- Attending meetings, described as chairing them.
- Quality described as following the QA system, with no example of it failing or improving.
- Long lists of responsibilities with no decision in them.
Leading without authority
Fictional example: highways, consultant, no line reports
I worked closely with the drainage and geotechnical teams to coordinate the design and ensure the programme was met.
Drainage and geotechnics were producing incompatible assumptions about the groundwater level, and neither team would move because each had a different source. I had no authority over either. I got the two leads into a room with the borehole logs and the drainage model on the same screen, and it took twenty minutes to establish that one had used the standing level at drilling and the other the long-term recovered level. We agreed the recovered level, I wrote it into the design assumptions register, and I got both leads to sign it. It removed a rework that would have cost about three weeks.
There is a specific problem, a specific reason nobody could just be told what to do, an action the candidate took, and a consequence. It also shows an understanding that the fix was a governance one (writing it into the register) rather than just a conversation.
Questions to ask yourself
- When did I have to choose between two things I could not both do?
Management evidence is made of trade-offs. Where there was no constraint there was no management decision.
- Who did I have to bring with me, and how?
Influence without authority is often the strongest CEng leadership evidence available to a junior-titled engineer.
- What did I delegate, and how did I assure myself it was done properly?
Delegation with retained accountability is the pattern reviewers look for.
- Who is better at their job because of me?
The CEng extension is 'develop others'. A specific person and a specific improvement answer it; a mentoring policy does not.
The same area, in different kinds of work
| Setting | What the evidence tends to look like |
|---|---|
| Contractor, site | Sequencing a possession, deciding what to drop when the weather went against you, and holding the quality line under programme pressure. |
| Consultant, project management | Restructuring a delivery team when a discipline fell behind, and being straight with the client about the consequence. |
| Client organisation | Directing a supply chain towards an outcome rather than a specification, and holding designers to account without designing for them. |
| Asset management | Prioritising an intervention programme against a fixed budget and defending what you chose not to do. |
Illustrative. The area is generic by design: ICE says the attributes can be achieved in a range of ways by anyone working as a civil or infrastructure engineer.
Developing someone, rather than helping them
Fictional example: contractor, section engineer
I mentored a graduate engineer and provided support and guidance to help them develop.
The graduate on my section could set out but could not read a temporary works design well enough to know when what was built did not match it. Rather than checking it for him, I took him through the propping design for the headwall — load path, what each member was doing, what would happen if the raking shore was 200 mm off. Then I had him do the pre-pour check himself and talk me through it. Two weeks later he stopped a lift because the toe restraint had not been installed. He would not have spotted it in March.
The CEng extension is 'develop others'. This names what the person could not do, what the candidate did about it, and the evidence that it worked. Compare the weaker version, which could have been written by anyone about anyone.
An evidence-planning exercise
Written for a notebook rather than a submission. Anything you cannot answer is a development action, not a writing problem.
How interviewers tend to approach this area
- Asking about a time the programme went wrong and what you personally did about it.
- Probing a conflict (with a client, a contractor, a colleague) and how you handled it.
- Asking how you knew work you had delegated was right.
- Asking what you would do about an under-performing team member.
There is a large bank of original practice questions in the question bank, filterable by area and by level.
Official sources
Selected publisher pages were rechecked in September 2026. Other source records were last checked in July 2026. Open the latest official document before relying on a requirement.