The Practice Automation Toolkit

Attached is 90 days of denial data from a [size]-clinician behavioral health practice: denial code, payer, CPT, billed amount, and date. No client identifiers.

Rank the root causes by total dollars denied rather than by claim count, and show both columns so I can see where the two disagree.

For each of the top causes, tell me:
- whether it is a front-end problem (eligibility, authorization, registration), a coding problem, or a documentation problem
- whether fixing it is a process change or a per-claim appeal
- which specific step in our workflow would have to change

Then name the three that are fixable with a process change, and for each one estimate the annual dollars we would recover if we fixed it and got it 80% right.

Finally, flag anything that looks like a data quality problem rather than a real denial pattern.

Write a first-level appeal for a claim denied with [reason code] by [payer].

I am giving you three things: the denial reason as written on the remittance, the payer's own medical policy language for this service, and a de-identified summary of what was documented in the session note.

Build the argument from the payer's own policy language. Quote the specific clause that supports payment and show how the documentation satisfies it. Do not argue fairness, abstract clinical necessity, or how long we have been in network.

Two paragraphs, plus one line stating exactly what we are asking them to do. Professional and direct, no filler, no apology.

Separately from the letter, tell me what additional evidence would make this appeal stronger if I can get it, and what would make it weaker if the payer asks for it.

Attached is the payer policy for [service line].

Turn it into a one-page checklist a biller can work down before submitting. Use the payer's own terms wherever the exact wording matters.

Structure it as four sections:
- Covered: what is payable, with any diagnosis, setting, or provider-type restrictions
- Prior authorization: what needs it, how far ahead, what expires and when
- Limits: units, visits, frequency, and the period over which they reset
- Documentation: what must be in the note for this to survive an audit

End with the three requirements in this policy most likely to cause a denial, ranked, each with the sentence from the policy it comes from.

Where the policy is silent or genuinely ambiguous on something a biller would need, say so explicitly instead of filling the gap with a general rule.

Attached is the billing manual for [payer]. We are a behavioral health practice billing mainly [CPT codes].

Build a pre-submission scrubbing checklist specific to this payer. Focus on the rules that actually cause rejections: modifier requirements and combinations, time-based unit rounding, place of service, telehealth requirements, same-day and concurrent service restrictions, and provider type or supervision requirements.

Output a table: Check, What correct looks like, What happens if wrong, Where in the manual.

Order the rows so the checks that catch the most claims come first.

Then list separately any rule in this manual that departs from standard Medicare or CPT convention. Those are the ones staff get wrong from habit rather than from ignorance.

Here are the CARC and RARC codes from a remittance advice for a behavioral health practice, with the dollar amount attached to each.

For each code tell me:
- what it actually means in plain English, not the official code text
- the most likely underlying cause in a behavioral health context
- the correct next action: fix and resubmit, appeal, bill the patient, or write it off
- which role on my team should own it

Group the codes by next action so I can hand each group to one person, and total the dollars in each group.

Then flag any code here that suggests a systemic problem rather than a one-off, and tell me what pattern in the next month's remittances would confirm it.

Attached is a payer contract for a [size]-clinician behavioral health practice. Summarize it for an owner who is not a lawyer.

Cover:
- term, how it takes effect, and exactly how renewal happens
- how rates are set, where the fee schedule actually lives, and how it can change without a new signature
- notice required to terminate, by each side, and any window we would have to hit
- what we agreed to on timely filing, appeal deadlines, audits, and recoupment
- any clause letting the payer change something unilaterally

Then give me two lists: clauses that are standard and not worth fighting, and clauses that are unusually one-sided. For each item in the second list, say what a reasonable alternative would have been.

Quote the contract language for anything you flag. If a term I would expect to see is missing entirely, say that too.

I am giving you two things: fee schedules from [payer A] and [payer B] for the CPT codes we bill, and my loaded cost per session by service type, including clinician compensation, benefits, supervision, administrative overhead, and space.

For each code and payer combination, calculate contribution margin per session in dollars and as a percentage, and identify which combinations are below zero.

For every underwater combination, give me the rate that reaches break-even and the rate that reaches a [target]% margin.

Rank everything by total annual dollars lost at current volume, not by margin percentage, since a thin loss on high volume matters more than a deep loss on a rare code.

Finally, state the assumptions you had to make about my cost allocation, and tell me which single assumption would most change the answer if I got it wrong.

Here is my CPT mix and monthly volume for the last 12 months, and the rate changes [payer] is proposing.

Calculate the actual annual revenue impact. Show your work by code: current rate, proposed rate, percentage change, annual volume, dollar impact.

