Case Conference Note: Definition, Template & Example

A case conference note documents a pre-arranged meeting held by two or more providers to discuss and direct one identified client's care. It records the participants, times, decisions, and allocated tasks, plus whatever elements the payer requires when the conference is billed. Conferences are billable in Australia and Ontario and in limited US contexts. Most notes run 150 to 400 words.

Free to use and share. No signup required.
Already have session bullets or a transcript? Generate a structured draft with BastionGPT — you review and sign it.
Who writes it

The organizing clinician; every provider billing a conference item keeps their own record

Audience

Conference participants, the referring team, the client's chart, payers, auditors

Typical length

150 to 400 words · 10 to 15 minutes by hand (clinical team estimate)

Format family

Meeting note (compare: multidisciplinary team meeting note, care coordination note)

When it's used

After a scheduled multi-provider conference about a single client, especially when billed

Standards context

Billed conferences carry enforceable content rules (MBS, OHIP); unbilled ones are convention

What is a case conference note?

A case conference note is the record of a formal, pre-arranged meeting held to discuss and direct the care of a single identified client by two or more providers, sometimes with the client, family, or other supports present. Unlike an ordinary progress note, its subject is a multi-party meeting rather than a one-to-one encounter. The most codified version is Australian: the Health Insurance (General Medical Services Table) Regulations 2021 define the multidisciplinary case conference and make an enumerated content list a condition of billing MBS items 735 to 758, a lineage that runs back to the Enhanced Primary Care package of the late 1990s. North America codified it differently: as the care planning conference in US long-term care and hospice regulation (42 CFR 483.21 and 418.56), as a mandated conference with listed note contents in Ontario long-term care (O. Reg. 246/22, s. 27), and as OHIP case conference K-codes for physicians. You will also hear it called a case conference record or summary, care conference note, family meeting note, or case review note.

Two boundaries matter. First, the multidisciplinary team meeting note covers the recurring internal meeting that may discuss several clients; the case conference note is single-client and, when billed, must satisfy the item's exact content rules. Second, the US special-education "case conference committee" under IDEA is a separate statutory instrument and not a clinical case conference. No universal template exists in any of the three countries: the enforceable content lists are jurisdiction- and payer-specific, and in Australia they bind only the practitioner who bills the item, a point the explanatory notes make expressly.

Who uses case conference notes and when

Therapists, psychologists, GPs and psychiatrists, allied health providers, and care coordinators use case conferences when one client's care crosses enough providers that decisions need to be made together: complex chronic conditions with behavioral health involvement, adolescents with school and family systems in play, discharge planning across agencies, and palliative coordination. In Australia the conference itself is a fundable service with organiser and participant items, including mental health case conferencing items introduced 1 July 2023; in Ontario, physicians bill OHIP K-codes; in the US, most clinicians document the conference inside care management work rather than billing it separately. Write a care coordination note for asynchronous coordination that is not a scheduled meeting, and a treatment plan review when the work product is a plan revision rather than a conference record.

Case conference note structure: what goes in each section

Purpose and pre-arrangement. State what the conference was convened to decide and that it was scheduled in advance. OHIP defines a case conference as a pre-scheduled meeting to discuss and direct the management of an individual patient, and expressly excludes educational rounds and journal clubs. Pitfall: writing up an ad hoc hallway discussion as a conference; the pre-arrangement is part of the definition.

Participants and minimum team. Every participant with name, credentials, discipline, and role, and whether the minimum team rule is met. Australian GP items require at least three members, no more than two of whom may be medical practitioners, each providing a different kind of care; OHIP requires the most responsible physician plus at least two others. Pitfall: a conference of three physicians, which fails the Australian mix requirement outright.

Consent and attendance. Record the client's agreement to the conference before it happens, and who attended. In Australia the client's agreement must be recorded and, for the mental health items, agreement to each participant; the client does not have to attend. In Ontario long-term care the resident and substitute decision-maker must be given the opportunity to participate. Pitfall: consent that exists in conversation but nowhere in the record.

Times and mode. The day, start and end times, and each participant's mode (in person, video, phone). Under the Australian regulations, recording the day and the start and end times is a legal precondition of billing an organiser item; OHIP pays in time units with a 10 minute minimum. Pitfall: a note with no times; for billed conferences that is not a style problem, it is an unpayable item.

Discussion: needs and outcomes. The clause the Australian definition enumerates travels well everywhere: the client's history, their multidisciplinary care needs, the outcomes to be achieved, and a review of previously identified outcomes. Pitfall: "discussed client's care" with no content; an auditor treats an empty discussion section as an undocumented service.

