If you’re preparing a Competency Demonstration Report, you’ve probably heard the same warning from every source: the Summary Statement for CDR is where most applications fall apart. It’s not a career overview; it’s a precise cross-reference table, and learning to build one correctly is arguably the single most important skill in the whole CDR process, because it’s the page an assessor uses to check, at a glance, whether you’ve actually proven what you claim.
This guide breaks the process down into a repeatable system, shows you the mistakes that trigger rejections, and gives you a practical checklist to follow before you submit.
What a Summary Statement for CDR Actually Is
Many applicants assume the Summary Statement is a short career summary, similar to a resume profile. It isn’t. According to Engineers Australia’s own migration guidance, “an overview of the competencies you’ve demonstrated in each of your career episodes” is exactly how the organisation itself describes this document; it is a cross-reference index, not a narrative.
In practice, a properly built Summary Statement for CDR is a table with three columns:
- The name of the competency element
- The paragraph number(s) in your Career Episodes where that element is demonstrated
- A brief note explaining how that paragraph proves the element
Writing it well is really a matching exercise, not a writing exercise. You are not creating new content here; you are pointing an assessor to evidence you’ve already written.
Why Your Summary Statement for CDR Matters So Much
Engineers Australia assesses applicants against a defined set of competency elements attached to each occupational category (Professional Engineer, Engineering Technologist, Engineering Associate, or Engineering Manager). Every element must be evidenced somewhere in your Career Episodes. As EA’s own preparation guidance puts it, applicants must be able to “demonstrate all 16 elements of competency at least once across your three career episodes.”
If even one element is missing, poorly matched, or only loosely implied, the assessor cannot verify it, and an unverifiable competency usually means a request for further information at best, or a rejected application at worst. This is exactly why a rushed Summary Statement for CDR is one of the most common reasons applications stall.
Step-by-Step: How to Build a Strong Summary Statement for CDR
Step 1: Get the Correct Competency Element List
Download the current Migration Skills Assessment (MSA) booklet and the Summary Statement template for your specific occupational category from the Engineers Australia website. Competency elements differ between Professional Engineer, Engineering Technologist, and Engineering Associate categories, so using the wrong list is a common and avoidable error.
Step 2: Number Every Paragraph in Your Career Episodes
Before you can write your Summary Statement, your three Career Episodes need sequential paragraph numbers (CE1.1, CE1.2, CE2.1, and so on). Engineers Australia’s own guidance confirms this is expected: applicants should demonstrate “all the competencies at least once somewhere in your three career episodes,” and numbering is what makes that traceable.
Step 3: Match Each Element to Specific Paragraphs
Go element by element, not paragraph by paragraph. For each competency element, ask: “Which specific paragraph shows me actually doing this?” Avoid vague statements like “demonstrated throughout the project.” Assessors want a precise paragraph reference, not a general impression.
Step 4: Write a One-Line Justification, Not a Summary
The third column of your table should explain how the referenced paragraph proves the element, in one clear sentence. Don’t restate the paragraph; interpret it. For example, “CE2.4 shows independent judgement in selecting a retaining wall design under site constraints” is stronger than simply repeating what happened in CE2.4.
Step 5: Cross-Check for Gaps and Duplicates
Once your table is complete, check two things:
- Every competency element has at least one paragraph reference.
- No single paragraph is being stretched to “prove” five unrelated elements; this is one of the fastest ways to raise assessor suspicion that the mapping is superficial.
Step 6: Verify Against the Occupational Category Template
Engineers Australia is explicit that applicants should “download and complete the relevant summary statement template for your occupational category” before submission. Using the correct, current template avoids formatting rejections that have nothing to do with the quality of your engineering evidence.
Common Mistakes in a Summary Statement for CDR
- Referencing the wrong paragraph type. Linking a safety-related competency element to a paragraph about budgeting or scheduling is a mismatch that assessors catch quickly.
- Copying career episode text into the summary table. The Summary Statement should analyse, not duplicate, your episodes.
- Leaving an element unmapped. Even one missing element can stall an otherwise strong application.
- Ignoring the specific indicators under each element. Elements often have sub-indicators; your paragraph should match the indicator, not just the general theme.
- Using an outdated template. EA updates its booklets and templates periodically; always check the current version before you finalise anything.
A Quick Example
Suppose the competency element is “PE2: Engineering Application Ability.” Instead of writing “I applied engineering knowledge throughout the project,” a properly mapped entry in your Summary Statement for CDR looks like this:
| Competency Element | Paragraph Reference | Justification |
| PE2.1 – Application of established engineering methods | CE1.6–CE1.8 | Applied AS/NZS structural load standards to redesign the beam support system |
That level of precision is what separates a Summary Statement that passes review from one that gets flagged for clarification.
Final Thoughts
Building a strong Summary Statement for CDR takes patience, but it’s a mechanical, learnable skill once you understand the logic: every claim needs a traceable, specific piece of evidence. Number your Career Episodes from the start, keep the correct occupational template on hand, and treat the Summary Statement as an index rather than a story.
If you’d rather have a second set of expert eyes check your work before you submit, CDRsample can review your Career Episodes and Summary Statement, flag mismatched or missing competency elements, and help you submit a CDR that’s ready for assessment the first time. Contact us today to get your Summary Statement for CDR reviewed before you send it to Engineers Australia.
Engineers Australia’s Migration Skills Assessment guidance and “Prepare your Migration Skills Assessment application” (engineersaustralia.org.au).