Then give me the blended percentage change weighted by my real volume, compare it to the headline number the payer is quoting, and explain in one paragraph why the two differ.

Model two scenarios alongside the base case: volume shifts 10% toward the codes whose rates fell, and volume shifts 10% the other way.

Finally, identify the single code where a small rate movement changes the total most. That is the one worth negotiating.

I want a rate increase from [payer] for a [size]-clinician behavioral health practice in [market].

Build my case in the terms a payer network manager actually responds to: network adequacy and member access, appointment availability and wait times, geographic coverage, the specialties and populations we serve that are hard to find, any quality or outcome data we can show, and effects on total cost of care.

Give me a one-page case with the three strongest arguments, each paired with the specific data point I would need to supply.

Then switch sides and argue the payer's counter-position as forcefully as you can: budget constraints, adequacy already met in our area, comparable contracted rates, our own utilization patterns. Give me the response to each.

End with the concessions that would cost me least, and the walk-away question I should be able to answer before the call starts.

Build a credentialing submission checklist for a [license type] clinician with [payer] in [state], for a group practice billing under a group National Provider Identifier (NPI).

List every document and form in the order I should collect them. For each: who provides it, typical turnaround to obtain it, whether it expires, and whether a missing or stale version blocks submission or merely slows it.

Separate the items into three groups: needed before we can start, needed to submit, and needed only if the payer asks.

Call out the requirements specific to this payer or this state that differ from a generic credentialing packet, since those are the ones that get missed.

Then list the three most common reasons a packet like this comes back as incomplete, and what to do up front to prevent each.

Attached is a transcript of my most experienced biller describing how she runs benefits verification.

Turn it into a standard operating procedure a competent new hire could follow on day one without asking her anything.

Number the steps. For each step: what to do, where to do it (system, portal, screen), what to enter or click, what a correct result looks like, and what to do when the result is not what you expected.

Then give me three lists:
- knowledge she assumed and never explained, each written as the question a new hire would ask
- decisions she makes by judgment that this procedure cannot yet specify
- steps where she described what she does but not why, so nobody could adapt when the situation changes

Do not smooth over vagueness. If she said something like "you just know by then," flag it rather than inventing a rule that sounds plausible.

Read the attached procedure as if you are a competent new administrative hire on your first day. You have no institutional knowledge and nobody available to ask.

Walk it top to bottom and stop at every point where you would get stuck, guess, or plausibly do the wrong thing. For each one tell me: the exact step, what is ambiguous about it, what a reasonable person might wrongly do instead, what that mistake would cost, and how long before anyone noticed.

Then list separately the terms, systems, and abbreviations used without definition, and the decisions the procedure asks you to make without giving criteria.

Be blunt and specific. Do not tell me it is well organized or mostly clear. Assume it has problems and find them.

For a behavioral health practice, list every way an insurance benefits verification can fail or return something we cannot act on.

Include at least: portal down or timing out, member not found, coverage terminated, coverage future-dated, two active plans, out-of-state or different network plan, provider not in network for that specific plan, benefits differing from what the client told us, an authorization requirement we did not know about, and returned data that contradicts itself.

For each exception give me: how staff would recognize it, exactly what to do next, who decides when the next step is not obvious, how long to wait before escalating, and whether the appointment can proceed in the meantime.

Then split the list in two: exceptions frequent and structured enough that software could handle them, and exceptions that genuinely need a person. Say what makes each one fall on its side of the line.

Compress the attached procedure into a one-page quick-reference card for someone who has already been trained on it.

Keep only the decision points, the three mistakes most likely to be made, and where to go when stuck. Cut everything explanatory.

It has to be readable at arm's length on a wall: short lines, no paragraphs, no sentence longer than about ten words. Give me a title, at most five sections, and at most four lines per section, as plain structured text I can format.

Then tell me what you cut that a newer person would still need, so I know who this card is safe to hand to and who still needs the full document.

Write a decision tree for front-desk staff at a behavioral health practice when a client's coverage looks inactive or wrong at check-in, with the client standing there.

Start from the moment the check fails. Branch on things staff can actually observe: is the card different from what we have on file, does the client know about a coverage change, is this a first or established visit, is the clinician already waiting, is this a crisis presentation.

Every branch must end in a specific action, a named role who owns it, and what we say to the client, written out. No branch may end in "check with billing" without specifying what happens when billing is unavailable.

Also specify when the appointment proceeds anyway, whether and how much we collect, and what gets documented so billing can pick it up afterwards.

Keep the whole tree short enough to fit on one screen.

