What you are preparing for

The Chartered Engineer Professional Review typically has two parts: a pre-submitted written application, including evidence of competence and commitment, followed by a structured Professional Review Interview (PRI). There may also be a short presentation. In the interview, trained reviewers explore how you explain and defend engineering decisions, judgement, responsibility, ethics, safety, sustainability and professional development, using your own work as evidence.

This is not a conventional revision exam: you need to know your evidence well enough to explain your contribution and respond to probing questions. Organise preparation around the UK-SPEC competences and the examples in your application. Check your professional institution’s current guidance for its application and review arrangements; do not assume another institution’s process or advice applies to you.

The plan below takes six weeks, with about four hours of focused work each week. If your review is sooner, keep the same order and combine weeks. If your application is not yet submitted, reserve additional time for drafting and checking it; interview practice does not replace the application work.

Set up your evidence before you revise

Choose three or four substantial examples from your own work. Across them, aim to cover the competences you need to evidence, rather than trying to force every example to demonstrate everything. Include a project or decision where your own responsibility is clear, a difficult technical or risk decision, and an example that lets you discuss leadership, ethics, sustainability or professional development. The examples may overlap.

For each one, make a one-page evidence record:

  • Context: the problem, objectives, constraints and stakeholders.
  • Your part: your role, authority, decisions and accountability. Separate these from what the wider team did.
  • Reasoning: options considered, evidence used, trade-offs and why you chose one route.
  • Assurance: safety, risks, relevant legislation or standards, review and escalation.
  • Result and reflection: what happened, what you learned and what you would change.

Remove confidential information. Use project names, values and details only where you are permitted to disclose them; otherwise describe the engineering issue at a safe level. Keep the application and your notes consistent. If a statement in the application is hard to explain or substantiate, resolve that before practising an interview answer.

A board built from candidate notes on a hypothetical pumping-station upgrade could be arranged like this:

Engineering Pumping-station upgradeStudy
CEng Review evidencePumping-station upgrade5 sections · 3 columns
Context and objectives
  • Existing station needed a capacity upgrade while maintaining service during the works.
  • Design brief set a target flow of 12 L/s at 18 m head (example project values).
  • Constraints included outage planning, access and an agreed capital limit.
Risk, safety and assurance
  • Identified service interruption and lifting operations as key delivery risks.
  • Recorded design assumptions, review actions and the person responsible for each close-out.
  • Checked applicable project requirements and standards with the responsible discipline lead.
My role and authority
  • Led options appraisal and prepared the design recommendation.
  • Escalated the final equipment selection for approval by the accountable technical lead.
  • Recorded which calculations and checks were completed by other team members.
Outcome and reflection
  • Recorded commissioning results against the approved project acceptance criteria.
  • Lesson: confirm access and maintainability constraints earlier in options appraisal.
  • Linked the lesson to a CPD action on whole-life asset decisions.
Options and engineering analysis4 due
  • Compared replacement pumps with a staged upgrade of the existing arrangement.
  • Checked duty-point assumptions against the available system information.
  • Selected the option that met the stated duty while allowing planned maintenance access.
Illustrative evidence board for a pumping-station upgrade, with a review section marked as due.

Six weeks of preparation

Keep the sessions short enough to repeat. A useful weekly pattern is two 60-minute evidence sessions, one 60-minute question-and-answer practice, and one 45-minute review. Add a separate application-writing session if your submission is still in progress. Start each session by choosing a specific output, such as one evidence record or one recorded answer, rather than rereading everything.

Week 1: Map the application to your evidence

Session 1 — 60 minutes: Read your submitted application, or the latest draft, alongside the current UK-SPEC and your institution’s guidance. Make a simple map: competence, application example, your contribution, and any supporting evidence you could explain. Do not copy competence wording into an answer without showing what you did.

Session 2 — 60 minutes: Choose your three or four examples. Write the evidence record for the strongest technical example. Mark unclear ownership, unsubstantiated outcomes and details you cannot disclose. Make a list of gaps to resolve, not a new narrative to memorise.

Session 3 — 60 minutes: Give a two-minute spoken summary of that example: problem, your role, decision and outcome. Record it. Check whether a listener could tell what you personally decided and what the team did.

Session 4 — 45 minutes: Review the recording and edit the evidence record. Create cards only for facts that need retrieval, such as a decision criterion, a risk control or a lesson. Cards should prompt understanding, not hold a full script.

Week 2: Test engineering judgement

Session 1 — 60 minutes: Build a decision table for one project: options, criteria, evidence, risks and trade-offs. Include why the rejected option was not selected. If you cannot justify a decision from the information available at the time, identify what you need to check.

Session 2 — 60 minutes: Practise questions such as “What alternatives did you consider?”, “What assumption mattered most?” and “What would have changed your decision?” Answer from the project record, not from what you know in hindsight.

