Program Outcomes · add-on under development · proof of concept
Human-services programs give the same questionnaire at intake, at follow-up and at exit. Today the scores live in a PDF, a spreadsheet or a separate portal. Program Outcomes puts the instrument, the score and the trend on the Contact, Case or Program Engagement record in Salesforce, reports baseline against latest per program, and lets a Flow act when a score crosses a line your organization drew.
Built for behavioral health, family support, housing and care-management programs that already run on Salesforce. It runs on the AutoSurvey engine you already have.
One design partner wanted
We look for one human-services nonprofit on Salesforce to help shape Program Outcomes, which is under development. We build around one instrument you give and one funder report you need.
What it does
Three steps, repeated per encounter. Each one lands as a Salesforce record you can report on.
Staff read the items aloud and tap the answers. Or they hand the device to the client in an isolated respondent session, and staff sign in again to return. Or the client gets a link by email or text and answers at home. Or your own Screen Flow asks the items and calls one action to score them.
The total, the subscale scores, the band, and the change since baseline and since the last visit are stamped on the administration record in the same save. One scorer serves all three modes. The bands are your organization's own approved protocol. The package ships none active.
A threshold rule you write fires an event: a score crossed a line, a critical item was answered, or no change after N administrations. Your Flow opens the task, notifies the supervisor, or schedules the next administration. Each event records whether someone acknowledged it. Two Flow templates ship as a starting point.
Why it is useful
A score-over-time chart on the Contact, Case or Program Engagement page, shaded with your bands and marked at each administration. A case manager sees intake to today in one glance, without opening a second system.
A schedule per client sends the next link or reminds the worker. A threshold event reaches your Flow the moment the record saves. The follow-up protocol runs the same way for every client, on every shift.
Baseline versus latest, the shift between bands, completion by mode, and the count of critical-item events, per program and per period. Built from the same records, exportable, and reproducible next quarter.
Bands and threshold rules are records, with an approver, an effective date and a change log. An active protocol is read-only; a change is a new draft. Published cut-points can be loaded as a starting point. Your clinical lead approves them before any rule fires. Nothing on this page is a clinical claim.
The screens
Proof-of-concept screens, rendered in the Salesforce Lightning style. The funder report comes first, because that is the deliverable; the record, the device and the protocol follow. Every organization, person, approver and score is illustrative data, not a customer result. Each screen carries a ribbon that says so.
01 · Program outcomes dashboard
Under development. Baseline against latest for the same people, with those still inside the follow-up window counted separately. Completion by collection channel, and critical-item alerts with their acknowledgement. The funder export is the same data. Illustrative data.
02 · Outcomes on the Case
Under development. The PHQ-9 trend over the bands this fictional organization approved, with its own cut-off line. Each point is an administration, with the channel and the worker. The next administration is scheduled, and each alert this record raised shows who acknowledged it. Illustrative data.
03 · Administer on a device
Under development. The worker starts the instrument from the record. Hand-the-device opens an isolated respondent session with no record context and no running score; staff re-authenticate to return. The answers save to the same record either way. Illustrative data.
04 · Threshold protocol
Under development. A band set is a short table your clinical lead approves, read-only once active. A threshold rule names the alert it raises and the Flow that listens. A rule on a critical item needs your recorded response pathway first. Every change is logged. The package ships no active rule. Illustrative data.
05 · Instrument library
Under development. Each instrument is versioned, with its items, the score per option, subscales and scoring method. A history measure such as ACEs is scored once and kept out of the trend. A custom instrument, like a home-safety check, is built the same way and is labelled custom, not validated. Illustrative data.
For your Salesforce admin · the first version
Kept for a later version: licensed instrument shells, custom Apex scoring, encounter records, a rater-certification gate, instrument text translations, and norm-referenced scores.
Instruments and licences
Where it stands
The proof of concept is complete, down to the data model, the screens and the effort by phase. We start the build when one organization names an owner, the report its funder asks for, the instruments it gives, and a pilot it will run with Salesforce as the system of record for the scores. No customer uses Program Outcomes yet. No number on this page is a customer result.
If that is you, become the design partner. Program Outcomes is one of two add-ons under development; the other is the Fraud & Quality Shield, which checks the quality of every response before it counts.
What costs what
You work with Erik Rogers, the founder of Mindshare Studio LLC, directly: support@mindsharestudio.com.
AutoSurvey already scores every survey and stores each response as a Salesforce record. Program Outcomes adds the instrument library, the bands, the trend and the threshold events on top. See Reporting.