Write a 30, 60, and 90 day follow-up email sequence for a credentialing application with [payer] that has gone quiet after submission.

Each email: short enough to read on a phone, application and tracking number in the first line, exactly one specific ask with a date attached.

Escalate in both tone and audience. The 30-day note is a straightforward nudge to the same contact. The 60-day note establishes a documented timeline and copies a second contact. The 90-day note goes to a named supervisor or network manager and states the business consequence plainly, in our case clinicians who cannot see their members.

Do not apologize for following up in any of them, and do not use the phrase "just checking in."

After the three emails, give me the phone script for the call I should make between the 60 and 90 day notes, including exactly what to write down afterwards.

Build a readiness checklist for a newly hired clinician at a behavioral health group practice: everything that must be true before their first billable session.

Cover credentialing, payer enrollment, group roster linkage, license and any required state registrations, malpractice coverage, supervision requirements if they are pre-licensed, EHR access and permissions, schedule and service setup, and telehealth platform access.

For each item mark: whether it blocks billing, blocks seeing clients, or neither; who owns it internally; and typical lead time so I can work backwards from a start date.

Then give me the ordered timeline: what must start 90, 60, 30, and 7 days before the first session.

Finally, call out the items most commonly assumed done but not actually done, especially anything payer-side that lags the hire date no matter how organized we are.

Attached are expiration dates for my provider roster: license, DEA where applicable, malpractice, CAQH (Council for Affordable Quality Healthcare) attestation, board certification, and payer recredentialing dates. Names replaced with initials.

Build a month-by-month reminder calendar for the next 12 months. Each entry shows what expires, whose it is, the actual expiration date, and the date we should start work on it using a 60 day lead time.

Flag separately:
- anything expiring in the next 90 days
- anything already expired
- any person with three or more items expiring in the same month, since that is a workload spike
- items where 60 days of lead time is not enough, and what it should be instead

Then tell me which of these, if it lapsed unnoticed, would make a clinician unbillable rather than merely out of compliance. Those are the ones that need a second reminder.

Rewrite the attached credentialing follow-up email so it actually gets a reply.

Rules: reference number and provider name in the first line. One specific ask, with a date. Under 120 words. No apology, no "I hope this finds you well," no explanation of why we are following up again. Make it trivially easy to answer by reducing the ask to a yes or no, or to confirming one missing item.

Give me the rewrite, then a short note on what you changed and why each change increases the odds of a response.

Then give me a second version for escalating to a supervisor: same brevity, business consequence in one sentence, and no trace of sounding aggrieved.

For a behavioral health group practice, list every way a credentialed provider can quietly become unbillable with a payer without anyone telling us.

Include at least: recredentialing lapse, stale CAQH attestation, license or registration expiry, malpractice lapse, being dropped from the group roster during a payer system migration, taxonomy or specialty mismatch, an unfiled location or tax ID change, effective dates that silently ended, and network changes on the payer's side.

For each one tell me: how it shows up first, usually as a specific denial pattern; how to detect it deliberately before that happens; what to check and where; and how often to check.

Then design the monthly roster audit: what to pull, what to compare it against, and the three checks that catch the most problems for the least effort.

Write a billing specialist job description for a [size]-clinician behavioral health practice. I want to attract someone who improves processes, not only someone who executes them.

Make that difference visible in the content, not in adjectives. Responsibilities should describe owning outcomes and changing how work gets done. Requirements should ask for evidence of having built or fixed something, and should avoid screening on years of experience with a particular tool where that is not what actually matters.

Include a short section describing a real, specific problem in this role and invite candidates to say how they would approach it. That section is the actual filter.

Avoid: detail-oriented, team player, fast-paced environment, wear many hats, and any sentence that would be equally true of a billing job at any organization anywhere.

Then tell me which lines in your own draft might deter the process-designer type, so I can decide whether to keep them.

Give me ten interview questions for an administrative role in a behavioral health practice where someone who follows processes and someone who designs them would give visibly different answers.

Avoid hypotheticals a confident person can talk their way through. Prefer questions about specific things the candidate has actually done.

For each question give me:
- the question as I should ask it, word for word
- what a strong answer sounds like, concretely
- what a weak but plausible-sounding answer sounds like, since those are the ones that fool interviewers
- the follow-up to ask when the first answer is generic

Then flag the two questions most likely to be answered well by a confident candidate who is not actually good, and tell me how to tell the difference in the moment.

Build a 30, 60, and 90 day plan for a new billing hire at a behavioral health group practice.

Every checkpoint must be observable and measurable by someone other than the hire. No "getting up to speed," no "building relationships," no "understanding our processes."

