The New AI Employee
Home › Services › Process mapping and handover
Running today

Business process mapping: what the job really involves, written down before they leave

Business process mapping usually starts with interviews. Ours starts with the mailbox. An AI employee reads a role's email history, read-only, and writes down what the person really does. When someone key is leaving, you get a handover before their last day.

Running today: handover documents written from a departing person's mailbox history and attachments, read-only.

Why does knowledge walk out of the door?

Business process mapping is hard because the real process isn't written down anywhere. It lives in one person's head and one person's inbox.

Say your bookkeeper hands in her notice. She knows which supplier needs a call, which customer always pays late and which report goes out on the first of the month. In two weeks she writes down half of it.

The half she forgets is the half that costs you money three months later.

How does it work?

We read the mailbox, then a person checks what we wrote. That's the whole knowledge transfer process.

  1. With your yes, we read the person's mailbox and attachments. Read-only.
  2. Emails and files are sorted by customer, supplier and repeating task.
  3. We work out who the person deals with and what comes back every month.
  4. We split what's finished from what's still open, and list the deadlines.
  5. We write it up: what the job involves, what's open, and a handover plan.
  6. A person reads it, fixes it and decides who takes over what.

What do you get?

You get process documentation built from what really happened, ready before the last day.

Who is it for?

It's for any business where one person knows things nobody else has written down.

What won't it do?

It only reads. It never changes the mailbox, writes to anyone or sends anything.

It starts only with your yes, and reading someone's mailbox should follow your own policies and the law where you are. The document stays a draft until a person approves it. Every action goes in a log you can read, and one command stops it.

The AI employee is ours. It's rented monthly and runs on our servers against your own accounts. The mailbox and the documents stay yours. If the rental stops, the workflow stops and you keep everything.

Questions, answered plainly

Is this a standard operating procedure template?

No. A standard operating procedure template is a blank form somebody has to fill in. This is written from what the person really did, and a person checks it.

Can it map a process when nobody is leaving?

Yes. Reading how the work really moves is how every AI employee we build starts, and the written map is useful on its own.

Does it change anything in the mailbox?

No. It doesn't move, delete, answer or send a single email.

How early should it start?

As early as you can. The plan is ready before the last day, so the person leaving can still answer questions.

Tell us which role needs mapping or handing over. Write to hello@thenewaiemployee.com and we'll tell you plainly if it fits and where to start.

Related workflows

All workflows

Write to us

Tell us which hours you want back.

Three lines are enough: what you do, what takes your time, how many hours a week it costs. Write to hello@thenewaiemployee.com.

Offices in Sheridan (Wyoming), Panama City, London, Bucharest and Milan.