PEO 34 Competencies Explained: The 7 CBA Categories and Evidence Applicants Need

Professional Engineers Ontario (PEO) licenses professional engineers and regulates engineering practice in Ontario. To assess whether an applicant can apply engineering knowledge safely, exercise sound judgment and accept professional responsibility, PEO evaluates experience through competency-based assessment (CBA). Rather than relying only on job titles, employment duration or general duties, CBA uses observable evidence from real engineering work. A competency is a defined combination of knowledge, practical skill, behaviour and judgment, demonstrated through a situation, the applicant’s personal actions and the resulting outcome.

PEO organizes professional readiness into 34 competencies across seven categories covering technical competence, communication, project delivery, teamwork, professional accountability, the wider effects of engineering and continuing professional development. This article explains how the framework fits together, what each category assesses, which evidence is useful and how to map genuine projects into clear, assessable examples before writing.

Quick Answer: What Are the 34 PEO Competencies?

The PEO 34 competencies are observable engineering capabilities arranged in seven CBA categories: Technical Competence; Communication; Project and Financial Management; Team Effectiveness; Professional Accountability; Social, Economic, Environmental and Sustainability; and Personal Continuing Professional Development. Applicants demonstrate them through specific, verifiable work examples that show what they personally analyzed, decided, communicated, managed or improved.

A category is a broad area of professional practice. A competency is one defined capability inside that area. An indicator is an official example of activity that may show exposure to that competency; it is guidance, not a checklist. A work example is the applicant’s own Situation-Action-Outcome account. A validator is the qualified practitioner assigned to confirm and independently rate the work.

Technical Competence	10	Analysis, design, methods, codes, standards, technical risk, safety and judgment
Communication	3	Oral, written and document-based communication for appropriate audiences
Project and Financial Management	5	Scope, schedule, resources, budget, change, risk and delivery decisions
Team Effectiveness	2	Collaboration, multidisciplinary coordination and constructive conflict handling
Professional Accountability	6	Ethics, limitations, conflicts of interest, responsibility, sealing and self-awareness
Social, Economic, Environmental and Sustainability	5	Public impact, regulation, sustainability and wider consequences of engineering work
Personal Continuing Professional Development	3	Learning needs, development activities, reflection and application of learning

How PEO Uses Competencies to Assess Engineering Experience

PEO’s CBA does not award competence merely for holding a particular title or spending a set number of years at work. As of July 1, 2026, applicants must have at least 24 months of eligible, verifiable experience and pass the CBA. PEO also notes that applicants commonly need three to four years, and sometimes longer, to develop evidence across all 34 competencies. Time opens the door; demonstrated competence is the standard.

Three perspectives contribute to the assessment. The applicant writes a work example and self-rating. The assigned validator independently rates the example based on familiarity with the applicant’s work. A PEO qualification assessor reviews the applicant’s example, self-assessment and validator input and determines the final rating.

That process makes personal authorship essential. “We designed the system” tells an assessor little about the applicant. “I checked the pressure-loss model against operating data, identified an undersized control valve and recommended a revised specification” identifies an action, judgment and result. The second version can be assessed and, if the validator observed the work, verified.

PEO uses a 0-to-5 competency rating scale. Most competencies have a minimum rating of 1. The six professional standards competencies have higher individual minimums: competencies 1.1, 1.6, 1.9, 2.3 and 5.1 require a minimum rating of 3, while competency 6.2 requires a minimum rating of 2. Each category must also meet its required average. A self-rating should match the independence, complexity, responsibility and risk demonstrated in the example rather than the applicant’s job title.

Category 1: Technical Competence (10 Competencies)

What This Category Assesses

Technical Competence is the largest category. Its ten competencies examine whether you can apply engineering principles in practice, work within constraints, analyze risk, develop and verify solutions, use codes and standards, consider safety, understand quality requirements, interpret technical documents and recognize the effect of engineering activities.

The category is not a software inventory. PEO needs to see the reasoning behind the output: why a method was appropriate, which assumptions mattered, how results were checked and what decision followed. A model, drawing or calculation becomes useful evidence only when your explanation connects it to a technical problem and a defensible judgment.

Evidence Applicants Can Use

• A calculation, model, design, investigation or specification you completed and independently checked.
• A comparison of design alternatives against performance, safety, constructability, cost or operating constraints.
• Diagnosis of a failure, nonconformance or technical risk, followed by a practical mitigation.
• Application of a code, regulation or standard that changed a design detail, material, test or operating procedure.
• A quality-control or peer-review process that detected an error and improved the deliverable.
• Multidisciplinary coordination in which you resolved a technical interface rather than merely attended a meeting.

