If you’ve started preparing for CPA Canada’s Common Final Examination, you’ve probably heard the term “Assessment Opportunity” — or just “AO.” It shows up in marking guides, debrief sessions, Capstone 2 workshops, and every piece of CFE advice out there. But most candidates don’t fully understand what an AO is, how it’s scored, or what it means for their study strategy.

This guide covers AOs from first principles. Whether you’re early in Capstone 2 or deep into your final study push, understanding AOs at a structural level will change how you prepare.

What is an Assessment Opportunity?

An Assessment Opportunity is a single, scoreable issue embedded within a CFE case. It’s the atomic unit of your CFE score. When CPA Canada says the exam tests your competence, they mean it tests your response to AOs — not your response to the case as a whole.

A typical Day 2 or Day 3 case contains between 4 and 6 AOs, though some have more. Each AO targets a specific competency area — Financial Reporting, Strategy & Governance, Management Accounting, Audit & Assurance, Finance, or Taxation — and your response to that AO is scored independently on a defined scale.

The case itself is the vehicle. The AOs are the test.

How are AOs scored?

Each AO is scored on a five-level scale:

Not Addressed (NA): You didn’t attempt the issue at all. Either you missed it entirely or your response addressed something different.
Not Competent (NC): You identified the issue but your response was superficial, incorrect, or lacked meaningful analysis.
Reaching Competent (RC): You demonstrated some relevant analysis but didn’t go deep enough. The right direction, but insufficient depth or missing case-specific application.
Competent (C): You provided a solid analysis that addressed the issue with appropriate depth and applied it to the case facts. This is the target for most AOs.
Competent with Distinction (CD): You exceeded the expected depth. Your analysis was thorough, well-structured, and demonstrated superior understanding.

Understanding the difference between RC and C is critical. RC is the most common “near-miss” score. It typically means you identified the issue and started the right analysis — but either didn’t quantify when you should have, didn’t tie your conclusion to specific case facts, or didn’t go far enough in your recommendation.

How do AOs map to the competency areas?

Each AO is tagged to one of the six CPA competency areas. Across the three-day exam, the AOs are distributed such that every competency area is tested — but not equally. Financial Reporting and Management Accounting tend to have the highest AO counts because they overlap with most case scenarios. Finance and Tax may have fewer AOs overall, which makes each individual score in those areas more consequential.

Here’s why this matters: if you only have 3–5 Finance AOs across the entire exam and two of them are NC, your entire Finance competency is at risk. In competencies with fewer AOs, every score counts more. This asymmetry is one of the reasons candidates fail despite feeling like they “did well” — a couple of NCs in a low-volume competency can tip the result.

How many AOs are on the CFE?

The exact count varies by year, but a reasonable estimate is:

Day 1: Typically a single long case with a broad strategic scenario. Scoring is holistic rather than AO-by-AO, focused on Strategy & Governance.
Day 2: One long case with approximately 8–12 AOs, usually emphasizing your chosen role (Assurance, Performance Management, Tax, or Finance) plus cross-competency AOs.
Day 3: Two medium cases, each with 4–6 AOs. More variation in competency coverage.

Across the full exam, a candidate might encounter 20–30 AOs. That’s your entire score. Twenty to thirty individual data points across six competency areas, scored on a five-level scale. There’s no room for systematic weakness — a pattern of NCs in any single competency area can fail you even if every other area is strong.

Why case-level tracking misses the point

Most candidates track their practice at the case level: “I wrote Case 83-2 today and felt okay about it.” This is nearly useless as a study signal.

A case might contain an FR AO where you scored C, an AA AO where you scored NC, and a Tax AO where you scored RC. Saying you “felt okay” about the case means nothing — you passed one thing, failed another, and almost-passed a third. The only way to understand your actual readiness is to decompose the case into its AOs and score each one individually.

This is what AO-level tracking means: instead of one data point per case (subjective feeling), you get 4–6 data points per case (objective scores by competency). After 15 cases, you don’t have 15 data points — you have 80–100, organized by competency, ready to reveal patterns.

What patterns should you look for?

Once you have AO-level data across 10–15 cases, three patterns become visible:

1. Competency clusters

Some competency areas will consistently score higher than others. If your FR AOs are mostly C/CD and your AA AOs are mostly NC/RC, that’s not random — it’s a signal. Your study time should shift toward the weak clusters.

2. NA gaps

NAs mean you missed the issue entirely. If you have NAs concentrated in a specific competency area, it usually means you’re not recognizing the triggers for those issues in the case facts. This requires a different fix than NC — you need to practice identifying the issue before you can practice analyzing it.

3. RC plateaus

If you have a competency area where your scores cluster at RC and aren’t converting to C, you have a depth problem. You’re seeing the issues and starting the right analysis, but you’re stopping too early. The fix is usually: quantify more, reference specific case facts, and carry your analysis through to a recommendation.

AO-level tracking in practice

Here’s what effective AO-level tracking looks like as a study routine:

After writing each practice case: Open the marking guide. For each AO in the case, honestly assess which score level your response hit. Don’t be generous with yourself — if you’re between RC and C, call it RC. Enter the AO with its competency tag and score.

Weekly: Review your score distributions by competency. Look at the heatmap. Are any competencies showing NC/NA clusters? Are any showing an RC plateau? What’s improved since last week?

When choosing your next case: Don’t just grab the next one in the stack. Pick cases that emphasize the competency areas where your scores are weakest. If AA is your problem, find AA-heavy cases.

This is the debrief loop that separates candidates who improve from candidates who just accumulate case count.

How Competent helps

Competent was built specifically around AO-level tracking. You log each case by entering its AOs, each tagged to a competency area and scored. The app immediately updates:

A heatmap showing your score distribution across all six competency areas
Trend lines showing how each competency’s scores are changing over time
Weakness flags that scan your recent cases and warn you about NC clusters or neglected competencies

The whole debrief takes about three minutes per case. The free tier includes 10 cases — enough to build the habit and see your first patterns. After that, $29 CAD (one time, no subscription) unlocks unlimited tracking.

The bottom line

Assessment Opportunities are not an exam implementation detail — they are the exam. Your CFE result is the sum of your AO scores across six competency areas. If you can see those scores, you can improve them. If you can’t see them, you’re studying blind.

Track at the AO level. Every case, every time.

What Is a CFE Assessment Opportunity (AO)? A Complete Guide