RCM Operations assessment - the certification gate

How the assessment is scored

The learner works the two scenarios below and is scored against the checklist in the next section. The gate, from Academy grounding, is:

• Practical score at least 80 out of 100 on the checklist.
• No critical error - the four auto-fail errors below override the score. A learner can hit 85 on the checklist and still fail if they commit one.
• Manager review - a manager confirms the learner's demo and validation reasoning, not just the written answers.

Score the checklist proportionally, but treat the critical errors as a hard gate: any one of them is an automatic fail and a re-sit, because each is the kind of mistake that loses a finance-literate customer's trust in a single sentence. The point of the assessment is not recall - it is whether the learner keeps the app honest under the pressure of a live call or a customer dispute.

Scenario 1 (Sales) - the live demo moment

Setup: You are demoing RCM Operations to a revenue-cycle leader and their CFO at an RCM provider. On Mission Control the top briefed signal is a payer with a large denial figure next to it. The CFO points at it and says: 'Good - so that is roughly what we will collect if we buy this.'

The learner must, in order: (a) correct the reading honestly on the spot; (b) say which value category the figure is and why; (c) show how they would drill to evidence to justify the priority; (d) reframe the number as a hypothesis with the owner and action named; (e) state the explicit limitation (seeded data; the app stops at an outcome hypothesis) without being asked.

What good looks like: 'That figure is recoverable or at-risk value, not collected cash - an opportunity if your team acts, which only a share of will be appeal-eligible and only a share of that won and collected. Let me show you why it is first' (drills to evidence) '...and here is the honest framing: if we appeal this cohort this week we protect this much recoverable value - that is the hypothesis; the cash is your validated result. And to be straight, this is seeded demo data and the tool deliberately stops at the hypothesis.'

Scenario 2 (CSM) - the validation and dispute moment

Setup: A customer's leader is about to present an RCM Operations figure to finance as a recovery result. The figure came from a report; finance has already queried it once. The customer asks you to confirm it is safe to present.

The learner must, in order: (a) run the source-scope-definition-freshness checks before endorsing anything; (b) identify the value category of the figure and whether it is a projection or a validated outcome; (c) check the figure is being carried with its scope and definition, not stripped into a slide; (d) decide and state whether it is safe to present, and if not, what must change; (e) name what escalates to the implementation specialist or product versus what is a CSM coaching fix.

What good looks like: the learner refuses to rubber-stamp, runs the four checks, catches that the figure is recoverable (not collected) and must be labelled as such, insists the scope and definition travel with it, and either clears it with the category labelled or holds it and escalates the specific gap - rather than letting the customer present an unvalidated or mislabelled number to finance.

The scored checklist (what a correct answer contains)

Award points across both scenarios (indicative weighting):

• Prioritisation handled as a starting point to verify, not a verdict - drills to evidence before acting (15)
• Correct value category named and kept separate - recoverable / billed / collected / capacity, never summed (20)
• Projection vs result stated - SLA risk / hypothesis framed as projection, not breach or banked result (15)
• Observed contribution vs proven causation - on any outcome, no causal overclaim (10)
• Scope and definition carried with the figure - nothing quoted stripped of context (10)
• Honest limitation stated out loud - seeded data, stops at hypothesis (10)
• CSM validation discipline - source, scope, definition, freshness run before endorsing (15)
• Correct escalation boundary - connection/mapping to implementation specialist, definition/logic/reconciliation to product (5)

Total 100. Pass at 80 or above, provided no critical error and a manager review.

Critical errors that auto-fail

Any one of these fails the assessment regardless of the checklist score, because each is a single sentence that loses customer trust:

• Presenting a projection as a result - calling an SLA at-risk flag a breach, or an outcome hypothesis an achieved recovery.
• Quoting recoverable or at-risk value as collected cash - the signature mistake, or summing the value categories into one 'opportunity'.
• Acting on the briefing without evidence - treating the prioritisation order as a proven verdict and skipping the drill-down.
• Quoting an unvalidated or mis-scoped figure as the customer's - endorsing a number for finance without source-scope-definition-freshness, or lifting a figure stripped of its scope.

A learner who does everything else well but commits one of these has not demonstrated the one thing the app exists to protect - honesty with a finance-literate buyer - and must re-sit. Note which error occurred so the re-sit targets it.