(Posted July 2026)
You’re deep into your preparation to write the Common Final Examination (CFE). You’ve written dozens of practice cases. You’ve pored over past Board of Examiners reports and dissected every case debrief until the patterns start to feel predictable. It’s only natural for a strategic thought to creep in: “If I track the assessment opportunities (AOs) carefully, prioritize those tied to depth requirements, and save time on the rest, I can optimize my way to a pass.”
It feels smart. Efficient. Like you’re finally in control of this high-stakes exam.
In reality, this “gaming” mindset is one of the most common—and most reliable—ways candidates undermine their own success.
The CFE isn’t a puzzle designed for clever hacks. It’s a professional competency assessment built to reward consistent, balanced, case-specific competence under pressure.
We’ve debriefed thousands of responses, both passing and failing. The pattern is clear: candidates who try to outsmart the system frequently produce responses that fall short of the Board of Examiners’ expectations. Those who succeed treat every case as a learning opportunity, addressing what is asked in the requireds with professional judgment. Below are some of the most common “gaming” tactics we see—and why they almost always backfire.
Counting and Classifying AOs Like a Card Counter
Many candidates turn AO identification into a mental (or an actual) spreadsheet, assigning each required to a technical competency area as they read: “Okay, that’s Financial Reporting number three… Taxation two… this one feels like Audit and Assurance.”
Even experienced coaches cannot predict AO classification or distribution with certainty. A straightforward accounting issue might be tagged under Level 3 for the Assurance role on Day 2. Quantitative analysis, qualitative points, and an overall conclusion for a single decision could be one AO—or split into two AOs in the same or different technical competency area. You’re not counting visible cards; you’re guessing in the dark. For a clear breakdown of the CFE’s evaluation methodology across the 4 levels, see our blog “The CFE Evaluation Methodology”.
The real cost? That mental bandwidth spent tracking and classifying is stolen from deeper case analysis and stronger writing. Markers don’t reward tally sheets—they reward competent, balanced discussions.
Cherry-Picking Competencies on Day 2
Day 2 brings a recurrent question: “Level 2 only requires competence in either Financial Reporting or Management Accounting. Can I go all-in on my stronger area and skip the other on Day 2, and then recover on Day 3?”
It’s tempting logic, but it’s a high-risk gamble. You don’t know the full distribution of AOs across Day 2 and Day 3, nor what is coming at you on Day 3. Deliberately skipping one competency area on Day 2 can jeopardize not just Level 2 (in Financial Reporting or Management Accounting), but also overall breadth (Level 4 across all six technical areas, including FR and MA), depth in your elected role (Level 3) and sufficiency (Level 1). For example, pursuing the Finance role, you fully address FR requireds on Day 2 (getting enough Cs for Level 2 depth) but give minimal effort to MA requireds (risking NC/NA). You nail some Finance AOs for Level 3 depth (Day 2 only). However, Level 4 still demands RC in both FR and MA (and all areas) across Days 2 and 3. Day 3 often provides additional FR/MA AOs to help breadth and Level 2 depth—but if your Day 2 MA coverage was deliberately weak, Day 3 may lack sufficient opportunities to fully recover the gap you created, risking failure on Level 4 breadth (or even Level 2 if overall FR Cs fall short).
Prioritizing Day 3 Based on Perceived Performance
On Day 3, some candidates keep a running competency scorecard and allocate time based on how they “felt” about Day 2 and the first and/or second Day 3 case —deprioritizing areas where they believe they already shone.
This approach has two fatal flaws. First, your perception of strength is often unreliable; what felt like a solid discussion might have missed key issues or depth and breadth markers expect. Second, the CFE is a relative exam—your success ultimately depends on how your performance compares to other candidates in that sitting, as the Board of Examiners sets the passing standard each time based on pre-established expectations for entry-level CPA competence. Day 3 is brutally time-constrained, so spending time tracking perceived gaps and reallocating effort steals directly from planning and writing—the activities that actually pay off with scoring Reaching Competence (RC) and Competent (C) rankings.
Dodging “Obscure” or Uncomfortable Requireds
Every case has at least one curveball: a niche tax rule, an unusual assurance standard, or a quirky governance issue. Some candidates give it a token sentence (or skip it entirely) and redirect time to familiar requireds.
This almost never pays off. The bar for RC on those unusual AOs is typically pretty low—a thoughtful, case-integrated attempt is often sufficient for RC, which is all Day 3 requireds typically need. Skipping a required will result in a Not Addressed (NA) ranking, which creates an avoidable gap and contributes to failing at Level 1. Overcompensating elsewhere does not guarantee scoring a C and frequently disrupts balance and time management.
Applying Templated Responses from Prior Cases
You nail a practice case with a beautifully structured response—clear headings, reasonable pros and cons, and a crisp recommendation framework. It earns rave reviews of your study partner in marking and scores C. Naturally, you think: “This template worked wonders last time; I’ll just adapt it here—it’s the same type of issue.”
It feels efficient and proven. Why reinvent the wheel?
The problem: CFE case writers and the Board of Examiners are masters at crafting requireds that feel familiar but differ in subtle, critical ways—perhaps a shift in user perspective, a new strategic constraint, or an integration requirement that changes the entire direction. Forcing a prior template onto the current case often leads to misaligned analysis, missed parts of the required, and/or a generic discussion that doesn’t fully address what’s actually being asked.
Read the required carefully every time. Respond directly to the specific wording and case facts in front of you. A templated approach without adapting sacrifices the tailored, professional judgment the marker grid rewards candidates for the illusion of speed.
The Approach That Actually Works
Successful candidates don’t try to outsmart the exam—they execute a disciplined, repeatable process. They clearly identify each required, and then deliver exactly what is asked: a competent, professional discussion that integrates case facts, balances quantitative and qualitative analysis where relevant, and concludes with realistic, definitive recommendations. They also stick to a realistic time budget for that required and move on.
You don’t need exhaustive coverage or perfection. Reasonable, balanced competence is the goal. Treat every required as if it’s your only opportunity to demonstrate proficiency in that area. When you consistently apply this approach, breadth and depth emerge naturally across the case. Your competency rankings align without any guesswork about the marker grid.
This straightforward method is what produces a passing CFE performance.
The Bottom Line
The CFE tests whether you can think and communicate like a competent entry-level CPA under pressure. It’s not a game you win by counting, skipping or templating. The candidates who pass are the ones who follow the process and adapt to each case.
You’ve already invested months building real skills through deliberate practice. Trust that preparation. Stay balanced, manage your time sensibly, and let your competence speak for itself. That’s the only strategy that consistently works.
You’re closer than you think. Keep writing like the CPA you’re about to become. You’ve got this!