CBA Rejected or More Information Requested? Your Recovery Plan

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.