Most of us wrote our practice policies the same way. You found a template, changed the name at the top, deleted the parts that obviously did not apply, and put it in the intake packet. It has been there ever since.
Then something happens that the document does not actually answer.
A patient cancels four hours before a Tuesday appointment, for the third time. Deductibles reset in January and suddenly several patients owe balances nobody collected. Someone transfers in taking clonazepam from a prescriber who retired. A refill request lands late on a Friday for a medication you have not discussed with the patient in months.
In each of those moments, you are not reading your policy.
You are making a decision.
And the decision you make in that moment is your real policy, whatever the document in the intake packet says.
That is the part a template cannot give you. A template gives you language. It cannot tell you how your practice works because it does not know.
And this matters more in private practice because there usually is not a committee upstream of you deciding these things first.
Nobody decided when you collect copays.
Nobody decided what happens after a second late cancellation.
Nobody decided whether you continue benzodiazepines started by another prescriber.
Nobody decided how far in advance a patient has to request a refill.
You did. Sometimes deliberately. Sometimes because the question showed up at 4:45 on a Friday and you had to answer it.
Take something that sounds like it should have one correct answer: when do you collect a known copay?
Before the appointment? At check-in? At the end of the visit? Automatically afterward using an authorized card on file?
Those are different workflows, and each has tradeoffs.
Collecting before the appointment means less outstanding patient responsibility, but you need a reliable pre-visit process and may create credits or refunds when appointments change.
Collecting at the beginning makes collection dependable while the patient is there, but it also puts the money conversation at the front of the encounter.
Collecting afterward may keep the visit itself more clinical, but now you need a dependable post-visit collection process.
None of those choices exists in a vacuum. The question is which one fits the practice you are actually capable of running consistently.
Deductible and coinsurance amounts are harder because the final patient-responsibility amount often is not known until the claim adjudicates.
One practice estimates the expected responsibility, collects it up front, and reconciles the account afterward. Another submits the claim first and waits for the payer-determined patient responsibility before collecting.
I use the second approach. And I am not neutral about it.
I do not think a patient should be asked to hand over money against an amount that has not actually been determined yet. The amount is still an estimate until the claim adjudicates, and the patient may have no reliable way to know whether the number is ultimately correct. I would rather wait and collect what the plan actually assigns.
That is not a workflow preference I would trade for better cash flow. But it is still my practice decision, not a universal rule.
A practice that estimates up front can have legitimate reasons for doing so. It may dramatically reduce receivables. It may work very well with good eligibility verification and a reliable reconciliation process.
But that last piece matters.
If you collected $120 and the patient ultimately owed $68, who notices the $52 credit? How quickly is it returned? Does your processor return the original transaction fee when you issue the refund?
The operational consequences are part of the policy decision too.
This is probably the distinction I care about most. When people write practice policies, three very different things tend to get mashed together.
What you are required to do. Law, payer contracts, board rules, and program requirements put real boundaries around some decisions. A Schedule II prescription cannot be refilled under federal law. A missed-appointment fee is not something you simply submit to insurance as though a visit occurred, and some plans or programs restrict whether the patient may be charged at all. State law may establish minimum requirements for when you check the prescription monitoring program. Those are constraints.
What is clinically or operationally sound. A policy should not tell you to abruptly stop a benzodiazepine because someone violated an office rule. If you collect estimated patient responsibility, you need a real process for reconciling accounts and returning overpayments. If unpaid balances affect future scheduling, your process still has to account for continuity and urgent clinical needs. Those may not all be legal mandates, but they are part of doing the thing responsibly.
What you simply choose. Everything left over. And there is a lot left over.
That is where another practice's template can become misleading. You can read someone else's choice and experience it as a rule. Or do the opposite and treat an actual legal or contractual constraint as though it were merely a preference.
A no-show policy looks like one paragraph. Operationally, it may contain a dozen decisions.
How much notice do you require?
Is a late cancellation treated the same way as not showing at all?
Is there a fee?
Does the first occurrence get handled differently?
What counts as an exception?
Does the policy vary depending on payer or program?
Can the fee be charged automatically to an authorized card on file?
What happens after repeated missed visits?
The finished paragraph hides all of that reasoning.
The first question may simply be: does this practice prescribe benzodiazepines?
Some clinicians do not. Some prescribe only short term. Some maintain selected patients on them long term. Some will continue an existing prescription after evaluation but generally do not initiate one.
Once you answer that first question, a whole second layer appears.
What happens when another prescriber started it?
What monitoring do you require?
How are early refill requests handled?
What about a lost or stolen medication?
How do you approach tapering?
What happens when opioids or other sedating medications are involved?
A generic "benzodiazepine policy" cannot decide those things for you.
This started as a project to improve the practice templates inside Think Beyond Practice. And the more I worked on them, the more obvious the problem became.
A template is the end of the process, not the beginning.
So the practice-policy side of the platform is now built around one question: where do you go when you have a policy problem? There is one place, and it holds the three things that question actually needs.
It starts by helping you understand the issue. Each topic opens with the questions a practice actually has to answer, the approaches clinicians use, the tradeoffs, and the places where state law, payer contracts, or program rules may change what is available to you.
Then it helps you make the decisions. Instead of handing you somebody else's policy, the Policy Builder asks how your practice actually operates. You choose your approach to payment collection, cards on file, missed appointments, benzodiazepine prescribing, and medication refills. Where practices legitimately differ, the choices sit side by side without one being labeled "recommended." Where something is genuinely constrained, it tells you there is something you need to check. As you decide, your policy language builds around your choices, and you can download one policy or your whole set as an editable Word document.
Or, where a generic starter policy is available, you can edit the document yourself. Forum members can download the editable Word starter, work through the options and placeholders, and keep the language that fits their practice. Full members can do the same thing, or use the Policy Builder to make those decisions interactively and generate the finished policy for them.
The Template Library is still there for everything that is not a policy. Card authorizations, Good Faith Estimates, the Notice of Privacy Practices, releases of information, telepsychiatry consent, collaborative practice agreements, the welcome letter. Documents you fill in rather than decisions you make. The policy documents are no longer duplicated there; they live with their topic in Practice Policies.
Forum members get the guidance for every topic and the generic starter policies. Full members also get the Policy Builder and the full set of Foundations documents.
My goal is not to get every private practice operating like mine. Several of the choices I make fit the structure and values of my practice and would not necessarily transfer to one built differently.
The goal is to make the decisions visible.
What am I actually permitted to do?
What are the tradeoffs?
What do I believe is the right way to run my practice?
And what process am I genuinely prepared to follow consistently, even on a bad week?
Because a policy you will not follow is not really a policy. It is a paragraph.
On Thursday I am going to take one of these apart in detail: when can you actually charge the patient's card? Copays, deductible and coinsurance estimates, balances after adjudication, self-pay charges, and missed-visit fees tend to get treated as one payment question.
They are not.