Hello world!

Welcome to WordPress. This is your first post. Edit or delete it, then start writing!

After more than 36 years practising engineering across Canada, the GCC, and Egypt, I have reviewed a lot of technical documents. Few frustrated me like the Competency-Based Assessment — not because it exists, but because of who it filters out.

The pattern I kept seeing

Colleagues and mentees — engineers I would trust with real structures and real budgets — were receiving “insufficient evidence” letters. When I read their submissions, the problem was never the engineering. It was structure: team language instead of personal action, duties instead of stories, outcomes never stated. Capable engineers were being turned away at the CBA stage over writing, and most of them had no one to tell them that.

What PengCBA does differently

• Every submission is reviewed by a licensed P.Eng. — not a copywriter, not a generalist editor.
• Every example is built on the SAO framework assessors are trained to score.
• We work per-association. PEO’s 34 competencies, APEGA’s 22, EGBC’s framework — each gets its own mapping, not a generic template.
• Confidentiality is structural, not a slogan. Your intake details, documents, and drafts are stored securely, accessible only to you and your assigned reviewer, and never shared with third parties.

The honest promise

No one can guarantee a regulator’s decision — and you should walk away from anyone who claims otherwise. What I can promise is that your submission will be properly structured, competency-aligned, and reviewed by a licensed Professional Engineer before it goes anywhere near an assessor. That is what our 98% approval rate is built on.

If you would like to talk through your situation, the intake form is free and we reply within one business day. You can also read more about our team or browse all articles.

There is no single path to an approved CBA — that is why we offer four service levels. But the outcomes converge: across our client base, 98% of submissions are approved. Here is what that looks like through three different packages.

Sophie L. — Environmental EIT, EGBC (Guided 1-on-1 Coaching)

Sophie booked coaching convinced her examples were too ordinary. Two sessions in, we mapped her experience against EGBC indicators and found stronger material she had overlooked. “The coaching sessions helped me realize I had stronger examples than the ones I originally picked. Worth every session.”

Rajiv P. — Mechanical EIT, APEGA (Expert Draft Review)

Rajiv’s draft was well written — and scored like a team report. Our line-by-line review flagged exactly where he described team outcomes instead of personal actions. “The review caught exactly where I was describing team outcomes instead of my own actions. Fixed those five examples and resubmitted with confidence.” Approved.

Amara T. — Civil EIT, PEO (Full-Service Writing)

Three failed solo attempts, then a full structural rebuild — read her full story here. Approved on the next submission.

What the 98% is made of

No guarantees — no ethical provider can promise a regulator’s decision. What the number reflects is process: story selection against indicators, SAO structure on every example, validator strategy, and a licensed-P.Eng. review before anything is submitted. The same process is available at every price point, from the $149 DIY Toolkit upward. See full pricing or start your intake form.

Client story, shared with permission. Civil EIT, licensed via PEO — Full-Service CBA Writing.

The situation

Amara had everything an assessor should want: four years on municipal infrastructure projects, design and construction exposure, a supportive supervisor. She also had three failed CBA submissions behind her when she found PengCBA.

What was going wrong

Her drafts told the story of impressive projects — but not of Amara. Paragraphs opened with “the project team,” actions were listed as responsibilities, and outcomes stopped at “the project was completed successfully.” Each resubmission polished the prose without changing the structure, and each came back with the same verdict.

What we did

In the intake interview, we mapped her experience against all 34 competencies and found something important: her best examples were not the ones she had chosen. A small stormwater design she dismissed as “routine” demonstrated independent technical judgment far better than the flagship project she had led with.

We rebuilt her submission around nine stories selected for indicator coverage, interviewed her to extract the personal decisions inside each one, and drafted every example in strict Situation–Action–Outcome form with named methods, codes, and quantified results.

The result

Approved on the next submission. In her words: “Having someone who actually understood how assessors read these examples made all the difference.”

If you recognize your own drafts in her “before” picture, start with a free consultation — or read why assessors reject good engineers to diagnose the pattern yourself first.

