Reports and the SLA compliance PDF

The Reports page answers the questions your leadership and your regulator ask: how many requests, of what kind, from where, and were they answered on time?

The overview

Pick a date range (presets cover the common periods) and you get:

• Totals: requests received, open, overdue, and closed in the period.
• On-time rate: of the requests closed, how many closed on or before their deadline.
• Average days to close, against the average legal target.
• Breakdowns: by status, by request type, by jurisdiction, and by assignee.
• Monthly trend: volumes over time, so you can spot the January spike before next January.

The PDF export

Export PDF produces an SLA compliance report for the selected period, laid out for sharing: the same headline numbers and breakdowns in a document you can attach to a board pack, an audit response, or a customer's due-diligence questionnaire.

Reading the numbers

• A falling on-time rate almost always traces back to slow collection tasks. Check which data sources' tasks age worst, then talk to those owners or split the source into smaller ones.
• A rising "somewhere else" jurisdiction count means requests are sitting unconfirmed. See Residence, jurisdiction, and which law applies.
• Zero requests isn't a data problem. Small organisations genuinely receive none for months. The value is being ready for the week that changes.