Evidence Is Easy to Find
Clear sections separate context, role, technical activity, and outcome, so an assessor can locate each competency without hunting through the text.
Career Episode Structure Checker
Paste your Career Episode and get a full structural read in seconds, covering word count, first person language, paragraph numbering, passive voice, and Engineers Australia section structure, all before you submit your CDR.
100% private, runs in your browser
Instant structural analysis
Free, no sign up needed
Analyse Your Career Episode in Seconds
Add up to three Career Episodes, paste your text in full or section by section, then run a detailed structural review against EA compliance checks.
Career Episodes
Build and analyse each episode. Everything runs privately in your browser.
How the episode tabs work
Each Career Episode is analysed on its own and never combined. Add up to three episodes using the tabs. Select an episode, then click Analyse to see that episode's result. Switching tabs hides the current result, so analyse each episode separately to review its individual score.
Nothing is uploaded. All checks run locally in your browser.
Career Episode 1 Analysis
N/A
Readiness Breakdown
Weighted across five assessment dimensionsIssues & Recommendations
This tool checks measurable structural properties. It does not assess engineering content quality, competency depth, or originality. Always have your complete CDR reviewed by an expert before submission.
How the Career Episode Checker Works
The checker reads your text the way an assessor scans structure. It measures each requirement, scores five readiness dimensions, and lists exactly what to fix before you map your Summary Statement.
- 01
Add Your Episodes
Work on up to three Career Episodes in one place. Each one is analysed on its own and never mixed with the others.
- 02
Paste Full or by Section
Drop in the whole episode, or fill the Introduction, Background, Personal Engineering Activity, and Summary one section at a time.
- 03
Run the Structural Analysis
The tool checks word count, first person density, team pronouns, numbered paragraphs, passive voice, and section coverage.
- 04
Read Your Readiness Score
See a weighted score across five dimensions, a clear metric grid, and a ranked list of issues to fix first.
- 05
Prepare Your Summary Statement
Strong evidence paragraphs are surfaced with suggested competency elements, ready for your Summary Statement mapping.
Not Sure Your Career Episode Is Ready?
Open with the project title, dates, duration, location, employer, and your position. Assessors need this context before any technical detail begins.
State the project objective, the engineering context, and your assigned duties. Leave out long company history that adds no engineering value.
This is the largest section. Write in first person and show what you analysed, designed, calculated, tested, and decided. Replace we and the team with I.
Number your paragraphs in order, such as 1.1, 1.2 and 1.3 for Episode 1. The Summary Statement cross references these numbers, so gaps make mapping impossible.
Back your decisions with calculations, standards, tools, and measurable results. Numbers and codes turn description into evidence an assessor can trust.
End with your personal contribution, the project outcome, and the competencies you demonstrated. Keep it specific rather than a general reflection.
Why It Matters
Why Career Episode Structure Matters
A well structured Career Episode lets assessors find your competency evidence quickly and lets you map it cleanly into the Summary Statement. Weak structure hides good engineering and slows your assessment.
Your Role Stands Out
First person writing keeps you at the centre of the work. Assessors reward a clear personal contribution over a team narrative.
Summary Statement Mapping
Numbered paragraphs let you point each competency element to the exact place the evidence appears, which is required for a valid Summary Statement.
Depth Proves Competency
Structure makes room for calculations, standards, tools, and design decisions, which is the technical depth that demonstrates real engineering.
Fewer Reasons to Reject
A systematic layout exposes missing details early, so you fix gaps before submission instead of after a negative outcome.
Who Gets the Most Out of This Checker?
This tool suits any engineer preparing a Competency Demonstration Report who wants an honest structural read before spending hours on final writing or Summary Statement mapping.
First Time CDR Applicants
See exactly what a compliant episode looks like, then check your draft against word count, numbering, and section coverage before you commit.
Reworking a Rejected Episode
Pinpoint the structural reasons behind a negative outcome, such as team pronouns, thin evidence, or missing paragraph numbers, and fix them fast.
Overseas and Onshore Engineers
Confirm your writing meets Engineers Australia expectations for first person voice and structure, whichever engineering discipline you nominate.
Before Summary Statement Mapping
Make sure each episode is numbered and evidence rich, so mapping competency elements later becomes a smooth, quick step.
Career Episode Format Required for a CDR
Each Career Episode follows a logical structure. Use this table to check the length and focus of every section before you run the analysis.
| Section | Approx. Length | What to Include | Common Mistake |
|---|---|---|---|
| Introduction | 50 to 100 words | Project title, dates, duration, location, employer, and your role. | Missing dates, location, or job title that assessors need for context. |
| Background | 150 to 250 words | Project objective, engineering context, team structure, and your duties. | Loading the section with company history instead of the engineering purpose. |
| Personal Engineering Activity | 700 to 2,000 words | Your calculations, analysis, designs, standards, tools, decisions, and problem solving. | Describing team actions with we instead of your own contribution with I. |
| Summary | 50 to 150 words | Your contribution, the project outcome, and the competencies you demonstrated. | Skipping the summary or keeping it too generic with no personal outcome. |
Always review the latest Engineers Australia migration skills assessment instructions before you lodge your CDR application.
Common Career Episode Structure Mistakes
A Career Episode can look finished yet still fail to show strong evidence. Check your draft against these errors before you move to final review.
Mistake 01
Writing a Duty Statement
Do not simply list duties. Explain a real engineering activity, the problems you handled, and the results of your decisions.
Mistake 02
Leaning on We Too Often
Assessors need your personal contribution. Use I to show your own actions instead of making every task read as a team achievement.
Mistake 03
A Weak Background Section
Do not overload the background with company history. Keep it focused on the project, your role, and the engineering context only.
Mistake 04
Missing Paragraph Numbers
Unnumbered paragraphs make Summary Statement mapping impossible. Number every paragraph before you build the competency matrix.
Mistake 05
Low Technical Depth
General statements are not enough. Include the tools, standards, calculations, constraints, and reasoning behind your work.
Mistake 06
Unclear Project Outcome
The summary must explain the result of the project and how your personal contribution helped achieve it.
Want an Expert to Review Your Career Episode?
Get your episode checked for structure, first person writing, technical depth, paragraph numbering, and Summary Statement readiness before you submit to Engineers Australia.
Frequently Asked Questions
Quick answers about CDR Career Episode structure, word count, paragraph numbering, first-person writing, and Summary Statement mapping.
A Career Episode is a written account of an engineering project, task, position, or problem that shows how you applied engineering knowledge and demonstrated competency for Engineers Australia assessment.
Engineers Australia requires three written Career Episodes for a Competency Demonstration Report pathway. Each must describe a different engineering project or experience.
A Career Episode should include an Introduction, Background, Personal Engineering Activity, and Summary. It should also use numbered paragraphs (e.g. 1.1, 1.2, 1.3) for Summary Statement mapping.
Yes. Write in first person and focus on your personal engineering contribution using statements such as "I designed," "I calculated," "I analysed," "I tested," and "I improved." Using "we" hides your individual contribution from the assessor.
Each Career Episode must be between 1,000 and 2,500 words. Episodes shorter than 1,000 words may not contain sufficient engineering evidence. Episodes longer than 2,500 words do not comply with EA guidelines.
Numbered paragraphs help you cross-reference each competency element in the Summary Statement to the exact paragraph where the evidence appears. Without them, you cannot complete your Summary Statement correctly.
Yes, but it is generally not recommended. Each episode should focus on a genuinely different engineering activity or phase, and the competency elements demonstrated must not overlap significantly.
No. This checker is a structural review tool. It helps you identify measurable compliance issues, but final assessment decisions depend on Engineers Australia and the quality, depth, and originality of your complete CDR submission.