Pathfinders for Hope · Operation Iron Gate Vallejo Pilot
What Should County Social Services Track After Making a Referral?
County social services referral outcomes should show what happened after a request was sent, not just how many requests staff created. Start with a shared definition of receipt, acceptance, the next action, and the eventual authorized outcome. Keep operational follow-up separate from evidence that a person received a service.
Choose the decision the report needs to support
A daily team queue and a county oversight report serve different purposes. Staff need to know what action is due and who owns it. Managers may need to see response delays, recurring capacity barriers, and incomplete information. Public reporting requires a further privacy review and should not expose individual referral histories.
Begin with a narrow question such as “Which pending referrals need a follow-up today?” or “Where do receiving responses remain unknown?” Do not collect additional personal information just because a dashboard could display it.
County Social Services Referral Outcomes: A Proposed Operational Record
Use a review cadence that keeps unknowns visible
County social services referral outcomes become more useful when teams review them on a predictable schedule. A same day queue can identify a missing acknowledgment. A weekly review can identify referrals that remain under review past the agreed response window. A monthly aggregate can show where unresolved referrals, routing errors, or capacity constraints continue to appear.
Keep each review focused on an operational question. Which referrals need action today? Which records have no authorized update? Which status labels are being used differently by different teams? Which barrier categories require a process change rather than another reminder to staff? A report should help teams decide what to do next, not simply document that work occurred.
Use separate measures for volume, response, and outcome. Volume is the number of referrals sent or received. Response is the time to an authorized acknowledgment or a documented next step. Outcome is the specific result that an authorized source can confirm. Pending and unknown records should remain visible beside completed records so that a favorable percentage does not hide the referrals still waiting for attention.
Before comparing county social services referral outcomes across programs, define the population and time period. State whether duplicate referrals are counted once or more than once. State how transferred cases, withdrawals, and unavailable services are handled. State what counts as a response and what counts as a confirmed outcome. These definitions make a trend interpretable and prevent a dashboard from giving more certainty than the underlying record supports.
Use results to improve the handoff. A recurring wrong destination may call for a routing update. A long review time may call for a clearer status rule. A frequent unknown outcome may show that the follow up owner or check date is not defined. These are process questions. They should be addressed with the organizations responsible for the handoff and within approved privacy and data governance rules.
- Authorized reference: use the identifier permitted in the relevant system, not a person's name in an open report.
- Sending and receiving roles: identify the teams responsible for the handoff within approved access rules.
- Current milestone: distinguish sent, received, under review, accepted for a next step, unable to proceed, and outcome confirmed.
- Action ownership: record the role responsible for the next permitted step and its agreed review point.
- Barrier category: where allowed and useful, separate routing errors, capacity constraints, missing authorized information, and other operational reasons.
- Evidence and uncertainty: show who confirmed a status, when it was updated, and whether the eventual service outcome remains unknown.
These are suggested workflow concepts, not a county reporting mandate or a replacement for required fields. Existing systems may already contain them under different names. Review the design with the appropriate program, data, and privacy leads before adoption. County social services referral outcomes should be interpreted with a documented denominator and a defined follow-up owner. Teams can use county social services referral outcomes to identify operational gaps, not to infer facts outside the record.
Read the numbers without erasing the human context
County social services referral outcomes are most useful when teams can explain what the measure includes and what it leaves unknown. A percentage can show a pattern. It cannot explain why a person chose not to continue, why a service was unavailable, or whether the information in a record is complete. Keep aggregate reporting connected to the operational review that checks whether the next action was actually defined.
Start each report with a short statement of scope. Identify the programs included, the period covered, the type of referral counted, and the status used as the endpoint. A receipt measure may answer whether a receiving team acknowledged a handoff. It does not answer whether the person received a service. A next step may answer whether an assessment or appointment was accepted. It does not establish a later outcome unless an authorized source confirms it.
Use a companion list for records that remain unresolved. Do not bury them in a general closed category. A referral can be administratively closed because a team completed its assigned task while the receiving response, the next step, or the final outcome remains unknown. County social services referral outcomes should retain that uncertainty in the record until there is an authorized update or a documented reason to close the follow-up.
When a trend changes, examine the workflow before drawing a conclusion. A higher unable-to-proceed count may reflect reduced capacity, a corrected routing rule, or a clearer definition. A faster acknowledgment time may reflect an automated technical receipt rather than a staff review. Ask which status changed, who supplied the evidence, and whether the same rule was applied across the period. This keeps comparisons fair and gives managers a basis for a specific improvement.
Use plain definitions in the report itself. Define sent, received, under review, accepted for a next step, unable to proceed, and outcome confirmed. State whether a result is a known fact, an operational status, or an unresolved question. County social services referral outcomes can then support responsible decisions about staffing, routing, partner coordination, and follow-up without overstating what the data proves.
Review privacy before sharing any aggregate. Small counts, combined characteristics, and local context can sometimes make a person identifiable even when names are removed. The appropriate county program, privacy, and data-governance leads should decide what can be shared, with whom, and at what level of detail. The purpose of the report is accountability for the handoff, not exposure of the people seeking support. Review every aggregate with the same care used for individual handoffs. Document the review date, the roles present, the decision made, and the next review point. That record connects a reported pattern to a real, accountable follow-up action.
Do not let a closed task hide an unknown outcome
A staff task may be finished because a message was sent, while the referral remains unresolved. Likewise, a referral may end because the person declined that option; that does not establish a delivered service. Choose labels that distinguish administrative closure from the person's known next step.
When reporting response times, define when the clock starts, which response ends it, how non-working hours are handled, and which referrals are included. An average that excludes every unanswered referral can make a slow process look healthy. Display pending volume alongside response-time statistics.
Review barriers without ranking people
Look for process questions that staff can act on. Is one routing address outdated? Is a partner receiving requests outside its stated scope? Are teams interpreting “accepted” differently? Use findings to improve coordination rather than attaching a blame label to the person seeking support.
Limit access to detailed records according to policy. Before publishing aggregates, have the responsible team assess whether small groups or combined attributes could reveal individuals. A countywide total is not automatically safe simply because names were removed.
Example: two different closure events
Illustrative example: a sending team finishes its clarification task, and the receiving team later confirms an assessment appointment. The county workflow records those as separate events. The appointment is not counted as housing obtained, and an unknown later outcome stays visible instead of being silently removed from the report.
Resources for the next step
Use the measurement guide for a sample calculation and HMIS follow-up planning for system-of-record questions. Where HMIS requirements apply, obtain the current HUD data standards through the local HMIS lead. HUD's Continuum of Care program information provides broader program background. The operational suggestions above do not change those requirements.
Frequently asked question
Should counties count referrals sent as successful outcomes?
No. Referrals sent measure activity. Reports should separately identify authorized receipt, a next step, and the specific service outcome that was confirmed, while keeping pending and unknown outcomes visible.
What a county can report depends on the standard it holds referrals to. See referral accountability for the five conditions and the metrics they make possible.
Operation Iron Gate Vallejo Pilot
Pathfinders for Hope is developing the pilot with organizational partners. Public intake is not open, and no service or placement is guaranteed. Discuss the pilot with Pathfinders for Hope or browse the resource hub.
Prepared by Pathfinders for Hope. Updated September 5, 2026. Resource scope and sources.