We capture how your organisation actually works and transform it into validated BPMN 2.0 process maps and professional documentation.
The standard service focuses on understanding and documenting the AS-IS process — not forcing a transformation or implementation programme. Future-state redesign, automation, software configuration and implementation sit outside the standard engagement unless separately agreed.
Built for the people who own how work gets done
Operations · Process · Quality · Compliance · IT · HR · Leadership
Important processes often live across employee knowledge, emails, spreadsheets, systems and outdated procedures — without one reliable representation of how the work actually happens.
Sound familiar?
“The process exists mostly in people's heads.”
“Nobody agrees on how this process works.”
“We need the AS-IS before we change the system.”
Knowledge depends on people
Critical operational knowledge sits with a few experienced employees. If they leave or change role, it goes with them.
Teams work differently
The same process is performed differently by different people, because no agreed representation of it exists.
Responsibilities are unclear
Processes crossing several departments carry ambiguous ownership, approvals and handoffs.
Procedures are outdated
Existing documentation is incomplete, years old, or disconnected from how the organisation actually operates.
Onboarding relies on word of mouth
New employees learn the process through informal explanation, which takes time and produces inconsistency.
Projects start without an AS-IS
System replacements and transformation initiatives begin without an accurate picture of current operations.
We define the process boundary, interview the people who perform it, review what documentation exists, model the AS-IS process in BPMN 2.0 and validate the result with your stakeholders.
Expert-led. AI-assisted. Stakeholder-validated.
Expert-led, AI-assisted
AI accelerates transcription, extraction and drafting. Process judgement, modelling decisions and quality review stay with an experienced practitioner.
AS-IS discipline
We document how the process actually operates — not the policy, not best practice, not what it ought to look like.
Formal BPMN 2.0, readable output
Proper notation for roles, decisions, events and exceptions — paired with a simplified business view your team can actually read.
A bounded engagement
Defined scope, defined deliverables, a fixed fee confirmed after scoping. The engagement is focused on understanding and documenting the process, independently of any future implementation platform.
Exact contents depend on the package you choose. Every engagement delivers a validated representation of the agreed process.
BPMN 2.0 AS-IS model
The formal current-state model, plus a simplified business view for non-specialist readers.
Roles and handoffs
Who does what, where responsibility moves between people and departments.
Decisions and business rules
The decision points that change the path, and the rules that govern them.
Systems and key documents
Which tools participate where, and what data or documents move through the process.
Exceptions and variants
Most diagrams document the happy path. Real operations happen in the exceptions — those get modelled too.
Process findings
Factual observations — duplicate records, unclear ownership, competing variants. Descriptive, not prescriptive.
Validation record
Who confirmed what, and when — so the documentation carries a traceable status, not just a date.
Delivered as PDF
You never need specialist BPMN software just to read your own documentation. Editable source where commercially included.
An illustrative supplier onboarding process, showing the business view and the structure of the documentation pack that accompanies it.
Supplier Onboarding — AS-IS business view
Illustrative sampleSimplified business view. Compliance and Finance reviews run in parallel and synchronize once all active review paths have completed successfully — the formal BPMN 2.0 model carries the full event, gateway and exception logic behind it.
Inside the documentation pack
Detailed Process Documentation carries the full set of registers. Lighter packages carry a subset — the comparison is in the packages below.
Download the sample (PDF)The process shown is a fictional illustration created for demonstration. It does not represent a real client, and no figures on this page are presented as client results.
Every package is quoted as a fixed project fee, confirmed after we scope the process — never an open-ended hourly estimate.
A high-level view of how one process currently operates. A low-risk way to start, or to decide how deep to go.
Expert discovery and a validated AS-IS BPMN 2.0 model, covering activities, roles, decisions, systems and exceptions.
The model plus structured operational documentation — built to be reused as an operational reference, not read once.
Multiple related processes across one business area, or a high-level view of how the whole organisation operates.
How pricing works: we assess the real complexity of the process — activities, roles, departments, systems, decisions, exceptions and variants — and then confirm one fixed project fee for the agreed scope. A straightforward process costs less than a genuinely complex one. Material additions are re-scoped and agreed before any extra work is done.
We agree the process boundary — trigger, start, end, outcome, what's in and what's out — before any substantive work begins.
Focused sessions with the people who actually perform the work, plus a review of whatever documentation already exists.
Activities, roles, decisions, business rules, systems, exceptions and variants are consolidated — and contradictions resolved, not averaged.
The AS-IS model is built at business granularity, using only the notation complexity the process genuinely requires.
A structured session where your team confirms the model reflects operational reality. Internal quality review happens before you ever see a draft.
Agreed corrections are incorporated and the final documentation is delivered, versioned and ready to reuse.
What we need from you
One main contact, the right stakeholders, available documentation and participation in validation.
Here is an honest account of how the alternatives compare — including where they beat us.
| Approach | Main trade-off |
|---|---|
| Internal team | Lower external cost, but consumes internal capacity |
| Freelancer | Can be efficient for diagram production; discovery depth depends on the individual |
| Transformation consultancy | Strong broader capability, but typically designed for larger programmes |
| Intelligent Insights Lab | Focused AS-IS discovery, modelling, documentation and validation |
Approach
Internal team
Main trade-off
Lower external cost, but consumes internal capacity
Approach
Freelancer
Main trade-off
Can be efficient for diagram production; discovery depth depends on the individual
Approach
Transformation consultancy
Main trade-off
Strong broader capability, but typically designed for larger programmes
Approach
Intelligent Insights Lab
Main trade-off
Focused AS-IS discovery, modelling, documentation and validation
To be clear about what this is not: we do not redesign, automate, configure or implement the process. If what you need is a transformation programme carried through to delivery, a transformation partner is the better fit — and we are happy to hand over a clean AS-IS baseline for them to work from.
10+ yrs
Practical business-process implementation experience behind every engagement.
BPMN 2.0
Formal modelling capability, not generic flowcharting — and models stay readable for business users.
12 stages
A documented delivery methodology, with internal quality review before you see a draft.
Validated
A defined validation step in which your stakeholders confirm the model reflects reality.
Every Business Process Mapping engagement is currently led directly by an experienced business-process professional.
The diagram is only one output. The engagement includes defining the scope, understanding the real process through stakeholder discovery, resolving inconsistencies, modelling correctly in BPMN 2.0, quality review, validation with the people involved, and reusable documentation.
For a standard process: a short kickoff, a small number of focused interviews of around 45–60 minutes each, and one validation session of 60–90 minutes. Exact effort is confirmed during scoping.
A single standard process is a relatively short engagement, but delivery effort and elapsed calendar time are different things — the latter depends heavily on stakeholder availability. Once we scope the process, we agree the expected schedule alongside the fixed project fee.
Business Process Mapping focuses on understanding, modelling and documenting the current process. Software configuration, automation and implementation are outside the standard engagement. Our role is to create the reliable current-state documentation that can then support whichever approach you choose.
No. We handle the formal modelling. We use BPMN because it gives the process consistent structure around responsibilities, decisions, events and exceptions — and we keep the final documentation understandable for business readers, with a simplified business view alongside the formal model.
You absolutely can, if you have the internal capacity and process-modelling expertise. What we add is an independent, structured discovery process, the willingness to challenge contradictions, formal BPMN 2.0 modelling and validated documentation — without consuming as much of your team's time.
Existing procedures are useful inputs and can reduce discovery effort. The question is whether they still represent how the process actually operates. We use them during discovery and then validate the current process with the people performing it.
AI can accelerate transcription, extraction and initial drafting, and we use it where it helps. The hard part is determining what is actually true, resolving conflicting descriptions from different stakeholders, choosing the right modelling granularity and validating that the model represents operational reality. The service is expert-led and AI-assisted.
The standard service documents the AS-IS process, which is what keeps it objective. If improvement ideas come up during discovery we can capture them separately, but redesign, automation and implementation are distinct activities and not part of the standard mapping engagement.
That's a common starting point. A Process Snapshot or a short scoping engagement establishes the process boundaries first, and then we can work out together whether deeper documentation is worthwhile.
Yes. Process knowledge is treated as confidential and is isolated between engagements — it is never reused across clients. Deliverables carry a confidentiality notice, and we operate from the EU under the GDPR.
Tell us which process you need documented. We'll confirm whether it fits the service, scope it properly, and come back with a fixed project fee.
The first conversation is a 20–30 minute qualification call. No preparation needed.
Tell us what needs documenting and why now. You don't need to know the scope — that's what the first call is for.
Enquiry sent
We'll come back to you within one business day to arrange a short qualification call.
We only use your details to respond to this enquiry. See our Privacy Policy for details.