What Happens to Staff After a DSO Sale?

Start with what each person will actually do

What happens to staff after a DSO sale depends on the actual employment and operating plan. A support proposal should explain which work moves to a central team, which work stays in the office, and who can resolve a problem. Staff need instructions they can use when a task is late or an answer is missing.

Start with the current job rather than the job title. An office manager may enter time, correct supplier invoices, manage schedules, and answer staff questions. Moving one system to a central team does not prove that all those duties disappear. Break the role into tasks before discussing the new arrangement.

The ADA's January 21, 2021 guide distinguishes limited support from broader service arrangements, including some in which nonclinical staff work for the DSO. Identify the actual employer and service scope. ADA: DSO business services guide

The staff communication guide covers announcements and confirmed answers. The staff retention guide covers roles, availability, and coverage. This guide tests the promised support after the sale: who owns the work, what remains local, and what demonstrates a completed handoff.

Separate employment terms from service responsibilities

Ask the responsible employer to confirm each person's proposed role, reporting line, work location, pay, hours, and benefits through the proper process. Have the relevant advisers address transaction structure and applicable duties. Do not assume the sale itself establishes a uniform staff-transfer rule or the terms every person will receive.

Then make a separate service map. A payroll vendor may process a file without deciding an employee's pay. A central human resources team may answer a policy question without supervising daily clinical work. A local manager may submit a correction without authority to approve it. Identify those differences before giving staff a generic support email.

Record the decision owner as well as the task worker. The decision owner is the named person authorized to settle the issue within the actual arrangement. The task worker gathers or processes the information. One person may perform both roles, but the plan should say so.

Use the DSO comparison guide to place these choices beside the seller's broader objectives. A seller who wants less administrative work needs evidence about the duties that remain.

Map local work, central work, and unresolved exceptions

Describe each task with a start, an input, a responsible person, and evidence of completion. Avoid broad entries such as payroll handled centrally. Instead, identify who submits time, checks the file, approves a correction, and confirms that the employee received the right result.

An exception is a case that the routine process cannot finish. A missing approval, rejected file, or unexplained deduction can create local work even when the standard processing sits elsewhere. Decide who investigates and who follows the matter until the affected person receives an answer.

This table is a planning aid, not an allocation imposed on every DSO. Fill it with the actual parties and terms. If two teams both say the other owns the decision, the handoff remains unresolved. Giving the employee both phone numbers does not resolve that gap.

Give payroll and benefits questions an accountable owner

A payroll error needs a private route that reaches the responsible employer and the people who can correct it. Tell the employee how to report the issue, what evidence to provide, and who will give the next update. Do not ask them to repeat personal details in a broad transaction email chain.

DOL guidance requires FLSA-covered employers to keep accurate hours and wage information for covered, nonexempt workers. Its recordkeeping page also identifies pay-period and payment-date information. Central processing should be checked against the actual records and covered relationship. DOL: Wage and hour records

For the operating plan, identify who preserves the source time record and who checks the processed result. If a correction crosses the proposed closing date, assign the review to the responsible parties for the relevant period. Counsel and payroll advisers should address legal duties; the workflow should not leave an error ownerless while they do so.

Benefits questions require the actual plan and employee circumstances. Name the employer or plan contact authorized to confirm the answer, with a backup for an unanswered request. Do not predict that coverage, cost, eligibility, or leave will improve because the buyer has a larger organization.

Keep permitted clinical duties separate from a staffing chart

A new title or central staffing request does not establish what a person may do in patient care. Ask the clinical lead to review the proposed tasks, qualifications, supervision, and applicable requirements. Record which work requires a qualified local decision and who provides cover when that person is absent.

ADA Code 2.C addresses qualified auxiliaries, legally delegable tasks, and dentist supervision. ADA: Auxiliary personnel duties

For example, if an administrative scheduler cannot determine whether a proposed change is appropriate, the plan should route the question to the authorized clinical person. Staff should not infer clinical permission from an open appointment slot or an instruction to improve office flow.

Patient information also needs a separate lawful access and security process. Use fictional or properly prepared test records when possible for workflow demonstrations. A sale NDA is not unrestricted permission to use patient charts for training. The records transfer and custody guide covers that separate workstream.

Test the service with an unfinished task

A presentation may show the routine task moving smoothly through a system. Ask the teams to demonstrate an exception too. Choose a harmless, approved example: a supply order lacks an authorization, or a user cannot reach a permitted screen. Follow it from the local report to the actual resolution.

Watch for handoffs that end with a forwarded message. Record who accepts responsibility after the transfer and how the local office knows it was accepted. If a request sits between two queues, staff need a route to escalate it without submitting the same work repeatedly.

Do not turn this demonstration into a promise that every future request will be fast. Its value is showing the path and revealing missing access or authority. Repeat a failed part after it is fixed, and keep the evidence narrow enough to show what was actually tested.

Work through a fictional local-workload case

