Policy & procedure answers
Most policy questions have a written answer sitting in a folder nobody can navigate at half past nine at night. This agent reads the policy and procedure library your organisation actually maintains and answers the question with the section quoted and the document linked. It is deliberately narrow: it repeats your policy, it does not interpret anybody's care.
Step by step
Connect the policy library
We point the agent at the policy and procedure documents you maintain, and at nothing else.
Set the rights, source by source
Read-only throughout. Care records and personal data stay outside the agent's reach unless you deliberately decide otherwise.
Agree what it must refuse
Your clinical lead writes the list of questions the agent stops on and hands to a person. That list is part of the build, not an afterthought.
Staff ask in their own words
Questions arrive the way they would be asked out loud, not as search terms, and the agent answers from the current document.
It quotes the section back
The answer carries the wording and a link to the policy, so the reader can see the original rather than take the agent's word.
It hands over what it refuses
Anything on the refusal list, and anything your policies do not cover, goes to the named person instead of being improvised.
Exactly what this agent can see, touch and change
The same five controls sit behind every ollo agent. These are this one's settings — visible before you build it, not buried in an admin screen afterwards.
Context
What reaches the modelCare, support and operations staff who need the written answer mid-shift, and the policy owner who has answered the same question all week.
Escalation
When it asks a personThis agent changes nothing outside ollo, so it runs without an approval gate. Its output is still cited and reviewable.
Applications & Rights
Which tools it uses, and what it may do in each
SharePointRead only
ConfluenceRead only
Google DriveRead onlyVerification
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
Care, support and operations staff who need the written answer mid-shift, and the policy owner who has answered the same question all week.
What you’ll need
- A current policy library connected
- Read-only rights agreed per source
- A refusal list from your clinical lead
- A named person for escalations
What you get
- A cited answer with the policy section
- A link to the source document
- A log of questions your policies do not cover
What it doesn’t do
It repeats what your policies say and nothing more. It gives no clinical advice, makes no judgement about an individual's care or medication, and where a policy is silent or out of date it says so rather than improvising.
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
Can it see care records?
Only if you connect them, and we would not start there. The first build is the policy library with read-only rights, which is where the everyday questions actually live. Widening scope later is a decision your information governance lead makes deliberately, not a default.
What stops it answering a clinical question?
A refusal list written by your clinical lead during the co-build. Questions about a person's care, medication or presentation are stopped and routed to the named person rather than answered. The agent's job ends at what the policy says.
Our policies contradict each other in places. What then?
It shows both and names the conflict rather than choosing a winner. Teams usually find this the most useful early output, because the contradictions have been there for years and nobody had a list of them.
What happens when a policy is updated?
Answers follow the current document in the connected library, so a superseded version stops being quoted once it is replaced. Pairing this with the policy change tracking agent is how you keep the rest of the estate in step.