Analytics

Records → Analytics is the whole organisation's AI work for one window: what agents asked people, how each request ended, how much the gate settled with nobody asked, how quickly people answered, where the risk sat, which agents did the work, and whether anybody read what was published. Owners and admins can open it. Choose the last 7, 30 or 90 days at the top right; every number is compared with the same length of time before it.

It opens with a few sentences saying what happened, in words you can read aloud in a meeting, then the headline numbers. Download report prints the page without the navigation and saves it as a PDF titled "AI activity and control report", with your organisation's name on the first page (and its logo from Organisation → Branding & domains on plans with custom branding) and who prepared it when, ready to send to a board or a regulator.

The headline numbers#

Beneath each is its change against the window before: a percentage for counts and times, points for rates. Green means better and red worse, which is not always up: a shorter time to decide is green on a falling arrow. Requests and gate checks are neither, so they stay grey. A change under half a percent reads as no change, and with nothing to compare against the tile says so. The small line shows the number day by day.

A very busy organisation is read up to the most recent 20,000 requests, gate checks and decisions of each kind. When that limit is reached the page says so and leaves the comparisons out, rather than compare against a period that came up short.

The charts#

• Requests to people, by outcome: one column a day, split into approved, changes requested, declined, expired unanswered, and open or withdrawn.
• Settled by policy: the share of gated actions a rule allowed, over the seven days to each date, with how many were allowed, sent to a person and refused. The axis is fitted to the line, so a rise from 70% to 78% is visible.
• Time to decide: how long people took to approve or decline, in six bands (Under 5 min, 5–30 min, 30 min–2 h, 2–8 h, 8–24 h, Over a day), with the median marked.
• When people are asked: requests by hour of the week, darker where there were more, in the time zone on your profile. Where the dark cells fall is when approvers need to be reachable.
• Where people decide: the decisions that settled a request, by where they were made: Deliverd app, Email, Slack or Teams, Guest link, In your product, Phone notification. Decisions recorded before the channel was kept are counted as "Not recorded".
• Outcomes by risk: each risk level's requests, split by outcome, with the share approved beside each level, and how many showed the approver an ethics concern.
• Agents: up to eight of the busiest agents, with how many requests each put to people, the share approved, its gate checks and the share policy settled.
• AI vendors: the agents' activity (requests to people and gate checks) added up by the company behind each agent's platform, such as OpenAI, Anthropic or Google, as a share of all agent activity. Agents connected with a plain key, any MCP client or your own agent count as "Not stated" until you name their platform. When one vendor carries half or more of at least 20 actions, the opening sentences say so: a dependency worth a fallback plan.

Point at a chart, or tab to it and use the arrow keys, to read each day or hour. Every chart has Show as table beneath it with the same numbers. Today is still in progress, so its column is drawn lighter and its line dashed, and both are labelled as today so far.

Readership#

Report opens and the number of different readers each day, across every published report. There is no session recording. One reader opening the same report again within 30 minutes counts once, so a reader refreshing a dashboard is one open, not twenty. Each member, guest or shared link counts as one reader, and an anonymous reader is counted by a one-way hash of their network address.

• Most read lists up to six reports people opened in the window, with opens and readers for each.
• Nobody is reading these lists up to six published reports with no opens in the window, with when each was last read, or "never read". They are worth archiving, or worth chasing.

Open a report from either list to see its own page. This screen shows counts, not names. Whether a report's owner sees who read it, rather than how many, is set by viewer identity in Organisation → Sharing; see Sharing.

How long views are kept#

Individual views are deleted once they are older than your plan's view retention, by a job that runs once a day. A report's lifetime view total is kept, so pruning old detail never makes a count go backwards.

While your organisation has a legal hold in place, nothing is pruned. See Security, audit and legal holds. Plans are compared in Billing and plans.