Classify a deviation by cause and recurrence
Takes a raw observed deviation and assigns its cause (analyst execution error, method gap, or ambiguous instruction) and recurrence tag (isolated vs. pattern), producing a structured log entry.
In / outRaw deviation observation → structured log entry with cause classification (execution error / method gap / ambiguous instruction) and recurrence tag
You might say…
“I've noticed the same kind of mistake three times but I haven't written it down consistently enough to know whether it's one analyst or a method problem.”
What it does
Takes a raw observed deviation and assigns its cause (analyst execution error / method gap / ambiguous instruction) and recurrence tag (isolated vs. pattern), producing a structured log entry. Used each time an observation needs to be turned into an actionable, classified record.
Trigger: Use each time a deviation observation needs to be turned into an actionable, classified record for the compliance log.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation