APEGA’s 22 Engineering Competencies Explained: Six Categories, Indicators and Canadian-Environment Evidence

APEGA uses 22 engineering competencies to assess whether professional engineer and engineering licensee applicants are ready for professional practice. The competencies are grouped into six categories: Technical Competence, Communication, Project and Financial Management, Team Effectiveness, Professional Accountability, and Social, Economic, Environmental and Sustainability. In the Competency-Based Assessment Tool (CBAT), applicants demonstrate each competency with a specific example from real work, explain their own actions and outcome, and select a self-rating. Eight competencies also require Canadian or equivalent work-environment evidence.

This guide makes the framework easier to navigate. For every competency, it explains what APEGA is assessing, what type of genuine evidence may fit, and which common mistake can weaken the response. It also separates areas that applicants often confuse, such as technical risk versus safety, results verification versus quality assurance, and applying sustainability versus promoting it.

The guide follows APEGA’s engineering framework current after July 18, 2026. It is for P.Eng. and engineering licensee applicants, not the separate 29-competency P.Geo. pathway. Use it to interpret and map your experience, not as a source of copy-ready answers. Every project, decision, validator, and outcome in the application must be genuine and verifiable.

Quick Answer: What Are the 22 APEGA Engineering Competencies?

APEGA’s 22 engineering competencies are the evidence framework used in the CBAT for P.Eng. and engineering licensee applications. They cover 10 technical competencies, three communication competencies, two project and financial management competencies, one team-effectiveness competency, one professional-accountability competency, and five social, economic, environmental and sustainability competencies. Applicants demonstrate each competency with specific first-person work evidence. Eight of the 22 require Canadian-equivalent evidence and an independent minimum score.

1. Technical Competence	1.1-1.10	10	3.0
2. Communication	2.1-2.3	3	3.0
3. Project and Financial Management	3.1-3.2	2	2.0
4. Team Effectiveness	4.1	1	3.0
5. Professional Accountability	5.1	1	3.0
6. Social, Economic, Environmental and Sustainability	6.1-6.5	5	2.0

These category averages were checked against APEGA’s current scoring guidance on August 12, 2026. The eight Canadian-environment competencies have independent minimums in addition to the category averages, so a stronger result elsewhere in the category does not replace an unmet independent requirement.

In This Guide

Competencies vs indicators	Use APEGA prompts without copying them
Categories 1-6	Understand what each of the 22 competencies assesses
Canadian-environment table	Check all eight independent minimums
Project mapping	Allocate genuine projects and validators
Scoring and mistakes	Test readiness before final drafting
FAQs	Resolve common count, indicator, project, and P.Geo. questions

Competencies vs Indicators: What Is the Difference?

A competency is the skill, knowledge, behaviour, or professional judgement APEGA assesses. An indicator is a generalized example that may help an applicant recognize relevant work evidence. Indicators support planning and gap analysis; they are not separate questions and not a checklist that must be fully satisfied.

A copied indicator says, for example, that the applicant ‘identified risks and developed mitigation plans.’ Demonstrated evidence instead identifies the actual uncertainty, explains how the applicant evaluated likelihood and impact, records the mitigation selected, and states what changed. This is an illustrative contrast, not application text. The value lies in the specific facts and personal decision.

What Changed in the July 2026 Engineering Framework?

From July 18, 2026, APEGA requires all professional engineer applicants to use the revised competency-based assessment process. The framework retains 22 competencies and integrates eight Canadian work-environment equivalencies into them. Applicants should therefore use current APEGA descriptors and scoring pages rather than an older mirrored PDF, an article describing five categories, or material written for another engineering regulator.

The integration does not create a seventh category. It makes Canadian-equivalent evidence explicit within selected technical, communication, accountability, and public-benefit competencies. The official page and this guide should be rechecked when APEGA changes a descriptor, minimum, character limit, or submission instruction.

Category 1: Technical Competence (Competencies 1.1-1.10)

Technical Competence tests whether the applicant applies engineering theory and judgement to real constraints, risks, solutions, safety, systems, lifecycle decisions, quality, and documentation. The required category average is 3.0. Routine construction, maintenance, testing, software use, or administration is not enough unless the example reveals professional-level engineering analysis and responsibility.

1.1: Regulations, Codes, and Standards [Canadian Environment]

