home / use cases / back-office operations / compliance-document-chasing

Compliance documents, collected before the deadline

Before every audit, tax season or renewal deadline, your Aivell emails each client the list of documents you need, tracks what has arrived in a spreadsheet, chases the stragglers on an escalating schedule, and hands you a clean status report — who is in, who is late, who is ignoring you.

Watch the demo

starts when: Every morning during collection season, on schedule

The problem

Every audit season, the same ritual. You need one signed declaration from ninety clients by the end of the month, so someone builds a spreadsheet, sends ninety emails, and starts ticking. A third of the clients respond in a day. The rest need a second mail, a third, a phone call — and each chase means re-reading the thread to see where things stand.

The chasing is the actual work, and it drowns in everything else: an office worker already receives 121 emails a day, and your reminder is just one of them — on both ends. When the partner asks “who is still missing?”, the answer requires archaeology across ninety threads.

How your Aivell does it

  1. The season starts with one list. You give it the clients, the documents you need and the deadline. The tracker is created, the first requests go out — each in the client’s own language, three weeks ahead.
  2. The cadence runs itself. Silence for a week earns a follow-up quoting the original request. Three days from the deadline, the client turns red in the tracker and Sofia lands in copy. Nobody is chased twice in the same week — persistence, not harassment.
  3. Arrivals are ticked immediately. A reply with the document closes the loop: tracker updated, client thanked, file kept. The wrong form or last year’s version gets a same-day answer spelling out exactly what to fix.
  4. The overview is always current. No more scrolling threads to reconstruct the state of play. The tracker is the state of play — live, complete, and honest about who has ignored three requests.
  5. Friday, the report. Collected, pending, silent — one email to Sofia, ready for the partner meeting.

The guardrails make it safe to let run: mail can only go to the contacts on the tracker, received documents are never forwarded outside your domain, and the client list itself can only be changed by a human. The chore is your collection procedure written down once — and finally followed to the letter, every season.

The chore, as you'd write it.

No flowcharts, no code — a chore is just a message to your Aivell, in your own words. It shapes it into a solid, guarded procedure and follows it to the letter. This one:

Giulia Aivell · collect annual certificates ● active

each morning, open the tracker and list clients still missing documents

first request goes out three weeks before the deadline, in the client's language

one week later, follow up with the original request quoted

three days before the deadline, mark the client red and put Sofia in cc

when a reply arrives with an attachment, tick the tracker and thank the client

wrong year or wrong form — answer the same day saying exactly what to fix

never chase the same client more than twice in one week

friday at 16, send Sofia the season status — collected, pending, silent

You
Got it — I'll start right away, and check with you whenever something needs a human.
Giulia Aivell

The tools it uses.

Connected with single-click passkeys — no copied tokens, no OAuth hell.

Email requests documents and chases the gaps
Spreadsheets keeps the collection tracker current
Schedule runs the round each morning until done

Sensible guardrails.

Every tool can be limited to exactly what this chore needs. For this one, you might set:

Email Outbound mail is limited to the client contacts listed in the tracker. Addresses not on the list are blocked, full stop.
Spreadsheets May update status and date columns on the tracker. Adding or removing clients is a human's job.
Email Attachments received are filed, never forwarded outside your domain.

Questions, answered.

Can it run several campaigns at once — audit papers, tax documents, renewals? +

Yes. Each campaign is its own chore with its own tracker and its own deadline, so the audit chase and the tax-season chase run side by side without mixing up clients or documents.

Does it verify that the documents clients send are valid? +

It checks the obvious — something arrived, it matches what was asked, the year is right — and ticks the tracker. Judgement calls about validity stay with your team; the chore's job is that nothing sits unnoticed.

Client documents are confidential. Where does the processing happen? +

On the box, in your office. The emails, the attachments and the tracker are read and written behind your firewall — no third-party AI service ever sees a client's certificate or even their name.

What happens to clients who never respond? +

Whatever you wrote. The usual pattern is escalate — mark them red, copy the partner, put them on a call list. The Aivell keeps score honestly, so the Friday report shows exactly who has been ignoring three polite requests.

Related.

What is an Aivell?

An Aivell is an on-premise AI colleague: a small box that plugs into your network, runs its own AI onboard and takes the repetitive work off your desk. Prompts, documents, data — nothing ever leaves your office. Unplug the internet: it keeps working.

You describe each task as a chore, in plain language. Your Aivell turns it into a solid, guarded procedure and runs it in the background — with guardrails on every tool, a complete audit trail, and approvals in your hand when you want them. One-time setup, fixed monthly fee. No tokens, no overages.

Watch the demo

onboard inference · air-gapped · fixed monthly fee