Knowledge and Skill Base
Show your engineering foundation, technical knowledge, and understanding of engineering principles.
Summary Statement Review Guide for Engineers Australia CDR Submission
Review your Summary Statement before you finalise your CDR. Check competency links, Career Episode paragraph references, evidence strength, and document consistency. Use this guide to identify weak mapping, unclear claims, and unsupported links before submission.
Definition
What Is a Summary Statement?
A Summary Statement is the competency mapping document in a CDR submission. It shows where each Engineers Australia competency element appears in your Career Episodes. Use it to connect every claimed skill with clear paragraph evidence. Engineers Australia describes it as an overview of competencies demonstrated in Career Episodes, with elements mapped to specific paragraphs.
Engineering Application Ability
Show how you applied engineering methods, analysis, design, problem-solving, or technical judgement.
Professional and Personal Attributes
Show communication, ethics, teamwork, responsibility, safety awareness, and professional conduct.
Career Episode Paragraph Links
Connect each competency element with the exact paragraph where the evidence appears.
Before CDR Submission
Why Summary Statement Review Matters Before CDR Submission?
Summary Statement review helps you test the strength of your competency mapping before final submission. It checks whether each selected paragraph proves the exact skill claimed in the Summary Statement.
01
Evidence accuracy
Confirm that each paragraph reference supports the claimed competency with real engineering action.
02
Mapping clarity
Link each competency element to a Career Episode paragraph that is easy to find and understand.
03
Claim control
Remove claims that do not match your real role, task, or project responsibility.
04
Paragraph relevance
Avoid using paragraphs that only explain project background or general duties.
05
Assessment flow
Make the Summary Statement easy to follow from each claim to the correct project evidence.
1
Correct occupational category
Select the Summary Statement template that matches your nominated pathway. Use Professional Engineer, Engineering Technologist, Engineering Associate, or Engineering Manager correctly.
2
Complete competency element coverage
Address every required competency element in the selected template. Do not leave sections empty or partly mapped.
3
Exact Career Episode references
Add the correct Career Episode number and paragraph number for each competency element. Make every reference easy to trace.
4
Relevant engineering evidence
Choose paragraphs that show your own technical work, decisions, calculations, analysis, design, testing, or problem-solving.
5
Clear evidence summary
Write a short summary that explains how the selected paragraph demonstrates the competency. Keep the link direct and specific.
6
No unsupported project claims
Use only details already explained in your Career Episodes. Do not add new duties, outcomes, tools, or responsibilities.
Structure Review
How Is a Summary Statement Structured?
Use a clear table format to organise competency areas, evidence notes, and Career Episode locations. Keep each row easy to follow, so every element leads to the right project evidence.
Competency area
Group the elements under the correct competency area from your selected Engineers Australia category.
Competency element
Place each required element in its own row. Keep the wording aligned with the official template.
Evidence explanation
Write a brief explanation of the engineering action shown in the selected Career Episode paragraph.
Career Episode location
Add the episode number and paragraph number beside the matching competency element.
Table sequence
Follow the same order as the selected Summary Statement template. Do not rearrange elements randomly.
Empty row check
Review the table for blank rows before finalising the document. Every required element needs a mapped reference.
Competency Matching
How to Match Summary Statement Competencies With Career Episodes?
Match each competency by choosing Career Episode paragraphs that show the same engineering skill. Focus on evidence that proves your action, decision, method, or result clearly.
Start with the competency requirement
Read the competency element first. Understand the skill it asks for before choosing any paragraph.
Find action-based paragraphs
Select paragraphs where you explain what you designed, analysed, tested, calculated, solved, or decided.
Avoid background paragraphs
Do not use paragraphs that only describe the company, project scope, team, or general duties.
Check the evidence strength
Make sure the paragraph clearly proves the competency. Weak evidence can make the mapping unclear.
Use specific paragraph numbers
Add the exact Career Episode paragraph number. Do not use broad references or section names.
Keep one clear reason for each link
Explain why the selected paragraph fits the competency. Keep the reason short and direct.
Common Issues
Common Summary Statement Issues Found During Review
Find the common mistakes that make a Summary Statement hard to follow. Fix weak wording, unclear evidence, missing details, and poor paragraph links before final submission.
Vague evidence notes
Replace broad phrases with clear actions. Show what you analysed, designed, checked, tested, improved, or decided.
Copied template wording
Remove sample-style sentences that do not reflect your project. Keep the wording tied to your own engineering work.
Missing competency rows
Check every required row in the selected template. Add evidence notes where the table has blank or incomplete entries.
Overloaded paragraph links
Avoid using one paragraph for too many competency elements. Choose stronger evidence from different parts of your episodes.
Weak action verbs
Use action verbs that show engineering involvement. Avoid passive phrases that hide your role in the project.
Evidence outside Career Episodes
Do not map claims to information that only appears in your CV or supporting documents. Use Career Episode evidence first.
Review Process
How to Review a Summary Statement Step by Step?
Review the document in a clear order. Start with the correct template, check each competency row, trace every paragraph link, and clean the table before submission.
01
Confirm the engineering category
Check whether the Summary Statement uses the right category format before reviewing the content.
02
Read the competency element
Understand what each element asks for before selecting or checking any Career Episode reference.
03
Open the linked Career Episode paragraph
Read the exact paragraph listed in the table. Check whether it supports the claimed competency.
04
Check the evidence note
Make sure the note explains your action clearly. Avoid wording that only repeats the competency title.
05
Remove weak references
Replace links that only show project background, team details, or general job duties.
06
Review the final table
Check missing rows, wrong paragraph numbers, repeated links, unclear notes, and formatting issues.
Checklist
Summary Statement Review Checklist Before Submission
Use this checklist before you finalise the document. Check the template, evidence notes, paragraph numbers, category fit, and overall consistency.
✓
Correct template
Confirm that the document follows the Summary Statement format for your selected engineering category.
✓
Complete competency rows
Check every required competency element. Do not leave any row blank or partly completed.
✓
Accurate paragraph numbers
Match each reference with the exact Career Episode paragraph. Avoid wrong episode numbers or broad section references.
✓
Strong evidence notes
Keep each note clear and specific. Show the action, method, decision, or result linked to the competency.
✓
Consistent CDR details
Check that roles, project names, dates, tools, and outcomes match your Career Episodes.
✓
Clean final formatting
Review spacing, table alignment, spelling, grammar, and readability before saving the final version.
Documents
Documents to Prepare Before Summary Statement Review
Prepare the documents that prove each competency link. Use them to verify paragraph numbers, project roles, dates, evidence notes, and CDR consistency.
Career Episodes
Compare each mapped paragraph with the matching Career Episode. Check whether the paragraph shows the claimed engineering skill.
Summary Statement template
Use the template for your selected engineering category. Match every row with the required competency element.
Updated CV
Check job titles, employment dates, organisation names, and project roles against the Summary Statement claims.
CPD record
Review CPD entries that support your engineering knowledge, technical learning, and professional development history.
Project evidence
Check drawings, calculations, reports, test records, or design notes that support the Career Episode evidence.
Final CDR draft
Read the full CDR together. Confirm that projects, responsibilities, tools, and outcomes stay consistent across all documents.
Review Limits
What a Summary Statement Review Should Not Change?
Review the Summary Statement without changing the facts behind your CDR. Protect your real project details, duties, technical work, and results.
Project facts
Use the same project title, location, organisation, dates, and scope already shown in your Career Episodes.
Actual responsibilities
Mention only the tasks you handled personally. Do not include work completed by supervisors, teams, or other engineers.
Career Episode evidence
Connect each competency to evidence already written in your Career Episodes. Do not invent claims for stronger mapping.
Technical methods
Refer to the tools, standards, calculations, tests, and methods you actually used in the project.
Project outcomes
State the real project result. Avoid inflated savings, approvals, performance gains, or project impact.
Applicant voice
Write in a way that reflects your own engineering experience. Remove copied phrases from samples, templates, or online examples.
Review Your Summary Statement Before Final Submission
Check each paragraph link, evidence note, and category format before you finalise your CDR.
Ask a Summary Statement Question
FAQs
Summary Statement Review FAQs
Where should paragraph references appear in a Summary Statement?
Paragraph references should appear beside the matching competency element. Add the Career Episode number and paragraph number clearly. This helps the reader find the exact evidence without confusion.
What makes an evidence note strong?
An evidence note becomes strong when it explains the exact engineering action behind the competency. Mention the task, method, decision, or result. Keep the note short, but make the evidence clear.
Should Summary Statement wording match Career Episodes exactly?
Summary Statement wording should not copy Career Episode sentences exactly. Rewrite the same evidence in brief and simple words. Do not change the meaning or add new project details.
Can one Career Episode support several competency elements?
One Career Episode can support several competency elements when it has enough relevant evidence. Use separate paragraphs for different skills where possible. This makes the mapping clearer and easier to review.
What happens if a paragraph reference is wrong?
A wrong paragraph reference sends the reader to unrelated evidence. It makes the competency claim harder to verify. Check each number carefully before finalising the Summary Statement.
How detailed should each evidence note be?
Each evidence note should explain the point in one clear line. Include the action and the competency link. Avoid long explanations that repeat the full Career Episode.
Should you review the Summary Statement after editing Career Episodes?
You should review the Summary Statement again after editing Career Episodes. Paragraph numbers, wording, and evidence links may change. A final check helps prevent mismatched references.
Can supporting documents replace Career Episode references?
Supporting documents cannot replace Career Episode paragraph references. Use them only to support evidence already shown in the episodes. The Summary Statement should still point to the correct Career Episode paragraph.