APEGA CBA vs. PEO CBA: What Is Different and What Is Transferable
Applicants who worked in multiple provinces — or who are relocating mid-application — constantly ask us how much of their CBA work transfers between APEGA and PEO. The short answer: the stories transfer, the structure needs adjusting.
The headline numbers
- PEO (Ontario): 34 competencies across 7 categories, including dedicated categories for communication, team effectiveness, and continuing professional development.
- APEGA (Alberta): 22 competencies across 6 categories, with heavier emphasis on technical application and professional practice folded together.
- EGBC (British Columbia): its own competency framework with a similar SAO-style evidence model.
What transfers between APEGA and PEO
Your underlying engineering stories: the situations, the analysis you did, the outcomes you delivered. A strong SAO example written for APEGA contains 80% of what PEO needs.
What does not transfer
- Competency mapping. One APEGA competency may split into two PEO competencies (or vice versa). Each example must be re-tagged, and some need an added paragraph to hit the new indicator.
- Category requirements. PEO standalone communication and CPD categories often require brand-new examples that APEGA applicants never wrote.
- Validator setup and submission mechanics differ by association portal.
- Word/character limits and scoring scales are not identical — re-trim rather than copy-paste.
Practical advice for multi-province applicants
Build a master library of 8–10 strong SAO stories, then map them per association. We maintain per-association frameworks for all nine CBA-using regulators — see the Provinces page, or start a free consultation and tell us both associations involved.
Every CBA example must be verifiable, and that is the validator’s job. Choosing the wrong one — or briefing the right one badly — can stall an otherwise strong P.Eng. application.
Who qualifies as a CBA validator
Requirements vary slightly by association, but the standard profile is: a senior engineer (usually a P.Eng.) with direct, first-hand knowledge of the work you described. Direct supervisors are ideal. Colleagues at the same level are usually not acceptable for technical competencies.
How many validators you need
Most applicants need two to four validators to cover all their examples, because few supervisors observed all four years of your experience. Map each example to a validator before you finalize your story selection — a brilliant example with no available validator is a liability.
How to brief your validators
- Send them the exact text of the examples they will validate — never make them guess.
- Tell them the timeline: associations typically email validators a verification form with a deadline.
- Confirm their current contact details and that they are willing and reachable (vacations and retirements cause real delays).
- Warn them against copy-pasting your text back; assessors flag identical wording.
If you cannot find a validator
Supervisor retired, company dissolved, or you worked internationally? Associations handle this more often than you think. Options typically include an alternative senior colleague, a client-side engineer who oversaw your work, or a statutory-declaration process. Contact your association early and document their guidance in writing.
Validator strategy is built into our Guided 1-on-1 Coaching — story selection and validator guidance are core parts of the sessions. See pricing for details.
Professional Engineers Ontario (PEO) assesses P.Eng. applicants against 34 competencies in 7 categories. Understanding what each category is really asking is half the battle. Here is the plain-English breakdown.
1. Technical Competence (10 competencies)
The core of your PEO CBA: applying engineering theory, analysis methods, design, and standards. Assessors want depth — show the equations, the codes you applied, the assumptions you checked. A common failure: describing the project instead of your analysis.
2. Communication (3 competencies)
Not “I am a good communicator” — specific instances: a technical report you wrote for a non-technical client, a design review you presented, a specification you defended.
3. Project & Financial Management (5 competencies)
Budgets, schedules, procurement, and resource decisions you personally owned. Numbers matter here — dollar values, timelines, and the trade-offs you made.
4. Team Effectiveness (2 competencies)
Where most PEO applicants accidentally write “we.” Assessors score your contribution to team function: resolving a conflict between disciplines, mentoring a junior engineer, coordinating contractors.
5. Professional Accountability (6 competencies)
Ethics, professional responsibility, and protecting the public. Strong examples involve a judgment call: refusing to sign off, escalating a safety concern, managing a conflict of interest.
6. Social, Economic & Environmental Sustainability (5 competencies)
How your engineering decisions accounted for impacts beyond the immediate deliverable — lifecycle cost, environmental mitigation, community effects.
7. Personal Continuing Professional Development (3 competencies)
How you identify and close your own knowledge gaps — courses, self-study, lessons learned applied to later projects.
The pattern across all 34 PEO competencies
Every category rewards the same structure: specific situation, personal action, measurable outcome. If you are unsure whether your draft does this across all 34, our Complete Revision Service evaluates your draft indicator-by-indicator, and the Provinces page compares PEO with the other eight associations we support.
If you started your P.Eng. application expecting to submit a resume-style work experience record, the Competency-Based Assessment (CBA) probably came as a surprise. Most Canadian regulators — PEO, APEGA, EGBC, APEGS, EGM, APEGNB, Engineers PEI, PEGNL, and Engineers Nova Scotia — now evaluate applicants on demonstrated competencies, not job titles and years worked.
What the CBA actually measures
Instead of asking “where did you work and for how long?”, the CBA asks “show us a specific situation where you personally applied engineering theory,” or “demonstrate how you managed risk on a real project.” Each competency is scored against indicators defined by your association. PEO, for example, assesses 34 competencies across 7 categories, while APEGA uses 22 competencies across 6 categories.
The SAO framework: how assessors want answers written
Nearly every CBA-using association expects examples structured as Situation–Action–Outcome:
- Situation: One specific project, with dates, your role, and the technical context. Two to three sentences — not your company whole history.
- Action: What you personally did, in first person. The calculations you ran, the judgment calls you made, the standards you applied. This section should be 60–70% of your example.
- Outcome: The measurable result of your action — and, where relevant, what you learned or would do differently.
How CBA scoring works
Assessors are trained volunteers — practising engineers — who read your examples against a scoring rubric, typically a 0–5 scale per indicator. Vague examples score low regardless of how impressive the underlying project was. That is why strong engineers with weak writing fail, while average projects described precisely get approved.
What this means for your P.Eng. application
Treat the CBA as an engineering document in its own right: scoped, evidenced, and reviewed before submission. If you want a second set of licensed-P.Eng. eyes on your structure before you submit, that is exactly what our Expert Draft Review is for — and our FAQ page answers the most common CBA process questions.