For example, a civil applicant might explain how they revised a drainage design after checking rainfall assumptions and downstream capacity. A mechanical applicant might compare equipment options using duty, reliability and maintenance constraints. An electrical applicant might document protection-coordination analysis and the verification used before issuing settings. The discipline changes; the evidence logic does not.

Evidence to Avoid

Avoid listing software, equations or codes without explaining the decision they supported. Do not describe a team’s complete design when only one part was yours. Routine drafting or data entry usually shows exposure, not independent technical judgment. “Complied with all standards” is also too broad; identify the relevant requirement, how you interpreted it and what changed because of it.

Category 2: Communication (3 Competencies)

What This Category Assesses

The communication competencies cover oral communication, written communication and the ability to review essential documents. PEO is assessing whether you can move engineering information accurately between people who have different expertise, responsibilities and decision needs.

Strong communication evidence includes an audience, a technical issue and a consequence. The question is not simply whether you wrote a report or attended a presentation. It is whether your communication clarified risk, enabled approval, prevented misunderstanding or led to a sound decision.

Evidence Applicants Can Use

• A technical recommendation presented to a client, regulator, operator or management team.
• A report, calculation note, field record, specification or design brief tailored to its intended reader.
• A design review, safety briefing or cross-discipline meeting where you explained a complex issue and answered objections.
• Review of a critical technical document, followed by a concise summary of its implications and required actions.
• Written clarification that resolved an ambiguous requirement or prevented rework.

Evidence to Avoid

“I attended weekly meetings” does not reveal communication skill. Neither does listing documents without their purpose, audience or effect. If you reuse a technical project, make the communication challenge central: what the audience needed, how you adapted the message and what happened next.

Category 3: Project and Financial Management (5 Competencies)

What This Category Assesses

These five competencies test your understanding of project-management principles, progressive responsibility, changing expectations, financial aspects and feedback on performance. The emphasis is on making or influencing delivery decisions within real constraints not on carrying the job title “project manager.”

PEO-relevant evidence may come from a small work package as readily as a major program. An early-career engineer who planned a test campaign, tracked hours and adjusted a sequence after a supplier delay may have clearer evidence than a senior applicant who merely states the total project value.

Evidence Applicants Can Use

• Building or revising a work plan, schedule, estimate or resource allocation.
• Assessing a scope change, cost variance, procurement issue or schedule risk and recommending a response.
• Balancing technical performance with budget, lifecycle cost or delivery constraints.
• Coordinating deliverables, quality checks, dependencies or a risk register.
• Requesting and using client or supervisor feedback to improve project performance.

Evidence to Avoid

Do not quote the whole contract value as if it were your budget responsibility. Distinguish decisions you made from those made by a project manager or commercial team. Seniority alone does not prove management competence; the example must show planning, monitoring, adjustment or financial judgment attributable to you.

Category 4: Team Effectiveness (2 Competencies)

What This Category Assesses

Team Effectiveness contains two competencies: working respectfully and effectively with others, and resolving differences constructively. The category looks for behaviour that improved a shared engineering outcome—especially where disciplines, priorities or viewpoints competed.

Good evidence makes the interaction visible. Explain who needed to contribute, where the disagreement or coordination risk arose, what you did to build alignment and how the solution protected quality, safety or delivery.

Evidence Applicants Can Use

• Resolving a design-interface conflict between civil, structural, mechanical, electrical or operational teams.
• Coordinating specialist input to reach a technically justified decision.
• Integrating feedback from field staff, contractors or operators into a revised solution.
• Supporting a colleague, transferring knowledge or improving a review process.
• Handling disagreement without concealing risk or damaging the working relationship.

Evidence to Avoid

Statements such as “I am a team player” or lists of team members are not evidence. Routine participation is also different from team effectiveness. Show a moment where your listening, coordination, feedback or conflict-handling changed the result.

Category 5: Professional Accountability (6 Competencies)

What This Category Assesses

Professional Accountability examines how you behave when engineering work creates obligations. Its six competencies address ethics, limits of competence, conflicts of interest, professional accountability, the appropriate use of a professional engineer’s seal and awareness of personal strengths and weaknesses.

This category often exposes the difference between knowing a rule and applying professional judgment. A definition of duty of care is not a work example. A decision to stop an unsupported issue-for-construction release, seek specialist review and document the residual risk is.

Evidence Applicants Can Use

• Identifying and escalating a safety, compliance, quality or ethical concern.
• Refusing, revising or delaying work that lacked adequate technical support.
• Recognizing that a task exceeded your competence and obtaining appropriate review.
• Managing a real or perceived conflict of interest transparently.
• Distinguishing your preparatory role from the licensed professional’s responsibility for sealing documents.
• Accepting responsibility for an error, correcting it and changing the process to prevent recurrence.

