Consulting service
Business Process Mapping
Documentation of how a process actually runs today — including the exceptions and the undocumented workarounds — as a basis for improving or automating it.
What you need to know first
- What problem does this solve?
- A process cannot be improved, automated, handed over or audited because nobody has an accurate description of it. What documentation exists describes an intended process; the real one lives in the heads of the people doing it, along with the workarounds nobody wrote down.
- What exactly do I receive?
- A clear map and written description of each process in scope as it is genuinely performed: the steps, who does them, the systems touched, the decision points, the handoffs, the exceptions, and where time and rework are actually going.
- How is it priced?
- Fixed fee per process, quoted on enquiryThe fee is quoted for your requirement, because scope, systems and complexity differ in every case.Priced as a fixed fee per process for a defined number of processes and participants. No figure is published yet; the fee is confirmed in writing before work begins. A whole-department or cross-division mapping exercise is quoted.
- How long does it generally take?
- Typically 1 to 3 weeks per processIndicative, and driven almost entirely by the availability of the people who perform the process.
- What happens next?
- Send an enquiry describing the requirement. We confirm the scope, the fee and the timescale in writing before any work begins. An enquiry is not an order: an engagement becomes binding only when it is expressly accepted, as set out in the Terms of Service.
Deliverables
- A process map per process in scope
- A written description covering steps, roles, systems, decision points and handoffs
- An exception register: what happens when the normal path does not apply
- Findings on where time, rework and risk are concentrated
- Where useful, a candidate list for automation or simplification
Included
- Working sessions with the people who perform the process
- Process mapping and written documentation
- Exception and workaround capture
- Identification of bottlenecks, rework loops and single points of failure
- Two revision rounds with the participants
Not included
Stating the boundary is part of the offer. Anything here can usually be arranged separately.
- Implementation of any change or automation
- Formal certification, accreditation or audit sign-off
- Organisational design, restructuring or role changes
- Software licences or tooling
- Ongoing maintenance of the documentation, unless separately scoped
Customer prerequisites
- Named processes with a defined start and end, rather than a whole department
- Access to the people who actually perform them
- Willingness for workarounds to be documented honestly
Information and access we need
We will ask for these. Where the work needs access to a system, access is arranged and scoped with you rather than assumed.
- The processes in scope, with their start and end points
- Access to the participants, and time in their calendars
- Any existing documentation, even if outdated
- Volumes: how often the process runs and how often each exception occurs
Expected process
Enquiry
You name the processes and what you intend to do with the map.
Written scope and fee
The number of processes and participants, the fee and the indicative timescale, in writing.
Sessions
Working sessions with the people who perform the work, following the real path rather than the documented one.
Draft and correction
A draft map and description, corrected by the participants across two rounds.
Delivery
Final maps, descriptions, exception register and findings.
Meetings, revisions and scope
- Meetings
- Meeting required, during the assessment (about 60 minutes)
- Revisions
- 2 revisions included. Two revision rounds, because the first draft is expected to be corrected by the people who do the work — that correction is part of the method, not a defect.
- Scope
- Deliverables are limited to those expressly included in the agreed scope. Additional revisions, meetings, research or services outside that scope may require additional fees — see the Consulting Terms.
Frequently asked questions about this service
How do revisions work?
Where a service includes a set number of revisions, the service page states the number and what a revision covers. A revision refines the agreed deliverable; it is not a route to a different deliverable.
Deliverables are limited to those expressly included in the agreed scope, and additional revisions, meetings, research or services outside scope may require additional fees — see Consulting Services Terms and Marketing Services Terms.
What kinds of workflows can you automate?
The recurring, rule-based ones that currently depend on somebody remembering: moving information between systems, producing and circulating a document, routing something for approval, generating a recurring report, keeping two records in step, triggering a notification when a state changes.
What is deliberately not automated is judgement. A good automation keeps the decision with a person and removes the clerical work around it, which is also what makes it safe to operate when something unexpected arrives.
Feasibility is established by an assessment rather than assumed up front — Workflow Automation Assessment.
What is discovery, or an assessment?
A defined, separately-scoped piece of paid work whose deliverable is a decision-ready document rather than a running system.
An assessment establishes what exists now, what is genuinely possible, what it would take, and what it would cost — and it belongs to you. You can act on it with us, act on it with someone else, or decide not to act at all.
It exists because the alternative is worse: quoting an implementation from a description produces either a padded estimate that protects the supplier, or an optimistic one that fails halfway through.
Next step
Reference business-process-mapping is added to your enquiry automatically so it reaches the right place.