Applications

The twelve Time Champ applications, taught as customer value - what each answers and how to sell and adopt it. Each application now carries its screen-level workflows: how to drive the screen and read it without misinterpretation.

12 application overviews · 194 screen workflows

Time and Activity - Application Overview

Applied, reference and assessment

Concept · 30 minTime and Activity - Concepts and Key TermsTime and Activity is built on one idea: take the hour a customer pays for and break it down honestly into what was present, what was available, how the available time was used, and which cases deserve a look. This module gives the core concept, a plain-language glossary of the terms, how they chain together, and the single concept people most often get wrong.Reference · 30 minTime and Activity - Data and Setup ReferenceEvery attendance and utilisation figure in this app rests on two foundations: the signals feeding it (coverage and freshness) and the rules that classify those signals (the denominator and the thresholds). This reference maps both at app-logic level so a CSM can validate trust before interpreting, and a Sales rep can speak to setup honestly without over-claiming. Exact connectors, capture policy and retention are confirm-with-product.Reference · 30 minTime and Activity - Common MisinterpretationsAlmost every dispute in this app is a misread, not a bug. The same figure answers a narrower question than people assume, or depends on a denominator, a rule or a coverage level that was never agreed. This is the quick-reference: each misread stated as the wrong reading, why it is wrong, and the correct reading - grouped by theme and drawn from the app's own interpretation guardrails.Playbook · 45 minTime and Activity - CSM Adoption PlaybookAdoption of Time and Activity is not a login count - it is a manager review routine that runs on a cadence and ends in logged actions. This playbook turns the app's own value model (available hours, exceptions, follow-through) into a staged rollout you can start with a real account this month, with the risks named up front and the success measures taken from the app's grounding rather than invented.Demo script · 30 minTime and Activity - Sales Demo ScriptThis is the five-beat demo - question, screen, evidence, interpretation, next step - built for Time and Activity. The arc is one team's paid hour, from attendance to the exception a lead should act on today, with the utilisation denominator named explicitly and the output limit stated before the customer can misread it. Runnable in seven minutes in a live call against the demo lab.Troubleshooting · 30 minTime and Activity - Troubleshooting and EscalationWhen a Time and Activity number is challenged, the fault is usually in coverage, denominator or rules rather than in the data itself. This guide is organised by symptom. For each, it gives the likely causes at app-logic level, the first checks a CSM runs before touching the vendor, and the clear line where the problem stops being a validation task and becomes an escalation. No invented error messages or UI paths.Assessment · 45 minTime and Activity - Practical AssessmentThis is the certification-gate assessment for the Time and Activity app. The learner works realistic scenarios, is scored against a checklist of what a correct answer contains, and fails on any critical error regardless of score. Pass requires a practical score of 80 or more, no critical error, and manager review. The self-check items below are the actual assessment questions with model answers.

Employee Monitoring - Application Overview

Application · 60 minEmployee Monitoring - Application OverviewEmployee Monitoring provides the activity evidence layer - application usage, monitored work, classifications and capture policy - that the rest of the platform reads from. This module teaches reps to lead with a visibility use case and the capture-policy conversation rather than a monitoring feature tour, and teaches CSMs to validate coverage, classifications, access and employee communication before anyone draws conclusions from the data.Workflow · 15 minEmployee Monitoring: Time Tracker - OverviewThis is the home screen most managers open first, and the page you will demo most often. It answers one question in layers: for the team I picked, on the day I picked, who was present, how were the hours spent, and where is time leaking. Everything on the page is a different cut of that question.

Applied, reference and assessment

Work Output - Application Overview

Applied, reference and assessment

Concept · 25 minWork Output - Concepts and Key TermsBefore any screen makes sense, you need the model. Work Output is built on one idea: busyness is not delivery, and the only honest way to know whether paid teams are producing the expected work is to count completed work, give the count meaning with complexity and an agreed standard, filter it for quality, and price it. This module defines the terms that carry that model and shows how they chain - and names the one concept people most often get wrong.Reference · 30 minWork Output - Data and Setup ReferenceWork Output is only as good as what feeds it. This reference lists the data and config the app depends on and draws the line between what you can describe at app-logic level and what must be confirmed with product. It extends the app overview's validation routine into a checklist a CSM runs before any number enters a customer conversation, and it names the point at which the implementation specialist takes over.Reference · 25 minWork Output - Common MisinterpretationsWork Output is powerful precisely because it reduces delivery to a few sharp numbers, and sharp numbers are easy to misuse. This reference collects the recurring misreads drawn from the app's workflow interpretation checks and the grounding guardrails, organised by theme: counting and coverage, comparison and normalisation, standards and attainment, quality and cost, and projection versus value. Use it as a catch-sheet, not a lecture.Playbook · 40 minWork Output - CSM Adoption PlaybookThis is the CSM's runnable plan for getting Work Output adopted on a real account this month. It builds on the app overview's validation routine (completion definitions, source coverage, standards, quality) and turns it into a staged rollout with a milestone at each stage, named risks and counters, and a measurable definition of 'adopted'. The through-line is that Work Output only earns adoption when a manager changes a decision because of output evidence - not when the dashboards merely light up.Demo script · 30 minWork Output - Evidence-Led Sales DemoThis is a runnable script for a live call, built on the app overview's time-to-outcome-then-utilisation-versus-attainment story. It specifies the exact screens in order, the single value point to make on each, the limitation you say out loud, and the discovery questions the demo answers. The demo's power is the contrast between activity and output; its credibility is the discipline of keeping opportunity separate from realised value and projections separate from results.Troubleshooting · 30 minWork Output - Troubleshooting and EscalationWhen a Work Output number is challenged, the fault is almost always upstream of the screen - in coverage, completion definitions, standards, the quality filter, the denominator or a blended value type - not in the display. This guide gives a CSM a repeatable diagnosis per symptom that works from the bottom of the time-to-outcome chain up, and a clear point at which the problem belongs to the implementation specialist or product rather than to interpretation.Assessment · 45 minWork Output - Practical AssessmentThis is the certification assessment for Work Output. It gives two realistic scenarios the learner must work end to end, a scored checklist of what a correct answer contains, and the critical errors that fail the assessment regardless of score. The self-check items are the actual assessment questions with model answers. The bar is mastery of the signature guardrail - output is not activity, and opportunity and projection are not realised value - demonstrated in a live reading, not recited.

