Audit evidence pack
Preparing for an internal audit means one person walking the whole document estate with a checklist, opening folders. This agent does the walking: it takes the checklist your quality lead has written, finds the documents that answer each line, and returns an indexed pack plus an honest list of the lines nothing answered. What the pack shows is your quality lead's call, not the agent's.
Step by step
Connect the document estate
Policies, procedures, meeting records, training records, audit files: the sources your evidence actually sits in, connected read-only.
Load your own checklist
The agent works to the checklist your quality lead maintains. It brings no standard of its own and applies none.
It searches line by line
For each checklist line the agent looks for documents that answer it and records where each one was found.
It assembles the indexed pack
Evidence is ordered against the checklist, with the location and the date of every document listed beside the line it supports.
It lists what is missing
Lines with no evidence, and lines answered only by something out of date, come back on a separate list rather than being padded out.
The quality lead approves
The pack and the gap list stay in the drafting folder until the quality lead has read both and approved their use.
Exactly what this agent can see, touch and change
The same five controls sit behind every Askollo agent. These are this one's settings — visible before you build it, not buried in an admin screen afterwards.
Context
What reaches the modelQuality and governance leads preparing an internal audit or an assurance review, and registered managers asked to evidence how something is done.
Escalation
When it asks a personThe quality lead approves the pack and the gap list before either is used or shared
Applications & Rights
Which tools it uses, and what it may do in each
SharePointRead only
ConfluenceRead only
Google DriveReadWrites newCreates new records or documents. Never edits, moves or deletes anything that was already there.Verification
How you know it’s rightEvery claim links to the document it came from. A statement the agent cannot cite does not make it into the output — which is what makes the result reviewable in minutes rather than re-read end to end.
Who it’s for
Quality and governance leads preparing an internal audit or an assurance review, and registered managers asked to evidence how something is done.
What you’ll need
- The document estate connected read-only
- Your own checklist supplied
- A drafting folder for the pack
- A quality lead to approve
What you get
- An indexed evidence pack
- A source and date per checklist line
- A gap list of unanswered lines
What it doesn’t do
It gathers and indexes what your checklist asks for. It does not decide whether a standard has been met, it makes no regulatory judgement, and the pack is evidence for your quality lead to read rather than an assurance opinion.
We build the first one with you
Not a template you configure alone. We sit with your team, build it on real data, and hand over the controls.
Scope
One session with the people who actually do the work. We agree what the agent reads, what it may write, and who approves.
Co-build
Built on your own data, not a sandbox. You watch it being made, so you know why it behaves the way it does.
Handover
You own the controls. Change the context, tighten the rights, move the approval gate — without coming back to us.
Parts of the work currently spread across the categories below. It does not replace any of those products outright.
Frequently asked
Does it tell us whether we would pass?
No, and it is built not to. It shows what evidence exists for each line of your checklist and what does not, with dates and locations. Judging what that means is your quality lead's work, and dressing it up as a verdict would be worse than useless.
What if the same evidence answers several lines?
It is indexed against each line it answers, with one copy in the pack. That tends to expose the lines resting on a single document, which is usually the more interesting finding.
Can it see records it should not?
Only what you connect. This agent is built on the document estate rather than care records, with read-only rights per source, and the scope is agreed with your information governance lead before anything is connected.
How current is the pack?
It is built from the connected sources at the moment you run it, and each item carries its date so an old document is visible as an old document. Re-running it once a gap has been filled costs a person a glance rather than another walk through the folders.