A supplier process that understands its own rules.

Supplier onboarding required coordination across procurement, finance, compliance, legal and operational systems, with rules that changed by supplier type, risk and contract conditions. In this customer engagement, Orgni was used to map the organization and its workflow rules before automation work began.

A fragmented operation

Every new supplier started the same way: a procurement manager chasing forms, a compliance team waiting on documents, an IT team waiting on both before provisioning access. The rules were real but scattered - some in policy documents, some in legal's inbox, many in the heads of whoever had onboarded a similar supplier before.

Average onboarding took three to four weeks - not because anything was complicated, but because every handoff was manual, every team had its own queue, and no system understood why a given step was required for a given supplier.

Building the organisational model

We built the onboarding process on Orgni, but the starting point was not a workflow diagram. It was connecting the organisation behind the workflow into one operational model:

• Roles. Who in procurement, finance, compliance, legal and IT is responsible at each step.
• Policies and rules. Which requirements apply by supplier type, risk level and contract conditions.
• Evidence and approvals. Which documents count, who signs off, and what has already been collected.
• System states and exceptions. Where each supplier stands, and how unusual cases were handled before.

What became possible

With the requirements mapped, the workflow supported intake, verification checks, approval routing and IT provisioning. Unusual cases could be routed to the appropriate people with their context; the work was logged so teams could follow the process.

People only show up to make decisions - and when they do, the context for the decision is already assembled.

The numbers

Applying the mapped process

In this case, onboarding time fell from three to four weeks to days. Compliance sign-off rates improved too, as documents were collected and reviewed systematically rather than chased over email. Unusual cases could be handled with the mapped requirements and the relevant people involved.

The mapped process was also reused for contractor onboarding, a parallel process with similar friction. This customer work offers a practical example of how representing organizational rules can support process changes.

"It used to feel like herding cats. Now the whole thing just moves on its own. People approve when they need to approve, and everything else happens automatically."- Head of Procurement, operations company