How to Write a Career Episode That Demonstrates Competency

Most weak reports are weak because of project selection, not writing. You cannot write competency evidence about a project where you had none.

Work backwards from the standard. You need three episodes that between them cover sixteen competency elements, and the four PE2 application elements carry the most weight. So look for projects where you can point to:

• A calculation you performed and the number it produced
• A standard or code you selected and applied
• A decision that followed from the number
• A consequence — what changed because of what you found

A useful shape for the three: one design episode, one problem-solving episode, and one project or interface management episode. That spread naturally covers knowledge, application and professional attributes without forcing anything.

Your final-year university project is legitimate for one of the three, and for applicants whose entire career has been construction, operations or maintenance it is often the only place a genuine design sits. It should not be all three.

The proportions matter. If Background runs to 900 words and Personal Engineering Activity to 500, you have written a project report with a paragraph about yourself at the end. Assessors see this constantly.

Paragraphs are numbered continuously within each episode — 1.1, 1.2, 1.3 in the first, 2.1 onward in the second — because your summary statement cites those exact numbers.

Here is the same work written two ways.

Before: "The project involved the design of a 12-storey commercial building. The design team used ETABS to model the structure and the design was completed in accordance with the relevant Australian standards. I was responsible for assisting with the structural analysis."

After: "I developed the ETABS model for the 12-storey moment frame and applied the load combinations from AS/NZS 1170.0. My analysis returned an inter-storey drift of 1/380 under serviceability wind, which exceeded the 1/500 limit I had adopted from the client's brief. I proposed relocating two columns to shorten the 11.4 m span, hand-checked the revised drift using a portal-frame approximation, and confirmed 1/620 in the updated model. The change was adopted at the design review."

Same project. Similar length. The second paragraph evidences PE1.1 (structural theory applied), PE2.1 (a method chosen and applied), PE2.2 (software checked against a hand calculation) and PE2.3 (options considered, one selected, design changed). The first evidences nothing at all.

The test: could a colleague who worked on the same project have written this sentence? If yes, it is describing the project. If only you could have written it, it is evidencing competency.

This is half your word count and all of your evidence. A structure that works, repeated three or four times per episode:

1. The problem or task — specific, with the constraint that made it non-trivial
2. What you chose to do — the method, and why that one
3. What you found — the number, the result, the measurement
4. What you decided — and what changed as a consequence

Four such passages fill 1,200 words comfortably and produce twelve to sixteen referenceable paragraphs. That is enough to carry a summary statement.

Things to include that applicants routinely omit: a standard you researched because it was unfamiliar (PE1.4), a sustainability or safety constraint that changed your design (PE1.6), a decision you made that cost the project something (PE3.1), and a technical point you had to explain to a non-engineer (PE3.2).

• First person singular. "I", not "we". This is the single most common failure. Competency is awarded to a person, and an assessor cannot award PE2.3 to a design team.
• 1,000–2,500 words. Under reads as thin; over buries the evidence.
• Numbered paragraphs, continuous within the episode. Without them the summary statement cannot reference anything.
• Three distinct episodes. Different projects, roles or periods — not three angles on one job.
• At least one design episode. PE2.3 is the element most often left unevidenced.
• Your own words. Every submission is text-matched against published samples and Engineers Australia's archive of prior applications. A match can mean a ban of up to twelve months.

The full set is in the MSA booklet, which is the document your assessor actually works from.

Defence projects, commercially sensitive process data, client information under NDA — many engineers have material they cannot disclose.

You can almost always write a strong episode anyway, because the evidence an assessor wants is the engineering reasoning, not the commercial detail. Practical approaches:

• Anonymise the client and the site — "a mineral processing facility in the north-west" rather than naming it
• Use relative figures where absolutes are restricted — "throughput improved 18%" rather than the tonnage
• Describe the method and the constraint fully, since those are rarely the confidential part
• Check your employment contract and, where it matters, ask your employer

What you should not do is drop the engineering because the numbers are sensitive. An episode with no numbers reads as an episode with no engineering, and the assessor cannot tell the difference between discretion and absence.

• Is it between 1,000 and 2,500 words?
• Are the paragraphs numbered continuously within this episode?
• Is the Personal Engineering Activity section roughly half the total?
• Does every technical paragraph contain a number, a standard, or a decision?
• Is it written in the first person singular throughout — no "we", no "the team"?
• Could a colleague on the same project have written any given sentence? If yes, rewrite it.
• Does it cover competency elements that the other two episodes do not?
• Is there at least one design somewhere across the three?
• Does the organisational chart show your actual position?
• Have you kept a note of which paragraph numbers evidence which elements, ready for the summary statement?

That last point saves the most time. Recording element-to-paragraph mappings as you draft turns the summary statement into a transcription exercise rather than a re-reading exercise — and it is what prevents the broken references that assessors check for.