An mso agreement can shape how a healthcare practice receives administrative support, pays for it, shares information, and responds when the relationship changes. Owners should review it as an operating document as well as a legal one: identify what work moves to the management organization, what remains with the practice, how fees are calculated, and what happens if the arrangement ends. Use the questions below to prepare for qualified healthcare counsel; this is not legal advice.
Discuss your practice’s operating priorities
Start with the scope of services. The agreement should make it possible to tell who performs each administrative task, what deliverable is expected, and how the practice will know the work was completed. A broad phrase such as “management support” is difficult to operate unless an exhibit or service schedule gives it practical meaning.
Build a responsibility map from actual workflows, not from generic labels. List each function, the party doing the work, the person who approves it, and the records that show completion. Include the handoffs where errors or delays commonly arise: payroll inputs, vendor invoices, scheduling workflows, marketing approvals, and monthly reporting. Ask counsel which matters must remain with licensed professionals or the practice under applicable law and the proposed structure.
| Review area | Operational question | Evidence to clarify |
|---|---|---|
| Service scope. | Which recurring tasks are included and excluded? | Service schedule, owner, frequency, and deliverable. |
| Fees. | How is each charge calculated and changed? | Formula, invoice detail, adjustment process, and examples. |
| Decision rights. | Who recommends, approves, and executes a decision? | Approval matrix and escalation route. |
| Data. | Who can access which records and for what purpose? | Access controls, reporting cadence, and return process. |
| Exit. | How does service continue during transition? | Notice, handover steps, records, and transition responsibilities. |
Ask for a service-level description specific enough to use in a monthly operating review. If a service is not included, identify who provides it and how the practice coordinates it. Compare the proposed arrangement with a broader practice operations system so internal responsibilities do not disappear between teams.
Then test the scope against a real work cycle. Choose one task, such as reconciling a vendor invoice or preparing a monthly performance report. Trace the request, inputs, review, approval, completion notice, and retained record. If the agreement only names the task but not the handoffs, ask for a schedule or process document that fills the gap. This exercise also reveals duplicate work: the practice may keep doing a task while paying for a service that appears to include it.
For each service, record its expected cadence and a practical completion signal. “Reporting support” could mean a report delivered by a specified date, a review meeting, or simply access to a dashboard. Those are different outcomes. Define how a missed deadline is reported, who receives the escalation, and whether the issue triggers a corrective plan. Avoid inserting operational assumptions into the contract informally; have counsel determine where the detail belongs.
Extend the map beyond recurring tasks. Note one-time work such as onboarding a new location, changing a vendor, or moving to a new scheduling process. Identify what triggers the task, what information the practice must supply, who bears responsibility for delays, and whether the work is part of the stated fee or separately charged. For example, “vendor support” may cover routine coordination but not a system conversion. The distinction matters when an owner budgets time and cost or compares two proposals.
Use a simple exception log during the review. For each recurring service, write down what happens when an input is late, a staff member is absent, a system is unavailable, or an approval is declined. The contract may not need to contain every workflow detail, but the parties should know where the operating procedure lives and which document controls if it conflicts with the agreement. Counsel can help determine how schedules and procedures should be incorporated.
Finally, check that the stated scope can be monitored without turning every month into a dispute. A deliverable should have an owner, a due point, and a way to confirm receipt. If “support as needed” appears, ask what request channel counts, who is expected to respond, and whether there are limits on volume or timing. A clear boundary protects both sides from assuming that an undefined request is automatically included.
Owners need to understand the complete fee model before judging whether the arrangement is sustainable. Read base fees, percentage-based charges if any, pass-through expenses, setup charges, reimbursement rules, and minimums together. Ask for sample calculations using realistic operating scenarios, including a slower month and a month with unusual expenses.
Do not assume an illustrative example changes the contract. Have counsel and the appropriate financial advisor compare examples with the actual fee language. Clarify whether charges are invoiced in arrears or advance, what supporting detail accompanies invoices, how disputed amounts are handled, and whether either party can change the formula unilaterally.
Build a monthly review with revenue, operating costs, service charges, and outstanding disputes visible in the same view. This does not replace accounting or legal review; it helps the owner notice when actual performance departs from assumptions. A cash-flow review process can help establish a consistent cadence for that operational check.
Use a side-by-side scenario worksheet. For each case, list the expected activity level, fixed charges, variable charges, pass-through expenses, and the source document for each assumption. Include an ordinary month, a lower-volume month, and a month with a one-time expense or service change. Do not treat the exercise as a forecast; its purpose is to see which contract terms drive the bill and whether the practice can verify them.
Also clarify the invoice dispute workflow before the first invoice arrives. Note the deadline to raise an issue, the information the management organization must provide, whether undisputed amounts remain payable, and who resolves disagreements. If the contract is silent, owners may discover that different people have different expectations about supporting documents and timing. Counsel can advise on suitable language and the financial team can confirm that the process is workable.
Make the example arithmetic auditable. Label every input as a contract term, a practice estimate, or an assumption supplied by the other party. If a fee is based on a percentage, define the underlying base and test what is included or excluded. If expenses are reimbursed, try a case with a shared vendor invoice and ask how the practice’s portion will be allocated. The purpose is not to decide whether a particular fee is fair in isolation; it is to determine whether the formula is understandable, traceable, and consistent with the services promised.
Review the timing of cash obligations as well as the total. An upfront setup charge, a minimum fee during a slow period, or a short invoice-dispute window can affect working capital differently from a stable monthly charge. Build a simple calendar showing when invoices arrive, when supporting records are available, when payment is due, and when an objection must be raised. Then ask the financial reviewer to identify which periods create the greatest strain and ask counsel whether the payment and dispute language matches that reality.
Separate operational recommendations from decisions that belong to the practice. The agreement and related policies should make clear who sets clinical policy, who manages administrative execution, and who has authority to approve spending, hiring processes, vendor commitments, and workflow changes. The precise allocation depends on the parties and governing rules, so have qualified counsel assess it rather than relying on a generic template.
Create an approval matrix for recurring decisions. For each item, name the responsible role, required approver, spending or risk threshold that triggers escalation, and expected response time. Check for contradictions between the agreement, existing practice policies, and related services or ownership documents.
A useful matrix distinguishes propose, approve, execute, and verify. For example, the management team may gather vendor quotes and recommend an option, while an authorized practice representative approves the commitment and a designated employee confirms that the service was delivered. The point is not to prescribe a universal allocation; it is to expose decisions that currently have no clear owner. Ask counsel to check that the division reflects the particular arrangement and applicable rules.
Set a route for urgent exceptions as well as routine approvals. Identify who can be contacted when the usual approver is unavailable, what information an escalation must include, and how the decision is documented afterward. Without this path, staff may either delay essential administrative work or act beyond their authority. Have the parties agree on a response expectation that fits the work rather than leaving “promptly” undefined.
Healthcare management service agreements describe non-clinical administrative services in some arrangements, but the SEC agreement candidate is a specific exhibit and does not establish requirements for every practice. Review the actual structure with counsel. The American Med Spa Association’s overview describes the management-services role in a med spa context: What Is a Management Services Agreement?
Run the matrix against decisions that happen frequently and decisions that are uncommon but consequential. Routine purchases may need a fast threshold rule; a change to core software or an important vendor relationship may require a documented review. For each category, define who gathers information, who gives final approval, who signs or submits the commitment, and where the record is kept. Avoid combining these roles into one vague label such as “management handles it.”
Consider what happens when an approval is withheld. Does the task pause, return for additional information, or move to a different decision-maker? Set a path for revisiting the request and recording the reason for the decision. This reduces the chance that a rejected proposal is treated as approved simply because someone began implementation. Counsel should review any authority language, while operating leaders can make sure the process is usable by staff.
Define which records each party may use, who can access them, why access is needed, and how access is secured, reviewed, and removed. Ask counsel to address applicable privacy, security, and recordkeeping obligations for the specific practice and arrangement. Do not treat a broad data-access clause as a substitute for a workable access-control process.
Specify reporting that supports management without obscuring underlying numbers. Owners should know the source, definition, owner, and update frequency for each core metric. Agree on how corrections are made, how a practice requests supporting detail, and what happens when data is unavailable or inconsistent.
Useful operating questions include:
Owners who track performance through a weekly and monthly KPI dashboard should check that reporting definitions align with the management agreement. Conflicting definitions produce arguments instead of decisions.
Clarify the format and frequency of routine reporting. For every recurring report, specify its owner, delivery date, source system, and recipient, plus the process for correcting an error. Define access by role rather than by broad labels such as “staff.” When someone changes roles or leaves, state who requests access removal and how the change is confirmed. These are operational controls to discuss with counsel and the parties, not a substitute for privacy advice.
Plan for a record that is temporarily unavailable, incomplete, or disputed. Identify who provides a substitute report, when the final version is due, and how both sides mark estimates versus confirmed figures. This matters because decisions made from inconsistent definitions can create unnecessary conflict about performance. Agreeing on a data dictionary for core operating measures can make monthly reviews more useful.
Build a practical sample report before signing. Choose three measures the owner actually uses, such as schedule utilization, outstanding invoices, or monthly service costs. For each one, write down the definition, system of record, reporting period, person who validates it, and acceptable correction path. A number without a definition can change meaning from one report to another; a data dictionary makes comparisons more consistent and helps identify whether a discrepancy is a source issue, timing issue, or calculation issue.
Review data access as a lifecycle, not a one-time grant. Document how a user is requested, approved, changed, and removed; decide how often permissions are reviewed; and identify who receives evidence that access has been adjusted. For reports delivered outside the practice’s systems, ask how the file is transmitted and who is responsible for retaining the source data. Counsel can advise on required safeguards and obligations, while the practice and provider can define workable routine controls.
Read termination provisions with the same care as the service description. Identify the term, renewal mechanism, notice requirements, cure periods, termination triggers, and any fees or obligations that continue after termination. Ask counsel to explain the effect of each pathway and how it interacts with other agreements.
Then plan the handoff. A contract may allow termination but still leave the practice unable to operate if credentials, vendor accounts, schedules, records, or payroll processes are not transferred cleanly. Ask who provides transition assistance, for how long, at what cost, and in what format records and work product are returned. Clarify which services continue during transition and who is accountable for each handover milestone.
For a broader view of continuity and accountability, compare the planned handoff with a structured operations audit. Owners preparing for a future sale can also review exit-planning considerations, because unclear dependencies can complicate diligence and transition planning.
Work backward from the date a replacement process must be running. Allow time to identify account owners, export files, test credentials, document recurring tasks, and train the receiving team. Ask which party bears responsibility for each task and what proof confirms completion. If a vendor account cannot simply be transferred, identify the replacement account and any approval or setup lead time before notice is given.
Test continuity without waiting for a dispute. A tabletop exercise can follow a single essential workflow from start to finish as if the management provider were unavailable for several days. Record what the practice cannot access, which decisions stall, and what information is missing. Use that list to improve the transition schedule and clarify any assistance the agreement should provide. This exercise is operational planning, not a prediction that the relationship will end badly.
Think through each possible ending separately. Expiration, a negotiated separation, a breach followed by cure, and an immediate termination event may create different timelines and obligations. For each path, note the notice recipient, the date that starts the clock, the services that continue, the records to be delivered, and the person responsible for communication with staff and vendors. Ask counsel to explain which steps are required by the agreement and which are simply prudent operational preparation.
Transition planning also needs a realistic inventory. Include software subscriptions, domain and email administration, payment workflows, vendor contacts, staff schedules, templates, reports, and recurring deadlines. Label each item as practice-owned, provider-owned, or shared, then verify the label against contracts and access records. This prevents the team from discovering late in the process that an essential task depends on an account or file no one can retrieve. Keep a copy of the inventory with the operating documents and review it when systems change.
A focused review is easier when counsel receives business facts alongside the document. Prepare a one-page operating brief with the practice’s goals, current workflows, expected services, proposed fee mechanics, decision points, data needs, and transition concerns. Mark unclear or conflicting clauses, but do not rewrite legal language without advice.
Make the review packet easy to navigate. Number the questions and tie each one to a section or exhibit in the draft. Separate facts the practice has confirmed from assumptions that need verification. If there are related documents, include them so counsel can check for inconsistent terms rather than reviewing the management agreement in isolation. This preparation does not replace legal judgment; it helps the reviewer see how the language will work in daily operations.
After counsel’s first review, assign an owner to each open business question. Keep a decision log with the issue, the person responsible for answering it, the required evidence, and the date it is resolved. Do not let a verbal agreement substitute for a documented change where the contract requires written amendments. Ask counsel how revisions should be recorded and approved.
Before the review meeting, send a short agenda organized by decisions rather than page order. Start with items that could change whether the practice proceeds, such as unclear scope, a fee formula that cannot be reproduced, authority language that conflicts with existing policies, or a transition obligation that appears impractical. Then list items that can be clarified through exhibits or workflow schedules. This helps counsel spend time on consequential questions first and gives the business team a clear list of follow-up work.
Keep a version-controlled issue list as drafts change. Record the clause or exhibit, the question, the proposed business outcome, the person who must confirm the facts, and the status. When a revision arrives, compare it against the resolved issues instead of relying on memory. If a clause changed in a way the team does not understand, flag it for counsel rather than assuming the edit is merely stylistic. A disciplined log reduces repeated discussions and makes it easier to confirm that the final draft reflects agreed decisions.
If the arrangement is intended to support growth, relate each service to a measurable operational need, such as faster close, reliable reporting, or consistent administrative execution. Avoid treating projected revenue or growth claims as a substitute for reviewing scope, economics, and responsibilities. PGC describes its work as serving medical aesthetics businesses; owners can learn more about its practice management consulting or med spa consulting resources.
Book a call to discuss your operating priorities
No. Structure, services, ownership, and applicable legal requirements differ. Have qualified counsel review the specific parties, documents, and jurisdiction.
No. A checklist helps organize business questions, but it cannot determine whether legal terms are appropriate or compliant. Use it to prepare for counsel’s review.
Trace one recurring process from request to completion. Confirm who acts, who approves, what record proves completion, how an exception is escalated, and how the practice can continue if the service ends.
Review them together. Fees are difficult to assess without knowing the exact services, exclusions, pass-through costs, reporting, and remedies for missed work.
An MSO agreement should be understandable as a working relationship, not merely a signed document. Map the responsibilities and operating risks first, then take the questions and draft to qualified healthcare counsel before making a decision.
Written by
Founder & CEO, Projected Growth Consulting
Kelly Smith is a med spa business consultant with 20+ years of industry experience and the founder of Projected Growth Consulting. A former 7-figure med spa owner, published author of 5 books, and international speaker, Kelly has helped 6,000+ practices generate over $250 million in additional revenue through proven growth strategies.
