Why 90 Days Decides the Next Five Years
Every practice management launch has two timelines running at once. The visible one is the project plan: setup calls, data migration, training sessions, go-live. The invisible one is the hardening of defaults. Every configuration choice made in the first 90 days, every workflow habit formed, every policy left unwritten, sets like concrete. Six months later, changing any of it means retraining people who have already built muscle memory around the wrong thing. Practices that launch well don’t work harder in month one. They decide better, in the right order, and they know which decisions belong to the software team and which belong only to them.
This guide is the operator’s companion to an AdvancedMD launch. The implementation team will handle the system. Your job is everything the system can’t decide for you, and this is that list, in sequence.
Before Day One: The Decisions Only You Can Make
Design the data model for the reports you’ll want later. This is the highest-payoff move of the entire launch, and almost nobody makes it on purpose. How you structure providers, profiles, financial groups, and appointment types today determines what you can measure cleanly in two years. Want revenue by service line someday? Then appointment types need to map to service lines now. Want per-location P&L? Financial groups need to reflect locations from the first charge. Name things for the questions you’ll ask, because renaming later means every historical report breaks at the seam. Sit down before setup begins and write the ten questions you’ll want answered monthly; then build the structure that can answer them. The ten questions on the owner’s numbers list are a working start.
Start payer enrollment paperwork immediately. Electronic claims, remittance, and funds transfer enrollments are the long pole of every launch, because they run on payer timelines, and payer timelines answer to nobody. A practice that starts enrollments the day the contract signs goes live with clean electronic rails. A practice that waits for the setup calls goes live on paper claims and manual posting, then wonders why month two feels like 2009. Build a one-page enrollment tracker, every payer, every enrollment type, status, and date, and review it weekly from day zero.
Decide your migration scope with your eyes open. The tempting answer is “bring everything.” The right answer is usually balances forward plus the active clinical record, with the old system kept accessible read-only for lookback. Migrating years of historical charges and messy old data means importing every categorization sin of the previous system into your clean one. Decide what the new system needs to run the practice, migrate that, and archive the rest where you can reach it.
Write the policies before the software opens. Card-on-file consent language and the auto-charge threshold. The late-cancel and no-show policy, in dollars and hours. The documentation standard: notes signed same day. The coding review threshold. These are one-page decisions, and every one of them is a behavior your new system will either enforce or ignore based on how it gets configured in week two. A policy written before setup becomes a system rule. A policy written after go-live becomes a memo, and memos lose to habit every time. The thinking behind this is covered in the variability guide.
Days 1 to 30: Build the Foundation Right
This month belongs to configuration, and your implementation team will carry most of it. Your job is to bring the decisions above to every call, so the system gets built around your policies instead of around defaults.
Templates for real workflows, tested by the people who’ll live in them. Have your highest-volume visit types built and clicked through by actual clinicians before training week, using real scenarios. A template that saves a clinician ninety seconds per note pays for the whole launch; a template built from a generic example creates workarounds by week six.
Train on policies, never on screens. The difference sounds small and decides everything. Screen training teaches where the buttons are; policy training teaches “every patient gets a card on file at first contact, and here’s the screen where that happens.” People forget buttons and rediscover them. People trained on the policy enforce it. Every training session should open with the rule and end with the click path, in that order.
Capture the card from patient one. If you’re using AdvancedMD Pay, the card-on-file motion starts with the very first patient registered in the new system, never as a phase-two project. Retrofitting cards onto an existing panel is a campaign; capturing them at registration is a default. The full collections build is in the patient collections guide, and every piece of it is easier to install on day one than on day 200.
Keep the enrollment tracker on the wall. Week four is when enrollment gaps become visible if nobody’s watching, and invisible if nobody is. Watch.
Days 31 to 60: Go Live Watching the Right Numbers
Go-live is where launches are judged, and most practices judge them on the wrong evidence: how the staff feels, how many support tickets got filed, whether the schedule looked normal. Those matter. The numbers below matter more, because they’re where a quiet configuration problem announces itself while it’s still cheap to fix.
Claims out daily, from the first day. Weekly batching is a habit practices import from their old life. Break it before it forms. Daily submission means daily feedback, and in month one, feedback speed is everything.
First-pass rate, counted honestly, watched daily then weekly. Early rejections are gifts: each one points at a settings problem, an enrollment gap, or a data mapping issue that would otherwise fail silently a thousand times. Work every rejection the day it bounces and trace it to root cause, because in week five a rejection is almost never about one claim.
The daily reconcile: visits to charges to claims. Every morning, yesterday’s appointment count against yesterday’s charge count against claims created. Gaps in this chain are how revenue disappears without a sound, and building the checking habit in month two means the practice never develops the leak at all.
Turn on electronic remittance posting and let it run. Manual posting during a launch steals the exact hours the team needs for exceptions. Automate the posting, then have a person verify the exceptions, in that order.
Start the weekly five. Unsigned work with names, claims out versus visits delivered, denials as an owned list, cash expected versus arrived, patient balances by age. Month two is when this ritual starts, because month two is when its absence starts costing.
Days 61 to 90: Tighten, Then Extend
Rebuild templates from real friction. By week eight, your clinicians know exactly which three clicks annoy them daily. Collect the list and fix it; template version two is where documentation speed actually arrives.
Push portal adoption while the newness helps you. Patients accept “we have a new system, set up your portal” in month two far more readily than “please start using the portal” in year two. Intake forms, statements, and messages all get cheaper with every activated account.
Write the automation shortlist. Ninety days in, the team knows which manual work hurts. List it, then run it through the 80% standard and the automation map. Month four is when the first automation should ship, and the shortlist written in month three is what makes that possible.
Know the deeper doors exist, even if you don’t open them yet. AdvancedMD ships enterprise-grade surfaces most systems in its class don’t: an ODBC offering for direct analytical access to your own data, and an open API the company builds alongside the product itself. You won’t need them in the first 90 days. Knowing they’re there changes your ceiling, because it means the system you just launched can grow into governed multi-site reporting, custom automation, and serious analytics without ever being replaced. When you’re ready for that conversation, the data services page covers what it looks like, and the AdvancedMD services hub maps the whole territory.
The Day-91 Scorecard
A launch that held looks like this: claims leaving daily, first-pass rate known and owned, the visits-to-charges-to-claims chain reconciled every morning, remittances posting themselves, cards on file for every patient registered since day one, notes signed same day behind every charge, the weekly five running with names attached, enrollment tracker fully green, and a written automation shortlist waiting for month four. If you can check those boxes, you installed more than software. You installed an operating standard, and the software is enforcing it.
The Five Ways Launches Go Sideways
Migrating everything, so the new system inherits the old system’s mess. Recreating old workflows screen by screen, so nothing actually improves. Training buttons instead of policies, so behavior stays personal. Starting enrollments late, so go-live runs on paper. And giving nobody the numbers, so problems surface as bad months instead of Tuesday flags. Every one of these is a decision, which means every one is preventable, which is the entire point of deciding on purpose.
Where to Start
If your launch is ahead of you, start with the pre-day-one list; it’s the cheapest week of work in your practice’s future. If you’re mid-launch and week six feels like chaos, that’s recoverable, and faster than you think. Either way, grab 30 minutes with us: prep nothing, and we’ll show you the report views a well-launched practice runs on, from real operations, so you know exactly what day 91 should look like.
PracticePath is not affiliated with, endorsed by, or sponsored by AdvancedMD. AdvancedMD is a trademark of AdvancedMD, Inc. All references to AdvancedMD are for informational purposes and to identify the software environment our services support.