Decisions and tasks allocated. What was decided and which named team member owns each task, with timeframes. Pitfall: outcomes with no owner; task allocation to named members is part of the Australian definition and the practical point of the meeting everywhere.

Distribution. A copy in the client's record, a summary offered to the client and carer, and a summary to each team member, all of which the Australian organiser rules require. Pitfall: a conference no one else can see; the distribution trail is the difference between coordination and a private memo.

Signature. The author signs with credentials. No regulation reviewed in the US, Canada, or Australia requires every participant to sign; OHIP accepts one shared chart note signed or initialled by the physician participants, and the Australian rules ask the organiser to record participants and distribute summaries instead. Pitfall: circulating the note for every attendee's signature; the trail reviewers check is participants recorded and summaries distributed, not a page of countersignatures.

Blank template (copy and adapt)

CASE CONFERENCE NOTE

Client: ______________  DOB: __________  Date: __________
Purpose of conference (pre-arranged): __________________________________
Client agreement recorded (date, scope): _______________________________
Client/carer attending: [ ] yes  [ ] no
  (most schemes require recorded consent, not attendance)

PARTICIPANTS (name, credentials, discipline/role, mode: in person/video/phone)
1. _____________________________  2. _____________________________
3. _____________________________  4. _____________________________
Minimum team check (payer-specific, e.g. 3+ members, mix of care types): [ ]

Start time: ________  End time: ________  Total: ________

DISCUSSION
History and current needs: _____________________________________________
Outcomes to be achieved: _______________________________________________
Previously identified outcomes reviewed: _______________________________

DECISIONS AND TASKS ALLOCATED (task, named member, timeframe)
1. ____________________________________________________________________
2. ____________________________________________________________________
3. ____________________________________________________________________

DISTRIBUTION
Copy in client record: [ ]   Summary offered to client/carer: [ ]
Summary provided to team members: [ ]
Next conference or review date: __________
Author signature/credentials/date: _____________________________________

Free to use and share, no signup. The PDF includes a one-page cheat sheet with section-by-section pitfalls and a pre-sign checklist; the DOCX is the blank template, ready to adapt.

Sample case conference note

Scenario: an outpatient behavioral health practice convenes a scheduled conference on a 47-year-old client with major depressive disorder and chronic low back pain whose recovery has stalled across providers. All details are fictional.

Case Conference Note. Client: L.K., 47  ·  Date: 07/22/2026  ·  Purpose: coordinate care for depression complicated by chronic pain and work absence  ·  Pre-arranged: yes, scheduled 07/10  ·  Client agreement recorded 07/10, including agreement to all participants; client elected not to attend

Participants and mode: A. Whitfield, LCSW (primary therapist, organizer, in person); Dr. P. Nunez, MD (family medicine, video); R. Osei, DPT (physical therapy, video); J. Lam, RN (practice care coordinator, in person). Minimum team check: 4 participants, 3 disciplines beyond the organizer, met.

Times: 12:05 to 12:39 pm (34 minutes).

Discussion: History reviewed: PHQ-9 16 on 07/15, unchanged over eight weeks; sleep fragmented by pain; out of work since 04/2026. Needs identified: depression treatment is stalled while activity avoidance and deconditioning maintain the pain cycle, and the client is discouraged by conflicting advice. Outcomes to be achieved: a single graded-activity message across providers, behavioral activation targets tied to physical therapy milestones, and a medication review for sleep. Review of prior outcomes: the 05/2026 plan (therapy plus standalone home exercise) was not implemented; client reported not understanding how the pieces fit.

Decisions and tasks: 1) R. Osei: restart supervised PT twice weekly with a written graded-activity ladder, share the ladder with the team by 07/29. 2) A. Whitfield: align behavioral activation homework to the PT ladder from the 07/28 session onward; re-administer PHQ-9 at four weeks. 3) Dr. Nunez: medication review for sleep at the 08/03 visit; assess fitness-for-work pathway. 4) J. Lam: send the conference summary to all participants and offer a copy to the client by 07/24; book the review conference.

Distribution and next steps: Copy filed in the client record; summary offered to the client 07/23 and accepted; summaries sent to all participants. Review conference set for 09/09/2026. Entry by A. Whitfield, LCSW, 07/22/2026.

This sample is fictional and for educational purposes. It does not describe a real patient.

↑ Back to the template and downloads

