What is Tail coverage, and what should an ABA practice owner know before applying it? Tail coverage is an extended reporting period that may allow claims to be reported after a claims-made policy ends for covered acts occurring after the applicable retroactive date and before termination. An ABA owner should verify eligible acts, claim definition, reporting deadline, cost, election, limits, individual and entity rights, notice route, contracts, and replacement coverage.
Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.
Tail coverage extends reporting time
The Texas Department of Insurance explains that claims-made coverage can include an extended reporting period, often called tail coverage. The extension gives additional time to report qualifying claims after the policy ends.
Tail coverage does not extend the time when services can occur. It generally concerns acts during the covered period and after any retroactive date. New services after policy termination need current coverage. The endorsement can also restrict which claim types or insureds qualify.
Read the claims-made trigger first
Confirm when a claim is first made, when it must be reported, and what counts as notice. Some forms treat a written demand, lawsuit, licensing matter, subpoena, or notice of intent differently. Circumstance reporting during the active term may connect a later claim to the earlier policy when the terms permit it.
An ERP cannot repair every gap. A missing prior-acts period, undisclosed known circumstance, excluded service, late notice, or ineligible insured may remain outside coverage. Review continuity before canceling the existing policy.
Basic and optional periods can coexist
A policy may provide a short automatic reporting period and offer a longer optional ERP for additional premium. Record the election deadline, purchase method, payment deadline, duration, cancellation terms, and whether the option varies with retirement, disability, death, sale, or carrier cancellation.
“Unlimited” tail language still requires review. It may mean unlimited reporting time for qualifying prior acts, while limits, exclusions, claim definitions, and other conditions remain in force.
Individuals and organizations need separate answers
An entity policy and an individual clinician's policy may have different retroactive dates and tail rights. Ask what happens when a clinician leaves, the practice sells, a subsidiary closes, ownership changes, or the professional entity dissolves.
Employment and contractor agreements sometimes assign the purchase or cost of tail coverage. Counsel should review whether that provision is enforceable and whether the available endorsement satisfies it. A receipt for premium does not prove every required person or service is protected.
Replacement coverage may use prior acts instead
A new claims-made policy can sometimes preserve continuity by accepting a retroactive date that reaches back to the original start of coverage. That is commonly called prior-acts or nose coverage. Compare it with an ERP rather than assuming one route is always preferable.
The comparison should include covered services, insureds, limits, exclusions, defense, claims history, known circumstances, carrier terms, cost, and contract requirements. When changing policy forms or carriers, obtain written confirmation of the retroactive date and any prior-acts limitation.
Limits may remain tied to the expired policy
Tail coverage often uses the expiring policy's limit or an ERP-specific aggregate. Claims reported during the extension may share that limit with claims already reported. Defense costs can further reduce what remains when the form places defense inside limits.
Ask whether purchasing the ERP creates a new aggregate, preserves the old one, or applies a separate sublimit. Confirm deductibles or retentions and how related claims are treated.
A fictional closure review
Bright Coast ABA plans to end operations. It identifies seven required ERP facts: eligible entity, insured people, retroactive date, covered act period, election deadline, reporting deadline, and available limit. Five are verified. The former-contractor rule and aggregate treatment remain unresolved.
ERP readiness is 5 of 7 facts, or 71.4%. The two unresolved facts stay in the closure plan with owners and written questions. The practice preserves the existing notice route and does not dissolve the entity or cancel coverage until counsel and the broker review the sequence.
This ratio reflects document readiness. It provides no estimate of claim frequency or insurer response.
Closure requires durable records and contacts
Keep the policy, ERP endorsement, application, invoices, proof of election, claim files, contracts, corporate records, and current notice addresses accessible for the entire reporting period. Clinical and business records follow their own retention and privacy requirements.
Assign a person who can receive legal papers and insurance notices after ordinary staff depart. Update the carrier and broker when required. An abandoned email inbox can turn a viable reporting right into a missed deadline.
Test the contact route before closure. Confirm that postal mail, registered-agent notices, former-client questions, subpoenas, and insurer correspondence reach an authorized person. Record backup ownership when that person becomes unavailable.
The SBA guide recommends licensed-agent support and comparison. For a sale, merger, retirement, closure, or carrier change, begin the comparison well before the cancellation date.
Related terms
Sources
Take the next step with clarity
Whether you are finding care, growing as a clinician, or building a stronger ABA practice, Finni brings the people, tools, and support together to help you move forward.
Start or grow your ABA practice with Finni