Guides

Competency indicators for engineering assessments | Competency Based Assessment

Published August 12, 2026 · Updated September 27, 2026

TL;DR: Competency indicators are the example tasks your regulator publishes under each competency to show what evidence demonstrates it. Assessors use them to judge whether an engineering applicant has enough real-world experience, judgment, and responsibility. Examples that meet them convincingly show clear role ownership, technical decision-making, safety awareness, ethics, communication, and measurable results. If your examples do not show what you did, why you did it, and what changed because of your work, they usually read as weak.

For many P.Eng. applicants, the hardest part is not having experience. It is showing that experience in a way an assessor can evaluate. That is where competency indicators matter. They turn broad claims like “I led a project” into evidence that your work meets engineering expectations.

At Competency Based Assessment, we see this gap often. Applicants have solid engineering backgrounds, but their drafts do not yet show the right signals. A strong submission makes those signals easy to find. It helps the reviewer see competence, not guess at it.

What are competency indicators in engineering assessments?

In the P.Eng. competency-based assessment, indicators are the published list of typical tasks under each competency: the kind of evidence the regulator expects an example to contain. The shared national system publishes a generic set for all 34 competencies, EGBC adds discipline-specific sets (for example civil municipal, electrical, structural and software), and APEGA publishes its own for its 22 competencies. One indicator under competency 4.1, for instance, is “Demonstrate respect for others’ responsibility and expertise”. Our guide to indicators in the CBA shows where each regulator publishes its lists.

In your write-up, indicators become the proof points behind a competency claim. They are not the claim itself. They are the facts that support it.

For example, saying you “managed a design change” is too broad on its own. A competency indicator would explain that you identified the technical issue, compared options, assessed risk, consulted stakeholders, updated drawings, and confirmed the final solution met code and client requirements. That is the kind of detail assessors can evaluate.

These indicators matter because engineering licensure is based on trust. Reviewers need to see that you can apply engineering judgment, work within limits, and protect public safety. Good indicators make that visible.

Why do assessors rely on competency indicators?

Assessors cannot see your day-to-day work. They see your written examples and your validators’ ratings and comments. So they look for indicators that connect your experience to the competency being tested. This is why vague language often leads to revision requests.

They are usually looking for evidence of:

your specific role in the task
the engineering problem or constraint
the actions you took and why
the standards, codes, or methods you used
the result, outcome, or impact
your judgment, not just your participation

These markers help separate passive involvement from professional engineering practice. A person can attend meetings, assist a senior engineer, or collect data without demonstrating competence. Competency indicators show where your own decisions and responsibility begin.

What are the most important competency indicators for engineering assessments?

Different regulators and assessment systems use different wording, but the core indicators are similar. You don’t need to cover every indicator on the official list, and APEGA asks you not to copy their wording; the signals below are what make those indicators convincing. A strong engineering assessment usually shows the following.

Technical problem solving. You identified an issue, analyzed options, and selected a solution based on engineering reasoning.

Engineering judgment. You made decisions with incomplete information, balanced trade-offs, and explained why your choice was appropriate.

Responsibility and ownership. You were accountable for part of the work, not just present for it.

Safety and risk awareness. You considered public safety, code compliance, reliability, or failure modes.

Communication. You explained technical issues clearly to clients, colleagues, contractors, or non-technical stakeholders.

Project or task management. You planned work, tracked deadlines, coordinated inputs, or handled changes.

Ethics and professionalism. You recognized limits, escalated concerns when needed, and worked within your competence.

Results. Your work led to a measurable or practical outcome, such as approval, cost reduction, fewer errors, improved performance, or a resolved technical issue.

How do you write examples that show competency indicators?

The easiest way is to use a simple structure. Start with the situation, then explain your actions, then show the result. Keep your focus on your contribution.

A useful test is this. If someone removed your name from the example, would the reader still know exactly what you did? If not, the example is probably too weak.

Here is a better pattern:

What was the problem?
What was your role?
What engineering factors did you consider?
What action did you take?
What was the outcome?

For instance, instead of writing, “I worked on HVAC design for a commercial building,” you could write, “I calculated peak cooling loads, reviewed occupancy assumptions, compared two equipment options, and recommended a unit that met energy and space limits. I then coordinated the revision with the architect and contractor.”

That version contains several competency indicators. It shows technical analysis, judgment, communication, and responsibility. In the CBA itself, each example is written for one competency, so use the details that match the competency you are writing for.

What makes a competency indicator weak?

Weak indicators are usually too general, too team-focused, or too outcome-free. They may describe a project, but not your role in it.

Common weak patterns include:

