Which decision is being passed between departments without anyone owning the resolution?
Describe the dependency in the other team’s language
A billing exception may require information or a decision from elsewhere in the practice. Explain what is missing, why the next step depends on it and what a usable response looks like. Sending an account back with an unexplained status creates another handoff problem. The aim is a shared understanding of the work, not an argument about which department created it.
Make cross-team decisions visible
Some questions cannot be resolved within a single work queue. Keep a short record of decisions that require several functions, including the accountable decision owner, contributors and next review. Distinguish a person who supplies information from the person who can authorize a change. This helps prevent a request from circulating indefinitely among people who cannot actually resolve it.
Check the effect on neighboring workflows
A process change can remove effort from one team while adding it to another. Before calling it an improvement, examine the next handoff, the unresolved work and the burden on staff or patients. Define the intended effect and look for unintended consequences. Use that feedback to revise the workflow instead of protecting a local productivity number at the expense of the wider operation.
Signals worth investigating
These are prompts for a review, not proof of a particular cause.
- Teams repeatedly return work without explaining the required response.
- A request circulates among people who can contribute information but cannot decide.
- Local productivity improves while downstream exceptions become harder to resolve.
What the working evidence should show
Documents to request or build during a review—not claims about completed client engagements.
- Dependency brief
- The missing input, its source, the waiting workflow and a usable response definition.
- Cross-team decision log
- The decision owner, contributors, evidence needed and next review.
- Change impact review
- Intended effects and unintended burdens across neighboring teams and patient-facing work.
One useful first step
Select a recurring cross-team escalation. Identify the person who can decide, not only the people who can pass the message along.
Use the practice onboarding checklist ↗︎Scope and references
This is an editorial approach to operating review, not a documented case result, clinical advice or official payer instruction. Specific billing decisions require current program and payer guidance and appropriate professional review.
Read the insurance & claim workflows primer and its primary references ↗︎