CMBB common mistakes
CMBB · Understand the traps and how to avoid them.
Writing about facilitation techniques or learner-centred design without ever naming a body of knowledge, standard, or competency framework that the teaching is anchored to, leaving the assessor unable to see a defensible curriculum rationale.
Candidates with strong delivery experience assume that good classroom practice is self-evidently professional and skip the step of mapping activities to a recognised standard, because in their day job nobody asks them to justify the syllabus on paper.
What to do instead
For each teaching example, add one sentence naming the framework or standard the content aligns to, one sentence on how you sequenced topics to build from simple to complex, and one sentence on how you checked the learning actually landed (assessment method, pass-rate data, or observation). Build a personal template with those three slots and reuse it for every teaching entry.
Describing a single training session the candidate personally delivered instead of the wider teaching role, so the entry reads as an anecdote about one afternoon rather than evidence of sustained instructional responsibility.
The most vivid memory is usually the best-received workshop, and candidates reach for narrative colour rather than scope; they also underestimate how much assessors weigh duration, cohort size, and repeat delivery.
What to do instead
Open each teaching entry with a scope line: number of cohorts, total contact hours, learner profile, and whether you owned the syllabus or inherited it. Then use the anecdote as supporting detail inside that frame, not as the frame itself.
Presenting coaching as advice-giving: the entry describes telling a junior colleague what to do and how it worked out, with no evidence of the coachee setting their own goal, no agreed actions, and no follow-up review.
Day-to-day workplace coaching is informal and directive, so candidates transcribe what actually happened without recognising that the exam distinguishes coaching (non-directive, goal-owned by the coachee) from instructing or mentoring.
What to do instead
Rewrite each coaching entry around a four-part cycle: the coachee's self-identified goal, the questions or structure you used to help them think it through, the actions they committed to, and the review date and outcome. If you genuinely only advised, label it as mentoring or technical instruction instead of forcing it into the coaching box.
Claiming coaching or mentoring impact with no measurable outcome and no third-party corroboration, e.g. 'the individual improved significantly' with nothing to back it.
Confidentiality instincts and the absence of formal records make candidates vague, and they assume the assessor will take the relationship at face value.
What to do instead
Attach one concrete indicator per relationship: a qualification achieved, a promotion or role change, a reduction in error rate, a shortened time-to-competence, or a signed statement from the coachee or their line manager. Where numbers are impossible, quote a specific behavioural change with a date.
Confusing mentoring with coaching and using the two terms interchangeably across the submission, so the same activity is described as both in different sections.
In many organisations the words are used loosely, and candidates mirror their employer's vocabulary without checking the exam's definitions.
What to do instead
Adopt a working distinction and state it once near the start: mentoring as longer-term development drawing on the mentor's experience and network, coaching as a structured, time-bound, goal-focused conversation. Then audit every entry and relabel any that sit on the wrong side of your own line.
Recounting occupational experience as a job description or CV chronology ('responsible for', 'involved in') rather than as evidence of personal accountability for decisions and their consequences.
Candidates copy from their CV because it is quick and already written, and they underestimate how strongly assessors look for ownership verbs and outcome statements.
What to do instead
Convert every bullet to a decision-outcome pair: what you decided, what constraint you weighed, what happened as a result, and what you would change. Delete any sentence that could have been written by your manager about your role rather than by you about your actions.
Omitting the responsibility dimension of occupational experience: no mention of budget, safety, regulatory compliance, staff supervision, or the consequences of failure.
Technical specialists see their craft as the substance of the role and treat duty of care as background context that needs no stating.
What to do instead
For each role, write one line on each responsibility axis that applies: people (how many, at what level), money (size of budget or commercial exposure), compliance (which regime, what audit history), and safety or risk (what could have gone wrong and how you controlled it). Include at least one example where you carried the consequence of a failure, not just a success.
Describing technical work at the level of activity rather than innovation: the entry explains that a new system was implemented, but never isolates what was novel, what problem the existing approach could not solve, or what changed as a result.
Candidates equate 'new to my employer' with innovation and assume the assessor will infer novelty from the description of the project.
What to do instead
Use a four-line structure per technical claim: the limitation of the prior approach, the specific change you devised or introduced, the evidence it worked (metric, trial result, adoption), and the extent to which it has been reused or recognised beyond your own team.
Overstating technical depth by listing tools, standards, and acronyms without demonstrating understanding of trade-offs, failure modes, or limits of the approach.
Keyword lists feel like coverage and are easy to assemble from a job spec, and candidates fear that admitting limits will weaken the claim.
What to do instead
For each technology or method claimed, add one sentence on when it is the wrong choice and one on how you would know it is failing. Depth is demonstrated by the boundary of your knowledge, not the breadth of your vocabulary.
Leaving the submission unbalanced: heavy on technical achievement and thin on teaching, coaching, and mentoring, or the reverse, so one domain is effectively unevidenced.
Candidates naturally write most where they feel most competent, and they run out of time before reaching the domains they find harder to document.
What to do instead
Before writing, allocate a target number of evidence entries per domain and draft the weakest domain first while energy is high. Then run a cross-check table mapping each domain to its entries and minimum evidence count, and fill gaps before polishing prose in the strong areas.