We already have SOPs written. Do we need to start over?

No. We use your existing procedures as the starting point and turn them into a working system rather than rewriting the content from scratch.

What if a process has a lot of exceptions?

We map the common exceptions into the workflow so they're handled by rule, and route anything unusual to a person to decide.

Will this add bureaucracy to simple tasks?

The goal is the opposite — routine steps run automatically, and people only get involved where a decision or exception genuinely needs them.

Can it escalate to a manager if something is overdue?

Yes. Overdue tasks can notify a manager directly, so problems surface while there's still time to act.

How many processes can be automated this way?

Most businesses have several — onboarding, purchasing approvals, quality checks. We typically start with the one causing the most disruption.

Workflow & SOP Automation

Put your standard operating procedures into a system that assigns, tracks and escalates work.

Most businesses already have SOPs written down somewhere — a document nobody opens once training is finished. This system turns the procedure itself into a workflow: tasks get assigned automatically, deadlines are tracked, and anything overdue is escalated without someone chasing it manually.

Find What We Can Automate See how we implement

How the system works

Illustrative interface

01SOP
Standard operating procedureSample

02Trigger
Trigger
Event
Status change
Process
Quotation review

03Task created
TaskIllustrative
Review customer quotation
Owner
Sales Manager
Due
Today
Status
Pending approval
- Pricing checked(completed)
- Terms confirmed(completed)
- Manager sign-off(pending)

04Owner
OwnerIllustrative
One named owner, not the whole teamAssigned

05Approval / escalation
ApprovalIllustrative
- Approved in timeCloses
- OverdueEscalates

06Completion / record
RecordIllustrative
- Step completed and timestamped
- Owner recorded
- Audit trail kept

The problem

A written procedure isn't the same as a working process

A document describes what should happen. It doesn't assign the next task, remind anyone of a deadline, or flag when a step has been skipped. So the procedure only runs correctly when someone experienced happens to be watching.

When that person is out sick, on leave, or has moved on, the process quietly reverts to whatever the next person remembers — which is rarely the full procedure.

Management finds out something went wrong after a customer complains, not while there was still time to catch it.

The old way — handled manually

Procedure exists only as a document
Process depends on one experienced person
Missed steps go unnoticed
No record of who did what

Every step depends on someone remembering. Nothing connects to the next step on its own.

Why it happens

SOPs live in documents, not systems

A PDF doesn't assign work or send a reminder.

Process depends on one person

Only the most experienced staff member reliably follows every step.

No escalation path

Missed steps aren't flagged until the consequence shows up later.

What we automate

The work this system takes off your team

Converting a written SOP into a sequence of tracked tasks
Assigning each step to the right person or team automatically
Tracking deadlines and sending reminders before they're missed
Escalating overdue steps to a manager without manual chasing
Recording who did what and when, for audit and training
Flagging exceptions that don't fit the standard flow

Before and after

What changes on the ground

Same people, same customers, same tools where they already work — a different flow between them.

Before: scattered work

Procedure exists only as a document
Process depends on one experienced person
Missed steps go unnoticed
No record of who did what

Information is copied between tools by hand. Nothing is connected, so nobody can see the full picture without asking someone.

ScatteredConnected

With ReLeaf: one connected system

01Procedure runs as a workflowNot a document nobody opens
02Anyone can follow itSteps assigned automatically
03Missed steps flagged earlyEscalated before they matter
04Full audit trailWho did what, and when

Each step hands the next one the information it needs. Work moves forward on its own and management can see where every job stands.

Use cases

Where businesses apply it

Onboarding a new customer

Every step — account setup, credit check, first order handling — is assigned and tracked instead of relying on a checklist someone might skip.

Quality control on production

Inspection steps are logged with sign-off, so gaps are visible immediately rather than at the audit.

Approval chains for purchasing

Purchase requests move through defined approval steps automatically, with escalation if someone doesn't respond.

Who benefits

Operations manager: Confidence that procedures run the same way regardless of who's on shift.
New employees: A system that tells them what's next, instead of guesswork.
Business owner: Less dependence on any single employee to keep things running.

Possible integrations

Microsoft 365
Google Workspace
Zoho
Excel
Google Sheets
Odoo

We work with what you already run. If a tool is not listed, we look at whether it can connect before recommending a change.

Implementation

How we put this in place

Scoped so the first version is running inside your business quickly, then extended.

01
Document the real process
We map what actually happens, not just what the manual says.
02
Design the workflow
We define tasks, owners, timings and escalation rules.
03
Build the system
We put the workflow into a tool your team already uses or a lightweight new one.
04
Run and adjust
We monitor the first weeks and refine steps that don't fit reality.

Questions we usually get asked

Related systems

Industries we build this for

Go deeper

See all seven systems

Turn your SOPs into something that actually runs

Send us one procedure you rely on and we'll show you how it could work as a tracked workflow.

Find What We Can Automate Book an AI Business Audit