> 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/south-carolina/south-carolinas-opioid-settlements.md). # South Carolina’s Opioid Settlements *This Community Guide will describe how South Carolina is spending its opioid settlements, and whether South Carolina is working to ensure community access to opioid settlement funds. Last revised September 1, 2024.*

Total Funds

$622.41 million[1]

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

Allocation

49%-79% to local governments and 19%-49% to a statewide fund

Mechanism

State-Local Agreement (South Carolina Opioid Settlement Allocation Agreement); Legislation (S.C. Code Secs. 11-58-10 through 11-58-100)

49-79% Guaranteed Political Subdivision Subfund Share

19-49% Discretionary Subfund Share

Ultimate DecisionmakerLocal officials for counties, cities, and townsSouth Carolina Opioid Recovery Fund Board
Decision-making ProcessLocalities and their approved entities apply for funding from this share, and the South Carolina Opioid Recovery Fund (SCORF) Board must approve applications if made for approved abatement strategies.The South Carolina Opioid Recovery Fund (SCORF) Board scores proposals and approves funding.
SupplantationProhibitedProhibited
Grant FundingYes. See the SCORF Board’s Apply for Opioid Recovery Funds page.Yes. See the SCORF Board’s Apply for Opioid Recovery Funds page.
Public InputUp to each locality (not required)

No opportunities available (not required)

But see SCORF Board’s Coffee Chats

Advisory Body

Up to each locality (not individually required). But see South Carolina Opioid Recovery Fund (SCORF) Board, which exercises only ministerial authority over this share.

The SCORF Board is not required to include member(s) with lived and/or living experience.

Yes (required). See South Carolina Opioid Recovery Fund Board, which exercises discretionary authority over this share.

The SCORF Board is not required to include member(s) with lived and/or living experience.

ExpendituresPublic reporting required. View the SCORF Board’s annual reports here.Public reporting required. View the SCORF Board’s annual reports here.
UpdatesTo find updates on the Guaranteed Political Subdivision Subfund share, a good starting point is to check the websites for your board of county commissioners or city council. You can also visit the South Carolina Opioid Recovery Fund Board’s website, which hosts an accounting of funding awards from both subfunds.For updates on the Discretionary Subfund, visit the South Carolina Opioid Recovery Fund Board’s website, which hosts an accounting of funding awards from both subfunds.
--- # 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/south-carolina/south-carolinas-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.