The Summary Statement is the section where your Career Episode evidence is connected to Engineers Australia competency elements. It looks simple, but weak paragraph references, repeated evidence and generic mapping can reduce the strength of an otherwise good CDR. This guide explains how to map competencies clearly, accurately and professionally.
Use this guide after drafting your Career Episodes and before finalising your Summary Statement.
Good mapping is not about filling rows quickly. It is about proving each competency with the best paragraph evidence available in your Career Episodes.
The Summary Statement is a competency-mapping table. It does not repeat the full Career Episode story. Its job is to show where each competency element has been demonstrated in your numbered Career Episode paragraphs. The assessor should be able to go from the Summary Statement to the exact paragraph and immediately see the evidence.
The Summary Statement is a roadmap to your evidence, not a separate essay.Do not map paragraphs only because they sound technical. First read the wording of the competency element. Then ask what kind of evidence the element needs. Some elements need engineering knowledge, some need design or problem-solving, some need communication, ethics, safety, teamwork or professional judgement. Select the paragraph that proves that specific requirement.
Match the evidence to the element, not the element to random evidence.Your Career Episodes should be numbered clearly, such as C.E.1.1, C.E.1.2 and C.E.1.3. In the Summary Statement, use exact references instead of broad ranges. A reference like C.E.2.8 is much stronger than a vague reference to the entire episode because it directs the assessor to a precise piece of evidence.
Exact paragraph references make the report easier to assess.Introduction and background paragraphs usually explain the project title, dates, organisation, team structure or project context. They rarely prove engineering competency by themselves. The strongest references normally come from the personal engineering activity section where you explain calculations, design decisions, analysis, testing, troubleshooting, standards, drawings, software tools, safety checks or quality control.
Choose paragraphs where you personally performed engineering work.A single Career Episode may contain several useful paragraphs, but not all evidence has equal value. If two paragraphs could support the same element, choose the paragraph with clearer technical detail and stronger personal contribution. A paragraph that says “I participated in the design” is weaker than one that explains what you calculated, compared, selected and verified.
Prefer specific engineering action over general participation.If most rows refer to only one Career Episode, the assessor may feel that the other episodes are weak or poorly used. You do not need equal references from every episode, but the Summary Statement should show a balanced professional profile. Use all three episodes where possible so your academic, project and professional experience support the competency framework together.
A balanced Summary Statement makes the whole CDR look stronger.One paragraph can sometimes support more than one element, especially if it contains design, analysis, communication and problem-solving evidence. However, repeating the same paragraph too many times can look like forced mapping. If one paragraph appears again and again, review your Career Episodes and add clearer evidence in other sections where needed.
Repeated references should be logical, not used as fillers.The Summary Statement must match your Career Episodes, resume, dates, roles and project titles. If a paragraph reference points to the wrong episode, wrong project or wrong activity, it can create confusion. After editing your Career Episodes, recheck all Summary Statement references because paragraph numbers may change during revision.
Final mapping should be checked after the final Career Episode edit.Before submission, review the Summary Statement row by row. Open the referenced paragraph and ask: does this paragraph clearly prove the competency element? Is the evidence personal? Is it technical where required? Is the reference exact? If the answer is weak, replace the reference or strengthen the Career Episode paragraph.
Every mapped reference should survive a direct evidence check.Points to a paragraph where you performed a clear engineering task, decision, calculation, design check or analysis.
Points only to project background, team description, organisation details or a general project objective.
Uses personal actions such as I designed, I calculated, I analysed, I selected, I tested and I verified.
Uses vague phrases such as the team completed, the project was done or I was involved without explaining your role.
Checks that every competency element has relevant, exact and defensible paragraph evidence.
Do not try to impress the assessor by adding too many paragraph references. Select the clearest evidence, keep the mapping accurate and make sure every reference leads to a paragraph that proves the competency element. Precision is stronger than volume.
● Typically replies within minutes