IMechE CEng Application Example: Competence Statements A-E

Writing an IMechE Chartered Engineer application is not mainly a test of elegant prose. It is a test of whether an assessor can find clear evidence that you meet the CEng competence and commitment requirements.

That distinction matters. A technically impressive project can still produce a weak application if the statement only describes what the team delivered. A less glamorous project can provide excellent evidence when it shows your judgement, calculations, decisions, leadership and measurable results.

This guide explains what to include in each of the five competence areas and provides original, fictional examples to illustrate the difference between description and evidence.

Important: The examples below are fictional and deliberately generic. Use them to understand structure, not as text to copy. Your application must accurately represent your own work, decisions and level of responsibility.

What does the IMechE CEng application require?

The IMechE application asks you to demonstrate five broad areas of competence and commitment:

• A — Knowledge and understanding: how you use and extend engineering knowledge to optimise technology.
• B — Engineering problem-solving: how you identify, investigate, develop, implement and evaluate solutions.
• C — Responsibility, management and leadership: how you plan work, manage resources, lead people and improve quality.
• D — Communication and interpersonal skills: how you communicate, present proposals and work effectively with others.
• E — Professional commitment: how you address conduct, safety, sustainability, development and ethics.

The IMechE Chartered Engineer application guidance also lists an organisation chart, development action plan and sponsors among the required application information. Applicants should follow the instructions and word limits shown in the current application form.

The competence statements are not five isolated essays. The same project can support several areas, provided you explain a different part of your contribution each time. A heat-recovery project, for example, might show technical modelling under A, option selection under B, budget control under C, stakeholder approval under D and reduced energy consumption under E.

What strong CEng evidence looks like

A strong statement normally answers six questions:

1. What was the engineering situation or problem?
2. What were you personally responsible for?
3. What technical or commercial constraints did you face?
4. What did you analyse, decide or change?
5. Why did you choose that approach?
6. What happened as a result?

The STAR method — Situation, Task, Action and Result — can help you organise the story, but do not let the first two elements take over. Most of the statement should explain your actions, reasoning and results.

Compare these two sentences:

Weak: “We designed and installed a new cooling system which improved reliability.”

Stronger: “I compared three cooling concepts against heat-load, contamination, maintenance and whole-life-cost requirements. My thermal model showed that the lowest-capital-cost option would exceed the allowable bearing temperature during summer operation, so I recommended a closed-loop water-glycol system. I presented the additional £24,000 investment to the operations manager using the predicted failure cost and secured approval. Following commissioning, maximum bearing temperature fell by 18°C and unplanned cooling-related stoppages reduced from six in the previous year to one.”

The second version gives an assessor something to evaluate: personal contribution, technical depth, alternatives, commercial judgement and a measured outcome.

Competence A example: Knowledge and understanding

What assessors need to see

For CEng, Competence A is about more than attending courses or using established calculations. It asks how you have maintained a sound theoretical approach and how you have applied knowledge creatively to new, advancing or unfamiliar technology.

Useful evidence might include:

• developing or validating an analytical model;
• applying first principles where a standard method was insufficient;
• learning a new technology and judging its limitations;
• combining knowledge from different engineering disciplines;
• leading research, testing or experimentation; or
• introducing a technically novel improvement.

Weak example

“I regularly use finite element analysis and keep up to date with new simulation software. I used FEA to improve a bracket, which was then manufactured successfully.”

This names a technical tool but does not reveal the theory applied, the assumptions made, the applicant's level of judgement or the improvement achieved.

Stronger fictional example

“I was responsible for resolving fatigue cracking in an aluminium actuator bracket used on a high-cycle packaging machine. The existing static FEA predicted an acceptable safety factor, so I reviewed the model assumptions and concluded that it did not represent the measured transient load or the welded heat-affected zone.

“I extended my knowledge of fatigue assessment by reviewing the relevant design standard and specialist literature, then created a strain-life model using load data that I captured at 2 kHz during representative machine cycles. I performed a mesh-sensitivity study, modelled the local weld geometry and compared the predicted strain with measurements from a strain-gauged prototype. The correlation was within 8% at the critical location.

