Guides

Tools for documenting competency examples in engineering

Published September 22, 2026 · Updated September 27, 2026

TL;DR. The best tools for documenting competency examples in engineering are the ones that help you collect evidence, write clearly, and track gaps before submission. For Canadian P.Eng applicants, that usually means a simple system made up of a spreadsheet or tracker, a document folder structure, a competency template, and a review process. If your examples are messy or too brief, the problem is usually not your experience. It is the way it is being recorded.

What are competency examples in engineering?

Competency examples are short, specific stories from your engineering work. They show how you applied technical knowledge, made decisions, handled risk, worked with others, and acted with professional judgment. In the Canadian P.Eng context, these examples are often used to demonstrate competency categories rather than just list job duties.

A strong example usually includes the situation, your role, the actions you took, and the result. It should show your own contribution clearly. That matters because assessors want evidence, not a project summary.

Why do engineers need tools to document competency examples?

Most applicants do not struggle because they lack experience. They struggle because their experience is spread across old emails, project files, meeting notes, and memory. Without a system, examples become vague, repetitive, or incomplete.

Good tools help you do three things. First, they help you capture evidence while the work is still fresh. Second, they help you organize examples by competency area. Third, they help you see where you still need stronger proof before you submit.

At Competency Based Assessment, this is the point where structure matters. A calm, guided workflow reduces revision cycles and makes it easier to move from rough notes to submission-ready competency cards.

What are the best tools for documenting competency examples in engineering?

The best setup is usually simple. You do not need a complex system. You need tools that fit the way engineers already work.

A spreadsheet tracker for listing each example, competency area, project name, date, and status.
A document template for writing each example in a consistent format.
A folder system for storing supporting evidence such as drawings, calculations, emails, and reports.
A review checklist for checking clarity, ownership, and relevance before submission.
A feedback platform if you want assessor-style comments and progress tracking in one place.

If you are using a guided platform like CBA Pro, these pieces can sit inside one workflow instead of being scattered across files and notes. That makes it easier to see what is done, what still needs work, and where a reviewer sees gaps.

How should you structure a competency example?

A good structure keeps the reader focused on your role. One common approach is:

Context. What was the project or problem?
Your responsibility. What were you accountable for?
Action. What did you do, decide, or change?
Result. What happened because of your work?
Reflection. What did you learn or how did you apply judgment?

This structure works well because it turns technical work into evidence. It also helps avoid a common problem. Many applicants write about the team outcome but forget to show their own contribution. A structured template keeps that from happening. When you move an example into your regulator’s system, fit it into the Situation / Action / Outcome fields and their character limits, for example 300 / 1,200 / 300 characters at APEGS, EGM, Engineers Nova Scotia and PEGNL, 400 / 1,800 / 400 at APEGA, and 300 / 1,650 / 300 on PEO’s PDF form.

Which digital tools work best for collecting evidence?

For most engineers, the best evidence tools are the ones already available. A shared drive, cloud folder, or project management system can work well if it is organized properly. The key is to save proof close to the example while the details are still easy to verify.

Useful evidence can include marked-up drawings, calculation notes, meeting minutes, inspection records, design change logs, emails confirming decisions, and photos where appropriate. Keep the file names consistent. For example, use project name, date, and document type. That makes later review much easier.

If you are preparing a P.Eng application, your evidence should support the competency example without overwhelming it. The example should stay readable. The documents should back it up, not replace it.

Can templates help with engineering competency examples?

Yes. Templates help because they reduce guesswork. When you use the same format for every example, you can compare examples side by side and spot weak ones quickly.

A good template should prompt you to explain the technical challenge, your decision-making, the standards or constraints involved, and the outcome. It should also leave room for reviewer comments. That is useful when you need to revise an example after feedback.

Competency Based Assessment uses structured checklists, competency cards, and document review panels to make this process more manageable. That matters when applicants have strong experience but need help expressing it in the right way.

How do you track progress across multiple competency examples?

Tracking matters because a P.Eng application is rarely one example at a time. You are usually building a full set of examples across several competency areas. Without a tracker, it is easy to overwrite one area and ignore another.

A simple tracker can show:

Which competency each example supports
Whether the example is draft, reviewed, or final
What evidence is attached
Whether the example needs more technical detail
Whether the example shows personal responsibility clearly

This is where progress bars and readiness reports are useful. They turn a long application into visible steps. If you want a clearer path, start with a free CBA assessment or review the CBA guide before you rewrite everything from scratch.

What mistakes do engineers make when documenting competency examples?

The most common mistake is writing too much about the project and too little about the engineer. Assessors need to see your judgment, not just the task list.

Another mistake is using vague language. Phrases like "I assisted with the project" or "I helped the team" do not show ownership. Strong examples use direct language. They explain what you decided, reviewed, designed, checked, or led.

A third mistake is waiting until the end to gather evidence. By then, details are often lost. A better method is to document examples as you go. That is why practical tools matter. They reduce memory gaps and keep your submission grounded in real records.

How can Competency Based Assessment help with documenting competency examples?

Competency Based Assessment is built for applicants who need structure, not guesswork. The platform helps organize examples, surface gaps, and show reviewer feedback in a clear format. That is useful if your first draft was rejected or if you are unsure whether an example is strong enough.

Instead of trying to interpret every comment alone, you can work through a guided remediation path. That is especially helpful for internationally trained engineers and EITs who may have strong technical experience but need help translating it into Canadian competency language.

If your submission needs targeted support, you can also review what to do when a P.Eng CBA is rejected or explore P.Eng CBA consulting for more direct feedback.

What is the simplest tool stack to start with?

If you want a practical starting point, use this:

One spreadsheet for tracking all examples
One folder for evidence files
One template for writing examples
One checklist for final review
One feedback source, ideally from someone who understands the P.Eng process

That is enough for most applicants to build a solid first draft. From there, you can move into a more guided system if you want faster revisions and clearer assessor-style feedback. If you are just getting started, the CBA P.Eng example page can help you see what a finished example looks like in practice.

What is the best format for documenting an engineering competency example?

The best format is a short structure that shows context, your role, your actions, and the result. It keeps the focus on your judgment and makes it easier for assessors to follow your contribution.

Should I use Excel or a document tool for competency tracking?

Use both if you can. Excel or a spreadsheet is good for tracking status and gaps. A document tool is better for writing and revising each example in detail.

What evidence should I save for engineering competency examples?

Save items that support your role, such as calculations, drawings, emails, reports, meeting notes, and change records. Keep only what helps prove the example. Do not overload the submission.

How many competency examples do I need for a P.Eng application?

You write one example per competency: 34 at PEO, EGBC, APEGS, EGM, Engineers Nova Scotia, APEGNB, Engineers PEI and PEGNL, and 22 at APEGA (whose CBA NAPEG and Engineers Yukon applicants also complete). Quebec’s OIQ uses a different, supervisor-based evaluation. Each example needs clear, specific evidence from your own work.

Can I reuse one project for multiple competency examples?

Yes. One project can support several competencies if each example shows a different skill, decision, or responsibility. Just make sure the examples are distinct and not repetitive.

What if my competency examples are too short or vague?

That usually means you need a better structure and more specific evidence. Start by adding your role, the technical context, the decision you made, and the result. If needed, get reviewer feedback before submitting again.