Before you design a better process, map the one that exists: the as-is (current state) process. Two rules make an as-is map useful.
Map what really happens, not what the procedure says. Build it from observation and from the people who do the work, then check it with them. Paper slips, side spreadsheets and phone calls belong on the map if they are part of the work today.
Keep the loops. Rework is where time goes: a missing receipt sends the staff member back to check again, a rejected form goes back to the customer. In BPMN, a loop is a flow back to an earlier step, usually from a gateway. A map without loops often hides the real cost of the process.
Use lanes, so hand-offs are visible, and stop at the level of detail the decision needs. You will compare this map with the future (to-be) map; the differences become the change.