“Using the validated model, I developed a radiused, bolted design that moved the peak stress away from the weld while remaining compatible with the existing envelope. Accelerated testing represented 18 months of service without crack initiation, and the design was adopted across 14 machines. I documented the modelling limits and validation method so that the engineering team could apply the approach to future fatigue investigations.”

Why this works

The example shows that the applicant:

• recognised the limits of an existing method;
• deepened their own technical knowledge;
• selected and justified a more appropriate analytical approach;
• validated theory against physical evidence; and
• converted the learning into an implemented organisational improvement.

For your own statement, name the engineering principles you applied, but keep the narrative understandable to a Chartered Engineer outside your precise specialism. Technical depth is valuable; unexplained jargon is not.

Competence B example: Analysis and solution of engineering problems

What assessors need to see

Competence B follows the engineering lifecycle. It covers how you identify opportunities or problems, conduct appropriate investigation and design, implement the chosen solution and evaluate its effectiveness.

Strong evidence often includes:

• defining requirements rather than simply receiving a finished specification;
• identifying constraints, risks and stakeholders;
• comparing credible options;
• conducting calculations, trials, research or trade-off studies;
• implementing a solution; and
• checking the outcome against the original success criteria.

Weak example

“I was asked to reduce compressed-air consumption. I reviewed the system and arranged for leaks to be repaired. This saved the company energy.”

The result may be useful, but the statement does not show a sufficiently developed investigation or engineering solution.

Stronger fictional example

“Analysis of site energy data led me to identify an unexplained 22% increase in overnight compressed-air demand. I established a baseline using two weeks of flow, pressure and compressor power data, then separated production and non-production loads. The measurements showed that leaks alone could not explain the increase and that the lead compressor was repeatedly unloading at low demand.

“I developed three options: repairing leaks only, adding local receivers at the two high-demand machines, or installing a variable-speed compressor with revised sequencing controls. I modelled the demand profile in 15-minute intervals and assessed each option against pressure stability, energy consumption, maintainability, production risk and payback. The combined receiver and control-sequencing option offered 86% of the predicted energy saving of a new compressor at less than one-third of the capital cost.

“I planned a staged installation during weekend shutdowns and defined acceptance criteria of at least 6.2 bar at the most remote user, no increase in machine faults and a 15% reduction in compressor electricity. After commissioning, I monitored four weeks of operation. Electricity consumption reduced by 19%, pressure remained above 6.3 bar and the project delivered a verified annual saving of £31,000. I then added automated alerts for future changes in non-production demand.”

Why this works

The applicant does not jump from problem to solution. They establish the need, collect evidence, compare options, implement the selected approach and verify the result. The example also demonstrates technical and commercial judgement without pretending the most expensive solution was automatically the best one.

Competence C example: Responsibility, management and leadership

What assessors need to see

You do not need a large department reporting to you to demonstrate CEng-level leadership. You do need evidence that you take responsibility, influence outcomes and manage engineering work beyond your own individual tasks.

Relevant evidence may include:

• planning scope, programme and delivery stages;
• controlling a budget or making commercial decisions;
• managing contractors, suppliers or multidisciplinary colleagues;
• resolving resource conflicts;
• developing or mentoring others;
• setting quality requirements; and
• using lessons learned to improve future delivery.

Weak example

“I managed a team of engineers and contractors to deliver the project on time and within budget. I held meetings, delegated work and ensured quality standards were followed.”

These are claims rather than evidence. The assessor cannot see the scale of responsibility, the decisions made or how the applicant led the work.

Stronger fictional example

“I led the mechanical workstream for the £1.2 million replacement of an ageing process line. My responsibility covered the £420,000 mechanical budget, programme integration, technical approval and coordination of three engineers, the installation contractor and two equipment suppliers.

“At the planning stage, I converted the operational requirements into a work breakdown structure and identified the shutdown duration as the principal business risk. When supplier drawings arrived three weeks late, I re-sequenced the design reviews, assigned one engineer to resolve interfaces directly with the electrical team and negotiated staged drawing releases from the supplier. This protected fabrication start without reducing the independent checking period.

“During installation, I chaired daily coordination meetings and used a risk-based punch-list to prioritise safety- and production-critical defects. I coached a graduate engineer through the alignment survey and calculation rather than taking the task back, then independently reviewed their result before acceptance. The line entered production after a nine-day shutdown against the approved ten-day plan, the mechanical package finished 3.5% under budget and the graduate subsequently led the alignment activity on the next project.