Session 3 — 60 minutes: Take a second example and explain the technical reasoning without relying on team-wide achievements. State your authority and when you sought approval or specialist advice.

Session 4 — 45 minutes: Review what was vague or unsupported. Turn repeated weak points into a short retrieval list: for example, the criterion you used, the evidence behind a choice, or the boundary of your responsibility.

Week 3: Make safety, risk and compliance explicit

Session 1 — 60 minutes: For each main example, identify the material risks, who could be affected, how the risks were assessed, and what controls or assurance were used. Name applicable legal, regulatory or standards requirements only when you can explain how they applied. Verify uncertain references with reliable project records or authoritative guidance.

Session 2 — 60 minutes: Practise a risk question in a clear order: hazard or uncertainty, consequence, assessment, control, residual risk and escalation. Make clear what you personally did and who held formal approval or accountability.

Session 3 — 60 minutes: Work through an ethics or public-interest scenario from your experience. Explain the competing duties, who you consulted, what action you took, how it was documented and what you learned. Do not describe a team process as your own action unless it was.

Session 4 — 45 minutes: Update your evidence records. Prioritise any safety or compliance gap that could undermine a central project example.

A picker can help choose the next practice topic from areas where your evidence or answers need work:

New lecture
How long have you got?5 min10 min15 min20 min
Options and engineering analysisRisk, safety and assuranceMy role and authorityOutcome and reflection

Options and engineering analysis · Struggling — 4 of 9 cards missed, with 41% on the last practice paper

Generate lecture ideas
Illustrative topic picker highlighting the evidence area that needs the most practice.

Use that signal to choose a revision task, not to infer what the review will ask. Your own evidence gaps matter more than a practice system’s estimate of question frequency.

Week 4: Cover stakeholders, sustainability and professional development

Session 1 — 60 minutes: Revisit each example from the perspective of users, operators, clients and affected stakeholders. Prepare a specific account of how their needs affected the decision, including any conflict between requirements.

Session 2 — 60 minutes: Identify sustainability and whole-life considerations that genuinely informed your work. Use evidence where possible: alternatives considered, resource or maintenance implications, and the basis for your decision. Avoid adding a sustainability claim after the fact if it did not influence the project.

Session 3 — 60 minutes: Prepare one answer on professional development. Connect a learning need to an action and then to a change in your practice. Be ready to explain how you keep your knowledge current in relevant areas.

Session 4 — 45 minutes: Practise follow-up questions on the limits of your knowledge, an error or a decision you would revisit. A measured answer that identifies learning and appropriate action is stronger than an unsupported claim of certainty.

Week 5: Practise the interview, not a speech

Session 1 — 60 minutes: Ask someone to question you on one project for 20 minutes, then spend 40 minutes reviewing. If no partner is available, record yourself answering unpredictable prompts. Use brief notes, not a memorised script.

Session 2 — 60 minutes: Practise a short presentation only if it is relevant to your review arrangements. Check your institution’s guidance for expectations. Keep the presentation focused on a project decision and your contribution, then prepare for questions that challenge your assumptions.

Session 3 — 60 minutes: Run a mixed practice interview: project evidence, judgement, responsibility, safety, ethics, sustainability and learning. Ask your partner to interrupt when an answer is unclear or too general.

Session 4 — 45 minutes: Review recordings. Note one improvement each for structure, specificity and accountability. Aim to answer the question asked before adding background.

Week 6: Consolidate and reduce avoidable gaps

Session 1 — 60 minutes: Recheck your application against your evidence records. Resolve inconsistencies and confirm that you can explain the evidence behind important claims.

Session 2 — 60 minutes: Practise your weakest two areas, using short questions and follow-ups. Explain the reasoning and trade-offs, not just the final decision.

Session 3 — 45 minutes: Give one final timed practice interview or record a set of answers. Review only the points that need attention; do not try to memorise complete responses.

Session 4 — 30 minutes: Prepare practical arrangements and review your own project summaries. Confirm interview or presentation details with your institution. Finish by identifying what you will clarify if a question falls outside your experience.

Track weak areas by the marks you lose in practice, not by assumptions about what reviewers ask most often:

Where marks go missing
46%Options and engineering analysis7×
62%My role and authority8×
74%Risk, safety and assurance6×
86%Outcome and reflection5×
Illustrative practice dashboard ranking answer areas by marks earned and appearances in practice prompts.

Use the lowest result to set next week’s first session. “Times” here refers to practice prompts, not the likelihood of a topic appearing in a real review.

How MySummaries helps

MySummaries can turn your own application material and project notes into a revision board, retrieval cards, written practice and recorded oral answers. For this preparation plan, use it to organise UK-SPEC evidence, practise explaining your decisions and revisit the areas where your answers lose marks.