Why this sample works

  • The definition is satisfied on the face of the note. Pre-arranged, single client, stated purpose, and a decision-directing discussion: the four things that make it a case conference and not a hallway chat.
  • Consent is recorded, attendance is not assumed. The client's agreement, including to the participants, is dated before the meeting, and the note is explicit that the client chose not to attend, which no rule requires.
  • The team mix and times are auditable. Four named participants with disciplines and modes, and a 34-minute bracket, cover the participant-minimum and time-tier questions every payer scheme asks.
  • Outcomes are reviewed, not just set. The note assesses why the prior plan failed before allocating new tasks, mirroring the review element the Australian definition enumerates.
  • Every task has a name and a distribution trail exists. Tasks are allocated to named members with dates, and the record shows the summary went to the team and was offered to the client.

Writing these after every session? BastionGPT drafts complete notes from bullets, dictation, or a transcript.

Generate a note from bullets

Documentation and compliance considerations

The case conference note is unusual: in two of the three countries, parts of its content list are set out in the instrument itself. Ontario's O. Reg. 246/22, s. 27 requires long-term care homes to hold a care conference within six weeks of admission and at least annually, and to keep a record of the date, the participants, and the results. Australia's General Medical Services Table Regulations make the recorded agreement, the day, the start and end times, the participants, the enumerated discussion activities, the copy in the record, and the summary offers legal preconditions of billing an organiser item, and the consultant physician notes add that a patient would not normally need more than five case conferences in 12 months. Only the practitioner who bills must meet the item's requirements; other participants document under their ordinary professional obligations. The format of the note is convention everywhere; those content lists are not.

In the US there is no standalone Medicare professional fee for a routine case conference: CPT team conference codes are bundled, and conference work is usually documented inside chronic care management, transitional care management, or care planning, so the note supports medical necessity rather than a conference claim; the care coordination note covers that documentation chain. One US change worth knowing: the 42 CFR Part 2 final rule (compliance date 16 February 2026) lets a single patient consent cover future uses and disclosures for treatment, payment, and operations, which simplifies bringing substance use disorder information into a multi-provider conference. Retention follows the chart the note sits in: state-law periods in the US (Massachusetts, one representative example, requires at least seven years from the last encounter), 10 years from last contact or the client's 18th birthday under Ontario college standards, and seven years for adults or until age 25 for minors under the Australian Psychology Board framework, with some state rules running longer.

↑ Back to the template and downloads

Common case conference note errors auditors flag

Case conference billing is actively audited. Australia's Professional Services Review has published case outcomes involving item 758, including a practitioner who rendered the highest volume of the item nationally and could not show the requirements were met, and PSR outcomes repeatedly turn on records that fail one enumerated element. In the US, an OIG audit of transitional care management found almost $1.7 million in overpayments where multiple practitioners billed the same beneficiary's same 30-day period. Ontario reviews check the pre-scheduled character, the participant minimum, and the time records behind K-code claims. The BastionGPT Clinical Advisory Board sees the same errors most often in case conference note reviews:

  • No start and end times. The most expensive omission: times select the time tier and are a billing precondition in Australia and the unit basis for OHIP claims.
  • Team composition that fails the rule. Too few participants, or the wrong mix, such as three doctors and no other kind of care under the Australian minimum-team requirement.
  • Consent recorded nowhere. The client's agreement, obtained before the conference, is a recorded element in Australia; a missing consent line can unwind the claim.
  • A plan review dressed as a conference. Australian rules require the conference to be clinically separate from preparing or reviewing a care plan; billing both for one discussion is a flagged pattern.
  • No distribution trail. No copy in the record, no summary to the team or client; the note exists but the coordination it claims cannot be shown to have left the room.

Case conference notes in the US, Canada, and Australia

AspectUnited StatesCanadaAustralia
StatusNo standalone Medicare conference fee; team conference CPT codes are bundled, and conference documentation lives inside care planning law (42 CFR 483.21, 418.56) and care management billingPayer policy plus one statute: OHIP K-codes (K121, K124, K700-series) for physicians, and O. Reg. 246/22 s. 27 mandating long-term care conferences with listed note contentsDelegated legislation: the GMST Regulations define the conference and make the content list a billing precondition for items 735 to 758 and the mental health case conferencing items
TerminologyCare planning conference, family meeting, IDT conferenceCase conference (K-codes), care conference (long-term care)Multidisciplinary case conference; organiser and participant items
What changesLittle is separately billable; the note's job is supporting medical necessity inside CCM, TCM, and plan documentationPhysician billing rules: pre-scheduled meetings only, most responsible physician plus two others, 10 minute minimum, documented times; one shared note initialled by physician participants sufficesRecorded consent, day and start/end times, minimum team of three with no more than two doctors, enumerated discussion elements, copy in the record, and distributed summaries are all payment preconditions
RetentionState law varies (Massachusetts: at least 7 years from the last encounter); Medicare claim-supporting documentation carries its own multi-year periodsCollege standards: 10 years from last contact or from the client's 18th birthday, whichever is later (CPBAO, CRPO)7 years for adults; for minors, until age 25 (Psychology Board framework; some state rules run longer)

