Program Outcomes · included in AutoSurvey
Track client progress. Build funder reports in Salesforce.
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.
What it does
Administer. Score. Act.
Three steps, repeated per encounter. Each one lands as a Salesforce record you can report on.
Administer, three ways
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.
Score and band, by your protocol
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.
Act in Flow
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
One record of truth for the score. No portal, no re-keying. Scheduled and unacknowledged follow-ups are tracked.
The trend is on the record
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.
Follow-up that does not depend on memory
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.
The funder report is a Salesforce report
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.
Your protocol, under your version control
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
The screens
Every organization, person and number on these screens is fictional. The funder report comes first, because that is the deliverable; the record, the device and the protocol follow.
For your Salesforce admin
What it does, and what it does not do
- An instrument library with versions, items, weighted options, reverse-scored items, subscales, and sum, count, mean or custom scoring.
- Three administration modes: staff device with an isolated respondent session for hand-the-device, tokened link, and your own Screen Flow through two invocable actions, one to score and one to finalize.
- An administration record on Contact, Case or Program Engagement with total, subscales, band, the measurement series it belongs to, and change since baseline and since previous.
- Severity band sets and threshold rules as records your organization approves, with a change log. None active at install.
- A platform event per threshold rule with an acknowledgement status, a list of unacknowledged follow-ups, and two Flow templates: open a task, and schedule the next administration.
- A score-over-time component for the record page, and a program outcomes dashboard with a funder export.
- Five permission sets: administer, view, protocol admin, instrument admin, and guest for the tokened link.
What it does not do
- It does not ship licensed instrument text. A licensed instrument is a shell that your organization fills after it records its licence.
- It does not run custom Apex scoring, encounter records, a rater-certification gate, instrument translations or norm-referenced scores.
- It does not diagnose, classify risk or recommend treatment. Bands and cut-points are your organization's protocol.
- It does not ship an active threshold rule. Nothing fires until a named person approves a protocol.
Requires AutoSurvey. The Fraud & Quality Shield checks the quality of every response before it counts.
Instruments and licences
Instruments whose developers require no permission ship with their text.
- No permission requiredPHQ-9, GAD-7, PSC-17. Instruments that need no permission ship with their item text and their developers' attribution on every screen. ACEs ships as an intake and history measure, scored once.
- ShellLicensed instruments. The scoring structure ships as a shell. The item text does not. Your organization records its licence for the edition and language it uses, attaches the evidence, then enters the text.
- YoursCustom instruments. Your own checklist or questionnaire, built in the same library with the same scoring and trend, and labelled custom, not validated.
- Severity bands and cut-points are your organization's configured protocol. Program Outcomes does not diagnose, does not classify risk, and does not recommend treatment. An instrument with a critical item cannot be administered until your response pathway is recorded.
- Answers live in the same objects as every other AutoSurvey response, so one erasure path serves both. Scores purge with the answers they came from.
See it on your own work.
Bring one program and one workflow. We will walk through Program Outcomes with you on that work and answer your questions.
Every person and organization on these screens is fictional.