A 14-year-old client's school counselor calls Maria on Tuesday. The pediatrician's office faxes a medication question on Wednesday. On Thursday, the father, divorced from the mother who brought the teen to intake, emails demanding "everything in my son's file," copying an attorney. Every one of those contacts is a collateral contact, every one needs documentation, and every one sits at the intersection of three legal frameworks that do not agree with each other: state minor-consent statutes, HIPAA, and FERPA/IDEA for anything touching the school. Get the documentation right and the treatment runs smoothly; get one disclosure wrong, to one parent who turned out not to hold legal custody of the health-care decision, and you have a board complaint with your name on it. This lesson teaches the discipline of the collateral-contact log: who may consent, who may access, what each collateral may be told, what AI may and may not do with custody information, and how to build a Collateral-Contact Log that satisfies minor-consent rules in your state. By the end you will have that log built and a verification habit that protects your license every time the phone rings.

What Counts as a Collateral Contact, and Why Minors Multiply Them

A collateral contact is any treatment-relevant communication with someone who is not the client: a parent providing history, a teacher describing classroom behavior, an IEP team meeting, a pediatrician coordinating medication, a stepparent at pickup, a grandmother who does the homework supervision. Adult therapy generates a few of these; child and adolescent therapy runs on them. You cannot treat a nine-year-old's school refusal without the school, or an adolescent's ADHD without the prescriber, or anyone's family-system problem without the family. The volume is the first documentation problem: a busy child clinician can log six collateral touches in a week per client, each a potential disclosure event, each needing a record of who, when, what direction information flowed, and under what authority.

The second problem is that every collateral contact is two-directional and the rules differ by direction. Information coming in (the teacher tells you the client sleeps in class) is generally low-risk to receive but must be documented as collateral report, attributed exactly the way the previous lesson taught: "teacher reported," not "client sleeps in class," because collateral reports are observations filtered through someone else's lens and stakes. Information going out (you tell the teacher anything at all, including the fact that the child is your client) is a disclosure of protected health information, and the entire legal apparatus of this lesson governs that direction. The collateral-contact log you will build records both directions explicitly, because the audit question is never "did you talk to the teacher" but "what did you tell the teacher, and who authorized it."

Hold this lesson's controlling analogy: the collateral-contact log is air traffic control for information around a minor's treatment. Every plane (each contact) gets logged with origin, destination, payload, and clearance. Most crashes in child-therapy compliance are not bad intentions; they are unlogged planes and missing clearances, discovered later by exactly the person with standing to complain.

Minor-Consent Statutes: Who Consents, Who Accesses, Who Gets Told

Before any collateral disclosure, you need to answer three questions your state's law controls: who consented to this minor's treatment, who may access the records, and what may be disclosed to whom. The statutes differ enough that practicing on a generalized memory is malpractice-adjacent. California Family Code §6924 permits a minor 12 or older to consent to their own outpatient mental health treatment if the clinician determines the minor is mature enough to participate intelligently; when the minor consents under §6924, the minor, not the parent, holds the records rights, and parental involvement is required only where the clinician deems it appropriate (and documents the inclusion-or-exclusion decision with reasons). New York Mental Hygiene Law §33.21 governs the consent of minors for mental health treatment and the conditions under which a minor's consent suffices, and it structures when parental notice or consent can be bypassed. Texas Family Code §32.004 allows a minor to consent to counseling for suicide prevention, chemical addiction or dependency, or sexual, physical, or emotional abuse, a narrower set of doors than California's. Each statute creates a different map of who is the consenting party, and the consenting party generally controls the disclosure authorizations the rest of this lesson depends on.

