In this guide
Use this material to examine your own work. Confirm current requirements, forms and dates with ICE before applying.
Show how you use engineering knowledge to solve problems and make decisions within your responsibility. Explain the judgements you made yourself and when you needed further advice.
What the area requires
That you know your engineering, that you use it to solve real problems, and that you make judgements of your own rather than passing every decision upwards.
Additional Chartered requirements
At IEng you contribute to solutions and select from established techniques with skill. At CEng you take on the definition of the problem itself (deciding what the requirements and risks are) and you undertake the solution rather than contributing to someone else's. The CEng clauses also expect you to have engaged in bringing something new or improved into use. That does not mean inventing technology. Introducing a method that was new to your organisation, and being the person who worked out whether it was sound, counts.
What strong and weak evidence look like
Look for
- A decision you made where the codes or the standard approach did not settle the answer, and you had to reason it out.
- An option you rejected, with the reason, and what would have had to be true for you to have chosen it instead.
- A calculation or model you produced and, separately, the sanity check you ran on it before you trusted it.
- A time your first answer was wrong, how you found out, and what you changed.
- An explanation of how the design choice affected construction and operation.
- A technique or tool you introduced or adapted, and how you satisfied yourself it was fit for use.
Watch for
- A description of the project's engineering with no sentence beginning "I decided" or "I recommended".
- "I carried out the design in accordance with the Eurocodes": this states compliance, not judgement.
- Software output presented as the engineering. Reviewers want to know what you did to check it.
- Claiming a whole team's technical work in the first person singular.
- Depth of theory with no application, or application with no theory behind it.
A design decision, written two ways
Fictional example: structures, consultant, footbridge over a canal
I designed the footbridge deck using finite element analysis and checked it in accordance with the Eurocodes. The design was approved by the checker and issued for construction.
The deck was a shallow steel box, and the first pedestrian mode came out at 1.9 Hz — inside the range where footfall excitation matters. I had three options: deepen the box, add a tuned mass damper, or accept the response after a proper comfort assessment. I ran the assessment in accordance with the National Annex, found a peak acceleration of about 0.6 m/s², and recommended accepting it with a note in the maintenance manual, rather than spending on a damper for a response the users would barely notice. I was wrong about one thing: I had used a hand-back stiffness for the bearings that turned out to be optimistic, and when the supplier data arrived the frequency dropped to 1.75 Hz. I re-ran it, and it still passed, but I now ask for supplier stiffness before I fix a dynamic model.
The second version contains a real engineering problem, three options with a stated basis for choosing, a number, a judgement about proportionality, and a mistake owned and learned from. The first version says only that the candidate used software and complied with a code.
Questions to ask yourself
- Which technical decision on this project was mine?
Choose a decision for which you can explain your own responsibility, reasoning and outcome.
- What would have happened if I had chosen the other option?
Being able to answer this shows the options were real to you, not written up afterwards.
- How did I know my answer was right?
Checking is where engineering judgement lives, and it is the question that most often exposes thin evidence.
- What did I get wrong, and how did I find out?
Reviewers are unfazed by mistakes and unimpressed by candidates who claim to have made none.
- Where does my knowledge run out, and how do I behave when it does?
Knowing the limit of your competence is separately assessed under Professional Commitment, and it makes technical claims more credible, not less.
The same area, in different kinds of work
| Setting | What the evidence tends to look like |
|---|---|
| Consultant, design | Choosing an analysis approach and defending why the simpler model was adequate; setting the design assumptions that others then worked to. |
| Contractor, temporary works | Working out a propping scheme, its load path and its failure mode, and deciding what had to be checked on site before load was applied. |
| Client, asset owner | Deciding whether a defect was structurally significant, and what evidence was needed before intervening or leaving it. |
| Geotechnics | Deciding what the ground model actually supported, and how much of the residual uncertainty could be carried by observation rather than by conservatism. |
| Water | Choosing between hydraulic modelling refinement and a physically robust design margin, and justifying which served the outcome better. |
| Digital engineering | Deciding what a model was fit to be used for, and being explicit about what it did not represent. |
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.
Judgement when the code does not settle it
Fictional example: geotechnics, client-side engineer, embankment slip
A slope stability analysis was carried out and remedial works were designed to bring the factor of safety up to the required value.
The back-analysis gave a residual friction angle of about 13°, which put the long-term factor of safety at 1.08 — below target but not obviously failing, and the slope had stood for forty years. The question was whether to regrade, which meant taking land we did not own, or to install a drainage solution and monitor. I judged that the mechanism was pore-pressure driven rather than progressive, because the movement correlated with winter recharge rather than accumulating year on year, and recommended counterfort drains with piezometric triggers. I set the trigger at 0.4 m above the winter baseline, on the basis that it gave a season's warning. That was my call and I documented the reasoning so that whoever inherits the asset knows what the trigger was chosen against.
The account explains why the engineer accepted one mechanism over another, the basis for the number chosen and the implications for future operation. These details demonstrate independent engineering judgement.
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
- Taking one calculation or drawing from your appendices and asking you to talk it through from first principles.
- Asking what you would do differently now, three years on.
- Asking how you would explain the same decision to someone who disagreed with it.
- Moving from your project to a fundamentals question in the same area.
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.