Work Understanding - Application Overview

Applied, reference and assessment

Concept · 30 minWork Understanding - Concepts and key termsThe core idea of Work Understanding is that a process is not a diagram someone drew - it is a shape you infer from observed work, carrying a confidence, against which you can localise where time is lost. This module gives the mental model and a plain-language glossary of the terms that recur across every screen (discovered workflow, variant, conformance, reference path, step time, waiting, friction, rework, detection confidence, coverage, opportunity vs released time), then chains them together and names the one concept people most often get wrong.Reference · 35 minWork Understanding - Data and setup referenceWork Understanding infers how work flows from captured signal. Its outputs are only as good as the signal feeding them: the activity capture that detects work, the taxonomy that maps detected work to processes, the reference path that conformance is measured against, and the coverage that bounds every finding. This reference lists those dependencies at app-logic level (specifics are 'confirm with product'), the apps it leans on, and the concrete checklist a CSM runs before trusting discovery, variants, conformance or friction - plus what to escalate to the implementation specialist.Reference · 30 minWork Understanding - Common misinterpretationsWork Understanding infers process shape and time loss from signal, which makes it unusually easy to over-read. This is the catalogue of its common misreads, grouped by theme: inference read as fact, friction read as proven waste, conformance read as a quality grade, waiting confused with handling, and opportunity reported as result. For each: the wrong reading, why it is wrong, and the correct reading. Use it as a pre-demo refresher and an in-call recovery tool.Playbook · 45 minWork Understanding - CSM adoption playbookWork Understanding is adopted when a customer stops acting on generated findings and starts running validated before/after experiments with named owners. This playbook stages that: a pilot that confirms detection confidence and taxonomy on one process, a team stage that establishes the finding-review habit, and a scale stage where improvement experiments become a standing routine. Throughout, the adoption risk is specific to this app - a customer treating an inferred, confidence-bounded finding as proven waste - so every stage counters that with the review discipline rather than more dashboards.Demo script · 40 minWork Understanding - Evidence-led demo scriptThis is the live-call demo script for Work Understanding. The story arc moves from 'you know it's slow but not why' to 'here is the observed flow, here is where the time sits, here is the one change we would validate first - with the evidence and the honest caveat'. It names the exact screens to show in order with the single value point each, the limitation to state out loud, and the discovery questions the demo answers. Built to run in about seven minutes with two drill-downs and one explicit limitation.Troubleshooting · 35 minWork Understanding - Troubleshooting and diagnosisMost Work Understanding problems trace back to the same few causes: thin capture coverage, low detection confidence, a taxonomy mismatch, an unagreed reference path, or a human reading an inferred hypothesis as a fact. This module organises the common symptoms, gives the likely cause and the first checks a CSM runs for each, and draws the escalation line. It describes everything at app-logic level - no invented error messages or UI paths.Assessment · 45 minWork Understanding - Certification assessmentThis is the practical assessment for the Work Understanding certification gate. It presents two realistic scenarios the learner must work through, a scored checklist of what a correct answer contains, and the critical errors that fail the assessment outright regardless of score. The self-check items are the actual assessment questions with model answers. The gate is the grounding standard: practical score at or above 80, no critical error, manager review.

Capacity Planning - Application Overview

Applied, reference and assessment

