We Knew January Was Coming

It comes around at roughly the same time every year.

No one wakes up on December 28 and says, “Wait. There’s a January this year?”

And yet, somewhere between Thanksgiving leftovers and the first week back after New Year’s, patient access teams across healthcare find themselves staring at a pile of eligibility checks, changed benefits, reset deductibles, new authorization requirements, payer portal issues, and patients who quite reasonably expect their care to continue.

And once again, everyone seems a little surprised.

That may be the real reverification problem.

It is not that healthcare organizations do not know the work is coming. They do.

It is that knowing something is coming and actually preparing an operation to absorb it are very different things.

January has a way of exposing the plan

Reverification is often discussed as an eligibility task.

Operationally, it behaves more like a stress test.

Take a therapy practice with patients coming in several times a week. Their coverage may still be active on January 2, but their deductible has reset. Their visit limit may have changed. A referral may need updating. A new authorization may suddenly be required.

Meanwhile, the patient is already on Tuesday’s schedule.

Multiply that by hundreds or thousands of patients and the problem becomes less about clicking “verify” and more about two very basic questions:

Do we have enough capacity to get through the work?

And:

Do we know what needs to be worked first?

Those sound simple. Under January volume, they are not.

A provider leader I spoke with recently described reverification as their annual “Super Bowl” season. That might be slightly dramatic, but only slightly. Her organization begins looking at the coming January workload in August and September, estimating volumes, reviewing what went wrong the prior year, identifying staffing needs, tracking payer changes, and preparing the people who will eventually have to explain those changes to patients.

That is less exciting than a Super Bowl.

It is also probably why they are better prepared for one.

One lesson is painfully obvious: start earlier

There is always a temptation to think, “How can we work January benefits when it isn’t January yet?”

Fair question.

You cannot verify information a payer has not made available.

But that does not mean there is nothing to do.

You can estimate volume.

You can identify which patient populations are most likely to require reverification.

You can understand which payers create the most manual work.

You can make sure portal credentials actually work.

You can decide who owns exceptions.

You can hire and train temporary resources.

You can configure and test automation.

You can make sure the front office knows what is coming.

And as payers begin making new-year benefit information available, sometimes in December, you can start working what is available instead of waiting for the entire workload to arrive at once.

The lesson from organizations that have lived through rough reverification seasons is not particularly glamorous:

Runway matters.

Hiring takes time. Training takes time. Workflow changes take time. Technology takes time.

Even getting everyone to agree on what the workflow is can take more time than anyone would like to admit.

Automation does not arrive wearing a cape

January is also an excellent time to discover whether expectations around automation were realistic.

There is a tendency to talk about automation as though a payer connection exists, someone flips a switch, and thousands of reverifications quietly disappear overnight.

Healthcare remains stubbornly committed to making things more interesting than that.

Payers have different portals. Plans have different rules. Organizations have their own requirements. Data has to map correctly. Credentials have to work. Workflows have to be configured. Results have to be tested and validated.

Then something changes.

That last part is important.

A workflow that worked last month may hit a payer change, a portal issue, or an unexpected exception next month. That is why automation needs monitoring after it goes live, not a congratulatory email and abandonment.

And automation does not have to complete every case to be useful.

If it retrieves most of the benefit information and leaves a specialist with two things to confirm, that is still less work than asking that specialist to do the entire case manually.

At scale, partial automation is not partial value.

It is capacity.

The people problem never really goes away

The other uncomfortable truth is that reverification still needs people.

Some cases need judgment. Some need phone calls. Some need investigation. Some payers simply refuse to cooperate with the beautifully automated future we were promised.

That means staffing for reverification should not be an afterthought.

It also does not necessarily mean adding permanent headcount for a problem that peaks seasonally.

The better approach is to understand when volume is likely to rise, build temporary capacity around the peak, use automation to remove repetitive work, and then adjust staffing as demand normalizes.

One of the most useful observations from our recent webinar planning was that technology and capacity have to scale together. Forecast the volume. Staff for it. Automate what is reasonable. Monitor what actually happens. Adjust.

None of those steps is particularly revolutionary.

Doing all of them consistently may be.

Patients experience the process too

Revenue cycle people can spend so much time thinking about throughput that it becomes easy to forget reverification has an audience.

The patient.

They may have been receiving therapy for weeks. Suddenly, a new deductible applies. Their insurance changed. Their authorization did not carry forward. Their financial responsibility looks very different from the visit they had two weeks ago.

From the patient’s point of view, “It’s a new benefit year” is not particularly comforting when the surprise arrives at check-in.

Some organizations are getting ahead of that too.

Brittany Lemoi described preparing front-office teams before the season and even communicating with patients in November and December that benefits may reset. Once new information is available, the conversation is no longer coming completely out of nowhere.

It is a small operational detail with a very human payoff.

Patients can handle information.

Surprises are harder.

Maybe the real goal is to stop relearning the same lesson

Every reverification season produces lessons.

Which payer created problems?

Where did volume exceed capacity?

Which workflows created unnecessary touches?

Where were teams flying blind?

What did patients hear too late?

What did automation handle well?

What still required a person?

The mistake is documenting those lessons in February, congratulating everyone for surviving, and rediscovering them the following December.

The organizations that seem to get better at this treat January as part of a cycle.

After the surge, learn.

In the spring, fix.

By late summer, forecast.

In the fall, prepare.

Before January, test.

Then when January arrives, execute and adjust.

There will still be payer surprises. There will still be exceptions. Someone will still be on PTO when you desperately wish they were not.

The goal is not to create a January with no chaos whatsoever.

Healthcare is probably not ready for that level of optimism.

The goal is to stop being surprised by the parts we already know are coming.

And maybe that is the most useful question for leaders right now:

When January gets here again—and it will—are we going to be dealing with a surge, or repeating a cycle of chaos we already knew how to prevent?