“My post-project review identified repeated ambiguity in supplier interface drawings. I introduced an interface schedule and a 30/60/90% design-review process, which the programme manager adopted for the remaining line replacements.”

Why this works

This evidence gives scale and context, but it focuses on leadership actions: planning, reprioritising, negotiating, delegating, developing another engineer and embedding a quality improvement. It also shows what changed because of the applicant's intervention.

If you do not control money directly, explain the resources you do control, such as engineering hours, test capacity, contractor time, equipment availability or shutdown duration. Do not invent budget responsibility that you did not have.

Competence D example: Communication and interpersonal skills

What assessors need to see

Competence D is not proven by saying that you write reports and attend meetings. Assessors need examples of communication that affected an engineering outcome, particularly where the audience had different knowledge, priorities or concerns.

Good evidence can include:

• explaining complex risk to a non-specialist decision-maker;
• presenting and defending a technical proposal;
• chairing a difficult multidisciplinary discussion;
• negotiating with a supplier or client;
• resolving conflict constructively;
• adapting communication for different audiences; or
• creating an inclusive environment in which others can contribute.

Weak example

“I have excellent communication skills and regularly communicate with senior management, suppliers and technicians. I give presentations and write technical reports.”

This could describe almost any experienced engineer. There is no specific situation, adaptation or outcome.

Stronger fictional example

“During a design review, production managers opposed my proposal to replace an unguarded manual sampling task with an automated system because they believed it would slow batch release. The technical risk assessment alone had not changed their position, so I adapted the discussion around their operational concerns.

“I created a simple process map comparing the existing and proposed workflows, translated the calculated risk into credible exposure scenarios and demonstrated a prototype to two operators before the formal review. I asked the operators to identify usability problems privately as well as in the group session, because one was new to the team and had contributed little in earlier meetings. Their feedback led me to reposition the controls and add a manual recovery mode.

“At the approval meeting, I presented the safety case to engineering and the cycle-time evidence to operations, then facilitated agreement on a two-week production trial with defined stop criteria. The trial showed a 12-minute reduction in average sampling time as well as removing routine access to the hazard. Operations approved permanent installation, and the revised engagement approach was used on two later automation projects.”

Why this works

The applicant identifies resistance, listens to different stakeholders, adapts the message, creates space for a less-confident colleague and uses evidence to reach agreement. Communication is shown as an engineering competence, not a list of documents produced.

Competence E example: Professional commitment

What assessors need to see

Competence E covers your obligations to the profession and wider society. Your evidence should address professional conduct, safe systems of work, sustainable development, continuing professional development and ethical principles.

Avoid treating this section as a list of policies you know. Show occasions when those obligations affected what you actually did.

Potential evidence includes:

• challenging or stopping unsafe work;
• improving a risk-management system;
• balancing environmental, social and economic impacts;
• recognising and managing a conflict of interest;
• protecting confidential information;
• responding to pressure to conceal or minimise a problem;
• reflecting on learning and applying it at work; and
• maintaining a forward-looking development plan.

Weak example

“I always comply with health and safety requirements and the IMechE Code of Conduct. I consider sustainability in my designs and complete the CPD required for my role.”

The statement expresses good intentions but provides no evidence of judgement or commitment.

Stronger fictional example

“While reviewing bids for a pump replacement, I found that the lowest-cost supplier had excluded the specified containment test and proposed an elastomer that was incompatible with one of the cleaning chemicals. The project manager asked me to accept the bid and resolve the details after purchase to maintain the schedule.

“I explained that acceptance would transfer an avoidable safety and environmental risk into commissioning and would make the tender comparison misleading. I documented the deviation, checked the chemical compatibility data with the site process-safety specialist and recommended that all bidders price the same corrected requirement. When the preferred supplier disclosed that one of its representatives had previously worked for my team, I also recorded the relationship and removed myself from the final commercial scoring while remaining available to answer technical questions.

“The revised evaluation selected a compliant pump with double containment. I then calculated the whole-life impact of the shortlisted options, including energy use at the actual duty point, seal-replacement frequency and disposal. A higher-efficiency motor added £3,800 to the purchase cost but had a predicted 2.4-year payback and reduced annual electricity consumption by 11 MWh, so I secured its inclusion.