What it assesses: Selecting and applying regulations, codes, and standards that directly govern technical work. Evidence signals: Code selection, compliance checks, design decisions, regulatory reporting, and constructability or operational requirements tied to a named rule. Common miss: Citing only an internal client or plant specification, or naming a code without showing how it changed the work. International applicants should identify the Canadian equivalent. Independent minimum: 3.

1.2: Technical and Design Constraints

What it assesses: Defining technical and design limits and working within them to reach a defensible outcome, including interdisciplinary impacts. Evidence signals: Physical, performance, material, process, site, interface, reliability, and cross-discipline constraints linked to a decision.
Common miss: Discussing only budget or schedule constraints without explaining their technical consequence.

1.3: Risk Management for Technical Work

What it assesses: Identifying technical risks, their causes and impacts, then developing proportionate mitigation and monitoring. Evidence signals: Risk analysis, uncertainty, failure modes, risk registers, contingency design, mitigation ownership, and residual-risk monitoring. Common miss: Writing only about public or worker safety; APEGA distinguishes technical risk from safety.

1.4: Application of Theory

What it assesses: Using mathematics, science, and engineering theory to develop or verify a design, process, operation, or technical solution. Evidence signals: Calculations, models, assumptions, boundary conditions, engineering principles, technical specifications, or a non-standard design.
Common miss: Naming software, equations, or a finished drawing without explaining the theory and engineering judgement applied.

1.5: Solution Techniques: Results Verification

What it assesses: Self-checking professional-level technical work through a separate and independent method before implementation.
Evidence signals: Manual calculations, independent models, field data, tests, reasonableness checks, sensitivity analysis, or comparison against an alternate method.
Common miss: Saying the software produced the result or that a colleague approved it without showing the applicant’s own verification process.

1.6: Safety in Design and Technical Work [Canadian Environment]

What it assesses: Using engineering knowledge to identify, manage, and control hazards or enable safe system operation.
Evidence signals: Hazard reviews, safeguards, safety regulations, operating envelopes, design protections, maintenance safety, and controlled escalation.
Common miss: Listing general safety meetings or personal protective equipment without a technical safety decision. International applicants should identify the equivalent Canadian safety requirement. Independent minimum: 3.

1.7: Systems and Their Components

What it assesses: Understanding a technical system, component interactions, constraints, monitoring, and controlled modification. Evidence signals: Interface analysis, process interactions, system performance, dependencies, control logic, monitored change, and effect on connected components. Common miss: Using an administrative workflow or describing only one component without the wider technical system.

1.8: Project or Asset Life Cycle

What it assesses: Showing awareness of and contribution across relevant stages from feasibility and design through operation, maintenance, retirement, or decommissioning.
Evidence signals: Feasibility, design, procurement, implementation, commissioning, operation, maintenance planning, lifecycle trade-offs, and closure.
Common miss: Listing lifecycle stages from a textbook without explaining the applicant’s involvement or decisions.

1.9: Quality Assurance [Canadian Environment]

What it assesses: Assessing and applying quality assurance in design, construction, or operations, including independent technical review.
Evidence signals: Quality plans, peer review, field checks, test-result evaluation, corrective action, validation, verification, and performance acceptance.
Common miss: Treating document control or final inspection alone as quality assurance. International applicants should identify Canadian-equivalent quality assurance. Independent minimum: 3.

1.10: Engineering Documentation

What it assesses: Reviewing, communicating, and transferring technical information through drawings, graphics, data, specifications, and reports. Evidence signals: Design reviews, drawing packages, technical reports, review comments, completion reports, knowledge transfer, and lessons learned.
Common miss: Describing routine filing, transmittals, or document control without technical review or engineering judgement.

Also Read: APEGA competency-based assessment guide.

Category 2: Communication (Competencies 2.1-2.3)

Communication tests professional-level technical and project communication in English. The required category average is 3.0, and all three competencies have an independent minimum of 3 as Canadian-environment competencies. Routine conversation, short progress emails, and ordinary team interaction rarely reveal enough complexity on their own.

2.1: Oral Communication in English [Canadian Environment]

What it assesses: Communicating professional-level technical and project-related issues orally, clearly, and in English.
Evidence signals: Formal technical presentations, design reviews, detailed project meetings, stakeholder sessions, public meetings, technical direction, and responses to questions.
Common miss: Using a routine site conversation or ordinary team update with no meaningful technical explanation. Independent minimum: 3.