Few letters sting like a CBA rejection after months of work. Take a breath: most “insufficient evidence” outcomes are recoverable, and many of our approved clients arrived holding exactly that letter.

Step 1: Decode what the letter actually says

Association letters are bureaucratic but precise. Highlight every competency named, and note the verbs: “insufficient detail” usually means your actions were vague; “does not demonstrate” means the example targeted the wrong indicator; “validator could not confirm” is a verification problem, not a writing problem.

Step 2: Separate the three failure types

• Structure failures (most common): right experience, wrong presentation. Fixable by rewriting into SAO form.
• Mapping failures: good example filed under the wrong competency. Fixable by re-tagging and light edits.
• Evidence failures: the experience genuinely does not show the competency. This needs a different story from your history — most applicants have more usable material than they think.

Step 3: Respect the resubmission window

Associations give a deadline for additional information. Work backwards from it: one week to inventory stories, one to two weeks to rewrite, one week buffer for validator re-verification if required.

Step 4: Get an outside read before resubmitting

You have already read your draft fifty times — you are the least qualified person to spot its remaining gaps. This is exactly what our Complete Revision Service (CAD $500, 1–2 weeks) was built for: a full indicator-by-indicator evaluation with an actionable revision guide. Many clients come to us after one or more failed attempts — including Amara, who was approved on the submission after hers.

If we could fix only one thing in every CBA draft we see, it would be this: applicants describe team outcomes when assessors score personal actions.

Why “we” scores zero on the CBA

The Competency-Based Assessment exists to determine whether you can practise engineering independently. “We redesigned the cooling system” tells the assessor nothing about your competence — for all they know, you booked the meeting room.

Before: how most CBA drafts read

“Our team was responsible for the HVAC redesign of a 12-storey office tower. We analyzed the existing system and implemented a new VAV design. The project was completed on schedule and the client was satisfied with the energy savings.”

Impressive project. Unscorable paragraph. No personal action, no method, no quantified outcome.

After: the same experience, SAO-structured

Situation: “In March 2024, as the mechanical designer on a 12-storey office tower retrofit, I found the existing constant-volume system exceeded the client energy target by an estimated 22%.”

Action: “I modelled three alternatives in eQUEST, selected a VAV system with demand-controlled ventilation, sized the terminal units for each zone using ASHRAE 62.1 airflow requirements, and presented the lifecycle cost comparison that got the $180K upgrade approved.”

Outcome: “The design was issued for construction with zero RFIs on the mechanical scope, and post-occupancy metering showed a 19% energy reduction in year one.”

The SAO pattern to copy in your own examples

First person. Named tools, codes, and standards. Numbers wherever they exist. Your decision, your analysis, your result. This is the exact transformation our Expert Draft Review applies line-by-line across your whole submission — book a free consultation to have one of your own examples assessed.

Some of the most capable engineers we have ever worked with came to us holding a “more information requested” letter. They designed real structures, commissioned real plants, managed real budgets. So what went wrong with their CBA?

Assessors do not score your career — they score your paragraphs

An assessor cannot see your decade of experience. They can only see the 200–400 words you wrote for each competency, read against a rubric. When those words are vague, the score is low — even if the underlying work was exceptional.

The five CBA rejection patterns we see most

1. “We” instead of “I.” Team achievements described without isolating your personal action. Assessors cannot score what the team did.
2. Job descriptions, not stories. “Responsible for structural design of residential towers” is a duty, not evidence. Assessors need one specific tower, one specific decision.
3. No engineering depth. Outcomes without method: “the design was approved” — but which code, which load case, which check?
4. Missing outcome. The action is described, but the result — approval, savings, failure caught — is never stated.
5. Wrong example for the indicator. A project-management story filed under a technical competency, scored against indicators it never addresses.

The fix for a rejected CBA

Every rejected pattern above is a writing and structure problem, which means it is fixable — usually in one review cycle. Our Red Flag Sanity Check (CAD $299, 5–7 business days) exists precisely for this: we identify the exact patterns above in your draft before the assessor does. Read the FAQ for timelines and what you get back.

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.