Missing data point
The policy requires a deadline, an owner or a procedure. The documents say nothing about it.
Where the policy promises something the documents do not support.
Coming soon
Policies are promises: inward to your own teams, outward to customers and supervisors. Whether day-to-day practice keeps them shows up only when you compare them with the documents that record that practice.
Status
This use case is not available yet either. The page describes the planned design and defines what counts as a gap.
Definition
What a gap is
Contradiction
Two places say different things: the policy states 24 hours, the procedure states five working days.
Outdated state
The document is older than the policy and has not been updated since.
Planned
How the comparison is designed
1 · Read the policy
The policy is read and split into statements that can be checked.
2 · Statement against document
For each statement it is checked whether your documents support it.
3 · Report open points
What is not supported is reported as a gap, not dressed up as an assessment.
4 · Document the decision
Your team decides whether to close the gap or consciously accept it.
FAQ
Common questions
Is this use case available?
No. It is in preparation; we name a date only once it runs.
Does it replace legal advice?
No. The analysis shows where a promise is not supported by your documents. Whether the promise satisfies your regulators is a decision you take with your compliance function.
Why does this sit under vendor risk?
Because it uses the same mechanics: read documents, evidence statements, present open points. Your vendor review set is usually the first place these mechanics are applied.
Contact
If your policies and your documents drift apart.
Bring one policy and the documents meant to support it. We walk the planned process and show which statements stay without a source.
Book a demo →Or email us: info@leaplytics.de
First call is non-binding, remote or on site.