Evidence to Avoid

Do not recite a code of ethics without a real decision. Avoid claiming that no project ever presented an ethical or accountability issue; ordinary choices about review, safety, disclosure, limitations and responsibility can provide relevant evidence. Do not imply that you used or authorized a P.Eng. seal if you did not have the legal authority to do so.

Category 6: Social, Economic, Environmental and Sustainability (5 Competencies)

What This Category Assesses

These five competencies test whether you understand engineering beyond the immediate technical deliverable. They cover safeguards for the public, the relationship between engineering and the public, the role of regulators and overlapping professions, sustainability requirements and the application of sustainability principles.

The strongest examples show that a wider impact affected an engineering choice. Sustainability should not be decorative language added after the design; it should influence the option, material, operating strategy, mitigation or recommendation.

Evidence Applicants Can Use

• Comparing options using lifecycle cost, emissions, energy, waste, resilience or maintenance impacts.
• Revising a design to reduce risk to users, neighbours, workers or the public.
• Addressing accessibility, community disruption, land use, climate exposure or stakeholder concerns.
• Interpreting the role of a regulator or another regulated profession in project delivery.
• Introducing a measurable reduction in resource use or environmental impact.

Evidence to Avoid

Avoid unsupported organization-wide claims such as “the project was sustainable.” Do not repeat policy statements without a project-specific action. Name the impact you considered, the trade-off you evaluated and how your recommendation changed.

Category 7: Personal Continuing Professional Development (3 Competencies)

What This Category Assesses

The final category examines whether you can identify learning needs, plan development and complete activities that improve your practice. PEO is looking for a learning cycle: recognize a gap, choose an appropriate response, apply the learning and consider what comes next.

This is distinct from simply listing courses or describing licence-holder CPD compliance. A course becomes useful evidence when it addressed a genuine need and changed how you performed engineering work.

Evidence Applicants Can Use

• Learning a code, calculation method, tool or technical subject needed for a project and applying it.
• Acting on feedback from a design review, field problem, incident or mentor.
• Preparing a development plan for anticipated responsibilities.
• Completing targeted training and showing the improvement in a later deliverable.
• Sharing newly acquired knowledge with colleagues through a guide, briefing or mentoring activity.

Evidence to Avoid

Do not submit a course catalogue. Avoid unrelated learning with no connection to your engineering practice. “I learned a lot” is not an outcome; explain what changed in your analysis, decision-making, quality or efficiency.

How to Match Projects to the 34 Competencies

Begin with projects, not empty competency boxes. List assignments where you made decisions, solved problems, managed constraints, communicated consequences or carried responsibility. Those moments are more useful than the largest or most prestigious project on your résumé.

Then create a competency-to-project matrix. Mark the strongest project for each competency before drafting any narrative. This reveals overused stories, missing non-technical evidence and validators who may not be able to confirm the work.

Equipment upgrade	Performed duty analysis and prepared specification	Technical; Communication	Capacity met with documented operating margin	Lead engineer
Site redesign	Coordinated disciplines and revised delivery plan	Team; Project and Financial Management	Clash removed and delay avoided	Project manager
Compliance review	Identified code gap and escalated corrective action	Technical; Professional Accountability	Design revised before issue	Supervising P.Eng.
Energy-reduction initiative	Compared lifecycle options and implemented change	Sustainability; CPD	Energy use reduced against baseline	Operations manager

Use the same project more than once only when each entry proves something genuinely different. One project might support technical risk, written communication and teamwork, but the first entry should focus on your risk analysis, the second on how you communicated it and the third on how you resolved competing inputs. Do not paste the same story under new headings.

Finally, check three forms of balance:

1. Coverage: Is every competency supported by a real example?
2. Depth: Does each example show action and judgment, not only exposure?
3. Verification: Can the assigned validator confidently rate the work?

If a gap is real, do not stretch a weak story or invent an outcome. Document it and look for legitimate experience that can develop the missing capability.

What Strong Evidence Has in Common Across All Seven Categories

Strong PEO CBA work examples are detailed enough to assess but narrow enough to follow. Across disciplines and categories, they usually contain:

• A specific situation with enough technical or professional context to understand the challenge.
• A clearly stated personal responsibility, written in the first person.
• A judgment, decision or problem that required more than routine participation.
• Actions that explain how and why you used a method, standard, consultation or control.
• Relevant constraints such as safety, cost, schedule, quality, stakeholders or uncertainty.
• A concrete outcome, quantified where the record supports it.
• A logical match to the selected competency rather than copied indicator language.
• A validator who had sufficient first-hand familiarity with the work.

PEO’s Situation-Action-Outcome structure is useful because it exposes missing reasoning. Keep the situation brief. Give most of the available space to your actions. Use the outcome to show the effect on the design, project, team, organization or public. Every statement must remain truthful, accurate and reflective of work you personally completed.

Common Mistakes When Covering the PEO Competency Framework

Treating competencies as definitions

Explaining what risk management or ethics means does not prove you practised it. Replace theory with a verifiable engineering event.

Repeating one generic project description

Project context may repeat, but the action and outcome must change with the competency. Otherwise, 34 fields become one unverifiable job summary.

Hiding behind “we”

Team context matters, but assessors must distinguish your contribution. Use “I” for the actions you personally performed and name others only to clarify interfaces or approvals.

Overloading technical detail

Calculations and acronyms can bury the professional decision. Include enough detail to establish complexity, then explain the choice and consequence.

Assuming a title proves competence

“Senior Engineer,” “Team Lead” or “Project Manager” does not automatically prove responsibility. Show the actual planning, review, judgment or accountability.

Writing ethics and sustainability as theory

These categories still require project-based evidence. Show the pressure, trade-off or wider impact that affected your action.

Listing training as CPD evidence

Connect learning to a gap and a change in practice. Attendance alone is weak evidence.

Choosing an unsuitable validator

A respected senior practitioner is not automatically the best validator if they cannot confidently rate the specific work. Map validators while choosing examples, not after drafting.

Using outdated requirements

PEO currently requires at least 24 months of eligible, verifiable engineering experience, completion of all 34 competency entries and validation of the submitted examples. Canadian experience is not mandatory, and international work may demonstrate professional standards competencies when it applies standards used in Canada or a suitable international equivalent. Drafts based on the former four-year threshold, older Canadian-experience language or superseded forms can create avoidable errors.

When Competency Mapping or Writing Support May Help

Independent support can be useful when your experience is substantial but still reads like duties, when the same two projects dominate every category, or when gaps appear in accountability, management, sustainability or development. Internationally trained engineers may also benefit from making jurisdictional context and equivalent standards clear to an Ontario assessment audience.

Good support should help you select and organize authentic evidence, improve clarity and check alignment. It should never invent experience, assign you work completed by colleagues or replace your responsibility for the truth of the application.

Frequently Asked Questions

1. What are the 34 PEO competencies?

They are the defined capabilities PEO uses to assess engineering experience for licensure. They cover technical work, communication, project and financial management, teamwork, professional accountability, wider social and environmental impacts, and continuing professional development.

2. What are the seven PEO CBA categories?

The seven categories are Technical Competence; Communication; Project and Financial Management; Team Effectiveness; Professional Accountability; Social, Economic, Environmental and Sustainability; and Personal Continuing Professional Development.

3. Does every PEO competency need a separate example?

Every competency needs a work example, but it does not need a separate project. PEO permits the same work example or project to support more than one competency when each entry is tailored to the capability being assessed.

4. Can I use the same project for several competencies?

Yes. A project may contain technical, communication, management and accountability evidence. Each response should isolate a different personal action and outcome; repeating the same generic narrative weakens the distinction between competencies.

5. What counts as strong evidence for a PEO competency?

Strong evidence describes a real situation, the applicant’s specific actions and judgment, and a concrete outcome. It also fits the selected competency, stays within the applicant’s actual responsibility and can be verified by the assigned validator.

6. Which PEO competencies require Canadian-environment evidence?

PEO does not require Canadian experience. Six professional standards competencies carry higher individual minimums: 1.1 Regulations, Codes and Standards; 1.6 Safety; 1.9 Quality Control; 2.3 Review of Essential Documents; 5.1 Code of Ethics; and 6.2 Engineering and the Public. Competencies 1.1, 1.6, 1.9, 2.3 and 5.1 require a minimum rating of 3, while 6.2 requires 2. Work from any country may support them when it demonstrates standards used in Canada or an appropriate international equivalent.

7. How are the PEO competencies rated?

The applicant and validator use a 0-to-5 scale, and the PEO assessor determines the final rating. Each competency has a minimum rating and each category a minimum average; the professional standards competencies have higher minimums than most other items.

8. Can international engineering experience demonstrate the competencies?

Yes. PEO states that Canadian experience is not required. Overseas examples should still make the engineering context, applicable jurisdiction, standards or equivalent requirements, personal responsibility and validator relationship easy to understand.

9. Does my validator need to verify every competency?

A validator must be assigned to each work example, but applicants may use more than one validator. PEO permits only one validator for a given competency. The assigned person should know that work well enough to rate it independently.