When it hesitates, it tells you plainly
No error screen to decode. Paco tells you what is blocking, on which document, and what it needs from you. Two clicks and it is done.
The reason is named, so the fix is obvious
Every item in review carries the exact reason that put it there. You know before opening the document whether it lacks a date, lacks a property, or states an interval that contradicts the law.
- Intervention date missing or unusable
- Property cannot be attributed with certainty
- Document interval conflicts with the regulatory text
- Document judged outside the regulatory scope
A visible gap beats a false green tick
When the date of a control cannot be established, the obligation is blocked rather than filled with the nearest guess. A gap gets chased; a register that wrongly states a control happened does not get chased.
- A blocked obligation never improves your compliance rate
- The blocking reason names the document that would lift it
Common questions
Does the queue end up filling itself?
It should hold only what deserves a human decision. A clear report with a readable date and interval goes straight to the register without touching the queue.
See the queue against your real documents
It is the best test of the tool: what it refuses to decide alone says more than what it extracts.
Book a demo