2.2: Written Communication in English [Canadian Environment]

What it assesses: Communicating professional-level technical and project-related issues clearly in written English.
Evidence signals: Technical memoranda, formal reports, field reports on technical issues, recommendations, peer-review comments, and audience-tailored explanations.
Common miss: Relying on emails, minutes, or progress notes with no substantial technical content or decision. Independent minimum: 3.

2.3: Reading and Comprehension in English [Canadian Environment]

What it assesses: Reading and understanding technical engineering documentation in English and applying its meaning to engineering work. Evidence signals: Interpreting standards, specifications, contracts, reports, technical literature, calculations, or drawings and showing the resulting decision.
Common miss: Saying a document was read or reviewed without explaining what was understood and how it affected the work. Independent minimum: 3.

Category 3: Project and Financial Management (Competencies 3.1-3.2)

This category tests the application of project-management and financial understanding to engineering work. Its required average is 2.0. A formal project-manager title is not essential; an applicant can demonstrate meaningful responsibility for scope, resources, changes, costs, options, contracts, or project economics within a technical role.

3.1: Project Management Principles

What it assesses: Applying project-management principles to scope, schedule, resources, change, stakeholders, and unforeseen issues. Evidence signals: Work planning, scope control, resource allocation, scheduling, change management, stakeholder expectations, design-option trade-offs, and risk-benefit decisions.
Common miss: Listing software, meetings, or administrative duties without a management decision, response, or consequence.

3.2: Finances and Budget

What it assesses: Understanding and applying the economic or financial aspects of a project or project element.
Evidence signals: Cost estimates, budgets, comparative cost studies, contract considerations, lifecycle costs, value decisions, design economics, and financial reporting.
Common miss: Saying a project stayed within budget without showing the applicant’s own analysis or cost-related decision.

Category 4: Team Effectiveness (Competency 4.1)

Because Category 4 contains one competency, its required category average of 3.0 is effectively the required result for 4.1. The example should show a meaningful team challenge and the applicant’s proactive contribution, not simply that several people worked together successfully.

4.1: Promote Team Effectiveness and Resolve or Mitigate Interpersonal Conflict

What it assesses: Promoting team effectiveness while managing, resolving, or mitigating interpersonal conflict professionally.
Evidence signals: Clarifying roles, facilitating collaboration, resolving disagreement, addressing difficult behaviour, mentoring, rebuilding trust, and restoring productive work.
Common miss: Describing routine teamwork, coordination, or leadership without a real interpersonal challenge, action, and outcome.

Category 5: Professional Accountability (Competency 5.1)

Category 5 also contains one competency, with a required category average and independent Canadian-environment minimum of 3. The example should show applied professional accountability: a limitation, ethical dilemma, liability concern, conflict of interest, or responsibility decision that required the applicant to act.

5.1: Professional Accountability [Canadian Environment]

What it assesses: Understanding professional limitations, ethics, conflicts of interest, liability, responsibility, and appropriate use of professional authority.
Evidence signals: Recognizing a limit, seeking qualified guidance, escalating an ethical issue, managing a conflict, protecting the public, documenting accountability, or addressing stamp-and-seal responsibility.
Common miss: Writing only that the applicant followed a code of ethics, with no real decision, dilemma, or consequence. International applicants should identify equivalent accountability in a Canadian work environment. Independent minimum: 3.

Category 6: Social, Economic, Environmental and Sustainability (Competencies 6.1-6.5)

Category 6 tests the broader public, regulatory, environmental, economic, and long-term effects of engineering work. The required category average is 2.0. One environmental-impact story cannot automatically cover all five competencies because protection, public benefit, regulation, application of sustainability, and promotion of sustainability ask different questions.

6.1: Protection of the Public Interest

What it assesses: Understanding how engineering work affects the public and how safeguards must respond to public behaviour and project conditions.
Evidence signals: Identifying public impacts, protecting users or communities, assessing access and behaviour, mitigating adverse effects, and revising safeguards as conditions change.
Common miss: Discussing worker safety only, without the broader public-interest dimension.

6.2: Benefits of Engineering to the Public [Canadian Environment]

