Why Assessors Reject Good Engineers (It Is Almost Never the Engineering)

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.