A sample report for a firm.
This is the report a firm gets after the AI audit. It is written about a real client, a private practice run by one person. I have changed details so that the practice cannot be recognised. How the work runs and what I recommend are as they were.
AI audit report
What the system should take on, in what order, and what stays in your hands
- Prepared for
- A private practice, one consultant (details changed)
- Prepared by
- Paweł Dobrzyński
- Date
- November 2026
Paweł Dobrzyński · AI audit report1 / 15
In short
Your practice is one person. You assess and support the people insurers refer to you, and everything around that work lands on you as well: reading each referral, inviting the person, booking, chasing forms, writing reports and adding up invoices.
What the day showed: a case passes through nine stages between the day the referral arrives and the day it closes, and keeping those stages moving takes you about two hours a day. I recommend a system that runs them inside the Google Workspace you already pay for, with an agent beside it. What should be left for you is about twenty minutes a day: reading what is ready, and saying yes.
Nothing is replaced. Your documents stay documents, your calendar stays your calendar, and your invoices stay in your accounting system.
The report ends with the price of every stage and a step-by-step recipe for the first automation, which your team can build alone or ask me to build.
- 9
- stages every case passes through
- 10 h
- of paperwork a week today
- 8 h
- a week I expect to come back
- 50+
- things the agent can do, each change confirmed by you first
Paweł Dobrzyński · AI audit report2 / 15
Your practice, as I understood it
Everything below comes from the day I spent with you and from your own documents. Where it is wrong here, it would be wrong in the build too, and one sentence from you corrects it.
| What | How it runs today | What matters for the build |
|---|---|---|
| Referrals | An insurer sends each referral as a document. You read it and type it into your records. | The same fields come every time, so a machine can read them and you can check them. |
| Appointments | You offer times by email, wait for the reply, confirm, and move things when plans change. | One calendar, with your rules for working days, hours and the gaps between meetings. |
| Forms | Consent and questionnaires go out by email and are chased from memory. | Each answer belongs to one case and has to be found again months later. |
| Reports | Written one by one from your notes, the questionnaires and the documents in the file. | Each kind of report has the same sections every time. |
| Invoices | Added up by hand from the calendar and your notes. | Every meeting held and every report sent is a line to bill. |
| Insurers | Each one wants to know where its cases stand. | The same questions come back every month. |
Paweł Dobrzyński · AI audit report3 / 15
A case from referral to invoice: today, and with the system
Nine stages. The middle column is how each runs today. The last column is what I recommend.
| Stage | Today | With the system |
|---|---|---|
| Referral | You read the document and type its contents into your records. | You drop the document into a folder. The system reads the person's details from it, checks the ones that must be there, opens the case and its folder, and lists anything missing as a note to follow up. |
| Invitation | Written by hand, with dates looked up in your calendar. | One invitation from your template, with up to four proposed times or a booking link. The letter, the holds in the calendar and the link are made in one step. |
| Booking | Emails back and forth until a time is agreed. | The person picks a time on a page of their own. The meeting is confirmed, the confirmation goes out and the insurer is told. |
| Consent and questionnaires | Sent by email and chased from memory. | The person fills them in online. The answers are scored and attached to the case, and a missing consent raises a note to chase. |
| Assessment | The outcome lives in your notes. | The outcome is recorded and decides the next stage. The report is drafted from the evidence in the case, and you sign it off. |
| Sessions | Each one confirmed by email and counted by hand. | Each confirmation books the meeting, counts the session, adds the line to bill and reminds you when a report falls due. |
| Reports | Typed from a blank page. | Drafted section by section from the evidence, in your own layout. You review, edit and send it through a link that expires. |
| Invoices | Added up by hand. | The system keeps the ledger and creates draft invoices in your accounting system. You finalise them there. |
| Closing | Dates and lengths looked up by hand. | Closing a case stamps its dates, and the case feeds your reporting to insurers. |
Paweł Dobrzyński · AI audit report4 / 15
The week in hours: where the time goes, and what comes back
The total is the practice's own: about two hours of paperwork a day today, and about twenty minutes with the system. How it splits across the kinds of work is my estimate, and every row says so. In your report the split comes from what I see on the day we work together and from your own documents.
| Kind of work | Today | After | You get back | What the number rests on |
|---|---|---|---|---|
| Reading referrals and typing them in | 2 h 30 min | 20 min | 2 h 10 min | My estimate of the split. |
| Writing invitations | 1 h 30 min | 15 min | 1 h 15 min | My estimate of the split. |
| Booking and moving appointments | 2 h 30 min | 25 min | 2 h 5 min | My estimate of the split. |
| Chasing consent and questionnaires | 1 h 30 min | 15 min | 1 h 15 min | My estimate of the split. |
| Adding up what to invoice | 2 h | 25 min | 1 h 35 min | My estimate of the split. |
| Together | 10 h | 1 h 40 min | 8 h 20 min | The total is the practice's own figure: about two hours a day, down to about twenty minutes. |
Paweł Dobrzyński · AI audit report5 / 15
The build: what I recommend, and in what order
Eleven parts in five stages. Each part gives you something you can use, and each runs on live work before the next one is started. You can stop after any of them.
Stage 1. The ground
Before the system does anything for a client, it has to live in your own accounts and speak in your words.
The installation
- What the system does
- Sets up the record, the folders, the calendar rules and a page that shows whether everything is sound, all inside your own Google Workspace.
- What stays in your hands
- The go-ahead for every release.
- Built on
- Google Workspace: Sheets, Drive, Calendar, Gmail.
- How you know it works
- The health page says the installation is sound.
Your templates
- What the system does
- Turns every routine email into a numbered template: the invitation, the confirmation, the request for questionnaires, the notice to the insurer, the report, the session confirmation, the reminder.
- What stays in your hands
- The wording. Each template is a document you edit yourself.
- Built on
- Google Docs.
- How you know it works
- You see the exact email before it goes, filled in from the case.
Stage 2. Coming in
Where a case starts, and where the typing is.
Referrals
- What the system does
- Lists the documents waiting in the referral folder, reads each one, shows you its fields one by one and turns it into a case with its own folder.
- What stays in your hands
- Checking the fields and confirming.
- Built on
- Google Drive, an AI reader for the document.
- How you know it works
- Anything the document left out is listed as a note to follow up, so nothing is silently missing.
The invitation and the booking page
- What the system does
- Sends the invitation with proposed times or with your genuinely free times, and gives the person a page of their own to pick one.
- What stays in your hands
- Choosing which times to offer.
- Built on
- Google Calendar, Gmail, a booking page.
- How you know it works
- The link belongs to one person and one invitation, works for fourteen days and stops working once it is used.
Consent and questionnaires
- What the system does
- Sends the forms, matches every answer to its case, scores it and keeps the history as a chart.
- What stays in your hands
- Reading what the answers mean.
- Built on
- Google Forms.
- How you know it works
- A consent that has not come back shows up as a note to chase.
Stage 3. The work itself
You do the work with the person. The system does what surrounds it.
Today
- What the system does
- Builds the day's list from the live record: follow-ups still open, reports due, cases waiting for a booking, for questionnaires or for a later review.
- What stays in your hands
- Doing them.
- Built on
- The record in Google Sheets.
- How you know it works
- Nothing on the list was typed there by you.
Sessions
- What the system does
- On each confirmation it books the meeting with its link, counts the session, adds the line to bill and raises the reminder when a report falls due.
- What stays in your hands
- Holding the session, and marking whether the person came.
- Built on
- Google Calendar, Gmail.
- How you know it works
- A meeting that was waived is not invoiced.
Reports
- What the system does
- Drafts each report from the case record, the questionnaires, your notes and the documents in the file, section by section, into your own layout.
- What stays in your hands
- Reviewing, editing and signing. The system drafts; it does not sign.
- Built on
- Claude, Google Docs.
- How you know it works
- Dates, scores and counts are filled in from the record and never pass through the AI.
Stage 4. Money and the insurers
The two things you add up by hand at the end of the month.
Invoices
- What the system does
- Keeps a ledger of everything that can be billed and creates the invoice as a draft in your accounting system.
- What stays in your hands
- Finalising the invoice and sending it.
- Built on
- Your accounting system.
- How you know it works
- Every line on the invoice points back to a meeting held or a report sent.
Reporting to insurers
- What the system does
- Shows your cases by status and by insurer, referrals month by month, and the averages you are asked for, ready to export.
- What stays in your hands
- Deciding what each insurer is sent.
- Built on
- The record in Google Sheets.
- How you know it works
- The numbers are counted from the cases, not kept in a separate spreadsheet.
Stage 5. The agent
Last, because it stands on everything before it.
The agent beside the screen
- What the system does
- Does on request anything the screens can do, and answers questions from the whole record.
- What stays in your hands
- The yes before every change.
- Built on
- Claude, and over fifty tools of the system.
- How you know it works
- Before any change it shows a card with exactly what it will do. Money and a person's identity need a typed confirmation.
Paweł Dobrzyński · AI audit report6 / 15
What each stage costs
Every stage has a fixed price, so you know the whole cost before anything is built. Stage 2 is the one the recipe after this table builds.
| Stage | Price | What you have after it |
|---|---|---|
| Stage 1. The ground | £1,000 | The system installed in your own Google Workspace, with your own templates and a page that shows it is sound. |
| Stage 2. Coming in | £1,500 | Referrals read into cases, invitations sent, a booking page, and consent and questionnaires matched to each case. |
| Stage 3. The work itself | £1,500 | A daily list, every session counted and billed, and a draft of each report waiting for your review. |
| Stage 4. Money and the insurers | £1,000 | Draft invoices in your accounting system, and reports to insurers counted from the cases. |
| Stage 5. The agent | £1,500 | An agent beside the screen that answers from the record and asks for your yes before any change. |
| Together | £6,500 | You can stop after any stage and pay only for the ones you order. After each one goes live you have 14 days of fixes at no charge. |
Paweł Dobrzyński · AI audit report7 / 15
Your first automation, step by step
I recommend starting with referrals. Reading each one and typing it into your records takes 2 h 10 min of your week, more than any other kind of work in the table above, and the same fields come in every time, so a machine can read them and you can check them.
Someone on your team who knows Google Workspace can build this in about a day: a morning for the folder, the sheet and the instruction, an afternoon for the test. You need a Google Workspace account with Drive and Sheets, access to Google's Gemini on your plan, one person who will check the results, and five real referrals to test with.
The rule that holds all of it together: nothing goes into your records until a person has confirmed it.
- Make the folder. In Google Drive, create a folder called “Referrals in” and, inside it, a folder called “Read”. Share it only with the people who handle referrals. From now on every referral document goes into “Referrals in”.
- Build the case sheet. In Google Sheets, create a sheet called “Cases” with these columns: Case number, Date received, Person's name, Date of birth, Email, Phone, Referrer, Reason for referral, Notes, Status, Checked by and Checked on. Give Status a drop-down with three choices: Waiting to be checked, Checked, Needs follow-up.
- Save the instruction. Copy the instruction below into a Google Doc called “Referral reader”. It sits next to the folder, so anyone on the team can improve it, and the wording stays in your hands.
- Read one referral by hand. Open a document from “Referrals in”, ask Gemini to follow the instruction, and read what comes back. Do this before anything is automated. Check that your Workspace plan covers Gemini under the same data protection terms as the rest of your Google account.
- Put the answer in the sheet. Paste the returned row into “Cases” with Status set to “Waiting to be checked”, then move the document to “Read”. The row is a proposal. It is not your record yet.
- Get a nudge. In Google Sheets, open Tools, then Notification rules, and choose to be emailed in Gmail whenever a row is added. You hear about a new referral without watching the sheet.
- Check it as a person. Read the row against the original document. Fix anything wrong, and look at every cell that says “missing”: ask the insurer for it, or note it in Notes and set Status to “Needs follow-up”. When the row is right, fill in Checked by and Checked on, set Status to “Checked”, and only then copy it into your records.
- Test on five real referrals. Run five of your own, including one that is messy and one with fields left out. Count the cells that came back wrong. Change the instruction and run them again until five in a row come back with nothing wrong. If you would rather not build this yourself, I will build it for the fixed price of Stage 2, with 14 days of fixes after it goes live.
Read the attached referral document.
Return one row with these fields, in this order: case number, date received, person's name, date of birth, email, phone, referrer, reason for referral.
Copy each value exactly as the document gives it. Do not correct, shorten or reword it.
If a field is not in the document, write “missing” in its place. Never guess, and never fill a gap from another field.
Add one last field, notes, for anything in the document that is unclear or contradicts itself.
Do not send, save or change anything. Only return the row.
Paweł Dobrzyński · AI audit report8 / 15
The agent, more closely
I recommend an agent that sits next to the screens. Everything you can do in the system with a click, it can do when you ask in one sentence. It works on your practice's own data, so it knows every case, every appointment and every invoice, and it answers from the record instead of guessing.
It reads what the screens read: the cases, the calendar, your mailbox, the documents in each file, the questionnaires that have come back, the ledger and the invoices, and its own notes of how you like things done. It has over fifty tools: about thirty that look something up and about twenty that change something.
The same rules hold for it as for the rest of the system. Before any change it shows a card and waits for your yes. An email is a draft first.
- A question. “Who has not sent their questionnaires back yet?” The answer comes from the live record, not from memory.
- A change. “Move Tuesday's session to Thursday at two.” The meeting moves with a fresh link, and the email to the person waits for you to read and send it.
- A piece of work. “Prepare this month's invoices.” Each case's unbilled work becomes a draft invoice in your accounting system.
Paweł Dobrzyński · AI audit report9 / 15
What the system will not do
Said plainly, because an honest boundary now is worth more than a pleasant surprise later.
- Sign for you. It drafts reports. It never signs one, and it never sends one you have not read.
- Send without you. Every email is shown to you as it will go, or left as a draft, before anything leaves.
- Guess. When a name is not an exact match, it asks which person you mean and waits.
- Write to strangers. Each case has a closed list of addresses it may write to: the person, the insurer's case manager, and a representative once their authority is on record.
- Move a case backwards. Automatic changes of status only ever move a case forward.
- Keep people in its own memory. The agent remembers how you like things done. It does not store anyone's personal details there; the system refuses.
Paweł Dobrzyński · AI audit report10 / 15
Where your data lives
This matters for your data protection file, so it is worth being exact.
| What | Where it is |
|---|---|
| The cases | In controlled sheets inside your own Google Workspace. |
| Documents and templates | On your Drive, as documents you edit yourself. |
| Appointments and email | In your own Calendar and your own Gmail. |
| The booking page | It can read one invitation and submit one booking. It cannot see other people, other cases or anything else in your calendar except the free times. |
| AI | It writes prose from the evidence in the case. Dates, scores and counts come from the record and never pass through it. |
| A shared service | There is none. One installation, yours, with no outside database holding your cases. |
| The trail | Every send and every change is written to a log. |
| Erasing | Only on your explicit word, as a deliberate act with its own confirmation. |
Paweł Dobrzyński · AI audit report11 / 15
The tools I recommend
You already pay for almost all of them. That is the point: the system is a layer over what you have.
| Tool | What I recommend it for |
|---|---|
| Google Workspace | The home of the whole system: your account, your domain, your ownership. |
| Google Sheets | The record: cases, appointments, the ledger and the log. |
| Google Drive and Docs | A folder for every case, and every template and report layout as a document you edit. |
| Google Calendar | Proposed times, confirmed meetings and your rules for working days and hours. |
| Gmail | Every templated email, as a draft or a send. |
| Google Forms | Consent and questionnaires, filled in online. |
| A meeting link | Google Meet or Zoom, made fresh for every meeting. |
| Your accounting system | Draft invoices, and whether they are paid. |
| Claude | Writes the reports and runs the agent. |
| Google's Gemini | Reads the referral documents, and stands in if the first model is unavailable. |
Paweł Dobrzyński · AI audit report12 / 15
What it costs to run
The system adds very little to what you already pay. I name every line, so that nothing arrives as a surprise.
| Cost | How much | What to know |
|---|---|---|
| Google Workspace | What you pay now | Nothing changes. |
| The accounting system | What you pay now | Nothing changes. |
| AI | By use | The bill comes straight to you, so you see every pound. I choose the model for each job, set a limit and watch the use with you. |
| A server | Nothing | The system lives in your own Workspace. You rent no server and pay me no subscription. |
| The build | Fixed price for each stage | Every stage has its price in the table “What each stage costs”: £6,500 for all five. You choose which to build and can stop after any of them. |
Paweł Dobrzyński · AI audit report13 / 15
What stays in your hands
A system like this can give the impression that it has taken over things it has not. These five stay yours.
| What | What it covers |
|---|---|
| The work with the person | Every assessment and every session, and what you conclude from them. |
| The signature | Every report is yours to review, edit and sign. |
| The send | Pressing send on an email, and finalising an invoice. |
| The words | Every template and every report layout is a document you change yourself. |
| The decisions on a case | Its outcome, what to charge and what to waive, and when to close it. |
Paweł Dobrzyński · AI audit report14 / 15
Yours would be about your firm.
The AI audit is one day with your firm, online or at your office if you are nearby. Nothing is built that day. Within the week you get a report like this one, about your own cases, your own calendar and your own people, with a step-by-step recipe for the first automation, and it is yours whether or not I build anything.
Paweł Dobrzyński · AI audit report15 / 15