“The incident exposed a gap in my knowledge of procurement ethics. I recorded this in my CPD review, completed training on conflicts of interest and sustainable procurement, and worked with supply chain to add mandatory technical-deviation and conflict declarations to future engineering tenders.”

Why this works

This example connects conduct, safety, sustainability, ethics and CPD through real decisions. It shows the applicant resisting schedule pressure, recognising a potential conflict, comparing whole-life effects and converting reflection into changed practice.

You will usually need more than one example to cover all of Competence E. A concise safety example and a separate CPD or ethics example may be clearer than forcing every requirement into a single story.

How to choose your own evidence

Start with projects, incidents or improvements in which you had genuine autonomy. For each candidate example, write short answers to these prompts:

• What decision was mine?
• What engineering knowledge did I personally apply?
• What alternatives did I consider?
• What constraint or risk made the work difficult?
• Who did I influence or lead?
• What changed because of my work?
• Can I quantify the result?
• What did I learn or improve afterwards?

Then map each example against A-E. Do not begin by trying to write five polished statements from a blank page. Build an evidence bank first and select the examples that collectively show your breadth and current level of responsibility.

Your strongest evidence will usually be recent, but an older project can still be useful if it demonstrates an important competence not covered by your current role. Make the timing clear and show how your responsibility has developed since then.

Common mistakes in CEng competence statements

Writing “we” instead of explaining your contribution

Engineering is collaborative, so it is reasonable to provide team context. However, the assessor must be able to separate your decisions from the team's activity. Use “I” for your analysis, recommendations, actions and accountability.

Describing responsibilities instead of achievements

“I am responsible for design reviews” describes a job. “I changed the design-review process after identifying repeated interface failures, reducing late changes by 30%” demonstrates competence.

Naming tools without showing engineering judgement

Software is not evidence by itself. Explain why you selected the method, the assumptions and limitations you considered, how you validated the output and how it informed a decision.

Giving results without a baseline

“Improved reliability” is difficult to evaluate. “Increased mean time between failures from four to eleven months over the following two years” is much stronger. Where exact figures are confidential, use percentages, ranges or appropriately anonymised values.

Claiming leadership only through job title

A senior title does not automatically prove Competence C, and a junior title does not prevent you from demonstrating it. Show how you set direction, coordinated people, accepted accountability, resolved problems and improved future delivery.

Treating safety, sustainability and ethics as slogans

Referencing a policy or UN Sustainable Development Goal is not enough on its own. Explain the trade-off you assessed, the action you took and its effect.

Copying an exemplar

Assessors use the application as the basis for the Professional Review Interview. Text that does not reflect your own work is likely to fall apart under detailed questioning and may raise professional-conduct concerns. Use published exemplars to understand the expected level, never to replace your own evidence.

Final CEng application checklist

Before submitting each competence statement, ask:

• Does every example make my personal contribution clear?
• Have I explained why I chose the approach, not only what I did?
• Is there enough technical detail to demonstrate engineering judgement?
• Have I included constraints, alternatives and risks where relevant?
• Are results quantified or otherwise verified?
• Does the evidence reflect CEng-level complexity, innovation or responsibility?
• Have I covered all sub-competences rather than concentrating on my favourite area?
• Could I confidently answer detailed interview questions about every sentence?
• Is all information accurate, original and permitted by my employer?
• Has a suitable sponsor or mentor challenged weak or unsupported claims?

Turn your experience into evidence

The hardest part of a CEng application is often not a lack of experience. It is remembering the right examples and extracting the decisions, calculations and results that demonstrate competence.

CharteredPath's Evidence Gatherer asks structured questions about your own work and helps you organise the answers against UK-SPEC A-E. Treat the resulting draft as a starting point: check every fact, rewrite it in your natural voice and make sure you can defend it at interview.

Official sources and further reading

• IMechE Chartered Engineer overview and application process
• IMechE Chartered Engineer application guidance
• IMechE CEng competence statements exemplar
• IMechE UK-SPEC competence profiles and case studies
• Engineering Council Chartered Engineer requirements

CharteredPath is an independent educational tool and is not affiliated with or endorsed by the Institution of Mechanical Engineers or the Engineering Council. Always check the current official application form and guidance before applying.