CFM common mistakes
CFM · Understand the traps and how to avoid them.
Treating every facility maintenance task as corrective and reacting to breakdowns instead of assigning work to preventive, predictive, or condition-based categories with defined triggers.
Candidates learn maintenance through day-to-day firefighting and never internalise the work-type taxonomy (reactive, preventive, predictive, condition-based, deferred), so they misclassify scenarios and pick the reactive answer under time pressure.
What to do instead
Build a one-page decision tree: is the asset still functional, is there a schedule or condition threshold, and does the trigger come from time, usage, or measurement? Drill 20 scenario stems and label the work type before reading the options.
Choosing a project schedule response (crash, fast-track, re-baseline) before checking whether the scenario's variance is on the critical path or whether float exists.
Candidates memorise schedule-compression techniques as standalone fixes and skip the network-logic step, so they recommend crashing non-critical activities that cannot shorten the project.
What to do instead
For any schedule question, first write the critical path and total float for the affected activity. Only then eliminate options: crashing non-critical work, resource leveling that extends duration, and re-baselining before exhausting float are wrong answers.
Reading a variance as favourable or unfavourable from the sign of the number alone, without anchoring to the budget baseline and the cost-versus-schedule direction convention.
Candidates conflate cost variance and schedule variance signs, and forget that earned value ratios (CPI, SPI) are interpreted relative to 1.0, not relative to zero, so they invert the conclusion.
What to do instead
Before answering, write the four formulas and the decision rules: CV = EV − AC, SV = EV − PV, CPI = EV/AC, SPI = EV/PV; negative variance and ratio below 1.0 are unfavourable. Apply the rule mechanically to each numeric stem.
Answering leadership scenarios with a directive or autocratic action when the situation calls for situational leadership matched to follower readiness or team maturity.
Candidates default to the decisive-sounding option because it reads as strong management, ignoring the readiness cues (new hire, low competence, high commitment) embedded in the stem.
What to do instead
Scan the stem for follower readiness signals and team development stage. Match: low readiness to directing, moderate to coaching, high readiness to delegating. Reject options that ignore the stated maturity level regardless of how confident they sound.
Blaming the individual for an error instead of tracing the human-factors chain (workload, interface design, procedure clarity, fatigue, communication breakdown) that produced the outcome.
Candidates apply a personal-accountability lens from general management and miss the systems view the exam expects, so they select disciplinary options over redesign or barrier options.
What to do instead
For every human-error scenario, list the contributing conditions before reading options: task demand, environment, equipment, procedure, and team communication. Prefer the option that changes the system or barrier over the one that retrains or disciplines the person.
Selecting the channel or medium that feels most efficient (email, memo) rather than the one matched to message complexity, audience, and need for feedback.
Candidates optimise for speed and habit, not for richness, so they miss that ambiguous, sensitive, or high-stakes messages require synchronous, high-feedback channels and documented confirmation.
What to do instead
Classify the message first: routine and factual goes lean and written; complex, sensitive, or consequential goes rich and interactive with a feedback loop. Then pick the option that includes confirmation of understanding, not just transmission.
Treating quality as inspection at the end of the process rather than as prevention built into design, procurement, and execution, and misapplying the cost-of-quality categories.
Candidates equate quality with checking finished work and cannot distinguish prevention, appraisal, internal failure, and external failure costs, so they choose rework-heavy options as 'quality control'.
What to do instead
Memorise the four cost-of-quality buckets with one example each and a rule: prevention and appraisal are conformance costs, failure costs are nonconformance. In scenarios, prefer the option that shifts spend upstream toward prevention and design review.
Evaluating a property decision on first-cost or headline rent alone, ignoring life-cycle cost, occupancy cost per unit area, lease structure, and total cost of ownership.
Candidates carry a capital-budgeting habit of comparing purchase prices and miss that property decisions turn on net effective cost, lease terms, operating expenses, and residual value over the holding period.
What to do instead
For any property scenario, compute or compare on a common basis: cost per square metre per year, net effective rent after concessions, and life-cycle cost including operations and renewal. Reject options that compare only acquisition price or face rent.
Recommending a technology deployment without first confirming data readiness, integration with existing systems, and a defined use case with measurable outcome.
Candidates are drawn to the newest tool named in the stem and skip the prerequisites, so they pick implementation options that fail on data quality, interoperability, or absent business case.
What to do instead
Apply a three-gate check before choosing: is there a defined problem and owner, is the data available and governed, and will it integrate with current platforms? Eliminate options that skip any gate, and prefer pilots with success metrics over enterprise-wide rollouts.
Confusing business continuity with emergency response, or writing a continuity plan that lists procedures but omits recovery time objectives, recovery point objectives, and dependencies.
Candidates treat continuity as an evacuation-and-response document and miss the recovery dimension, so they select options that address life safety only or that set no prioritised recovery targets.
What to do instead
Separate the two artefacts in your notes: emergency response covers life safety and immediate stabilisation; continuity covers prioritised functions, RTOs, RPOs, dependencies, and alternate arrangements. In scenarios, choose the option that names a recovery objective or dependency, not just a response action.