CDR Report Guide
Understand how a CDR brings Career Episodes, Summary Statement, and CPD records together for Engineers Australia pathways. Use this guide to check structure, project evidence, competency links, and report flow.
View CDR GuideSkills Assessment Guides for CDR, ACS RPL, KA02 and EA Pathways
Compare the main assessment documents required for Engineers Australia, ACS RPL, KA02, NER, and Stage 2 pathways. Use these guides to check document structure, evidence requirements, competency links, and common errors before preparing your draft.
Assessment Guides
Choose the Skills Assessment Guide That Matches Your Pathway
Select the guide based on your assessment body, document type, or draft stage. Each guide explains what to include, how to present your experience, and which details need review before submission.
Career Episode Guide
Learn how one engineering project should show your personal contribution, technical decisions, tools, standards, problem-solving, and project outcome.
View Career Episode GuideSummary Statement Guide
Check how to link Career Episode paragraphs with the right competency elements. Use this guide to avoid weak references, missing evidence, and unclear mapping.
View Summary Statement GuideCPD Guide
Organise your professional learning with clear activity names, dates, providers, and outcomes. Use this guide to present CPD records in a clean assessment-ready format.
View CPD GuideCDR Review Guide
Review your self-written CDR before submission. Check structure, paragraph numbering, technical clarity, grammar, originality, Summary Statement links, and overall consistency.
View CDR Review GuideACS RPL Guide
Understand how ACS RPL project reports should show ICT knowledge, tools, platforms, responsibilities, technical decisions, and project outcomes linked to your ANZSCO role.
View ACS RPL GuideKA02 Guide
Prepare KA02 evidence for Engineering New Zealand-related pathways. Use this guide to present engineering knowledge, project involvement, competency evidence, and professional responsibility clearly.
View KA02 GuideNER Guide
Understand how to present professional engineering practice for the National Engineering Register pathway. Focus on responsibility, experience, evidence, competency, and conduct.
View NER GuideStage 2 Guide
Explore Stage 2 requirements for advanced engineering practice. Use this guide to check leadership, communication, ethical conduct, risk management, and professional judgement evidence.
View Stage 2 Guide
Pathway Match
Match the Guide to Your Assessment Pathway
Check your assessment authority, document type, and evidence requirements before selecting a guide. Start with the pathway that matches your profession.
Start here when your documents relate to CDR, Career Episode, Summary Statement, CPD, NER, or Stage 2.
Choose this pathway when your assessment depends on ACS RPL project reports and ICT work experience.
Follow this pathway when your document needs structured engineering competency evidence for Engineering New Zealand-related assessment.
Free Tools
Free Tools for Skills Assessment Preparation
Use these tools after choosing your pathway. Review structure, evidence gaps, competency links, and draft readiness before submission.
CDR Checklist
Review Career Episodes, Summary Statement, CPD, and support details.
Open ToolCareer Episode Tool
Review introduction, background, personal activity, and summary.
Open ToolSummary Mapping Tool
Match competency references with strong Career Episode paragraphs.
Open ToolACS RPL Readiness
Review tools, systems, duties, decisions, and outcomes.
Open ToolCPD Checklist
Organise learning activities with dates, providers, and topics.
Open ToolDraft Review Checklist
Find weak evidence, unclear duties, and originality risks.
Open Tool
Before Submission
What to Check Before Finalising Your Assessment Document
Check whether your assessment document proves the right experience, evidence, and pathway fit before submission.
Document Structure
Check whether each section matches the expected document type, such as CDR, ACS RPL, KA02, NER, or Stage 2.
Role Clarity
Show your exact role in the project or workplace. Make your duties, decisions, and technical input easy to identify.
Technical Evidence
Support your claims with tools, standards, drawings, calculations, systems, testing methods, reports, or measurable outcomes.
Pathway Alignment
Match your content with EA competencies, ACS ANZSCO roles, KA02 areas, NER requirements, or Stage 2 indicators.
Writing Quality
Fix unclear sentences, weak transitions, repeated wording, grammar issues, heading flow, and formatting problems.
Originality Check
Remove copied wording, template-style phrases, sample-based content, and unsupported claims.
Draft Review
Review Your Draft Before Submission
Improve your self-written draft before you finalise it. Identify weak evidence, unclear explanations, missing competency links, and originality risks.
Career Episode Structure
Confirm whether each episode follows the required format and shows your personal engineering contribution clearly.
CDR Report Flow
Assess how your Career Episodes, Summary Statement, and CPD work together as one complete document.
Summary Statement Mapping
Verify that each competency reference connects to a strong and relevant Career Episode paragraph.
ACS RPL Project Clarity
Improve how your ICT project reports present tools, systems, responsibilities, decisions, and ANZSCO role alignment.
Originality and Evidence Risks
Remove copied phrases, sample-style wording, unsupported claims, and details that do not match your real experience.
Assessment Readiness
What a Strong Skills Assessment Document Should Show
Present your real role, technical work, decisions, and outcomes with clear evidence.
Project or Role Scope
Explain the project, workplace role, or assessment activity you selected.
Personal Responsibilities
State the tasks you completed yourself. Separate your contribution from team duties.
Technical Methods and Tools
Mention software, systems, standards, calculations, drawings, testing methods, or procedures.
Problems and Decisions
Describe the technical issues you handled and the reason behind your approach.
Evidence Behind Claims
Support your statements with documents, outputs, reports, references, dates, or results.
Pathway Fit
Show how your work matches the required competency, ANZSCO role, or document purpose.
Avoid vague claims like “I handled the project successfully.” Show the exact action, method, evidence, and outcome.
Common Errors
Common Mistakes That Weaken Assessment Documents
Avoid mistakes that make your experience look unclear, unsupported, or inconsistent.
Copied Sample Content
Remove wording taken from samples, websites, old reports, or another applicant’s document.
Unsupported Duties
Do not add responsibilities that your CV, reference letters, or project evidence cannot support.
Unclear Dates and Roles
State project dates, job titles, organisation names, and role changes clearly.
Team-Focused Writing
Replace broad team achievements with your own actions.
Missing Technical Evidence
Support your work with tools, standards, calculations, drawings, systems, and test results.
Inconsistent Claims
Compare your report with your CV, references, employment dates, duties, and project records.
Start Here
Start With the Right Skills Assessment Guide
Choose the guide that matches your pathway, review the document requirements, and prepare your draft with clear evidence.
CDR Preparation
What Applicants Should Do and Avoid in CDR Preparation
What Applicants Should Do
- Use real academic or workplace projects that reflect your actual engineering duties.
- Write your Career Episodes in your own words.
- Focus on your personal engineering contribution, not only the team outcome.
- Support your claims with drawings, calculations, standards, tools, reports, or project evidence.
- Match your CDR details with your CV, reference letters, dates, and job duties.
What Applicants Should Avoid
- Do not copy wording from samples, templates, websites, or another applicant’s report.
- Do not add duties, tools, standards, or responsibilities you cannot prove.
- Do not describe only what the company or project team completed.
- Do not exaggerate your role, authority, or project responsibility.
- Do not expect any draft, review, or writing support to guarantee assessment approval.
Note: A reviewer can improve clarity, structure, grammar, formatting, evidence flow, and competency links in your self-written draft. However, a reviewer cannot create false experience, add unsupported duties, write the full report for you, or guarantee assessment approval.
FAQs
Frequently Asked Questions
Which skills assessment guide should I read first?
The right guide depends on your assessment authority. Choose CDR for Engineers Australia, ACS RPL for ICT, and KA02 for Engineering New Zealand. This keeps your preparation focused from the beginning.
What documents should I prepare before writing a skills assessment draft?
Your main documents should include your CV, academic records, employment references, project dates, job duties, and supporting evidence. These records help you write a consistent and evidence-based draft.
How do I know if my project is suitable for a CDR or RPL report?
A suitable project should show your personal technical work, decisions, tools, problem-solving, and results. Choose a project that clearly proves what you handled.
Why do skills assessment drafts get weak feedback?
Skills assessment drafts get weak feedback when they hide the applicant’s real contribution. Vague duties, missing evidence, copied wording, and poor mapping weaken the document.
Can I use one project for different assessment documents?
Yes, one real project can support different assessment documents when it fits each purpose. Rewrite the explanation for CDR, ACS RPL, KA02, or Stage 2 requirements.