The Evidence File is an append-only record of every input, decision, model version and human approval behind each outcome. It is how we prove the work, and how we decide what gets billed.
Evidence FileExample entries
09:14Certificate of insurance issuedACORD 25, general contractor. Record 3f9a…c21eVerifiedBillable
09:16Renewal policy checked against quoteBOP renewal, 4 discrepancies logged. Record b71d…0a94VerifiedBillable
09:21Invoice matched and postedINV-20931 to PO 7718. Record e02c…5f3bVerifiedBillable
09:23Endorsement prepared: add vehicleCommercial auto, licensed review. Record 91be…77d0Awaiting your sign-offNot billed
The hardest question in agentic AI is not whether an agent can do the task. It is whether anyone can show what it did, on what basis, and who approved it. In Omdia’s polling of MSPs and IT decision-makers, 47% named governance and compliance as the top barrier to agentic AI, well ahead of technical skills at 16%.
We answer that question by default. Every billable outcome has a record, every record can be traced to its source documents, and nothing reaches your invoice without one.
What each record holds
The inputs: documents, system records and requests, as received
Each step the agent took and the rules it checked against
The model, version, prompt and tools used at each step
Confidence checks, and where the item was routed if they failed
Exception desk actions and your team’s approvals, with names and times
The outcome definition applied, and whether the item was billed
One record, opened up.
A renewal policy check for an insurance agency, as it appears in the Evidence File. The example is illustrative.
Your account manager gets the four discrepancies. Your auditor gets the full trail. Your invoice gets one line, linked to this record.
Record b71d…0a94: renewal policy checked
Verified
Input
Carrier renewal policy (PDF, 38 pages) and the bound quote from the agency management system
What the agent did
Compared limits, deductibles, forms and endorsements line by line
Result
4 discrepancies found and listed with page references
Checks passed
All 38 pages read; every quoted coverage line matched to a policy line or flagged
Human involvement
None required. Discrepancies sent to the account manager for carrier follow-up
Model and version
Recorded per step, with prompt and tool versions
Outcome definition
Policy checked: every coverage line compared and discrepancies delivered to the agency
Integrity
Hash-chained to the previous record, so any later edit is detectable
Billing
Billable once, as one verified policy check
What you can do with it.
Check any invoice line
Every billed item links to its record, so disputes are settled with evidence, not opinion.
Answer your auditor
Export records for a period, a process or a single item, with the approvals attached.
Show your regulator or insurer
Demonstrate human oversight where it is required, and exactly where it was applied.
How it is built.
Workflows run on a durable orchestration layer that keeps a full history of every step, including waits for human approval. That history is written to a separate, append-only log where each record is hash-chained to the last.
Records are stored in your region and isolated from other clients. Model calls go through our own gateway, which records the model and version used and enforces per-client limits.
The Evidence File is Agentic MSP's record of every outcome we deliver. For each item it keeps the inputs, what the agent did, the checks it passed, the model and version used, any human approvals, and whether the item was billed.
Can records be changed after the fact?
Records are append-only and each one is hash-chained to the one before it. A correction is added as a new record that points to the original, so any later edit is visible.
Who can see it?
You can. Every line on your invoice links to its record, and you can export records for your auditors, regulators or insurers.
Does the Evidence File cover human work too?
Yes. Actions by our exception desk and approvals by your team are recorded in the same way as agent actions, so the record shows who did what.
See the Evidence File on your own process.
A Proof of Value runs on your data and shows you every record before you commit.
Evidence File