← All capabilities

3 capabilities

Reporting & Analytics

What the work produces, for the people who have to act on it

The problem

The audit committee pack is often rebuilt by hand every quarter from data that was already in a system. It takes days, it goes stale the moment it is produced, and the numbers in it cannot be traced back to the records that produced them.

How it works

01

Reports & Board Packs

Server-rendered PDF, Word and Excel from templates, signed and scheduled to run unattended

  • Reports render server-side to PDF, Word, Excel and HTML from templates, rather than being exported and reformatted
  • Output is signed, so a report can be verified as genuine and unaltered after it leaves the building
  • Schedules run unattended, which is what turns the quarterly pack from a project into a delivery
02

Analytics & Dashboards

Coverage maps, temporal trends and role-specific dashboards for the committee and the CAE

  • Coverage maps show what the audit universe says should be covered against what has been
  • Temporal views show trend rather than a point in time
  • Role-specific dashboards mean the CAE and the committee are not handed the same screen
03

Committee & Auditee Portals

A read surface for the audit committee, and a response surface for the managers who own the actions

  • The audit committee gets a read surface rather than a PDF attachment
  • Auditees respond to findings, update actions and upload evidence in their own portal, so the audit team is not a relay

What it produces when someone asks for proof

Reports rendered from live data, signed, with the run recorded

Committee materials produced on a schedule without anyone assembling them

Dashboards that show what changed since the last time the reader looked