- A new clinician's first month concentrates documentation risk: unfamiliar templates, an inherited caseload, unclear payer expectations and nobody reading their notes yet.
- Before the first session, set up role access, note types, supervision and co-signature routing, the documentation deadline, and a one-page sheet of what your payers expect.
- In week two, read every note the clinician has signed, not a sample, against the schedule, attendance and treatment plan.
- Fix patterns in conversation and corrections through your addendum policy, never by quietly rewriting signed notes.
- Taper review in weeks three and four based on what week two found, and write down what you checked.
Say a 30-bed residential program hires a therapist to replace one who left in March. The new clinician inherits a caseload of fourteen patients, three treatment plan reviews coming due, two groups a day, and a template library built by someone who no longer works there. Orientation covers fire exits, the HR portal and how to log in. Nobody covers what a defensible progress note looks like at this program, for these payers. Four weeks later the clinician has signed sixty notes, and every one of them carries whatever habit they brought from their last job. If a payer later pulls a sample from that month, the program will be defending documentation that no one inside it ever read.
Why the first month is where the risk concentrates
Experienced clinicians are not careless. The problem is that nearly everything about documentation is local: your note types, your program's definition of a billable group, which payers want start and stop times, who co-signs for whom, how your treatment plans are numbered and referenced. A clinician who wrote excellent notes at an outpatient practice can write notes that do not fit a PHP schedule at all.
Three things make the first month worse than any later month:
- Habits form fast. The structure a clinician uses in their first twenty notes is usually the structure they use for the next two hundred. Correcting it in week two is a conversation. Correcting it in month six is a retraining project and possibly a lookback.
- The caseload is inherited. The new clinician is picking up patients mid-episode, with treatment plans they did not write and, often, unsigned notes from the person who left. The temptation to copy the predecessor's last note forward is strong, and it is exactly the wrong move.
- Nobody is looking. Most programs' internal chart audits sample across the whole staff. A new hire's notes might not come up for months, and by then the month that matters is already in the claims history.
The cheapest documentation review a program will ever do is reading one new clinician's notes in their second week.
Before the first session: what to have in place
None of this is elaborate. It is a short list that someone has to own, ideally the clinical director or the supervisor the new clinician reports to. If it is nobody's job, it does not happen.
- Access that matches the role. The clinician should be able to see their own caseload and the groups they run, write the note types their role writes, and nothing more. If they need to be set up before their credentials are fully verified for every payer, decide in advance which sessions they can and cannot be scheduled for. That question belongs to credentialing; the point here is that it should be settled before the schedule fills.
- The note types they will actually use, walked through once. Sit with them for thirty minutes and open each template they will write: individual, group, family, crisis, treatment plan review, whatever applies. Show a completed example from your own program that you would be comfortable sending to a reviewer. Explain which fields are required and why, not just that they are.
- Supervision and co-signature routing. If the clinician's license level or payer rules require a supervisor to co-sign, configure that routing before the first note is written, not after the first claim is held. Confirm with the supervisor that they know the notes are coming and how quickly they are expected to review them.
- The documentation deadline, stated plainly. Tell them your program's window for completing and signing notes, and what happens when it is missed. If your policy says notes are due by end of next business day, say that, and say who gets notified.
- A one-page payer expectations sheet. Not the full contracts. A single page listing what your main payers commonly look for in a note for each level of care you run: time documented, individualized response, link to a treatment plan goal, signature and credentials. Mark it as a summary and tell them to ask when a payer is not on it. Confirm the contents against each payer's current requirements before you hand it out.
- Instructions for the inherited caseload. Tell them explicitly: do not complete, sign or edit notes for sessions you did not deliver. Unsigned notes left by the previous clinician go to the supervisor or compliance lead to handle under your policy. Read the last treatment plan and recent notes for context, then write your own first note from what you observe.
- A named person to ask. One supervisor, one backup, and a realistic expectation of how fast they answer. New clinicians who cannot get an answer guess, and guesses become habits.
Week one: let them document, then look at the first few
There is a case for reading a new clinician's very first notes the same day they are signed, especially for group notes and anything involving a safety concern. It does not need to be a formal review. The supervisor opens the first two or three, checks that the structure is right, and gives a two-minute correction if it is not. One early correction prevents twenty identical problems.
Beyond that, let week one run. You want the week-two review to see how the clinician documents when nobody is standing next to them.
Week two: read every note, not a sample
By the end of week two the clinician has signed enough notes to show patterns and few enough to read in an afternoon. Read all of them. Sampling makes sense for a staff of forty; for one new hire, the whole set is small and the point is to see habits, which a sample can miss.
Read each note against three other records: the schedule, the attendance record, and the patient's current treatment plan. A note read in isolation can look fine and still not match what happened.
Timeliness
When was each note signed relative to the session? A clinician who signs everything on Friday afternoon is writing from memory, and notes written days later tend to be vaguer and more alike. If notes are late, find out why before treating it as a discipline issue. Often the schedule leaves no documentation time, or the clinician did not know the deadline.
Does the note match the schedule and attendance?
Check the service type, date, start and stop times, and attendance status against what was scheduled and recorded. A patient marked as leaving group early should not have a note describing full participation. An individual session scheduled for fifty minutes should not have a note that reads as a check-in. These mismatches are easy for a reviewer to find and hard to explain afterward.
Is the patient in the note?
Read the response and progress sections for each patient across the two weeks. If the same sentences appear for different patients, or for the same patient on different days, that is the habit to address now. Shared session content in a group note can reasonably repeat; what each patient said, did and how they responded should not. Our longer piece on cloned notes and medical necessity covers where that line falls.
Is the treatment plan visible?
Can you tell from the note which goal or objective the session addressed? Inherited caseloads are where this breaks: the clinician is working from what they think the patient needs, not from the plan someone else wrote. If their clinical view differs from the plan, the answer is to update the plan through your review process, not to let the notes drift away from it.
Signatures, credentials and co-signatures
Confirm that every note is signed by the clinician with the right credentials shown, and that every note requiring a co-signature has one. A queue of uncosigned notes in week two usually means the supervisor did not know they were responsible, which is a setup problem, not a clinician problem.
Anything copied from the predecessor
Compare the new clinician's first note for each inherited patient with the previous clinician's last note. Close similarity is a sign they started from the old note rather than from the session. Also check that none of the predecessor's unsigned notes were completed by the new hire.
If the review finds a note that is inaccurate or incomplete, the fix is a dated, attributed addendum or late entry under your written policy, made by the clinician who delivered the service. Do not have anyone quietly rewrite a signed note, and never change dates. If a claim has already gone out on a note that turns out to be deficient, bring in your compliance lead to decide what follows. See late entries, addenda and amendments for how to handle each.
Running the review conversation
Book thirty to forty-five minutes with the clinician. Bring two or three examples of what they are doing well and two or three patterns to change, with the actual notes open. Keep it to patterns; a list of twenty individual nitpicks teaches nothing.
Frame each correction around why it matters to the patient record and to a reviewer, not around rules. "A reviewer reading this cannot tell which of these three patients said this" lands better than "notes must be individualized." Then agree what you will look at next and when.
Write down what you reviewed, what you found and what you agreed. A short dated record in the supervision file is useful later if a payer or accreditor asks how your program oversees new staff, and it gives the next supervisor something to work from.
Weeks three and four: taper on evidence
What happens next depends on week two. If the notes were sound, move to spot-checking a handful each week through the end of the month, then fold the clinician into your regular internal audit. If week two found real patterns, read every note again in week three to confirm the change took. Do not taper because the calendar says so.
At the end of the month, ask the clinician what was unclear. Their answers are the best input you will get for fixing the orientation for the next hire: the template field nobody explained, the payer sheet that was missing a plan, the co-signature that routed to the wrong person.
Making it repeatable
The whole process fits on a checklist: the seven setup items, the week-one glance, the week-two full read, the review conversation, the taper decision. Put the checklist in the hiring workflow so it starts when an offer is signed, not when someone remembers. Some of it is easier with software doing the watching: a documentation clock that shows each encounter against your deadline makes late notes visible during the first week rather than at the end of it, and note similarity flagging puts near-identical notes in front of the clinical director with the comparison attached. Neither replaces a supervisor actually reading the notes in week two.
Frequently asked questions
What should a new behavioral health clinician have set up before their first session?
Role-appropriate access, a walkthrough of the note types they will use with a good local example, supervision and co-signature routing, the program's documentation deadline stated plainly, a one-page summary of what your main payers look for, instructions for the inherited caseload, and a named person to ask.
How should a supervisor review a new clinician's notes?
In week two, read every note the clinician has signed rather than a sample, and read each one against the schedule, attendance record and current treatment plan. Look at timeliness, whether the note matches what happened, individualized patient content, the treatment plan connection, signatures and co-signatures, and anything copied from the previous clinician.
Can a new clinician finish a departed clinician's unsigned notes?
No. A clinician should not complete, sign or edit notes for sessions they did not deliver. Unsigned notes left by a departed clinician should go to the supervisor or compliance lead to handle under the program's written policy.
How do you correct errors found in a new clinician's signed notes?
Through a dated, attributed addendum or late entry made under your written policy by the clinician who delivered the service. Signed notes should not be quietly rewritten and dates should never be changed. If a claim already went out on a deficient note, involve your compliance lead.
When can you stop reviewing every note from a new clinician?
Taper based on what the week-two review found, not on the calendar. If the notes were sound, move to weekly spot-checks through the end of the month; if there were real patterns, read every note again in week three to confirm the change took.