“I helped with the design.”
“I attended meetings and learned a lot.”
“The project was successful.”
“I supported the senior engineer.”
“I was part of the team that solved the issue.”

These statements do not show what an assessor needs to see. They do not identify your decision-making, your technical reasoning, or the effect of your work. Without those details, the reviewer may mark the example as insufficient.

If you are unsure how your draft reads, compare it with examples of successful engineering competency assessments. Seeing strong examples side by side often makes the difference clear.

How can internationally trained engineers show competency indicators clearly?

Internationally trained engineers often have excellent experience, but the challenge is translating that experience into the format expected in Canada. The assessment is not asking you to prove you are a good engineer in general. It is asking you to prove specific competencies through clear evidence.

That means you should name the standards you used, explain the local or organizational context, and show how you adapted your work when conditions changed. If you were not the final approver, say so. If you worked under supervision, explain exactly where your own responsibility sat.

Most regulators also assess eight Canadian-environment competencies: 1.1 codes and standards, 1.6 safety, 1.9 quality management, 2.1–2.3 communication and 5.1 code of ethics (each at least 3), and 6.2 engineering and the public (at least 2). They replaced the old time-based Canadian-experience requirement at EGBC, APEGS, EGM, APEGNB, Engineers PEI, PEGNL and, since July 18, 2026, APEGA, and Engineers Nova Scotia accepts them in place of its 12 months in a Canadian environment. PEO applies the same minimums to six of them, which it calls professional standards competencies (1.1, 1.6, 1.9, 2.3, 5.1 and 6.2). Examples from outside Canada can count, but for the technical ones you must name the Canadian code, standard or practice that would apply and explain how. If one of these competencies falls short, the regulator may ask you to revise it, assign units of the online Working in Canada Seminar, or ask for more experience. Our guide to the 8 Canadian environment competencies shows how to write them from international experience.

Many applicants also benefit from understanding the broader path from EIT to licensure. The EIT to P.Eng journey in Canada explains how experience, validation, and professional practice fit together. That context makes it easier to write examples that match the assessment stage you are at.

How does Competency Based Assessment help identify the right indicators?

Competency Based Assessment is built to help applicants check their own drafts before they submit. The platform makes it easier to see whether an example contains the indicators assessors expect. That includes role clarity, technical depth, and outcome-focused writing. Your examples stay your own work: you write them, and you remain responsible for them.

Instead of guessing what is missing, you can review your draft against a structured set of expectations. That reduces revision risk and helps you fix weak spots before submission. For many applicants, that alone lowers stress.

If you are still shaping your report, how to write a CBA for P.Eng. application is a useful companion guide. It shows how to turn experience into a format that is easier for assessors to read.

What should you check before submitting your assessment?

Before you submit, read each example and ask whether it shows the right competency indicators. You should be able to point to the evidence for each one.

Is my role clear?
Did I explain the engineering problem?
Did I show my reasoning, not just my task list?
Did I mention safety, standards, or risk where relevant?
Did I show communication with others?
Did I include a clear result or impact?

If the answer is no to several of those questions, the example probably needs more work. A good submission does not try to sound impressive. It tries to be specific.

For applicants who want a broader view of common reporting styles, CBA vs traditional experience reporting can help explain why competency based writing feels different from a standard resume or project summary.

What is the difference between a competency claim and a competency indicator?

A competency claim says you have demonstrated a skill. A competency indicator is the evidence that proves it. The claim is the conclusion. The indicator is the detail that supports it.

How many competency indicators should one engineering example include?

Most strong examples show more than one indicator. A single story can demonstrate technical analysis, judgment, communication, and responsibility if it is written clearly and with enough detail. Remember that each example is written for, and rated against, one competency. A single project can support several competencies, but write a separate example, with its own Action and Outcome, for each.

Can team projects still show individual competency?

Yes, as long as you explain your own role. Assessors want to know what you personally did, how you contributed, and what decisions or actions were yours. Describe only your own actions: PEO’s August 2026 guide says not to describe work done by colleagues or your team.

Do competency indicators need to be technical only?

No. Technical ability matters, but assessors also look for communication, ethics, safety, leadership, and professional judgment. Engineering competence is broader than technical calculation.

Why do assessors ask for more detail even when the project was successful?

Success alone does not prove competence. Assessors need to see how you thought, what you did, and why your actions were appropriate. A good result without process detail is often not enough.

How can I tell if my example is strong enough?

Read it as if you were the assessor. If you can clearly identify your role, your reasoning, and your outcome, the example is likely on the right track. If it still sounds general, it needs more evidence.