The practical consequence: your intake for every minor must establish and document the consent basis (parental consent, minor's own consent under the applicable statute, or both), because that basis determines the rest of the chart's plumbing. A 13-year-old self-consented under CA Fam Code §6924 has confidentiality rights against her own parents; the collateral conversation you may freely have with the mother of a parental-consent 9-year-old may be a breach if you have it about her. And the adolescent-confidentiality frame you set verbally at intake (what you will share with parents, what stays in the room, what safety exceptions override everything) should be documented as part of the consent record, because it is the agreement every later disclosure is measured against.

Layer the divorce scenario on top. When parents are divorced with shared legal custody, both parents typically hold equal rights to consent to and access the minor's treatment records, regardless of physical custody schedules, unless a court order says otherwise. The parent who never brings the child to session usually still holds full legal authority. The reverse trap is sharper: a parent whose legal custody has been limited or terminated by court order may present convincingly as entitled, and a disclosure to them is a breach. The only way through is the rule this lesson exists to drill: verify legal custody documentation before any disclosure. Ask for and read the operative custody order, log which document you reviewed and its date, and treat "Mom said Dad lost custody" as a claim, not a fact. Both the claim and your verification go in the log.

FERPA, IDEA, and the School Boundary

The moment your collateral work touches a school, a second privacy regime enters: FERPA, the Family Educational Rights and Privacy Act, governs education records held by the school, and IDEA, the Individuals with Disabilities Education Act, governs the special-education process including IEPs. The overlap question that confuses clinicians: which rules cover which records? Your treatment records are HIPAA-covered (or state mental health records act-covered) health records; the school's records about the same child, including what the school counselor writes, are FERPA-covered education records. When you send the school a letter, your HIPAA disclosure rules govern the sending; once your letter sits in the school's file, FERPA governs its life there, including FERPA's parental access rights, which can be broader than what the family expected. Translation for practice: anything you send a school should be written knowing both parents (in a shared-legal-custody divorce, FERPA access generally extends to both parents unless legally limited) and potentially other school personnel can read it.

IEP participation deserves its own discipline. When you attend an IEP meeting as the outside clinician, you are making a real-time oral disclosure to a room: special education teacher, general education teacher, administrator, school psychologist, sometimes an advocate or attorney. Your authorization needs to cover that audience and that purpose, your contribution should be scoped in advance (what diagnosis language, what functional impacts, what accommodations you will speak to), and your documentation afterward records what you disclosed, to whom, under which authorization. School-based clinicians live a harder version of this: a therapist employed by or contracted to a school district may be generating records that are themselves FERPA education records rather than HIPAA health records, a classification question worth resolving with the district in writing before the first session, not during the first records dispute.

For documentation, the practical kit is a school-communication template family: a request-for-information letter (what you ask the teacher to describe, behaviorally), a clinician-input letter for the IEP or 504 process (diagnosis only as authorized, functional impacts, recommended accommodations, no therapy-content narrative), and a release form whose scope lines name the school, the specific personnel roles, the information categories in each direction, and an expiration. AI drafts these templates well, and the verification you owe is scope-matching: every sentence in the outgoing letter checked against the authorization's named categories before it leaves.

Verify, then disclose, then log: the custody order is a document you read, not a story you are told, and AI never infers custody or authority from anything said in session.

The AI Guardrail: No Inferred Custody, No Assumed Authority

Here is this lesson's hard AI rule, and it is subtler than the previous lessons' because the failure mode is quiet: AI must not infer custody arrangements from session content, and you must not let inferred custody leak into documentation or disclosure decisions. The mechanism of the failure: your scribe hears a month of sessions in which the child says "I live with Mom," the mother schedules everything, and the father is described in the past tense. A summarization model will, with high probability, write "mother has custody" or "father is not involved in the client's care" into a draft, because that is the pattern the transcript suggests. But physical living arrangements are not legal custody; an uninvolved-sounding father may hold full shared legal custody and full records rights; and a sentence in your chart asserting a custody arrangement you never verified is both a factual error and, worse, a premise later disclosure decisions silently rest on. Six months later, a staff member reads "mother has custody" in the chart and declines the father's lawful records request, and now the practice has interfered with a parent's legal rights based on a hallucinated legal conclusion.

The discipline has three parts. First, a standing instruction in your scribe configuration and your prompts: "Do not state or imply custody, guardianship, or decision-making authority. Record family-structure information only as attributed report ('client stated she lives primarily with her mother')." Second, a chart convention: legal authority facts live in one place only, a custody-and-consent section of the record populated exclusively from documents you have read (the custody order, the guardianship letter, the consent signature), each entry citing the document and date reviewed. Third, a pre-signature scan of every AI-drafted note for authority language: custody, guardian, rights, primary parent, allowed to. Any such phrase either traces to the verified custody-and-consent section or comes out.

The same guardrail extends to authority adjacent questions AI will volunteer answers to: whether a stepparent can consent, whether a 16-year-old's self-consent covers a records release, whether the grandmother with a notarized letter counts as a guardian. These are legal determinations resting on documents and state law. AI can help you build the verification checklist (what documents to request for each claimed relationship); it cannot perform the verification, and a model's confident answer about your state's minor-consent statute is a hypothesis to check against the statute, never a basis for disclosure.

Anatomy of the Collateral-Contact Log

Now build the artifact's structure. A defensible collateral-contact log entry carries eight fields. One: date, time, and duration of the contact (duration matters because some collateral work is billable in some structures, and because a 40-minute call with a parent is clinically different from a 4-minute scheduling exchange). Two: the collateral's identity and role (name, relationship to client, organization). Three: direction of information flow, in, out, or both. Four: authority for any outbound disclosure, named specifically: the consent basis (parental consent dated X; minor self-consent under CA Fam Code §6924), the release on file (scope, signatories, expiration), or the exception relied on (emergency, mandated report, safety). Five: content summary, attributed for inbound ("teacher reported client sleeping in class twice this week") and scoped for outbound ("confirmed treatment attendance and shared the two classroom accommodations listed in the 504 letter; no therapy content disclosed"). Six: custody-verification status where a parent or claimed guardian is involved ("custody order dated 2025-03-14 reviewed; joint legal custody confirmed"). Seven: clinical relevance, one line tying the contact to the treatment plan. Eight: any follow-up created.

Two structural decisions complete the design. Where does the log live? Inside the minor's chart, as a running structured section, because scattered contacts buried in session notes are unfindable in an audit and invisible to the colleague covering your caseload. And who can read it? Remember that records-access rights attach to the chart: under a §6924 self-consent, the minor controls access; under parental consent in a shared-custody divorce, both parents typically can access, which means the log itself must be written to the same both-readers standard as the couples note in the previous lesson. "Father called, hostile, attempting to interrogate" fails that standard; "father called requesting session information; clinician confirmed attendance only per release scope; father expressed dissatisfaction with scope limits" survives it.

AI's legitimate role in the log is exactly its role throughout this chapter: structure after judgment. Dictate the contact in shorthand within minutes of the call ("school counselor, inbound, sleeping in class, no disclosure out, ties to goal 2, will raise in Thursday session"), and let the model expand it into the eight fields, with your standing no-custody-inference instruction active, and your verification pass confirming the authority field cites a real document and the content summary matches what you actually said. The model formats; the clearance decisions, every one of them, were yours before the call ended.

The Divorced-Parents Stress Test

Run the hardest common scenario end to end, because it integrates everything. Mother brings 10-year-old to intake, signs consent, mentions "Dad's not really in the picture." Eight sessions later, father emails requesting records and a phone call, copying an attorney. Step one: do not stonewall and do not comply; acknowledge receipt and state that the practice verifies legal authority before discussing any minor's care, a sentence that offends no lawful parent and deters no unlawful one. Step two: verify. Request the operative custody order from the father (or the mother, or both); read the legal custody provisions yourself; log the document, its date, and what it establishes. If he holds joint legal custody, he generally holds consent and access rights you must honor, including the right to be involved going forward, and the fact that intake proceeded on one parent's signature gets revisited: many practices require, or at minimum strongly prefer, both legal custodians' consent for a minor's non-emergency treatment precisely to avoid the parent who appears at session eight with an attorney and a grievance.

Step three: manage the disclosure itself within the verified rights. Records access for a parent is not unlimited: state law may protect the minor's self-consented treatment, psychotherapy notes have their own carve-out, and information that endangers the child can in some frameworks be restricted with documentation of the reasoning. What you produce, you log. Step four: document the system change: the custody-and-consent section now reflects joint legal custody verified by order dated X; both parents added to communication protocols; the adolescent-confidentiality frame re-explained to both parents and documented. Step five: watch the litigation horizon. A records request copying an attorney is often the overture to a custody modification, and everything from the subpoena discipline of the previous lesson applies: the chart, including your collateral log, may be read by a family court, which is one more reason every entry was written attributed, scoped, and neutral.

The AI postscript to the stress test: at no point did any model decide whether the father had rights, whether the mother's account was accurate, or what he could be told. It drafted the acknowledgment email from your template (a generic, scope-neutral text, the same lesson as the IPV declination), expanded your shorthand into log entries, and scanned drafts for authority language. Every clearance was human. That division of labor is the chapter's entire thesis, and nowhere does it earn its keep more visibly than the week both parents' attorneys request the same child's chart.

The Applied Problem: Build the Collateral-Contact Log That Satisfies Minor-Consent Rules

Your artifact is a Collateral-Contact Log template plus its companion custody-and-consent section, installed in your EHR for every minor client. Build it in four steps.

Step one, write the consent-basis header yourself for your state: for a California practice, the header fields are "Consent basis: [ ] parental consent (signatory, date, custody verified by document/date) [ ] minor self-consent under Fam Code §6924 (clinician maturity determination documented, date) [ ] both; Records access controlled by: [name]; Adolescent-confidentiality frame documented: [date]." Adapt the statutory citation for your jurisdiction (NY MHL §33.21, TX Fam Code §32.004) and verify it against the statute, not a summary.

Step two, prompt your AI tool, no client data: "Create a structured Collateral-Contact Log template with eight fields per entry: (1) date/time/duration; (2) collateral identity and role; (3) direction of information flow (in/out/both); (4) authority for outbound disclosure (consent basis, release scope and expiration, or exception relied on); (5) content summary, attributed for inbound and scoped for outbound; (6) custody-verification status citing document and date where a parent or guardian is involved; (7) one-line clinical relevance to the treatment plan; (8) follow-up created. Add a header note: 'Legal authority facts are recorded only in the custody-and-consent section, from documents reviewed; do not state or imply custody, guardianship, or decision-making authority anywhere else in this record.' Do not include any field that infers or concludes legal authority from session content."

Step three, run the verification pass: confirm the no-inference instruction appears verbatim; confirm field four forces a named authority rather than a free-text rationalization; confirm the statutory citations in your header are character-correct against the codes; and test the both-readers standard by drafting two sample entries (the school counselor call and the father's records request) and reading each aloud as if the parent it concerns were listening. Step four, integrate the workflow: shorthand dictation within minutes of each contact, AI expansion under the standing instructions, your scan of every draft for authority language (custody, guardian, rights, primary parent), and a quarterly self-audit pulling one minor's chart to check that every outbound disclosure in the log traces to a clearance. Done looks like this: any auditor, either parent's attorney, or your own covering colleague can open one section of the chart and see every plane that ever flew, with origin, destination, payload, and clearance, and not one entry that guesses at the law.

Key Takeaways

• Collateral contacts (teachers, parents, IEP teams, pediatricians) are the operating system of child and adolescent treatment, and each is a two-direction event: inbound reports get documented as attributed collateral report, while every outbound word, including the fact of treatment, is a PHI disclosure requiring named authority.
• Minor-consent statutes set the chart's plumbing and they differ sharply: CA Fam Code §6924 lets a mature minor 12 or older self-consent to outpatient mental health treatment and hold the records rights; NY MHL §33.21 structures when a minor's consent suffices; TX Fam Code §32.004 opens narrower doors (suicide prevention, chemical dependency, abuse). Document the consent basis at intake because it controls every later disclosure.
• In divorce with shared legal custody, both parents typically hold consent and records-access rights regardless of the physical schedule, and a parent whose rights were limited by court order can still present convincingly. The rule is mechanical: verify legal custody by reading the operative order, log the document and date, and treat any verbal account of custody as a claim.
• School contact adds the FERPA/IDEA layer: your records are health records, the school's are education records, your letter becomes a FERPA record once filed at the school, and IEP participation is a real-time oral disclosure to a defined room that your authorization must cover and your follow-up note must record.
• The hard AI guardrail: AI must not infer custody arrangements or authority from session content. Keep a standing no-inference instruction in every scribe configuration, confine legal-authority facts to a custody-and-consent section populated only from reviewed documents, and scan every AI draft for authority language before signing.
• The eight-field log entry (date/time/duration, collateral identity, direction, named authority, attributed and scoped content summary, custody-verification status, clinical relevance, follow-up) lives as one structured section in the minor's chart and is written to the both-readers standard, because records-access rights mean either parent, or the self-consented minor, may someday read it.
• In the divorced-parents stress test, the safe sequence is acknowledge, verify, disclose within verified rights, document the system change, and anticipate litigation; AI drafts templates, expands shorthand, and flags authority language, but every clearance decision, from who may consent to what the teacher may be told, is the clinician's alone.