Service · Process mapping
Process mapping: your operations, documented
We document how your business works today - step by step, system by system. It is what makes a build scopeable on facts instead of guesses, and the documentation is yours to keep whatever you decide next.
What we do
01
Walk each process end to end
With the people who run it, from the first trigger to the point the work is finished.02
Record it as it is
Steps, systems, hand-offs and decision points as they actually happen - not as the manual describes them.03
Mark the manual and the repeated
Where work is retyped, copied between systems, or waiting on one person to be available.04
Separate rules from judgement
Which decisions follow a fixed rule and which rely on someone's experience. Only one of those automates cleanly.05
Agree a target version
What the process looks like after the change, so everyone can see what is being proposed before it is built.What you get
A documented picture of your operations that keeps its value long after the project - for onboarding, for audits, and for any future build.
- Process maps for each mapped workflow, current state.
- A written description of steps, owners, systems and hand-offs.
- A marked list of the manual and repeated steps, flagged as automation candidates.
- A target-state map showing exactly what changes if the automation is built.
- Documentation in the form that funding applications and internal reviews ask for.
Where this fits
Comes after business analysis and feeds development planning - you cannot scope a build honestly without knowing the process it replaces.
Start a project
If your processes live in people's heads rather than on paper, this is usually where to start.