> For the complete documentation index, see [llms.txt](https://www.opioidsettlementguides.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opioidsettlementguides.com/indiana/indianas-opioid-settlements.md). # Indiana’s Opioid Settlements This Community Guide will describe how Indiana is spending its opioid settlements and whether Indiana is working to ensure community access to opioid settlement funds. Last updated September 1, 2024. *This Community Guide will describe how Indiana is spending its opioid settlements and whether Illinois is working to ensure community access to opioid settlement funds. Last revised September 1, 2024.*

Total Funds

$941.96 million[1]

[1] Total is rounded. See The Official Opioid Settlement Tracker Tally. Accessed September 1, 2024.

Allocation

50% to the state and 50% to local governments


Mechanism

Legislation (Ind. Code Ann. Secs. 4-6-15-1 to 4-6-15-5, 4-12-16.2-1 to 4-12-16.2.8, 4-12-16.3-1 to 4-12-16.3-8, 5-14-6-4)

50% State Share

50% Local Share

Ultimate DecisionmakerIndiana Family and Social Services Administration and State Budget Committee (for 35%) and Indiana General Assembly (for 15%)Local officials for towns, cities, and counties
Decision-making Process

For 35% of funds, the Indiana Family and Social Services Administration (FSSA) submits a spending plan to the state’s Budget Committee for approval.

The Indiana General Assembly directly appropriates the remaining 15% of Indiana’s total funds.

Localities decide autonomously but must report uses to the Indiana Family and Social Services Administration.
SupplantationNot prohibitedNot prohibited
Grant FundingYes. See the FSSA’s Division of Mental Health and Addiction's Funding Information page. Up to each locality (availability and processes will vary)
Public InputNo opportunities available (not required)Up to each locality (not required)
Advisory BodyNo (not required)Up to each locality (not required)
ExpendituresPublic reporting required. See NextLevel Recovery’s Opioid Settlements website.Public reporting required. See NextLevel Recovery’s Opioid Settlements website.
UpdatesFor updates on the state and local shares, visit the Family and Social Services Administration’s (FSSA) NextLevel Recovery: Opioid Settlements and the Indiana Attorney General’s Opioid Settlement & Litigation websites and sign up for the FSSA Division of Mental Health Addiction’s and IN Attorney General's email lists.

For updates on the state and local shares, visit the Family and Social Services Administration’s (FSSA) NextLevel Recovery: Opioid Settlements and the Attorney General’s Opioid Settlement & Litigation websites and sign up for the FSSA Division of Mental Health Addiction’s and IN Attorney General's email lists.

For updates on specific local shares, a good starting point is to check the website for your county board of commissioners or county council, city council, town council, or local health department.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://www.opioidsettlementguides.com/indiana/indianas-opioid-settlements.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.