Introduction
Start with clear facts about the project, dates, location, organisation, and your position. This gives the assessor context before the technical details begin.
Career Episode Structure Checker
Paste your Career Episode text and get a full structural analysis, including word count, first-person language ratio, paragraph numbering, passive voice detection, and EA section compliance, all checked before you submit.
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.
Understand Your Career Episode Structure Result
Your analysis shows how well your Career Episode meets EA structural requirements. Use the findings to improve each section before moving to Summary Statement mapping.
Background
Explain the project purpose, objectives, team structure, and your area of responsibility. Keep this section clear, brief, and directly connected to your role.
Personal Engineering Activity
Use this main section to prove what you personally analysed, designed, calculated, tested, solved, improved, coordinated, or delivered. This is the largest section.
Summary
Close the episode by summarising your contribution, the engineering result, and the competencies demonstrated through your work.
Paragraph Numbering
Number every paragraph so each competency element can be cross-referenced in the Summary Statement without confusion (e.g. 1.1, 1.2, 1.3 for Episode 1).
First-Person Evidence
Write in first person and show your own engineering actions. Avoid writing about the company, the team, or the product without placing yourself at the centre.
Career Episode Format Required for CDR
A strong Career Episode follows a logical structure. Each section supports your CDR evidence and makes Summary Statement mapping easier.
| Section | Approx. Length | What to Include | Common Mistake |
|---|---|---|---|
| Introduction | 50 to 100 words | Project title, dates, duration, location, organisation, and your role or position. | Missing dates, location, or job title, which assessors need for immediate context. |
| Background | 150 to 250 words | Project objective, engineering context, team structure, and your assigned duties. | Overloading with company history instead of focusing on the engineering purpose. |
| Personal Engineering Activity | 700 to 2,000 words | Your calculations, analysis, designs, standards, software, problem-solving, decisions, safety, and communication. | Describing team actions with "we" instead of your individual contribution with "I". |
| Summary | 50 to 150 words | Your personal contribution, project outcome, lessons learned, and competency evidence. | Omitting the summary entirely or making it too generic without personal outcomes. |
Always review the latest Engineers Australia migration skills assessment instructions before lodging your CDR application.
Why Career Episode Structure Matters for Engineers Australia
A structured Career Episode helps assessors find competency evidence quickly. It also helps you connect your project details to the required Summary Statement.
Clear Assessment Evidence
A proper structure separates context, role, technical activity, and outcome. This makes your engineering evidence easier to review and score.
Better Summary Statement Mapping
Numbered and focused paragraphs make it easier to map each competency element to the correct Career Episode reference number.
Stronger Personal Contribution
The main body should show your individual engineering decisions. It should not read like a project summary written on behalf of the full team.
Improved Technical Depth
Clear sections help you add calculations, standards, software, methods, and design decisions without mixing them with background information.
Reduced Structural Gaps
A systematic approach helps you detect missing introduction details, unclear duties, weak personal activity, or absent paragraph references.
More Professional Presentation
A well-organised Career Episode shows that you can communicate engineering work clearly, logically, and professionally in written form.
Career Episode Checklist Before Submission
Use these quality checks after the structural analysis. They help you refine content quality before final CDR submission.
Check Technical Evidence
Add clear details about calculations, design standards, engineering methods, testing, analysis, software, or technical judgement.
Check First-Person Writing
Replace team-based sentences with direct statements that show what you personally did, decided, solved, or improved.
Check Paragraph Numbers
Number every paragraph in a consistent format so your Summary Statement references stay easy to follow and verify.
Check Originality
Write your own project story and avoid copied wording, generic templates, or unsupported technical claims.
Common Career Episode Structure Mistakes
A Career Episode can look complete but still fail to show strong evidence. Avoid these mistakes before moving to final review.
Writing a Duty Statement
Do not list duties only. Explain an actual engineering activity, the problems you handled, and the results of your decisions.
Using "We" Too Often
Assessors need your personal contribution. Use "I" to show your role instead of making every action sound like a team achievement.
Weak Background Section
Do not overload the background with company history. Keep it focused on the project, your role, and the engineering context only.
Missing Paragraph Numbers
Unnumbered paragraphs make Summary Statement mapping impossible. Add paragraph numbers before preparing the competency matrix.
Low Technical Depth
General statements are not enough. Include the tools, standards, calculations, constraints, and engineering reasoning behind your work.
Unclear Project Outcome
The summary must explain the result of the project and how your personal contribution helped achieve that outcome.
Need a Proper Career Episode Review?
Get your Career Episode checked for structure, first-person writing, technical depth, paragraph numbering, and Summary Statement readiness before submission.
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.
