A process map: from receipt to dispatch

When a process lives in people's memories and verbal agreements, it can be neither assessed nor improved: everyone knows only their own stretch and nobody sees the whole picture. A process map puts that picture on a single sheet. It shows every step, who performs it, the document and the system. Control gaps then stand out: a point the goods pass through but nobody answers for.

What the map contains

For a warehouse the most convenient format is a swimlane diagram. Each lane belongs to one role: supplier, receiving clerk, storekeeper, manager, accountant. Steps run left to right in time, and a move from one lane to another shows a hand-over, that is, who now carries responsibility. The symbols are simple:

• rectangle: an action ("count the quantity");
• diamond: a decision ("does the quantity match the delivery note?");
• document symbol: which paper or file is produced;
• system symbol: which program records the entry (1C, Excel, WMS).

How to draw it

1. Set the boundaries: from where (the truck enters the yard) to where (the customer takes the goods).
2. Pull the steps out of your walk-through notes and interviews. Write each step as "verb + object": "prepare the discrepancy report", "post the receipt".
3. Against each step, note the performer, the document and the system.
4. Do not forget exceptions: what happens if the quantity does not match, the goods are damaged, or the supplier sends the load without documents.
5. Mark and number the control points (C1, C2…): places where a check is built into a step.
6. Show the map to the process owner: "Is this what really happens?" They will make corrections.

The tool does not matter. A whiteboard, paper or draw.io will do, and sometimes a plain Excel table (step, who, document, control) is enough.

Example: a household appliance importer

From receipt to dispatch to a regional dealer there were eight steps: 1) the container arrives and the driver hands over the waybill; 2) the receiving clerk inspects the seal and packaging; 3) the storekeeper counts the boxes; 4) the clerk writes a report; 5) an operator posts the receipt in 1C; 6) the goods are put away; 7) picked to order; 8) sent to the region.

The map immediately showed three gaps:

• steps 3 and 5 are done by one person, who counts the goods and also enters them in the books;
• at step 4 a report is written only when there is a discrepancy, so the "all is well" case leaves no document;
• between steps 7 and 8 nobody checks the picked goods against the delivery note.

None of this was visible in the written procedure, because at every stage it said "the responsible employee".

What to look for on the map

• A step with no owner: unclear who answers for it.
• A step with no document: the action happens and leaves no trace.
• One person both receives goods and keeps the records.
• Places where a document is created after the physical movement.
• No return loop: it is not drawn where rejects and returned goods go.
• Two routes: an "official" one and a "fast" one, with the second missing on paper.

Gaps found are marked in red and then moved into the register of findings.

Telling the control points apart

Control points on the map are of two kinds. A preventive control stops an error before it happens: for example, at receiving a second person recounts the quantity (C1). A detective control finds it afterwards: for example, a weekly reconciliation of shipped goods with the issues in 1C (C2). Both are needed, but a process that relies only on detective controls usually notices a loss late. Using the map, the auditor checks that every significant risk has at least one control point. A risk with no control is a gap. A control that nobody performs is a gap too.

The current map and the target map

First the actual (as-is) map is drawn: not what the procedure says but what happens. Then an improved (to-be) version is drawn up. The difference between the two maps becomes a list of recommendations: a check to add, a duty to separate, a document to introduce.

Conclusion

A good map reveals more than a many-page description: it shows at a glance the step nobody answers for. OmborAudit draws the map together with the process owner and turns the gaps it finds into concrete recommendations.