Concept · 30 minCapacity Planning - Concepts and Key TermsCapacity Planning rests on one idea: turn a demand projection into a defensible staffing requirement by applying stated, testable assumptions, then set that requirement against available capacity to expose the gap - read by skill and interval, not as a lump. This module defines the core concept, the eight or so terms you need to use the app fluently, how the concepts chain from demand to a sized requirement, and the single distinction (requirement versus execution) that trips people up most.Reference · 35 minCapacity Planning - Data and Setup ReferenceCapacity Planning is a computation, and its output is only as good as its inputs. The requirement is built from demand volume, handling standards, shrinkage and occupancy, service goals, skills, and the forecasting model - each of which is a setup choice that can be a validated customer figure or a silent default. This reference lists what the app consumes, what has to be configured, where it depends on other apps, and the validation gate a CSM runs before anyone trusts a plan. Exact sourcing, methods and connectors are 'confirm with product'.Reference · 30 minCapacity Planning - Common MisinterpretationsCapacity Planning produces numbers that look definitive but are projections and simulations layered on configurable assumptions. The predictable misreads cluster into five themes: projection versus result, simulation versus execution, the balance-versus-coverage trap, assumption-driven figures read as facts, and capacity versus cash. For each misread below: the wrong reading, why it is wrong, and the correct reading. Use this as a fast check before you present or defend any capacity figure.Playbook · 45 minCapacity Planning - CSM Adoption PlaybookCapacity Planning is adopted when a customer produces a capacity requirement they trust enough to act on - sized from their own validated inputs, with assumptions visible, reviewed on a cadence, and signed off by a named owner. It is NOT adopted because a login exists or a plan was generated once. This playbook stages the rollout from a single pilot queue to the full operation, names the risks that stall this app specifically (placeholder shrinkage, FTE-balance complacency, plan-as-execution confusion), and sets the metric and cadence that tell you adoption is real.Demo script · 40 minCapacity Planning - Evidence-Led Sales DemoThis demo proves one thing: Capacity Planning turns a buried, intuition-based headcount guess into a defensible requirement with its assumptions on the table. The arc moves from the customer's current pain (a single number nobody can defend) to a requirement read by skill and interval, to a what-if that shows how sensitive that requirement is, and closes on defensibility to finance. Every beat separates projection from result and simulation from execution. Runnable in roughly seven minutes with two drill-downs and one explicit limitation.Troubleshooting · 35 minCapacity Planning - Troubleshooting and DiagnosisMost Capacity Planning problems are not bugs; they are input or interpretation issues. A number looks wrong because an assumption is a placeholder; coverage looks fine but service misses because the total hid a skill/interval gap; a customer disputes a figure because they are comparing a requirement to an actual. This module organises the common symptoms, gives the first checks a CSM runs for each, and draws the line where diagnosis stops and the specialist takes over.Assessment · 45 minCapacity Planning - Certification AssessmentThis assessment puts the learner in two realistic situations - a sales defensibility demo and a CSM input-validation review - and scores whether they handle the app's core honesty distinctions. The self_check items ARE the assessment questions with model answers. A scored checklist defines what a correct response contains; the critical-error list defines what fails the learner outright regardless of other points. Tied to the certification gate from grounding: practical score at least 80, no critical error committed, and manager review.

Scheduling - Application Overview

Applied, reference and assessment

Concept · 25 minScheduling - Concepts and Key TermsScheduling has one core idea: a schedule is a plan against a forecast. Everything else - the draft, coverage by interval, optimization, violations, publication, acknowledgment - follows from that. This module sets out the core concept, a plain-language glossary of the terms that matter, how they chain from requirement to published commitment, and the single concept people most often get wrong.Reference · 30 minScheduling - Data and Setup DependenciesScheduling is only as right as its inputs. A schedule is a plan against a forecast, so the forecast version is the first dependency; the rules, skills and time zones you set bind every draft that Generate/Optimise produces; and coverage shown is planned, not actual. This reference sets out the data and configuration Scheduling depends on, the apps it chains with, and the CSM validation stops that decide whether a clean-looking draft can be trusted or must be escalated.Reference · 25 minScheduling - Common MisinterpretationsMost Scheduling mistakes are not tooling failures - they are misreads. A plan is read as a result, a draft as a commitment, a daily total as interval coverage, a clean view on a stale forecast as a safe one. This catalogue groups the common misreads by theme and, for each, gives the wrong reading, why it is wrong, and the correct reading. The one line under all of them: a schedule is a plan against a forecast, coverage shown is planned not actual, and a draft is not live until published.Playbook · 45 minScheduling - CSM Adoption PlaybookAdoption of Scheduling is not 'a schedule was generated'. It is a team that builds drafts on the live forecast, clears rule violations before publishing, publishes one acknowledged version with enough notice, and owns change afterwards. This playbook stages that from a single pilot team to the operation, names the adoption traps that make a clean-looking schedule wrong, and ties each stage to the grounding's own measures - coverage by interval, rule exceptions, acknowledgment, publication timeliness and schedule stability.Demo script · 30 minScheduling - Evidence-Led Sales DemoThis is the runnable demo script for Scheduling. It follows the five-beat pattern (question, screen, evidence, interpretation, next step), shows a concrete shortage window and then separates planning, optimization and publication as distinct steps, and states the one limitation out loud so the story stays honest. It is built to run live on schedules.demo.timechamp.io against the seeded W42 week.Troubleshooting · 30 minScheduling - Troubleshooting and EscalationWhen a schedule looks wrong, the cause is almost always an input or a boundary, not a broken screen: the draft is on a stale forecast, the rules or time zone are misconfigured, a plan is being read as actual, or a draft is being treated as published. This guide works symptom by symptom - likely cause, first checks, when to escalate - at app-logic level, with no invented error messages or UI paths.Assessment · 40 minScheduling - Practical AssessmentThis is the certification assessment for Scheduling. The learner works one or two realistic scenarios and is scored on a checklist that mirrors the app's core guardrails. The pass bar is the Academy gate: practical score at or above 80, no critical error, and manager review. The critical errors that fail the assessment are the ones that would mislead a customer - presenting a plan as a result, trusting a stale-forecast draft, or calling a draft a commitment. The self-check items below are the assessment questions with model answers.