What it assesses: Applying knowledge of public impact, public input, and the benefits engineering work provides in a Canadian-equivalent environment.
Evidence signals: Public engagement, responses to concerns, feasibility or impact studies, accessibility decisions, service improvement, and clear communication of project benefits.
Common miss: Making a generic claim that a project helped society without showing the benefit, input, decision, or result. International applicants should identify an equivalent Canadian public benefit. Independent minimum: 2.

6.3: Role of Regulatory Bodies

What it assesses: Understanding why regulatory bodies exist and how their requirements protect the public and environment and shape engineering practice.
Evidence signals: Regulator interaction, permit or approval decisions, interpretation of protective purpose, compliance strategy, and changes to work based on regulatory responsibility.
Common miss: Naming a regulator, licence, or permit without explaining its protective role or influence on the applicant’s work.

6.4: Application of Sustainability Principles

What it assesses: Considering and applying sustainable options in professional work, structures, processes, operation, and maintenance.
Evidence signals: Resource efficiency, environmental effects, lifecycle, maintainability, resilience, component life, sustainable alternatives, and trade-off evaluation.
Common miss: Adding a sustainability statement after the design rather than showing how sustainability affected a choice.

6.5: Promotion of Sustainability

What it assesses: Promoting the application of sustainability principles through recommendation, influence, implementation, or advocacy.
Evidence signals: Persuading stakeholders, proposing a better option, establishing a practice, influencing criteria, sharing lessons, or implementing sustainable change.
Common miss: Repeating the 6.4 example without showing promotion, influence, or action beyond personal consideration.

The Eight Canadian-Environment Competencies at a Glance

1.1	Regulations, codes, and standards	3
1.6	Safety in design and technical work	3
1.9	Quality assurance	3
2.1	Oral communication in English	3
2.2	Written communication in English	3
2.3	Reading and comprehension in English	3
5.1	Professional accountability	3
6.2	Benefits of engineering to the public	2

These eight are a subset of the 22 engineering competencies, not another category. For an applicant without direct Canadian experience, Canadian-equivalent evidence means identifying the relevant Canadian code, safety requirement, quality approach, professional expectation, communication setting, or public-benefit context and explaining a reasoned equivalency. Naming a Canadian standard after the fact is not a substitute for demonstrating the competency.

How to Choose Projects Across the 22 Competencies

Start with a project inventory rather than 22 empty answer boxes. List projects, dates, role, technical decisions, constraints, communications, stakeholders, results, and people who directly reviewed the work. Then map each project to the competencies for which it contains the clearest evidence.

1. Map projects by demonstrated action, not by words that happen to resemble a competency title.
2. Reuse a project only when it contains distinct decisions and outcomes for the different competencies.
3. Avoid forcing one flagship project into every category; breadth can make the record easier to assess.
4. Balance recent work, increasing responsibility, varied stakeholders, and different evidence types.
5. Check that every selected project appears in the WRVL with consistent employer, role, dates, and responsibilities.
6. Assign only a validator who directly knows the work used for that competency.

A useful mapping worksheet can contain columns for project, competency, evidence signal, personal decision, outcome, WRVL position, validator, Canadian-equivalent requirement, and likely evidence gap. It should remain a planning aid; it should not become an answer bank detached from the applicant’s own work.

How Indicators Should Shape, but Not Become, Your Answer

Use indicators to search your own experience. Select only those behaviours you genuinely demonstrated, then write a coherent Situation, several personal Actions, and an Outcome. The response should name the real decision, calculation, code, communication, conflict, review, or result that proves the competency.

Do not answer each indicator as an isolated bullet or copy a generalized phrase into the CBAT. APEGA asks for specific details and first-person ownership. The applicant’s job is to show why the work demonstrates the competency; the validator confirms accuracy and rates the work from direct knowledge.

How Category Scores Affect Readiness

Every engineering competency receives a self-rating on APEGA’s 0-5 scale, and validators provide their own ratings for assigned examples. The average within each category must meet the current minimum: 3.0 for Technical Competence, Communication, Team Effectiveness, and Professional Accountability; 2.0 for Project and Financial Management and for Social, Economic, Environmental and Sustainability.

The eight Canadian-environment competencies also have independent minimums. A high result in another competency cannot compensate for an unmet independent minimum. Scores should follow the evidence already written, not lead the writing. APEGA’s Board of Examiners considers academic credentials, relevant work history, demonstrated competencies, and validator feedback across the complete file.

Common Mistakes When Mapping APEGA Competencies

