AI for Recovery Community Organizations: Grant Reports, Volunteers, and Outreach

Recovery community organizations run on volunteers, small grants, and people who care too much to quit. They also run on paperwork. Quarterly reports. Narrative sections. Volunteer schedules. Event calendars. Social posts that someone writes at midnight.

This is one of the best fits for AI in the whole field. A lot of RCO admin work can be done with no participant information at all.

Grant reporting

Grant reports usually ask for two things: numbers and story. How many people you served, what you did, and what changed.

The numbers. Pull the counts from your own tracking system. Contacts this quarter. Events held. Volunteer hours. Trainings delivered. Then use an AI assistant to help format them into the funder's template, write a summary paragraph, or compare this quarter to last. The AI never needs to see a participant list. It needs the totals.

Check every number before you submit. AI tools can drop a digit, swap two rows, or "round" something they shouldn't. Funders don't accept "the software did it."

The narrative. This is where RCOs often struggle, because the people writing it are doing the work and don't have time. An AI assistant can help you go from a few bullet points ("held 12 all-recovery meetings, started a family support group, two volunteers got peer certification") to a readable narrative. Then you edit it until it sounds like you and every claim is true.

Stories. Funders love a story. Your participants' stories belong to them. If someone agrees to share, get their written permission for that specific use, let them read what's written, and strip names and identifying details before anything goes into an AI tool. "A woman in her 30s who came to us after leaving jail" is very different from her name and hometown.

Small numbers can out people

Aggregate data feels safe. It usually is. But small counts can identify people, especially in rural areas. If your report says "one participant from Elmore County started medication for opioid use disorder this quarter," someone who knows that county may know exactly who that is.

The usual fix is to combine small categories or suppress them. Some organizations set a floor and don't report any count below it. Ask your funder what they require, and decide a rule for yourself.

HHS's de-identification guidance is written for HIPAA, but it's a useful reference even if HIPAA doesn't apply to you. It shows how much information, including geography below the state level and dates, can point back to a person.

Volunteers and events

Scheduling. Volunteer shifts, coverage for meetings, reminders. AI scheduling assistants and ordinary scheduling software can handle a lot of this. Volunteer information isn't health information by default, but if your volunteer list is also a list of people in recovery, treat it carefully.

Event promotion. Flyers, posts, newsletter blurbs, press releases for a recovery month event. Good fit for AI drafting. Keep faces and names out unless people have agreed in writing.

Training materials. Volunteer orientation, a handout on naloxone, a guide to running an all-recovery meeting. AI can help draft. A person who knows the subject checks it, especially anything medical.

Outreach

AI can help you write outreach to partners: hospitals, courts, churches, employers. Letters, one-pagers, talking points for a meeting with a county commissioner.

What it can't do is build the relationship. RCOs earn trust in their communities by showing up for years. A well-written email opens the door. A person walks through it.

One caution on outreach to treatment providers and sober living homes. Never accept or offer money, gifts, or anything of value tied to referrals. The federal Eliminating Kickbacks in Recovery Act, 18 U.S.C. § 220, covers remuneration for referrals to recovery homes and clinical treatment facilities. RCOs are trusted neutral ground. Keep it that way.

Where the privacy line sits

Safe with de-identified or aggregate data. Grant report formatting and narrative from totals. Event promotion. Training materials. Partner outreach letters. Volunteer schedules, with care. Resource lists. Board meeting minutes with no participant details.

Needs a BAA, if HIPAA applies to you. HIPAA covers health plans, clearinghouses, and health care providers that conduct standard electronic transactions, according to HHS's covered entities page. An RCO that bills insurance for peer services, or works as a contractor for a covered entity, may be handling protected health information. In that case, any AI vendor that touches participant records needs a Business Associate Agreement. If you're not sure, ask counsel.

Treat as protected either way. Participant contact logs, intake information, notes from peer contacts, anything tying a name to recovery status. Funders, state law, and your own policies may require confidentiality even where HIPAA doesn't. Use tools that commit in writing to protecting the data and not training on it.

Don't automate. Peer conversations. Decisions about who gets help. Anything tied to referral payments. Sharing a participant's story without their written yes.

A starting setup for a small RCO

Choose one AI assistant for writing work, with a written rule that no participant information goes into it. Choose one system of record for participant data, set up with proper access controls. Never let the two mix.

Have one person, often the director, own the rule and check in on it monthly. The staff training guide has a simple policy you can adapt for volunteers too.

For the peer specialists on your team, AI tools for peer recovery specialists covers documentation and resource lookup.

What this buys you

If AI takes the quarterly report from two days to half a day, that's a day and a half back. At most RCOs, that time goes straight back to people. That's the trade worth making.