Skip to content
corepilot
Start free

Insight · Analytics & Reporting

Reports that cannot show you what the screens will not.

Start freeBook a demo

Included from Starter upward.

Reporting is a separate tool with its own copy of the data and its own idea of permissions — which is how a manager ends up exporting salaries they cannot open in the HR screen.

The report library

What it does

The same scope rules the screens use, applied to the numbers.

  1. 01

    One scope predicate, everywhere

    A report runs through the same rule the screen does. There is no second permission model to keep in step.

  2. 02

    Operational, tactical and strategic

    From today's queue to the quarter's shape, off the same rows.

  3. 03

    Report activity

    What was run, by whom, and when — because a report is an export, and exports are a governance question.

  4. 04

    Audit and outbox

    What the system did on the company's behalf, and what it sent, kept where an auditor can read it.

For example

A manager who cannot open a salary cannot export one either

  1. 1A delivery manager runs the utilisation report: 59% billable, 571 of 971.75 hours logged.
  2. 2It runs under their own scope — their reporting line, not the whole company.
  3. 3The finance controller runs the same report and sees everything, because their scope is global.
  4. 4Neither of them configured a permission in a reporting tool, because there is no reporting tool.
  5. 5Both runs are on the record: what was run, by whom, and when.

There is no second copy of the data and no second permission model, so a report cannot show somebody what their screen would refuse.

The audit trail
The audit trail

How it runs

In, through, out

Input

Somebody asks a question

Process

The report runs under their own scope

Output

The answer is theirs to see, and the run is on the record

Nobody has to trust that the reporting tool was configured correctly, because there is no second tool to configure.

In the product

Actual screens, not mockups

Which reports were run, by whom
Which reports were run, by whom

It does not work alone

What Analytics & Reporting is connected to

The point of one set of records is that these are not integrations. They read the same rows.

DeliveryProjects & DeliveryHours booked, work delivered, and what has not been billed.MoneyFinance & AccountingGST invoices, receivables and a ledger that balances.PeopleHR & PeopleThe record every other module reads.

Problems it solves

Get off spreadsheetsOne view of the businessControl who sees what

Where to go next

The other fifteenGrouped by what they do, with what goes wrong without each one.Which plan holds Analytics & ReportingRead from the entitlement table the product actually enforces.See it inside a real hourStep by step, ending where the work becomes somebody else's problem.