Writing a Summary Statement That Survives Paragraph-Level Checking

The summary statement is not a summary of your career. It is a navigation instrument, and it is the first thing an assessor opens.

They read your claim — "PE2.3 is demonstrated at paragraphs 1.7, 2.11 and 3.4" — turn to those paragraphs, and decide whether they support it. Then the next element, and the next, through all sixteen.

Two failure modes follow directly from that reading order.

A reference pointing at a paragraph that does not demonstrate the element reads as padding. One might be carelessness. Several read as a report where the mapping was invented after the writing, which invites scrutiny of everything else.

An element with no reference at all is an outright gap, and gaps are a direct route to a negative or deferred outcome.

Material your summary statement never cites contributes nothing. A brilliant paragraph in episode two that no element points to may as well not be there.

Three columns: the element and its code, a brief description of how it was demonstrated, and the paragraph references.

Three rules govern it:

• Paragraph numbers, never page numbers. This is why the MSA booklet requires continuous paragraph numbering within each episode — without it the statement cannot function.
• Use the prefix matching your category — PE, ET or EA. PE labels in an Engineering Technologist application signal you wrote to the wrong standard.
• Describe, do not assert. "Demonstrated excellent design skills" is not a description of how. Name what you did.

Typical length is three to five pages. Length matters far less than whether every element is covered and every reference holds.

This is a mechanical check and it is worth doing properly, because it is exactly what the assessor will do.

Take each row. Open the paragraph it cites. Ask a single question: if I had only this paragraph, would it convince me this element is demonstrated?

Three common failures:

• The paragraph is adjacent to the evidence, not the evidence. You cited 1.7 because the calculation is in 1.8. Cite 1.8.
• The paragraph demonstrates a different element. Genuine engineering content, mapped to the wrong row.
• The paragraph is generic. "I worked closely with the design team" cited for PE3.6. It says a team existed, not that you were effective in it.

Do this for all sixteen rows before submission. It takes an hour and it removes the most checkable reason for a negative outcome.

PE2.3 is the one that fails reports. If none of your three episodes contains a design you personally developed — from requirement through options to detail — find one before submitting. It does not need to be large. It needs to be yours.

All sixteen elements and the evidence each accepts are in the Stage 1 competencies guide.

You have finished three episodes and a gap appears. The instinct is to rewrite an episode. Usually you do not need to.

First, re-read for evidence already present. Gaps are frequently gaps in the mapping, not in the work. The ethical decision is in your episode; you simply never labelled it PE3.1.

Second, add a paragraph rather than a section. Most elements can be evidenced in 80 to 150 words placed where the work naturally sits. A single paragraph about the standard you researched, inserted at the point you researched it, closes PE1.4 without disturbing anything around it.

Third, check your word count has room. Episodes run 1,000 to 2,500 words. An episode at 1,600 has space for three added paragraphs; one at 2,450 does not, and something has to be trimmed.

Only rewrite if the project genuinely lacks the content. If an element requires design and the project had none, no amount of rewriting will produce it — you need a different project.

Nearly every broken summary statement is a retrofitted one. The writer finished three episodes, then went hunting for paragraphs to satisfy sixteen rows, and pointed at the nearest plausible candidate.

The alternative costs nothing. Before drafting, build a grid: sixteen rows, three columns, one per episode. Mark which episode will carry which element. Then, as you write, record the paragraph number against each element the moment you write it.

Two benefits. The summary statement becomes a transcription exercise rather than an investigation. And gaps surface at the planning stage, where moving an element between episodes costs a minute instead of a rewrite.

If your episodes are already written and you want to know where you stand, our CDR review audits coverage element by element and verifies every reference against the paragraph it points at — which is the same check an assessor performs, done before the fee is spent.

The pattern is easier to see than to describe.

The claim: PE2.2 — Fluent application of engineering techniques, tools and resources — 1.9

Paragraph 1.9: "I used ETABS to model the structure and the results confirmed the design was adequate for the applied loads."

An assessor reads that and finds software named, not judgement demonstrated. There is no indication you understood what the model was doing or whether you would have noticed if it were wrong.

The paragraph, rewritten: "I built the ETABS model and cross-checked the base shear it returned, 1,840 kN, against a hand calculation using the equivalent static method from AS 1170.4, which gave 1,790 kN. The 3% difference confirmed the mass distribution in the model was correct. Had the discrepancy exceeded 10% I would have re-examined the diaphragm assumptions before trusting the output."

Same task, same software. The second version shows a tool used with judgement, an independent check, and a stated threshold for distrusting the result — which is precisely what "fluent application" means in the standard.

Do this check on every reference. Where the paragraph does not carry the element, fix the paragraph rather than moving the reference.