The hand-back.

At some point in every engagement, there is a hand-back: the moment when we transfer the running operation to the client's internal team and step out of the day-to-day. Done well, this is one of the most valuable things an outside firm can do. Done poorly — or without planning — it is the moment where the work of the build starts quietly unraveling.

The difference between a hand-back that holds and one that doesn't is almost entirely preparation. We build the hand-back package from day one of the engagement, not from the last two weeks of it.

What the package contains

A complete hand-back package has six components:

1. The provider data file.A clean, validated roster of every contracted and credentialed provider — NPI, taxonomy, contract effective dates, fee schedule applied, and credentialing status. Not the output of whatever system we were using during the build, but a clean export that the client's team can use in their systems going forward. The file should be validated against the CMS provider file format before hand-back, not after.

2. Documented processes.The contracting workflow, the credentialing workflow, the provider data maintenance process, and the adequacy monitoring process — each documented well enough that someone who wasn't involved in the build can execute them. Process documentation is easy to deprioritize when you are in the middle of a build; it needs to be built incrementally, not assembled the week before hand-back.

3. The contracting pipeline. A complete status report on every provider who is still in the contracting or credentialing pipeline at the time of hand-back — what stage each is at, who owns the relationship, and what the next action is. The new team should not have to reconstruct pipeline state from email threads.

4. The operating cadence.The weekly reporting structure, the monthly adequacy review protocol, the quarterly provider relations outreach calendar, and the annual recredentialing cycle. These should be in the client's calendar before we leave — not described in a document, but actually scheduled.

5. The key contacts.For every major provider relationship we managed during the build — health systems, large group practices, FQHCs, behavioral health providers — a current contact name, phone, and email, plus a brief note on the relationship history. Relationships that were built by us and handed over to a new team don't always survive the transition; a warm introduction to the key contacts helps significantly.

6. The open issues list. Every known adequacy gap, every contract that is still being renegotiated, every credentialing file with outstanding deficiencies. Nothing is more disorienting to a new team than discovering in month two that there was a known problem nobody told them about.

Staffing the hand-back

The internal team that receives the hand-back needs to be identified and brought into the build long before the hand-back date. We prefer to have the incoming team operating alongside us for at least 30 days before the full transition — attending the weekly operating review, owning a portion of the contracting pipeline, building the relationships with the providers they will manage going forward.

A hand-back to a team that has never been in the room is not a hand-back. It is a rebuild with different people.

The goal is not to hand back a network. It is to hand back an operation that can maintain the network.

The 90-day check-in

We build a 90-day post-hand-back check-in into every engagement. Not a formal review — a working conversation: how is the adequacy holding, what has changed in the contracting pipeline, what is the state of the credentialing queue, what problems have surfaced that the team needs a second set of eyes on.

This is not about dependency. It is about catching problems at 90 days that are much easier to address than at 180 days. The organizations that have the smoothest transitions are the ones that use the 90-day check-in to make small adjustments rather than waiting for a problem to become a crisis before asking for help.