For each stage give me: what they should be able to do unsupervised, one specific measurable target, what I should see evidence of, and the specific failure signal that means we intervene now rather than at the next review.

Make the 30 day targets things a competent person can genuinely hit in a practice this size, and the 90 day targets things that require real ownership rather than more of the same.

Then tell me what I have to do at each stage for the plan to be fair, since most of these fail because of the manager rather than the hire.

Rewrite the attached administrative performance review template around outcomes rather than activity.

Then propose the five metrics that actually matter for a behavioral health billing role. For each: the definition, where the number comes from, how often to measure it, a realistic target range for a practice of [size] clinicians, and how it could be gamed.

Discard anything that measures effort, hours, or volume of work processed unless it maps to a result. Be explicit about what you dropped from the original template and why.

Then flag which of your five are substantially outside a biller's direct control. Holding someone to those is how good people are lost, so tell me how to weight or caveat each one.

Role play with me. You are a billing specialist with twelve years at my practice. You are genuinely good at your job, you know the payers better than I do, and you have concluded that the automation I am introducing is the first step toward replacing you. You are not hostile. You are guarded, and your objections are specific and concrete.

I am going to try to have the real conversation with you. Push back realistically. Do not be won over easily and do not soften because I said something reassuring. Raise the concerns a person in that position actually raises, including the ones I would find awkward to answer.

Stay in character for five exchanges. Then stop and give me a straight assessment: where I was unconvincing, where I said something that would have made it worse, what I never addressed at all, and the one sentence that would have landed best.

Attached is 12 months of profit and loss for my behavioral health practice, aggregate figures only. Margin dropped in [quarter] and I do not know why.

Decompose the change. Give me the three most likely drivers ranked by how much of the total change each one explains, with the arithmetic shown, and state what share of the drop you cannot account for from this data.

Distinguish carefully between: revenue per session falling, session volume falling, payer mix shifting, collection rate falling, and cost lines rising. Those have completely different fixes and they look identical on a margin line.

For each driver, name the one report or number I should pull next to confirm or kill it.

Be explicit about what this data cannot tell me. Do not present a guess as a finding, and say so plainly when the honest answer is that the P&L alone is not enough.

I want to add 5 clinicians over the next 12 months at a behavioral health practice currently at [size] clinicians and [number] administrative staff.

Model the fully loaded cost, including the administrative headcount this growth implies at my current admin-to-clinician ratio. Include compensation, benefits, supervision time, the credentialing and enrollment lead time before they can bill anything, space or technology, and the ramp period before they reach full caseload.

Show monthly cash flow across the 12 months, since the cost lands well before the revenue does. Tell me the deepest point and which month it falls in.

Then model the same growth with the admin-to-clinician ratio improved by 30%, and express the difference both in annual dollars and in the number of admin hires avoided.

State your assumptions on ramp time and target caseload, and flag which assumption the answer is most sensitive to.

I am considering expanding my behavioral health practice into [state or market].

Build the strongest possible case for it, then the strongest possible case against. Argue each side as though it is the position you hold. Do not hedge, do not write a balanced summary, and do not conclude.

The case for should address demand, the payer landscape and rates, competitive gaps, and what we could genuinely reuse from the current operation. The case against should address licensure and credentialing lead time, contracting with payers from scratch, hiring in a market we do not know, management attention, and what breaks in the existing practice while I am distracted.

Then, separately, list the three questions whose answers would actually decide this, and what I would have to go and learn to answer each one.

Turn the attached meeting notes into a decision log, as three tables.

Table one, decisions actually made: the decision written so someone who was not there would understand it six months from now, the owner by name, the date, the deadline if one was set, and status.

Table two, discussed but not decided: the topic, why it stalled (no owner, missing information, nobody with authority in the room, or genuine disagreement), and what would unblock it.

Table three, asserted but unverified: anything stated as fact that nobody checked, since those quietly become assumptions.

Do not invent owners or dates. Where a decision was made without anyone being assigned, say so explicitly. That is the most common way a decision fails to happen.

Rewrite the attached [financial policy, consent form, or no-show policy] at roughly an 8th grade reading level, without changing anything it commits us to or obliges the client to do.

Keep every substantive term: amounts, timeframes, what happens on non-payment, what the client is agreeing to. Shorten sentences, drop legal doublets, replace jargon with plain words, and add headings and short paragraphs.

Then give me two lists:
- anything you had to leave vague because the original was genuinely ambiguous, quoting the original phrase
- anything a client would most likely misunderstand or be surprised by, even after the rewrite

Do not soften obligations to make them more palatable. If a term is harsh, it should read as clearly harsh.