The conference itself looks the same in all three countries: scheduled, multi-provider, single client. What changes is enforcement. Australian and Ontario billers work against enumerated content lists with audit programs attached, while US clinicians write the note to prove coordination and necessity inside other billed services. Write to the strictest list that touches your claim.

How BastionGPT helps

BastionGPT is specifically trained, tuned, and clinically tested on case conference notes.

  • Draft the conference record from your agenda, dictation, or a meeting transcript, with participants, times, decisions, and allocated tasks in their places.
  • Check the note against the elements your payer enforces: consent recorded, minimum team met, start and end times, outcomes reviewed, and the distribution trail, before anything is claimed.
  • Convert the record into the summaries the rules expect: a plain-language copy for the client and carer, and a team summary ready to send to each participant.

See how clinicians use it day to day on the AI therapy notes page.

Many BastionGPT users report saving more than 90 minutes per day on documentation.

HIPAA-compliant with a signed BAA on every plan. Your data is never used to train models. BastionGPT drafts, you review and sign.

Frequently asked questions

Usually not, and the rules are precise. In Australia the client must agree to the conference (and, for the mental health items, to each participant) but does not have to attend. In Ontario long-term care, the resident and any substitute decision-maker must be given the opportunity to participate fully. In US settings, attendance follows the care-planning participation rights of the setting rather than a conference-specific rule.

Yes. Australian items allow each participant to join in person, by video, or by phone, and OHIP permits personal attendance, videoconference, or telephone. Record each participant's mode in the note, because a reviewer reconstructing the conference will look for it.

It depends on the scheme. In Australia, a medical practitioner organises and bills the organiser items (735, 739, 743 by time tier) while other providers bill participation items, including allied health items 82001 to 82003 for eligible clients. In Ontario, physicians bill the K-codes. In the US there is no separately paid Medicare conference fee for routine care; the work is documented inside care management services, the chain the care coordination note covers.

No. In Australia, only the practitioner who bills an item must meet all of that item's record requirements; other participants document under their ordinary professional obligations. In Ontario, one shared chart note signed or initialled by the physician participants satisfies the record requirement. Non-billing clinicians should still note their participation and any tasks they accepted, because those tasks live in their own scope of practice.

No hard cap exists for most items, but Australia's consultant physician notes state that a patient would not normally require more than five case conferences in a 12-month period, and auditors treat that as a benchmark. If a client genuinely needs more, the records need to show why.

No. OHIP expressly excludes educational meetings such as rounds, journal clubs, and continuing professional development sessions from case conference billing, and the Australian definition requires a conference about an individual patient's care. A recurring internal meeting that reviews several clients is a multidisciplinary team meeting, which has its own note.

No jurisdiction reviewed mandates a template or a minimum length; most case conference notes run 150 to 400 words, and a billed conference needs the payer's enumerated elements more than it needs length. Retention follows the record the note sits in: state law in the US (Massachusetts, for example, requires at least 7 years from the last encounter), 10 years from last contact or the client's 18th birthday under Ontario college standards, and 7 years for adults or until age 25 for minors under the Australian framework.

The regulations enumerate it: the client's recorded agreement, the day and the start and end times, the participants, and the discussion elements (history, multidisciplinary care needs, outcomes to be achieved, tasks allocated to team members, and review of previously identified outcomes), plus a copy in the medical record, a summary offered to the client and carer, and a summary to each team member. The conference must also be clinically separate from preparing or reviewing a care plan.

Bring the conference however you captured it: dictation on the walk back, the agenda with notes, or a transcript. BastionGPT drafts the record with participants, times, decisions, and allocated tasks structured for your payer's checklist, flags missing preconditions like the consent line or an unmet team minimum, and produces the client and team summaries the distribution rules expect. BastionGPT is HIPAA-compliant with a signed BAA on every plan, and your data is never used to train models.

Educational content, not legal or billing advice. Sample notes are fictional. Follow your organization's policies and your board, payer, and jurisdiction requirements.