The first 30 days of a new medical practice: an operations playbook

The first patient has left. The visit may still have work attached to it: a note awaiting review, a requested record, a claim exception or a follow-up that has not been arranged. In a new practice, the team is learning where each of those things belongs.

This playbook covers the first 30 days after opening an independent medical practice. It helps the team see what is waiting, assign responsibility and improve one recurring problem at a time. It assumes the practice has completed the requirements for the services it is providing. For the work before opening, start with the physician launch guide.

Download the first-month operations workbook (Excel). It contains an action plan and a weekly review sheet with blank fields for your observations. Use it for aggregate operational information. Keep patient names, clinical details and individual follow-up tasks in the practice's approved systems.

Prepared by the Moxcares team · September 30, 2026.

Use fictional test information to work through the experience from a patient's first contact to the final handoff. Include the people who will actually perform each step. A manager clicking through the software alone cannot show whether the whole team understands the process.

Do not submit fictional clinical claims as real claims or make real patient charges during a rehearsal. Coordinate any test transactions with the relevant vendor or billing partner. Clinical leaders should define the safety and escalation requirements for the services offered.

Record each issue, its owner and whether it must be resolved before the session. Recheck the issue after the change. An agreed workaround needs to be understood by the people who will use it.

List the places work arrives: phone messages, online requests, intake, incoming documents, clinical messages and billing exceptions. For each, name a primary owner, a backup and the route for questions that need clinical or management judgement.

Agree how often the owner reviews each queue and what changes the urgency. The clinical team should set clinical response and escalation rules. Avoid using one arbitrary deadline for every type of message. Make after-hours instructions and absence coverage explicit.

Start each session with a short review of today's staffing, appointments, missing preparation and unusual requirements. End with a check of work that remains open and its next owner. AHRQ's TeamSTEPPS tools distinguish planning briefs, huddles to adjust the plan and debriefs to learn from what happened. Adapt the approach to your team.

For example, if the coordinator leaves before a clinician finishes the last session, agree who checks the final messages and booking tasks. A handoff should be acknowledged by the receiving person. Putting a task in a shared inbox does not establish that someone has taken it.

Choose an issue the team has encountered more than once. It might be an unclear entrance instruction, an unsuitable appointment type, an intake question patients cannot answer or a document that arrives without enough information to match it confidently.

Observe the path from the patient's request to the staff response. Ask the person doing the work what they need. Agree one change, give it an owner and set a date to check the result. Keep the old and new process clear during the transition so staff do not follow different versions.

A practical example: patients are arriving without a report that the clinician needs for that visit type. Check when the requirement is explained, who requests the report and where staff record that it has arrived. The fix may involve booking instructions and task ownership rather than adding another reminder to everyone.

Have clinicians approve changes that affect care or clinical instructions. Use the first-patient acquisition article to review how public messages and booking expectations line up with the experience you are delivering.

Review how the team knows a visit's next step has been completed. A request sent to another organisation may still need a response. A message routed for review may still be waiting. Define the completion event for each workflow and keep exceptions visible in the appropriate system.

Work with the responsible clinicians to check the handling of results, referrals and patient messages, including coverage when the usual clinician is absent. Use your approved clinical policies to identify and escalate overdue or urgent work. An aggregate management review complements that process; it does not replace individual patient follow-up.

For an insurance-based workflow, trace a small set of actual visits with the billing lead from completed documentation to claim submission, acknowledgement and the next status. Claim acceptance is different from payment. Record which exceptions need the clinician, front desk, billing team or payer.

For a direct-pay workflow, check how staff explain the agreed charges, process a payment and handle an unresolved balance or refund request. Reconcile the relevant records through your normal accounting process. Our revenue cycle guide provides more detail on assigning billing follow-up.

Compare the planned day with the day the team is experiencing. Look at appointment length, preparation work, breaks, messages and unfinished tasks. Ask where someone regularly stays late or where another role waits for a decision.

A schedule with open slots may still leave the team overloaded if every visit creates an unclear handoff. Conversely, an early delay may come from a setup problem you have now corrected. Use several observations and staff input before treating either pattern as permanent.

Decide whether to adjust visit types, session capacity, task allocation, training or support. Keep any changes within the practice's clinical and staffing requirements. If hiring is the next step, revisit the first-hire guide and describe the work that person will own.

Write a short decision record at the end of the month: what worked, what remains unresolved, who owns each next action and what the team will review in month two. Keep the list short enough that it gets used.

The workbook provides blank weekly columns. Choose a consistent cutoff and use the definitions below. These are suggested operating measures, not benchmarks or targets. A blank means the team has not recorded the value; zero means it checked and found none.

Weekly enquiries and completed visits may involve different people, so do not use those two counts as a conversion rate. Open-task counts are snapshots and should not be added together across weeks. Read them alongside the reasons for delay and the actions taken.

Put the current procedure where staff can find it. Record the owner and the date it changed. When someone learns a better way to complete a task, test the change with the other people involved and update the shared instruction.

For AI-assisted work, agree what the system may draft or collect, what a person reviews and how uncertainty reaches the right team member. Try the exception path as carefully as the successful path. Have the responsible leaders approve any change to clinical or patient-facing workflows.

Does this mean we can open in 30 days? This guide begins after opening. Licensing, premises, payer arrangements and other launch dependencies need their own plan.

Does a small team need a daily meeting? Choose a short, workable method to confirm coverage and unfinished work. Two people may only need a brief conversation, provided the next actions are recorded in the right place.

What if an urgent clinical issue appears in the weekly review? Use the practice's clinical escalation process immediately. The weekly review is for improving operations and must not delay individual care.