Prepare for the EngTech Professional Review by practising one skill above all: converting routine technical tasks into first-person competence claims mapped to the recognised standard, each showing the technique applied, the problem solved, your personal responsibility, and the outcome. Contrast EngTech scope with IEng scope honestly, build a verifiable CPD record, and rehearse defending your claims aloud.
What the Professional Review actually asks you to demonstrate
The review assesses evidence of competence, commitment and ethical practice against the Engineering Council's standards, judged by your licensed institution. Your job is to show how your own work already meets each required area, not to study new technical theory.
The Engineering Council sets the standard for Engineering Technician registration, but assessment is carried out by a licensed professional engineering institution, so your first practical decision is which institution fits your sector. Registration is explicitly open to technicians from all routes into the profession, including apprenticeships and work-based learning, which means your evidence comes from practice rather than from a syllabus.
The review areas for EngTech cover engineering knowledge, designing solutions to practical problems, technical and commercial management, interpersonal and communication skills, professional standards and ethical practice, and personal commitment to professional development. Treat these as six lenses on work you have already done. Before writing anything, sort your recent projects and responsibilities under these headings; any area left thin shows you where you need to seek experience, not where you need to memorise content.
EngTech versus IEng: getting the scope of your claims right
EngTech recognises the application of proven techniques and procedures to practical problems; IEng recognises broader use and adaptation of engineering technology. Your claims must sit honestly in the EngTech scope, because assessors will probe any overreach.
This distinction shapes every sentence you write. An EngTech claim centres on doing things properly with established methods: following a maintenance procedure, producing accurate survey data, setting out work, testing to a specification, or supporting a design with well-understood tools. An IEng claim would involve selecting and adapting technologies more autonomously across a wider scope. Claiming IEng-style leadership or novel design work under an EngTech application creates a mismatch an assessor can question line by line.
Getting this right does not mean understating yourself. If you improved a process, that can be EngTech evidence when you describe the proven technique you applied and your responsibility for its outcome. The comparison below gives you wording patterns. Use it as a calibration tool when drafting: if a draft claim reads like the right-hand column, either reframe it around your hands-on contribution or move that experience aside and build the claim from work you genuinely owned.
| Aspect | EngTech claim pattern | IEng-style claim (avoid in this application) |
|---|---|---|
| Core role | Applies proven techniques and procedures to solve practical problems | Exercises independent engineering judgement across varied technologies |
| Typical evidence | Fault diagnosis, testing to specification, setting out, quality checks, safe systems of work | Leading design development, technical strategy, novel solutions |
| Wording example | I applied the standard calibration procedure to trace and correct a recurring measurement error | I designed a new measurement system and set the technical approach for the team |
| Responsibility shown | For the quality and safety of your own work and its effect on the task | For wider technical decisions made by others |
| Review focus | Reliable, safe, effective execution with sound engineering reasoning | Technical leadership and broader engineering judgement |
Writing a competence claim that survives assessor scrutiny
A strong claim names the competence area, states the practical problem, identifies the proven technique you applied, and closes with the outcome and your personal responsibility. Vague task lists cannot be probed; specific claims can.
Compare two phrasings. A task list says: responsible for routine maintenance on production equipment. A competence claim says: when a packaging line stopped repeatedly, I applied the manufacturer's diagnostic sequence to isolate a sensor alignment fault, corrected it within the shift plan, and updated the checklist so the fault was caught earlier. The second version gives an assessor four things to explore: the problem, the method, your action, and the consequence.
Write each claim in the first person with an active verb, and include enough context for someone outside your company to follow it. Explain one abbreviation the first time it appears. Where you worked under supervision, say so plainly and describe what you were responsible for within that supervision; honesty about boundaries is itself evidence of professional standards. Aim for a small number of well-chosen examples that collectively cover all areas rather than a long inventory of tasks.
Worked scenario: the maintenance technician's flat claim
A maintenance technician drafts generic upkeep statements for a CNC cell. The better application picks one diagnostic episode, explains the proven procedure applied, and shows ownership of the fix and its prevention.
The mistake: the draft reads, I carry out planned and reactive maintenance on CNC machines and keep them running. Every phrase is a task, so the assessor has nothing to test against engineering knowledge, safety, or communication. When probed, the technician cannot point to what was personally decided, and the claim reads as attendance rather than competence.
The better decision: rewrite around one episode. A recurring alarm on one machine was causing unplanned stoppages; I worked through the manufacturer's fault-finding sequence, ruled out the drive, identified a degraded sensor cable, replaced it to the current standard, and added the cable check to the planned maintenance routine, cutting repeat alarms. This shows applying a proven technique, diagnosing within a defined procedure, taking responsibility for quality and safety, and improving practice. It matters because it converts the same job into testable evidence of the standard.
Worked scenario: claiming design work you only supported
A drawing-office technician drafts a claim of designing site drainage layouts. The honest reframing describes producing and checking setting-out data under supervision, which is solid EngTech evidence; the inflated claim is not.
The mistake: wanting the design and development area to look impressive, the technician writes that she designs drainage arrangements for small sites. In the review conversation she is asked about the hydraulic assumptions and cannot answer, because the engineer made those decisions. The claim collapses, and the collapse casts doubt on her other claims too.
The better decision: she reframes truthfully. Working to the engineer's design, she produced the setting-out drawings, ran established checks for clashes and levels, flagged a manhole location that conflicted with an existing service, and corrected the drawing before issue. This still evidences design support and development, communication, professional standards, and quality of her own work. The lesson is scope honesty: describe the decision boundary precisely, and claim full credit for everything inside it rather than borrowing credit from the engineer's decisions.
Proving personal commitment: CPD and ethics you can evidence
Personal commitment is demonstrated through a maintained record of continuing professional development and through concrete ethical practice at work. Both must be evidenced with dates, reflection, and application, not aspirations.
Build a CPD record with a simple repeating structure: what you did, why you chose it, what you learned, and how you applied it. Training courses count, but so do structured reading, supplier briefings, learning a new test method, and mentored practice. A record that lists a course title alone is weak; a line that says you attended a briefing on an updated wiring standard, then rewrote your inspection sheet to match, shows learning converted into practice.
Ethical practice evidence should come from situations you actually faced. Useful examples include following a safe system of work when a deadline made shortcuts tempting, escalating a quality concern rather than passing it on, respecting confidentiality in drawings or data, and declaring the limits of your competence when asked to do something beyond them. If your history feels thin here, the constructive response is to seek such situations deliberately, for example by volunteering for quality or safety reviews, and then record what you did.
A preparation sequence with a claim-rewriting exercise and readiness checks
Prepare in three passes: map your work to the standard, draft and rewrite claims, then rehearse defending them aloud. Use the rubric below as your own quality gate before you submit anything to your institution.
A workable sequence: in the first two weeks, keep a work diary and tag every task with the competence area it evidences. In weeks three and four, draft two or three claims per area using the problem-method-action-outcome structure from the scenarios. Next, assemble your CPD record into the same structure and agree on examples with your sponsor or referee, since their endorsement must match your evidence. Finally, rehearse a mock review: a colleague picks any claim and asks why you chose that method, what could have gone wrong, and what you would change.
Exercise: take five bullets from your job description and rewrite each as a competence claim. Score each rewrite 0 to 2 on four checks: it names a specific competence area, it identifies the proven technique or procedure applied, it shows your personal responsibility including any supervision boundary, and it states a concrete outcome. A rewrite scoring 7 or 8 out of 8 is ready to draft into your application; anything below, identify which element is missing and redraft. These scores are learning milestones to guide your drafting, not a prediction of any review outcome, and administrative details such as process steps and current requirements should be confirmed with your chosen licensed institution via the Engineering Council's professional registration pages.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.