What Process Mapping Covers
Process mapping is the starting point for cleaner operations. We document how tasks move from one person or department to the next, where approvals happen, what gets captured manually, and where delays or errors creep in. The goal is to give you a clear picture of current workflows before any system changes are made.
For South African SMEs, this often includes sales order handling, purchasing, stock control, finance approvals, service jobs, payroll handoffs and customer updates. We look at the practical side too, such as load-shedding interruptions, offline workarounds, branch communication and the way teams split work between spreadsheets and business software.
What We Include in the Mapping Work
Each mapping assignment is tailored to your departments and the way your business already operates. We can work with one function or a full cross-department process, depending on how much detail you need and how many sites are involved.
- Current-state process interviews with key users and managers
- Step-by-step workflow diagrams for each department
- Roles, approvals and exception paths
- System touchpoints, manual steps and data handoffs
- Gap analysis showing where processes do not match the ERP or other systems
- Improvement recommendations with clear priorities
- Updated future-state process maps for implementation planning
We also note data fields, document inputs, report outputs and any points where compliance or internal controls need to be tightened. That includes traceability for audit purposes, as well as practical items like cut-off times and who signs off on what.
How We Work Through the Process
We keep the process structured so your team knows what is happening at each stage. Most assignments start with a scoping session, followed by interviews, workflow capture, validation and a final recommendations pack. If needed, we can split the work by branch or by function, which helps when different teams operate differently in Centurion, Johannesburg or Durban.
- Step 1: Define the scope, departments and outcomes
- Step 2: Gather process information from users and managers
- Step 3: Map current workflows and document exceptions
- Step 4: Review inefficiencies, duplication and control gaps
- Step 5: Design improved system-supported workflows
- Step 6: Validate maps with stakeholders before sign-off
Our team looks at both process and system fit, so the final maps are usable for ERP implementation, integration work or internal process improvement. This makes it easier to plan changes without guessing where the bottlenecks are.
Typical Turnaround Times
Turnaround depends on how many departments are included and how many people need to be interviewed. A focused mapping exercise for one function can be completed in 2 to 3 weeks, while a multi-department project for a growing SME may take 4 to 8 weeks. Larger businesses with multiple branches or more complex approval chains can take longer.
We generally schedule the work in short, practical sessions so we do not disrupt operations. If your teams are under pressure, we can work around month-end, stock counts, or seasonal trading peaks. For sites in coastal areas like Cape Town, Durban or Gqeberha, we also take local operating realities into account, including connectivity issues and power interruptions that affect process timing.
Pricing Approach and Deliverables
Pricing is usually based on scope rather than a fixed template. We consider the number of departments, locations, users involved, and whether you need detailed future-state design, validation workshops, or support for ERP implementation afterwards. This gives you a fair quote that matches the work required, not a one-size-fits-all package.
Deliverables are normally issued as a mapped workflow set, a findings summary, and a prioritised action plan. Depending on scope, you may also receive process notes for system configuration, control points for management sign-off, and recommendations for training. If you need, we can prepare the maps in a format that your internal team can maintain later on.
Keeping the Maps Useful After Go-Live
Process mapping should not sit in a file and gather dust. Once your ERP or integrated systems are in use, we recommend reviewing the maps after go-live, then again at 3 months and 6 months to catch issues that only appear during day-to-day operation. After that, an annual review is usually enough for most SMEs, unless you add a new branch, product line or approval layer.
We can also support maintenance updates when your processes change because of new reporting rules, staff turnover or system upgrades. That way your business does not drift back into old habits. Many teams find that a small change in one department, if left unrecorded, causes errors elsewhere very quickly.
- Post go-live review at 2 to 4 weeks
- Follow-up review at 3 months
- Stability review at 6 months
- Annual process refresh for mature operations
Key facts
| Service focus | Current-state and future-state process mapping for SMEs |
|---|---|
| Typical scope | 1 to 8 departments, single site or multi-branch operations |
| Common outputs | Workflow maps, gap analysis, action plan, control points |
| Turnaround | 2 to 8 weeks depending on complexity |
| Pricing model | Quoted by scope, departments, users and deliverables |
| Maintenance interval | Post go-live review, then 3-month, 6-month and annual checks |
