Your Reconciliation Spreadsheet Has 100 Unique Status Codes
Ken Wogan
We analyzed 14 mid-sized EMS agencies last year. All of them tracked PCR status. None of them could reliably tell you which PCRs were actually complete.
One agency had 47 unique status variations across 189 staff members. Another had spreadsheets in three different locations that disagreed with each other about which calls had been documented. A third relied on a color-coded system where nobody could remember what the colors meant anymore.
The symptom is always the same: auditors and billing staff spend more time translating status codes than actually doing their jobs.
Why This Happens
It usually starts innocently.
A supervisor tracks PCR completion on a spreadsheet. They use “Pending” for calls that need documentation. Works fine. Then someone else starts using “In Progress” for the same concept, and nobody harmonizes it. Then billing adds “Submitted.” Then someone adds “Needs Revision.” Then a crew member puts “Almost Done” in there.
Over time, you end up with a language problem. The spreadsheet technically tracks status, but nobody agrees on what the statuses mean.
In some agencies, the problem is more chaotic. Different supervisors maintain different sheets. Different shifts use different terminology. Your EMR has one status system. Your billing spreadsheet has another. Your paper charts have a third.
The result: you have lots of data about PCR status, but the data is unusable. You can’t pull a reliable report. You can’t identify which calls are genuinely outstanding. You can’t tell an auditor with confidence what your actual completion rate is.
Real Example: The Color-Coded Chaos
One agency we reviewed had a spreadsheet that looked like this: green for complete, yellow for in progress, orange for missing info, red for not started, blue for… nobody could remember. The color system had been in place for four years and had accumulated meanings organically.
When a new billing manager arrived, they spent a week trying to decode what the colors meant. They finally asked a supervisor, who said, “Oh, blue is for calls that we need to follow up on but the crew is off duty so we’re waiting for them to come back.”
That’s not a status code. That’s a reminder. It shouldn’t be in the status system at all.
But it was, because there was no structured way to handle “we’re waiting on something.”
The Invisible Compliance Gap
Here’s what happens with uncontrolled status codes: you develop blind spots in your compliance without realizing it.
An auditor requests a list of all complete PCRs from March. You give them a list based on your best interpretation of the status spreadsheet. But because your status codes are loosely defined, you might include PCRs that are technically “Submitted” but haven’t passed quality review. Or you might exclude PCRs that are “Final” because you thought they meant something different.
Either way, your list to the auditor doesn’t match what you’d actually defend as “complete.”
Or consider billing: your billing department is trying to match PCRs against payer denials. They search the spreadsheet for all “Billed” records. But because different people use “Billed,” “Submitted,” “Complete,” and “Sent to Insurance” interchangeably, they miss calls that actually got submitted but weren’t coded as “Billed.”
Or they try to track why certain calls weren’t submitted. They filter for “Incomplete” or “Missing Info” or “Needs Revision”—not realizing the same condition might be labeled differently in three places on the sheet.
The compliance gap isn’t that you don’t have the information. It’s that the information is there but unusable.
The Revenue Impact
Every call that can’t be reliably identified in your status system is a call that might not get billed.
If your billing staff can’t easily identify which calls are complete and ready for submission, they might not submit them. Or they might submit incomplete records (without knowing they’re incomplete) and get denials. Or they might reprocess the same calls multiple times because the status codes don’t make it clear what’s been done.
One agency we consulted with was reprocessing the same 30 PCRs every month because their status system made it impossible to track which ones had already been billed. Over three months, that was roughly $18,000 in duplicate work and administrative overhead.
The auditor later asked why they were billing claims multiple times. The answer was: because we couldn’t tell from the status codes which ones were already processed.
The Standard Everyone Needs
You don’t need a complicated status system. You need a simple one that everyone understands.
Here’s what works:
Status 1: Not Started. The crew ran the call but hasn’t begun documentation.
Status 2: In Progress. Someone is actively working on the documentation. It’s not done yet.
Status 3: Complete. The documentation has been finished and is ready for whatever comes next (QA, billing, submission).
Status 4: On Hold. Documentation is paused for a specific, documented reason. This status includes the reason (waiting for crew verification, missing information pending follow-up, etc.). It includes the expected resolution date.
That’s it. Four statuses. Add a notes field if you need to capture additional context, but the status code itself should be one of those four.
With four statuses:
- Billing knows exactly which calls to bill (Status 3 and any Status 4 with a resolved reason)
- Supervisors know which calls need follow-up (Status 2 without recent activity, Status 4 past the expected resolution date)
- Auditors get a clear answer about your completion rate
- The system is reliable enough that you can actually run reports
Making the Transition
If you’re currently swimming in a sea of unclear status codes, the transition is worth the initial effort.
First, audit your current system. Look at every unique status code you’re using, either in your spreadsheet or your EMR. List them. Then ask: what does this actually mean? If you can’t define it in one sentence, it’s not a real status code.
Second, define your four statuses and what each one means in your specific context. Write them down. Make sure everyone involved (supervisors, billing, quality review) understands the definitions the same way.
Third, clean your historical data. Go back through your previous months of tracking and recode everything into your four statuses. This is tedious but necessary—if you keep the old data as is, you’ll never have reliable historical reports.
Fourth, retrain everyone. Explain the new system. Show examples. Make it clear that everyone uses the same four codes, and that’s non-negotiable.
Fifth, audit compliance. Spot-check your tracking for the next month. Are people using the codes correctly? Are there drift and reversion? Reinforce the standard until it sticks.
What Gets Better
With a clear, standardized status system:
Your billing process becomes efficient. Staff can reliably identify which calls are ready to submit.
Your audits become defensible. You can pull a report and confidently say how many calls were complete in a given period.
Your QA process improves. Supervisors can identify which PCRs need review and which ones are stalled.
Your staff actually uses the system, because it’s simple and makes sense.
The Bottom Line
A status system with a hundred variations is worse than no status system at all. It creates the appearance of tracking while providing no actual visibility.
You don’t need fancy. You need clear, standardized categories that everyone uses the same way. Four statuses. Consistent definitions. No exceptions.
That’s the difference between tracking that looks good in a spreadsheet and tracking that actually drives decisions.
Ryan Wogan Wogan Solutions