Real-Time Adherence - are people doing the planned work, and is it producing enough?

Applied, reference and assessment

Concept · 25 minReal-Time Adherence - mental model and key termsThe one idea to hold: adherence is a comparison, not a performance score. It asks 'did the actual state match the plan?' RTA layers that one comparison into three - schedule, work and output - because presence, effort and results are three different questions. Get that model right and the glossary and the guardrails fall out of it.Reference · 30 minReal-Time Adherence - data and setup requirementsEvery adherence verdict is computed from three inputs - a published schedule, live activity capture, and a set of rules that define what counts as adherent - plus, for the output layer, a trusted output standard. If any of those is wrong, stale or missing, every screen downstream is wrong in a way no floor review can fix. This reference lists what to wire and what to validate first.Reference · 25 minReal-Time Adherence - common misreads and the correct readingRTA's single biggest misread is reading schedule adherence (presence on plan) as proof the work is getting done. The rest follow from conflating the three layers, treating a red state as a verdict, or trusting a number without checking the rules that produced it. This is the high-value card to keep open during a demo or a customer dispute.Playbook · 40 minReal-Time Adherence - CSM adoption playbookRTA only pays off intraday. The adoption risk is not that nobody logs in - it is that the Control Room becomes a wall display nobody acts on, or that a lead reads a green schedule board as proof the work is getting done. This playbook stages rollout from a single pilot team to the floor, fixes the plumbing before the numbers are trusted, and defines what 'adopted' actually looks like.Demo script · 30 minReal-Time Adherence - evidence-led demo scriptThe demo has one job: make the prospect feel the gap their current adherence tool leaves. Two agents look identical on a normal green board; one is producing and one is not. RTA shows the difference while the shift is still fixable. Run it in under eight minutes with two drill-downs and one explicit limitation, exactly as the sales certification requires.Troubleshooting · 30 minReal-Time Adherence - diagnosis and escalationAlmost every RTA problem is one of three things: the inputs are wrong (stale schedule, bad time zone, unmapped state, thin capture), the rules are mis-tuned (grace/thresholds), or the number is being misread (presence taken for productivity). Diagnose at app-logic level - the four plumbing checks resolve most of it - and escalate the plumbing, never guess at it.Assessment · 40 minReal-Time Adherence - certification assessmentThis is the practical gate for RTA. The learner works two scenarios - a sales demo-and-objection and a CSM dispute-and-validate - and is scored against a checklist. The critical errors are the ones that would mislead a real customer: presenting presence as productivity, treating a red state as a verdict, presenting the directional output layer as substantiated, or arguing a disputed number without validating the rules.

Intraday Management - is today's plan still viable, and which fix best protects delivery?

Applied, reference and assessment

Concept · 30 minIntraday Management concepts - the mental model and the language of the same-day control towerIDM is the 'now what' layer of workforce management: a same-day control tower that runs a detect - decide - act - review loop. The core idea is that the plan built days ago will not survive the day, so the value is a faster, evidenced, auditable decision when reality diverges - the engine proposes options, a human disposes, and the service result stays the customer's to own.Reference · 35 minIntraday Management data and setup - what IDM needs before its reforecast and what-if can be trustedIDM is a same-day control tower, and every figure it shows is only as good as the live feeds and the rules behind it. A stale actuals feed, a wrong skill map or an unvalidated cost rule corrupts the reforecast, the staffing gap and every simulation with no visible symptom on the day-of screens. This reference lists what IDM depends on, the setup it needs, where it inherits from Capacity Planning and Scheduling, and the CSM validation and escalation line.Reference · 35 minIntraday Management misinterpretations - the common misreads and the correct reading of eachIDM's whole value - a live control tower that reforecasts and simulates - also creates its characteristic misreads: treating a projection as delivered, a green tower as an SLA guarantee, a net balance as coverage, an alert as a problem, a configured figure as objective fact. This catalogue groups those misreads by theme and gives the honest correct reading for each, pulled from the app's workflow interpretation checks and the signature guardrails.Playbook · 40 minIntraday Management adoption playbook - from reforecast curiosity to a logged, reviewed daily decision loopIDM is only adopted when the detect - decide - act - review loop becomes a daily habit with a memory. This playbook stages that from a single pilot team to the floor, names the milestone at each stage, calls out the adoption risks specific to a same-day control tower, and ties progress to the measures IDM itself exposes - time to detect and respond, action completion, forecast drift and the service/backlog outcome the customer owns.Demo script · 35 minIntraday Management sales demo - the evidence-led script for 'when the day goes sideways, how does your duty manager decide?'This is the question -> screen -> evidence -> interpretation -> next-step demo for IDM. The arc is one shortage carried all the way through the loop: the day drifts, you quantify it, locate the gap, simulate two fixes, compare, and show how the decision is logged and reviewed. The discipline that makes it credible is stating the boundary - IDM simulates and recommends; execution happens in the customer's systems - before the prospect asks.Troubleshooting · 35 minIntraday Management troubleshooting - when the numbers look wrong, coverage seems off, or a customer disputes a figureMost IDM problems are input problems wearing a model's clothes. A same-day control tower is only as good as its live feeds and configured rules, and the dangerous failures are silent - a stale skill map or a lagging actuals feed shows no symptom on the day-of screens while corrupting every figure. This guide works symptom by symptom: numbers look wrong, coverage gaps, a disputed figure - each with likely cause, first checks and escalation line.Assessment · 45 minIntraday Management assessment - prove you can run the loop and hold the honesty lineThis assessment puts the learner on a live-ish IDM shortage and a customer dispute and scores how they decide and how they talk. The pass bar is not whether they can click the screens - it is whether they keep simulated, executed and achieved apart, read coverage by interval and skill, check the rule behind a disputed figure, and hold the execution boundary out loud. Any collapse of projection into result is a critical, failing error.

