Home/Platform/Reporting & Exports
Reporting & exports
Bring the work into view. Take the evidence with you.
Evidence is useful when the people who did not run the work can inspect it. These exports package the operation records for a client, underwriter or security reviewer, with the source figures attached.
How a pack is assembled
Operations, their receipts, and the links between them.
An export is not a report we write about your quarter. It is the quarter's operations and the records they produced, packaged with the links that let a stranger confirm nothing was edited afterwards.
- PDF for humans — the pack a client reads, under their branding.
- JSON and CSV for systems — the same records, for a SIEM, a spreadsheet, or someone's own analysis.
- Per operation or per client per period — one incident, or a whole quarter.
- Unmetered on every plan. A platform that charges per receipt teaches you to ration your own evidence.
The quarterly review
A page where every figure can name where it came from.
The QBR is where an MSP either sounds like a supplier or sounds like a partner. The difference is usually whether the numbers survive being asked about. Each figure here is a count of records, and each record opens.
The questionnaire
Answer the privilege section with records instead of prose.
Cyber-insurance renewals and vendor-security questionnaires ask the same shape of question: who can get administrator rights, how, for how long, who approved it, and how would you know if something else happened. That is an export here, not an essay.
- It covers agents and people in the same table, which is exactly the question an underwriter is circling when they ask about automation.
- It is generated from grants that actually happened — not from a policy document describing what should happen.
- An empty answer is an answer. A period with no elevation shows as none, rather than as a gap you have to explain.
This is a privilege and evidence export. It is not an assessment against a named control framework and we do not produce one — a compliance report that fills in its own findings is the specific thing this company exists in reaction to. What we hand you is the underlying record, in a form your assessor can read.
Formats, retention, cost
Nothing here is metered, and that is deliberate.
Three formats
PDF for the person reading it, JSON and CSV for the system that has to store or search it. Same records underneath — the format changes who can read it, never what it says.
Retention per client
Records live in that tenant's own isolated storage for the life of the workspace, with retention set per client — because one of your clients has a five-year obligation and another does not.
How the walls work →Unmetered
Receipts and exports are never charged per artifact, on every plan. Metering evidence would teach you to produce less of it, which would quietly destroy the thing you bought.
Pricing →You generate a pack and hand it over. We do not claim scheduled report delivery by email today — the export is something you pull, not something that turns up in a client's inbox on the first of the month. When that ships it will be on the release notes with a date, like everything else.
The questions that decide whether this is useful to you.
Can a client verify a pack without involving you?
Yes, for the property that matters most: whether anything in it was altered after the fact. Every record carries a fingerprint of the one before it, so recomputing the fingerprints and following the links exposes any edit. That check needs the file and nothing else — no login, no call to us.
Does a failed operation appear in the export?
It does, with what was attempted, what privilege it held, where it stopped and whether the declared undo ran. An export of only the successes would be marketing material with a chain attached. How a receipt handles failure →
Can I put my own branding on it?
Yes — per client. The pack goes out looking like it came from you, because it did. Your client should not have to learn our name to read their own service review.
What about time and billing?
Time tracked against an operation is attributed to the client that owns it, including work that carried on after you switched context. Billing here is your labour at your rates, not a resale of our running costs — what it costs us to run an operation is our problem, not a line on your client's invoice. The MSP economics →
How far back can I go?
As far as that client's retention setting keeps records, and they are kept for the life of the workspace by default. Since the records are chained, an old export and a fresh one covering the same period should agree exactly — and if they did not, you would be able to see where.
Take one to your next renewal
See a quarter's evidence assembled, then pick a line and open it.
Bring the questionnaire that took your team three days last year. We will show you which parts of it are already an export.