Your three career episodes are drafted and every paragraph is numbered. Now you are looking at an empty summary statement table, unsure whether "CE2, Background" counts as a reference and which paragraph actually proves PE3.4. This Engineers Australia summary statement mapping guide covers that single step: matching specific paragraphs to each of the 16 Stage 1 Professional Engineer competency elements, writing an entry an assessor will accept, and avoiding the three mapping patterns that most reliably trigger an additional information request.
What the Summary Statement Mapping Table Proves
Before reading a word of your episodes, an assessor opens your summary statement and uses it as an index: read the element, jump to the paragraph you named, check whether those lines genuinely demonstrate the competency. Each row is a promise verified on its own. A strong project buried under a vague reference still fails the row.
How assessors cross-reference each row
Take PE2.3, which the standard describes as the application of systematic engineering synthesis and design processes. The assessor reads your cited paragraphs and asks one question: do these lines show design synthesis, or do they only describe a project? Paragraphs that set context without demonstrating the competency fail the row even when the underlying work was excellent. The reference you choose matters as much as the work you did.
The 16 Stage 1 elements you must cover
The Professional Engineer standard splits into three groups: PE1 Knowledge and Skill Base (PE1.1, PE1.2, PE1.3), PE2 Engineering Application Ability (PE2.1, PE2.2, PE2.3, PE2.4, PE2.5, PE2.6), and PE3 Professional and Personal Attributes (PE3.1, PE3.2, PE3.3, PE3.4, PE3.5, PE3.6, PE3.7). All 16 must be addressed in at least one career episode. None may be left blank, and none can be satisfied by a CPD list entry in place of a paragraph reference.
What to Have Ready Before You Map
Two things sit upstream of a clean table, and skipping either is why applicants stall halfway through.
The MSA booklet sets the words you must match
Open the Migration Skills Assessment (MSA) booklet for your occupational category and read the exact wording of every element before writing a single justification. Your justification column has to echo that wording. Assessors match your language to the standard's language, so the booklet is the authoritative source for element descriptions, not a competitor's blog. If the booklet frames an element around specific terms, carry those terms in your entry rather than a paraphrase you invented from a sample site.
Numbering your paragraphs first
Number every paragraph in all three career episodes sequentially before you open the table. The mapping cites paragraph ranges, so the numbers have to exist first. If you have not done this yet, our career episode guide covers the numbering convention EA expects. Renumber nothing once you start mapping, or every reference you wrote will point to the wrong line.
A Valid Entry Versus a Section-Level Citation
Every mapping entry has four components: the element code, the career episode number, the paragraph range, and a one-sentence justification in the element's own vocabulary. Miss any of the four and the row is incomplete.
Here is one row done correctly:
PE2.1 → CE2 → paras 14-17 → "Selected and justified the foundation design method for the site's load and settlement constraints, applying established engineering methods to a defined problem."
Now the same row done poorly:
PE2.1 → CE2 → "Design section" → "Shows engineering application."
Two failures in the second entry: it cites a section title instead of a numbered range, and the justification restates the element name rather than pointing to evidence. An assessor cannot navigate "Design section" to a specific paragraph, so they cannot verify the claim. Citing a heading rather than paras 14-17 is the most common cause of a formal information request.
Mapping PE1: Knowledge and Skill Base
PE1 is where applicants over-map, because knowledge feels easy to claim. The trap is citing paragraphs that describe a technology rather than paragraphs where you applied it.
Demonstrated knowledge versus background description
"The plant used a SCADA system for real-time monitoring" is background. "I calculated the control loop tuning parameters and set the sampling rate to keep the process stable" is demonstrated knowledge. PE1.1 and PE1.2 want the second kind: fundamentals applied to a defined problem, methods selected on purpose, results interpreted. If a cited paragraph would still make sense in an encyclopaedia entry about the technology, it is background and will not carry a PE1 element.
When your work spans two disciplines
Multi-disciplinary work helps PE1 mapping rather than complicating it. Map each PE1 element to the episode where the underlying knowledge is most explicit. A mechanical engineer who did structural analysis on one project and thermal design on another should cite whichever paragraph shows the deeper reasoning, not spread thin references across both. Depth in one paragraph beats a scattered pair.
Mapping PE2: Engineering Application Ability
Six elements, the heaviest lifting in the standard. Assessors on PE2 prioritise engineering judgement, decisions you can defend, and outcomes you can attribute to yourself rather than to the team.
The paragraph choice that fails PE2
The failure pattern is citing a paragraph that reports what the project delivered instead of what you decided. "The bridge was completed on schedule" is an outcome with no engineering in it. "I compared two girder configurations, ran the load cases, and chose the composite option to meet the deflection limit" is engineering application. When mapping PE2.1 through PE2.6, hunt for the verbs: selected, compared, calculated, resolved, verified. A paragraph without a decision rarely holds a PE2 element.
Covering several PE2 elements from one episode
One rich design episode can legitimately carry several PE2 elements, but give each element its own paragraph range rather than pointing all six at the same four paragraphs. PE2.1 might sit in paras 14-17, PE2.2 in paras 18-20, PE2.6 in the paragraph where you documented and handed over the design. Duplicated paragraph references across PE2 mappings are a listed red flag, because they suggest one thin episode stretched to look complete.
Mapping PE3: Professional and Personal Attributes
Most information requests originate here. PE3's seven elements cover professional identity, ethics, communication, creative problem-solving, teamwork, lifelong learning, and project management, and none of those labels appear in a technical narrative. The evidence exists in your episodes. Finding it requires knowing which element lives in which kind of sentence.
The two PE3 elements left blank most often
In the CDRs we review, PE3.4 (professional and ethical responsibilities) and PE3.6 (lifelong learning) go unmapped more than any others. Applicants assume they never wrote about ethics or self-directed learning, when in fact the evidence is already in the narrative: the paragraph where you followed a code or standard, refused an unsafe shortcut, or taught yourself a method the project demanded. Those lines map to PE3.4 and PE3.6 directly.
Referencing evidence buried in the narrative
PE3 evidence hides inside paragraphs written about something else. A sentence about coordinating with the client and contractor to resolve a design clash carries PE3.2 (effective oral and written communication) and PE3.5 (team functioning), even though the paragraph is nominally about a change order. Map the range that contains the behaviour, and in the justification name the attribute explicitly: "coordinated across three stakeholder groups to resolve the interface conflict, demonstrating communication and multidisciplinary team functioning." You are directing the assessor to evidence they would otherwise read past.
Three more PE3 elements deserve specific attention:
PE3.1 covers professional identity and conduct within the engineering team and broader community. Look for the paragraph where you operated as the responsible engineer on a deliverable, chaired a technical review, or represented the project to an external body. The evidence is usually one or two sentences inside a longer paragraph about a milestone.
PE3.3 covers creative and innovative thinking applied to an engineering problem. The paragraph you want is not necessarily your most complex one. It is the one where you identified that the standard approach would not work and proposed something different: a modified test method, an alternative material, an unconventional sequencing decision. Those lines demonstrate creative problem-solving more clearly than a paragraph about a textbook design.
PE3.7 covers project and asset management. If any of your episodes involved scheduling, resource allocation, risk registers, or scope control, those paragraphs satisfy PE3.7. Engineers who worked as designers rather than project managers often have a paragraph buried in their CE where they coordinated subcontractor deliverables or tracked a critical path item. That is enough.
When One Paragraph Fits Many Elements, or None
Two situations stall applicants at the finish line: a paragraph that seems to prove everything, and an element that nothing proves.
One paragraph across several elements
The same paragraph can legitimately support more than one element, and assessors expect some overlap. A paragraph describing a design decision made under a safety code can serve a PE2 element and PE3.4 simultaneously. The practical ceiling is four to five elements per paragraph. Beyond that, the same reference appearing in six, seven, or eight rows tells the assessor your episodes lack the depth to spread evidence across distinct paragraphs, which invites scrutiny rather than saving effort.
An element with no strong match
Do not cite a weak paragraph and hope the assessor overlooks the mismatch. Three real options exist before submission. First, revisit the relevant episode and expand the paragraph where the competency is closest to the surface, making the evidence explicit; this is permitted because you are clarifying work you actually did. Second, add a paragraph documenting genuine work that went unrecorded in the original draft. Third, if the competency is genuinely absent from all three episodes, consider replacing a weak episode with a project that demonstrates it. A CPD entry cannot substitute for a paragraph reference, and a blank row will generate a request.
Three Patterns That Trigger an Information Request
An additional information request extends your processing time and signals to the assessor that your CDR needs closer examination. Three mapping habits cause most of them.
A title instead of a paragraph range
Citing "CE1 Background" or "CE1, Design section" instead of "CE1, paras 8-11" is the single most reliable trigger. A section title gives the assessor no line to verify, so they cannot confirm the competency and must ask you to specify. Always cite a numbered range.
One paragraph stretched across eight elements
Mapping the same paragraph to eight or more elements signals that your three episodes do not hold enough distinct engineering evidence to cover 16 competencies. Assessors read heavy over-mapping as thin content, and thin content draws a request for clarification or additional evidence.
Every PE3 field left blank
A summary statement with populated PE1 and PE2 rows and empty PE3 rows is an immediate flag. The standard requires all 16 elements addressed. Blank PE3 fields read as an incomplete assessment, not a modest applicant, and they reliably generate a request.
Where Mapping Weakness Clusters by Discipline
Across the CDRs we review, weak mapping is not random; it follows discipline lines. This is our own observation from reviewing summary statements, not a published EA figure, but the pattern is consistent enough to plan around.
Software engineers map PE1 and PE2 strongly and under-map PE3, especially PE3.4, because their episodes rarely reference codes, standards, or regulatory context that demonstrates ethical and professional responsibility. Civil engineers usually cover PE1 and PE2 well and lose ground on PE3.2 communication, because their narratives describe structures rather than the stakeholder coordination they actually performed. Mechanical engineers tend to be strong on PE2 design synthesis and thin on PE3.6 lifelong learning, since self-directed skill acquisition gets compressed out of results-focused writing. Knowing your discipline's blind spot tells you which rows to check first.
A Final Check Before You Submit to Engineers Australia
Before you submit, run these checks:
Every one of the 16 elements has at least one entry. No blank rows, PE3 included.
Every entry cites a paragraph range, such as CE2, paras 14-17, never a section or episode title.
No single paragraph appears in more than four or five rows.
Every justification uses the element's own wording from the MSA booklet and names the specific evidence, not a restatement of the element.
Cross-check the whole table against the skills assessment criteria and your submission checklist so the mapping lines up with the rest of your CDR.
FAQs
Can one paragraph be cited for more than one competency element?
Yes. One paragraph can legitimately support several elements, and assessors expect some overlap. Keep it to roughly four or five elements per paragraph. Beyond that, the repetition signals that your episodes lack the depth to demonstrate 16 competencies across distinct paragraphs.
What if no career episode demonstrates a specific PE element?
You cannot leave it blank. Expand the paragraph where the work is closest so the competency becomes explicit, add a paragraph documenting work you did but never wrote up, or replace a weak episode with a project that demonstrates the element. A CPD activity cannot fill the gap in the mapping table.
Is one paragraph reference per element enough?
One well-chosen paragraph range that clearly demonstrates the element is enough. Assessors value a precise, verifiable reference over a long list of loosely related ones. Add a second range only when a single paragraph does not fully cover the element.
Does the format differ for Engineering Technologist applicants?
The four-component entry format is the same, but the competency set differs. This guide maps the Professional Engineer Stage 1 elements (PE1 to PE3). Engineering Technologist applicants map to the ET competencies instead, so pull the element list for your own category from the MSA booklet before you start.
Can I cite CPD activities instead of paragraphs for PE3?
No. The mapping table accepts only career episode paragraph references. Your CPD list is a separate document and cannot demonstrate a PE3 attribute in the summary statement. Every PE3 row must point to a numbered paragraph in one of your three episodes.
Not sure your mapping covers every required element? Our summary statement review flags gaps and weak paragraph references before you submit, so you find the problems an assessor would while you can still fix them.