RCM Operations - which revenue-cycle issue should a leader address first, and on what evidence?

Application · 55 minRCM Operations - which revenue-cycle issue should a leader address first, and on what evidence?RCM Operations is the business-outcomes front door for a revenue-cycle leader. It does not just display metrics - it prioritises which payer, denial category, backlog or SLA issue deserves attention first, lets the user follow the evidence behind the signal, and frames a proposed action with an outcome hypothesis. It is the application that connects 'the team was busy' to 'the revenue cycle moved'.Workflow · 10 minRCM Operations: Denials & AppealsDenials and Appeals breaks the denial load into categories and surfaces the appeal queue so a leader can work the cohorts that protect the most recoverable value first. It answers 'which denials, appealed this week, protect the most cash.'Workflow · 10 minRCM Operations: Mission ControlMission Control is the AI-native front door of RCM Operations: it decides which revenue-cycle issue a leader should look at first, instead of displaying a flat wall of charts. It answers 'what do I put my limited analysts on today, and why.'Workflow · 10 minRCM Operations: OutcomesOutcomes closes the loop RCM Operations opens: it connects operational actions to revenue-cycle results. It answers 'did the thing we did actually move the cycle, and in which value category' - the honest counterpart to the outcome hypothesis set on Mission Control.Workflow · 10 minRCM Operations: OverviewOverview is the at-a-glance state of the revenue cycle - AR, denials, backlog and SLA posture in one place. It answers 'where does the cycle stand right now' and sets up where to look next; it is a summary, not a diagnosis.Workflow · 10 minRCM Operations: QualityQuality surfaces where process quality in the revenue cycle is weak - the errors and rework that cause downstream denials and leakage. It answers 'where do quality problems put cash at risk', feeding prioritisation rather than standing in for a financial result.Workflow · 10 minRCM Operations: ReportsReports is the output layer of RCM Operations - the place to assemble and share revenue-cycle figures. It answers 'what do we put in front of finance or a client', and its discipline is that every figure travels with the scope and definition that make it true.Workflow · 10 minRCM Operations: SLA & RiskSLA and Risk is the early-warning layer: it flags which SLA clocks and filing or appeal deadlines are trending toward trouble so a leader can intervene before the window closes. It answers 'what is about to go wrong, in time to stop it.'

Applied, reference and assessment