Assume a fictional office spends 48 local staff-hours in one week on a defined group of nonclinical administrative tasks. The measured group excludes patient care, required clinical supervision, and all other work outside the example. Hours are supplied teaching inputs, not a staffing benchmark or a description of a real practice.

The proposed support plan moves routine tasks that previously took 24 of those hours to a central team. Assume that team completes the full assigned routine scope. The other 24 hours of original work remain local. The handoff also creates eight additional local hours resolving exceptions and four additional hours coordinating with the central team.

The eight and four hours are distinct new work, outside the retained 24-hour routine workload. That boundary is essential. If a task was already in the retained total, it must not be added again. Likewise, central staff-hours are not measured here; the 24-hour deduction refers to the office's former time on the transferred tasks.

Local workload falls from 48 to 36 hours, a reduction of 12 hours. It does not fall to 24 hours as a calculation that ignores the added work would suggest. The support plan still reduces the measured local workload in this base case, but by less than the transferred routine task estimate alone implies.

The result does not establish a reduction in headcount, payroll, or safe clinical staffing. It does not value central service fees or show the whole practice's profit. It answers a narrower question: how much local time remains for this task group under the supplied assumptions.

Test central completion and exception work independently

First change only the amount of original routine work the central team actually completes. Assume it completes tasks representing 16 former local hours instead of 24. The remaining original local work becomes 32 hours. Keep the eight hours of added exceptions and four hours of coordination unchanged. Total local workload becomes 44 hours.

That is eight hours above the 36-hour base and only four hours below the original 48. The assumed service shortfall matters because the uncompleted original tasks return to the local workload. The model does not assume staff can absorb those hours without a change in priorities or coverage.

For a second independent sensitivity, return to full completion of the 24-hour transferred scope. Change only added exception work from eight to four hours. Keep coordination at four hours. Local workload becomes 32 hours: 24 retained routine hours plus four exception hours plus four coordination hours. This is four hours below the base.

The branches point to different decisions. A shortfall in completed central work may need a revised service scope or local cover. Excess exception work may call for better inputs, clearer authority, or a simpler correction path. A generic request to work faster does not identify which problem exists.

Use actual observations before changing the real staffing plan. Compare equivalent task groups and periods, noting unusual events. Ask staff whether extra work has moved outside the measured categories. Otherwise, a lower total may reflect an omitted task rather than a completed handoff.

Train for the assigned role and verify usable access

Give people enough preparation to perform their assigned tasks. A login email is not evidence that a user can complete the work. Check the relevant permissions, instructions, support route, and backup process. Use the actual staff role when choosing what to demonstrate.

OSHA's recommended safety-program practices call for training that explains assigned roles, reporting routes, and procedures. They also emphasize understandable training and opportunities for questions. These recommendations are a program framework; applicable training requirements need separate review. OSHA: Safety education and training

For the service handoff, ask the user to show the approved task and explain where an exception goes. Identify any unresolved access issue and its owner. A person who can finish the routine example may still need help with the failed or urgent case.

Define any seller support and availability through the actual arrangement. The seller work-back guide addresses the scope and resources continued work needs.

Time involvement around the work staff must perform

Keep initial buyer outreach seller-blind and obtain an NDA before identifying the practice to a buyer. Then involve the relevant staff when their actual work or duties require preparation, review, or notice. Coordinate timing with the seller, buyer, and advisers. There is no operational plan in simply keeping everyone uninformed until closing.

Give each participant the information needed for the task. A payroll setup discussion may need employment details through a private route; it does not require circulating all offer terms. A system test may need approved access; it does not justify sharing an unrestricted patient database.

If closing moves, confirm which instructions remain in force and which planned changes should wait. Identify who can authorize the next step. Staff should not have to infer the legal employer or active system from an old calendar invitation. Required notices and professional duties remain separate from the announcement plan.

Common mistakes in a DSO staff handoff

One mistake is treating a service list as proof that work has moved. Ask for a completed task, an accepted exception route, and a named decision owner. A central team may perform substantial work while the local office still carries an unplanned correction burden.

Staffing decisions need the full operating plan, qualifications, availability, employment terms, and professional review. The limited workload case cannot establish those facts.

Avoid assuming a broad support inbox can answer every payroll or benefits question. Identify who has authority to confirm the actual terms and who follows up with the employee. Unanswered personal questions should not disappear from the action plan because they cannot be discussed publicly.

Finally, do not close a handoff item when the sender has merely forwarded it. Confirm that the receiving team accepted the task and that the agreed result reached the person who needs it. Reopen the item if a material assumption changes.

Summary: verify the work and the people responsible

A useful DSO staff plan explains the employer, local duties, central services, and authority to resolve exceptions. Test completed work and measure the local effort that remains, including new coordination and corrections. Keep clinical duties, patient privacy, and required notices within their own proper review. To discuss the commercial staff-transition questions with Jason Taken, business broker at HedgeStone Business Advisors, book a confidential intro call.