How to map a revenue cycle process

Start with one unit that can be followed from beginning to end: a claim, batch, payment, denial, or information request. A map called simply ‘billing’ is too broad to show who owns a decision or where work waits.

Write a specific start event and end condition, then record what is included and excluded. The boundary should be narrow enough that the team can trace real examples without changing the subject halfway through the exercise.

Observe how people complete the work in the systems they actually use. Compare that path with the written procedure, because undocumented workarounds, duplicate entry, and personal tracking files often explain delays that a policy-only map misses.

For every step, capture the owner, information received, system used, action performed, output created, next receiver, expected timing, and evidence of completion. Keep the wording concrete enough that another person could recognize the event in a work queue or audit trail.

Map the normal path first, then add the exceptions that materially change ownership, timing, or evidence. At each decision, record the criteria, the role with authority, the reason captured, and the next owner and deadline.

Do not treat sent, received, accepted, and completed as the same state. A clean handoff states what the receiver must acknowledge and what happens when the item is incomplete, rejected, or not accepted on time.

A useful control detects missing, late, duplicate, or incorrect work before the failure becomes an aged balance or compliance issue. Define its owner, criteria, frequency, evidence, and resolution route instead of labeling a box only as ‘quality check.’

Use independent reconciliation where a downstream total must agree with an upstream source. A dashboard can show volume, but the process still needs a named owner who investigates differences and records their disposition.

Trace at least one normal example and one exception through the completed map. If the team cannot identify a current owner, system state, or completion record at any point, the map has exposed an operating gap that needs a decision.

Assign one owner for maintaining the map, define review triggers, and link the approved map to the procedures, training, and control evidence it governs. Update it when systems, payer requirements, roles, or escalation paths change.