Concept · 30 minRCM Operations concepts - the mental model and the vocabularyRCM Operations is built on one idea: prioritise revenue-cycle attention by outcome, follow the evidence, and keep the value categories honest. This module defines that core concept, gives a plain-language glossary of the terms a rep must use precisely (recoverable, billed, collected, capacity value; signal, evidence, hypothesis, outcome; prioritisation vs verdict; projection vs result; observed contribution), shows how the concepts chain from signal to validated outcome, and names the concept people most often get wrong.Reference · 35 minRCM Operations data and setup - what the briefing needs to be trustworthyRCM Operations prioritises revenue-cycle issues and connects actions to outcomes. It is only as trustworthy as the data feeding it and the definitions behind each figure. This reference lists the signals it depends on, the setup and integrations required (described at app-logic level, specifics to confirm with product), its dependencies on other Time Champ apps, and the validation a CSM runs before a customer acts - so a prioritisation reflects the customer's real payers and a figure is never quoted stripped of its scope.Reference · 30 minRCM Operations misreads - the metric mistakes that cost credibilityEvery screen in RCM Operations can be misread the same few ways: a projection read as a result, a recoverable figure read as cash, a prioritisation order read as truth, a scoped number read as universal. This catalogue collects those misreads by theme and gives the correct reading for each. It is the quick-reference a rep scans before a QBR or a demo, and the first thing a CSM checks when a customer disputes a number.Playbook · 40 minRCM Operations adoption playbook - from briefing shown to priorities ownedAdoption of RCM Operations is not 'the dashboards load'. It is a behaviour: a leader opens Mission Control, picks the prioritised signal, follows evidence, assigns an owner, and later checks the outcome with recoverable, billed, collected and capacity value kept separate. This playbook stages that from a scoped pilot to a team routine to scale, names the milestone at each stage, lists the adoption risks specific to this app and how to counter them, and sets the success measures to watch from the app's own grounding.Demo script · 35 minRCM Operations sales demo - the evidence-led, outcome-honest scriptThis is the demo to run on a live call. It follows the signal-to-outcome spine the app is built on: open on prioritisation, drill to evidence, make the value honest, then close the loop on Outcomes. Each beat pairs a business question with one screen and one value point, states the limitation explicitly, and ends on a next step. The discipline that wins the room is honesty - prioritisation is a starting point to verify, SLA risk is a projection not a breach, and recoverable value is never quoted as collected cash.Troubleshooting · 35 minRCM Operations troubleshooting - numbers wrong, gaps, and disputed figuresWhen RCM Operations looks wrong it is almost always a data, scope, definition or freshness issue - not a broken screen. This guide works by symptom: numbers look wrong or missing, coverage gaps, and a customer disputing a figure. For each it gives the likely cause, the first checks a CSM runs before escalating, and the line where it stops being a CSM check and becomes an implementation specialist or product escalation. No fabricated error codes or UI paths - everything is described at app-logic level.Assessment · 45 minRCM Operations assessment - the certification gateThis is the scored, practical assessment that gates certification on RCM Operations. The learner works two realistic scenarios - a live-demo moment and a CSM validation moment - against a checklist, and must avoid the critical errors that auto-fail regardless of score (presenting a projection as a result, quoting recoverable value as collected cash, acting on the briefing without evidence, or quoting an unvalidated figure as the customer's). The self_check items are the actual assessment questions with model answers. Pass is at least 80, no critical error, manager review.

Quality and Call QA - where are the quality risks, and how do we make evaluation consistent and actionable?

Applied, reference and assessment

Concept · 25 minQuality and Call QA concepts - the mental model and key termsThe mental model is a loop - evaluate, review, coach - whose trust lives in four supports: a rubric that defines 'good', a sample that represents the operation, calibration that keeps scoring consistent, and coaching that closes the loop. AI accelerates the loop; it does not own it. Get the terms right and the whole app reads cleanly; blur them and coverage gets mistaken for quality. This module defines the concepts and shows how they chain.Reference · 30 minQuality and Call QA data and setup - what the app needs to produce scores you can trustA QA score is only as good as four things beneath it: the interactions and evidence it was scored from, the rubric it was scored against, the sample it was drawn from, and the reviewer consistency behind it. This reference describes those inputs in product-logic terms, names the dependencies on other apps, and sets out what a CSM validates before a figure is trusted. Specifics of recording and transcription sources, AI scoring models and dispute workflows are entitlement- and configuration-dependent - confirm with product, never assert.Reference · 30 minQuality and Call QA misinterpretations - the common misreads and the correct readingAlmost every mistake in this app is the same error wearing different clothes: treating a number as proof of something it cannot prove. Coverage is read as accuracy, a tile as a verdict, a pattern as a cause, completion as improvement, an AI score as the final word. This catalogue groups the misreads by theme, and for each gives the wrong reading, why it is wrong, and the correct reading. Use it as a bench card before any QA number leaves a review or a demo.Playbook · 40 minQuality and Call QA adoption playbook - standing up a trusted evaluate-review-coach loopAdoption of Quality and Call QA is not 'calls are being scored.' It is a loop the customer runs every cycle: a rubric that matches how they define quality, a sample that represents the operation, reviewers who agree on the same call, a dispute path agents trust, and coaching that closes and shrinks recurring errors. This playbook sequences that from a pilot to scale and names the risks that stall each stage. The signature caution runs through all of it - coverage is not accuracy, and a confident score no one calibrated is worse than honest sparse sampling.Demo script · 35 minQuality and Call QA sales demo - the evaluate-review-coach story, honestly positionedThis demo does not sell coverage - it sells trust. The arc takes one interaction from evaluation, through review, calibration and a dispute, to the coaching action and the recurring-error pattern it feeds, and positions Ask Quality AI precisely as acceleration under human review. The winning move is to answer the three questions most QA programmes fail - coverage, consistency, closure - on screen, and to say the one limitation out loud before the buyer raises it: coverage alone is not quality.Troubleshooting · 30 minQuality and Call QA troubleshooting - numbers look wrong, coverage gaps, disputed figuresMost QA problems a CSM meets are not product faults - they are trust breaking somewhere in the loop: a rubric that does not fit, a sample that is skewed, reviewers who disagree, an AI score nobody reviewed, or coaching that never closes. This guide is organised by symptom. For each, it gives the likely cause in product-logic terms, the first checks to run upstream, and when to escalate to the implementation specialist or product rather than keep digging.Assessment · 45 minQuality and Call QA assessment - prove you can read and position the quality loopThis assessment is pass-or-fail on honesty as much as knowledge. A learner who can quote every screen but presents coverage as quality, or an AI score as a verdict, has made a critical error and does not pass. Two scenarios test the real skill - reading a figure with its sample and calibration basis, and positioning the loop to a sceptical buyer. The gate is a practical score of at least 80, no critical error, and manager review.

RCM Insights - can a business user answer a real question and inspect the evidence behind the answer?

Application · 50 minRCM Insights - can a business user answer a real question and inspect the evidence behind the answer?RCM Insights lets a non-analyst ask a meaningful business question and get an answer they can trust because they can see the data, scope and freshness behind it. Its value is not that it talks fluently - it is that the answer is inspectable and reusable. The core discipline: a fluent answer on thin or stale data is a liability, so evidence inspection is the skill the customer must learn.Workflow · 10 minRCM Insights: AdminAdmin governs who can see what - the role-scoping that controls which data an answer draws on. It answers 'is this answer complete for the person asking', with the discipline that an answer's completeness depends on the asking user's role scope.Workflow · 10 minRCM Insights: AskAsk is the natural-language front door of RCM Insights: a business user poses a question in plain language and gets an answer tied to inspectable data. It answers 'can a non-analyst get a defensible answer themselves', where the value is the evidence, not the fluent wording.Workflow · 10 minRCM Insights: DashboardsDashboards let useful analyses be reused rather than re-derived - a saved, shareable view of the questions a team returns to. It answers 'what do we watch regularly', with the discipline that each dashboard reflects its own filters and data scope.Workflow · 10 minRCM Insights: DataData is the evidence pane of RCM Insights - the sources, coverage and freshness behind an answer. It answers 'can I see what this answer is built on', and it is the habit that keeps users safe from trusting fluent but thin answers.Workflow · 10 minRCM Insights: DiscoverDiscover helps a user find what they can meaningfully ask - the questions the data can support and the directions worth exploring. It answers 'what can I actually ask here', orienting a user who does not yet know the shape of the data.Workflow · 10 minRCM Insights: MetricsMetrics exposes the definitions behind the numbers - what 'AR days', 'denial rate' or 'recoverable' actually mean here. It answers 'does this number mean what I think it means', and the definition is what governs whether any two figures can be compared.Workflow · 10 minRCM Insights: SavedSaved is where useful questions and analyses are kept for reuse rather than re-derived each time. It answers 'which analyses are worth running again', with the discipline that a saved question carries its own frozen scope even as the data refreshes.

Applied, reference and assessment

Concept · 30 minRCM Insights concepts - the mental model and the words behind the answersRCM Insights rests on a single idea: an answer is only as good as the evidence and scope you can see behind it. Everything else - Ask, Discover, Data, Metrics, Dashboards, Saved, role scope - serves that idea. This module defines the terms plainly and shows how they chain, so a Sales or CSM person can explain the product without selling it as a chatbot.Reference · 35 minRCM Insights data setup - what the app needs before any answer can be trustedRCM Insights is only as good as the data, definitions and scope behind its answers. This reference lays out what the app needs to generate trustworthy answers - without inventing connectors or refresh cadences. It names the dependencies, the setup areas, the upstream apps, and the validation a CSM runs so a fluent answer is backed by real coverage, agreed definitions and correct role scope.Reference · 30 minRCM Insights misreads - the metric misinterpretations that turn a fluent answer into a liabilityThe sharpest risk in RCM Insights is not a wrong number - it is a right-looking number read the wrong way. This catalogue lists the recurring misreads: fluency mistaken for proof, a source mistaken for coverage, a label mistaken for a definition, a dashboard figure mistaken for a universal truth, a projection mistaken for a result, and capacity value mistaken for cash. Each is a quick fix once you can name it.Playbook · 40 minRCM Insights adoption playbook - from impressive demo to a reflex of inspecting the evidenceRCM Insights adopts differently from a dashboard product. The risk is not low usage, it is confident misuse: a fluent answer trusted without its evidence. 'Adopted' here means a small set of genuinely useful analyses that get re-run for real decisions, and a user base that opens the data and definitions behind an answer by reflex. This playbook stages that outcome and names the habit to build at each step.Demo script · 30 minRCM Insights sales demo - a prepared question, then the evidence that makes it defensibleThis demo wins by doing the opposite of a chatbot demo. Instead of improvising clever questions to show off fluency, you ask ONE prepared, decision-linked question and then spend the demo on the evidence behind the answer. The value point the buyer remembers is 'I could take this into a QBR', not 'it talks well'.Troubleshooting · 35 minRCM Insights troubleshooting - when an answer looks wrong, thin, or disputedMost RCM Insights problems are not bugs - they are evidence problems: a thin source, a definition mismatch, a scope misread or a stale feed. This guide works symptom-first so a CSM can diagnose calmly, because in this app a wrong-looking number is usually a correctly-working tool telling you something about the data behind it.Assessment · 45 minRCM Insights assessment - prove you sell and support the evidence, not the fluencyThis assessment tests whether a Sales or CSM person has internalised the one discipline that makes RCM Insights safe to sell and support: an answer is only as good as the evidence and scope behind it. The scenarios are built so that the tempting fluent answer is the wrong one, and the scoring rewards inspecting evidence, naming definitions and scope, and knowing when to say 'not enough data' or 'confirm with product'.

Value Leakage - where is value lost, who can act, and what has actually been recovered?

Application · 55 minValue Leakage - where is value lost, who can act, and what has actually been recovered?Value Leakage is the money layer of the platform. Every other app finds a problem; this one puts a defensible number on it, says who can act, and tracks whether it was actually recovered. The discipline that makes it credible: each finding is quantity times unit-cost times confidence (so soft findings are discounted, not hidden), and the recovery screen keeps recovered capacity and cash recovered as separate lines that are never summed.Workflow · 10 minValue Leakage: AI ₹61 LThis screen answers 'how much value is leaking from missed AI and automation opportunities, and is that a capacity opportunity or a cash one?' It isolates one of the six leakage categories so a finding can be sized and owned.Workflow · 10 minValue Leakage: AttributionThis screen answers 'who can actually act on this leak?' It attributes findings to an owner, turning a sized number into something a real person is accountable for.Workflow · 10 minValue Leakage: Capacity ₹78 LThis screen answers 'how much value is leaking from unused or idle available capacity, and is that a capacity opportunity or a cash one?' It isolates one of the six leakage categories so a finding can be sized and owned.Workflow · 10 minValue Leakage: Outcome ₹1.09 crThis screen answers 'how much value is leaking from poor business outcomes - missed revenue, denials, avoidable losses, and is that a capacity opportunity or a cash one?' It isolates one of the six leakage categories so a finding can be sized and owned.Workflow · 10 minValue Leakage: OverviewThe Overview is the front door to the money layer: it answers 'where across the operation is value being lost, and which category is biggest?' before anyone drills into a single finding.Workflow · 10 minValue Leakage: Process ₹1.12 crThis screen answers 'how much value is leaking from process friction, rework, handoffs and avoidable steps, and is that a capacity opportunity or a cash one?' It isolates one of the six leakage categories so a finding can be sized and owned.Workflow · 10 minValue Leakage: Quality ₹96 LThis screen answers 'how much value is leaking from quality failures, defects and rework, and is that a capacity opportunity or a cash one?' It isolates one of the six leakage categories so a finding can be sized and owned.Workflow · 12 minValue Leakage: RecoveryThis screen answers 'what has actually been recovered, and is it capacity or cash?' It is the honesty core of the whole app - where sized opportunity becomes verified, evidenced recovery.Workflow · 10 minValue Leakage: ReportsThis screen answers 'how do we communicate leakage and recovery to leadership and finance without inflating it?' Reports packages the ledger for sharing while keeping the honesty rules intact.Workflow · 10 minValue Leakage: System ₹54 LThis screen answers 'how much value is leaking from system waits, latency and tool downtime, and is that a capacity opportunity or a cash one?' It isolates one of the six leakage categories so a finding can be sized and owned.Workflow · 10 minValue Leakage: Top Value LeaksThis screen answers 'of everything we have detected, which findings are the biggest and should be worked first?' It ranks findings across all categories so effort follows value.Workflow · 10 minValue Leakage: Workflow DetectionThis screen answers 'where do the leakage findings come from?' It shows detection surfacing candidate leaks from observed workflows, which is the input to the whole ledger.

Applied, reference and assessment

Concept · 30 minValue Leakage concepts - the mental model and the words that make the number honestValue Leakage turns 'we are leaking value' into a defensible, owned, trackable number. Its mental model is a chain: observed work is detected as a candidate leak, sized as quantity x unit-cost x confidence, routed to one of six categories, ranked, attributed to an owner, and tracked through states to Verified recovery - with recovered capacity and cash recovered never summed. This module defines the terms plainly and shows how they chain, so the formula and the capacity-vs-cash rule become second nature.Reference · 30 minValue Leakage data and setup - what the app needs to produce an honest numberValue Leakage is a money layer that sits on top of the other apps. It does not generate raw observation; it takes observed work and outcomes, sizes the loss as quantity x unit-cost x confidence, routes it to one of six categories, and tracks recovery. This reference explains what feeds that model, what must be configured and agreed before the numbers are trustworthy, and exactly what a CSM checks before a figure leaves the room. Specific integration mechanics are described at logic level - confirm the exact connectors and methods with product.Reference · 30 minValue Leakage misinterpretations - the metric misreads to catch before they reach financeValue Leakage exists to produce honest, defensible numbers, which means its misreads are high-stakes: a blended total or a detected-as-recovered claim is exactly the inflation that destroys finance's trust in the whole programme. This is the catalogue of those misreads, grouped so a CSM or Sales person can catch them in a review or a demo before the number leaves the room.Playbook · 40 minValue Leakage adoption playbook - from a sized list to a living, owned recovery ledgerMost leakage work dies as a slide: an impressive total that no one owns and no one verifies. This playbook defines what adopted looks like for Value Leakage, stages the rollout from a single pilot finding to a scaled ledger, names the adoption risks specific to this app and how to counter them, and sets the success measure and review cadence from the app's own grounding. The non-negotiable through-line: value = quantity x unit-cost x confidence, six categories, and capacity never summed with cash.Demo script · 30 minValue Leakage sales demo - one defensible finding, from sized to VerifiedThe weak Value Leakage demo lists six categories and a huge total. The strong one picks a single finding and walks it end to end, so the buyer sees provenance, a confidence-discounted number, a named owner and an honest recovery state. This script is built for a live call: a tight arc, the exact screens in order with the one value point each, the limitation to state out loud, and the discovery questions the demo answers. Never quote the seeded magnitudes as the customer's opportunity.Troubleshooting · 30 minValue Leakage troubleshooting - when the numbers look wrong, incomplete or disputedBecause Value Leakage produces money numbers, a wrong or disputed figure is a trust problem, not just a data problem. This guide works by symptom. For each, it names the likely cause in terms of the app's model - quantity, unit-cost, confidence, recoverable share, overlap, owner and recovery state - the first checks a CSM runs, and the point at which it escalates to the implementation specialist, product or the customer's finance. The recurring root cause is almost always an input, not the screen.Assessment · 40 minValue Leakage assessment - prove you can produce and defend an honest recovery numberThis assessment puts the learner in two realistic situations - a sales demo moment and a CSM validation moment - and scores whether they produce a defensible number and defend it honestly. The pass bar is not fluency; it is honesty discipline. Presenting a projection or a sized figure as a recovered result, or blending capacity and cash, is an automatic fail regardless of the rest. self_check holds the actual assessment questions with model answers.