7. Using an old five-category guide or a pre-July-2026 mirrored document.
8. Mixing the 22 engineering competencies with the separate 29-competency P.Geo. framework.
9. Copying indicators or treating every indicator as mandatory.
10. Selecting a project by topic rather than by the applicant’s demonstrated action.
11. Writing team achievements without separating personal responsibility and judgement.
12. Confusing technical risk in 1.3 with safety in 1.6.
13. Confusing independent results verification in 1.5 with quality assurance in 1.9.
14. Using routine conversation, emails, or document handling for the communication competencies.
15. Describing ordinary teamwork for 4.1 without conflict mitigation or a team-effectiveness action.
16. Writing ethics theory for 5.1 without an applied limitation, dilemma, or accountability decision.
17. Repeating the same sustainability narrative for 6.4 and 6.5.
18. Naming Canadian equivalents without explaining their application to the example.
19. Assigning a validator who cannot directly confirm the work.

APEGA Competency Evidence-Gap Checklist

• I have a specific, genuine example for all 22 engineering competencies.
• Every example shows my personal Actions and a clear Outcome.
• I can distinguish the closely related technical and sustainability competencies.
• All eight Canadian-environment competencies contain explicit Canadian or reasoned equivalent evidence.
• Each category appears capable of meeting its required average.
• My examples align with the employers, roles, dates, and responsibilities in my WRVL.
• An appropriate validator directly knows each assigned example.
• No indicator, public sample, project fact, calculation, decision, validator, or result has been copied or invented.

When to Request Competency Mapping or Example Review

Professional support is useful when genuine experience is spread across many projects, several answers are repetitive or generic, Canadian-equivalent evidence is difficult to articulate, self-ratings appear stronger than the examples, or WRVL roles and CBAT evidence do not align.

The legitimate scope is to review and improve applicant-owned evidence: test relevance, clarity, personal ownership, competency fit, consistency, and validator readiness. It must not invent work, supply a fictional decision, contact validators as the applicant, submit confidential forms, or guarantee APEGA acceptance.

Frequently Asked Questions

1. What are the six APEGA competency categories?

They are Technical Competence; Communication; Project and Financial Management; Team Effectiveness; Professional Accountability; and Social, Economic, Environmental and Sustainability. These categories contain 22 engineering competencies in total.

2. How many technical competencies does APEGA require?

Category 1 contains 10 technical competencies, numbered 1.1 through 1.10. The full engineering CBAT contains 22 competencies across all six categories.

3. What is the difference between competencies and indicators?

A competency is the skill, knowledge, behaviour, or judgement APEGA assesses. Indicators are generalized examples that help an applicant recognize possible evidence and gaps.

4. Do I need to address every APEGA indicator?

No. APEGA states that achieving every indicator is not necessary, but the selected work example must demonstrate the competency. Copying indicator wording is not accepted.

5. Which APEGA competencies require Canadian-environment evidence?

The eight are 1.1, 1.6, 1.9, 2.1, 2.2, 2.3, 5.1, and 6.2. Competency 6.2 has an independent minimum of 2; the other seven have an independent minimum of 3.

6. Can international work experience satisfy the 22 competencies?

International experience may be relevant when it demonstrates the competency, appears consistently in the WRVL, and can be validated. For the eight designated competencies, the applicant must identify and explain the applicable Canadian-equivalent context.

7. Can I use one project for several competencies?

Yes, when the project genuinely contains distinct evidence for each competency. Each response should isolate different personal Actions and Outcomes rather than repeat the same narrative under new headings.

8. Can I use the same validator for several competencies?

Yes, if that validator directly reviewed and knows the work used in each assigned example and is suitable for the relevant category and professional context.

9. What score do I need in each competency category?

The required category averages are 3.0 for Categories 1, 2, 4, and 5, and 2.0 for Categories 3 and 6. The eight Canadian-environment competencies also have independent minimum scores.

10. Are the APEGA P.Geo. competencies the same as the P.Eng. competencies?

No. Engineering applicants use the 22-competency framework described here. New P.Geo. applicants use a separate 29-competency geoscience framework and should not reuse engineering counts, categories, or descriptors.

11. Can I copy an APEGA competency example from a PDF?

No. Public material can explain structure, but submitted situations, actions, decisions, calculations, employers, validators, and outcomes must come from the applicant’s own genuine and verifiable experience.