Work Understanding: Conformance and compliance
Objective. Read a conformance figure correctly - as deviation measured against a chosen reference path - so a reader never quotes a conformance percentage without stating which reference it was measured against.
Conformance answers 'how often does reality follow the intended path, and where does it deviate?' The single most important point here is that the reference path choice drives the number.
See it in the demo
What this screen answers
The customer question is: how consistently does this process follow its intended path, and where does it break away? A Sales person uses it to show that deviation is visible and localised. A CSM uses it to find where the process routinely departs from standard and whether that deviation matters.
The task
Scope to the process and period, confirm which reference path conformance is being measured against, then read the conformance level and the main deviation points. The essential move is to state the reference explicitly: a conformance number is only meaningful once everyone agrees what the intended path is. Agree the reference with the customer before reading the figure out loud.
How to read it
Conformance is measured against a chosen reference path, so the reference choice drives the number. The classic misread is quoting a conformance percentage as an absolute process-quality score - change the reference and the same process scores differently. A low conformance figure is not automatically bad: deviation can be legitimate handling of genuinely different cases. Read it as 'how often it follows this specific reference', then investigate whether the deviation is a problem.
Honest limits
Conformance does not prove deviation is waste or non-compliance, and it is entirely dependent on the reference path chosen. It does not define what the correct path should be - the customer does. Confirm the reference path with the customer and confirm detection coverage with product before any conformance figure becomes a claim.
Interpretation check
A conformance percentage is only meaningful against a stated reference path - the reference choice drives the number, so never quote conformance without naming the reference and agreeing it with the customer.
In the field
KnackGlobal RCM: a claim process can score low conformance simply because payers force different routes - the figure is a prompt to ask which deviations add days, not a compliance grade on its own.
Practical task
On the conformance view for one process, record the conformance level, write the reference path it is measured against, and write one deviation you would investigate before deciding whether it is a problem.
Self-check
A prospect asks 'is 72% conformance good or bad?' What is the honest answer?
It depends entirely on which reference path it was measured against and whether the deviations are legitimate. Name the reference, agree it with the customer, then investigate the deviation rather than grading the number.
Why can low conformance be fine?
Deviation can be correct handling of genuinely different cases. Low conformance is a prompt to investigate, not proof of non-compliance or waste.
What one thing must you always state alongside a conformance figure?
The reference path it was measured against - because changing the reference changes the number for the same process.
Verified vs demo. Screen is live in the demo at /#/conformance; exact controls, the reference path and figures are SME-validation-pending.