ONGOING INVESTIGATION • Public-records evidence dossier • San Francisco

The HSH Transparency Record

A source-first examination of HSH public records, supportive-housing service design, the DPH→HSH transition, caseloads, resident autonomy, street-response records, Critical Incident Reports, and SOTF File 25134.

LAST UPDATED: SEPTEMBER 23, 2026

ONGOING INVESTIGATION: This page is updated as additional public records, SOTF proceedings, audio archives and agency responses become available. Conclusions and evidence labels may be revised when new material changes the record.
Method: This project does not assume that an unavailable record was improperly withheld. It documents what was requested, what was produced, what SOTF found, what participants alleged, and what remains unresolved. Written materials have been reviewed; relevant audio archives have not yet been systematically scanned or transcribed.

Evidence status

Verified documentary record

Known knowns

Official SOTF materials establish the complaint, committee proceedings, March 4 findings, Order of Determination, reconsideration process, and the existence of substantial HSH productions.

Documented allegation

Claims requiring separation

Cantarutti's submissions identify specific records he contends remained outstanding and raise the public visibility of completed requests in NextRequest. These claims are evidence in the proceeding, not automatically SOTF findings.

Unresolved

Known unknowns

Questions remain about particular logs, communications, SMS/MMS content, withholding explanations, publication status, and the final disposition of the June 3 reconsideration hearing.

Unreviewed evidence

SOTF audio archives

Audio from June 3 and potentially relevant earlier proceedings has been located but not systematically reviewed or transcribed. It may resolve some questions that the written packets do not.

From DPH to HSH: what changed in 2016?

HSH did not begin with a blank slate. San Francisco created the department by bringing together homelessness programs, staff and resources that had previously sat in several City agencies. HSH's own strategic framework says the department was launched in 2016 to unite those functions, and defines Direct Access to Housing (DAH) as a low-threshold permanent supportive housing program started by DPH and later managed by HSH.

Before 2016
DPH Housing & Urban Health / DAH
→
2016 reorganization
DAH housing administration moves to HSH
→
After 2016
HSH housing + supportive services; DPH remains a clinical partner
Documented

DAH was a health-centered housing model

City records describe DAH as serving people experiencing homelessness with complex medical, mental-health and/or substance-use diagnoses. Contemporary DPH material shows Health Worker III case managers working in supportive housing as part of an interdisciplinary health-care team.

Documented

The DAH function moved

HSH's strategic framework describes DAH as having been started by DPH and then managed by HSH. A later City housing-finance document states directly that the new department consolidated DPH's DAH functions with HSA Housing & Homeless programs.

Continuity

The six former-DAH hotels

Pre-HSH DPH records place Health Worker/social-work classifications in a six-hotel group that includes Star, Camelot, Empress, Le Nain, Pacific Bay Inn and Windsor. DISH's history independently identifies those same six as the original DPH supportive-housing portfolio it managed in 2006–07.

Still being reconstructed

Which positions moved?

The exact position-by-position transfer remains an open research task. The record already establishes that DAH moved to HSH and that health-oriented classifications appeared in HSH's early staffing, but this project will not assume that every pre-2016 DPH position transferred without a contemporaneous crosswalk.

Working question: When DAH administration moved from DPH to HSH, which elements of the original health-centered supportive-housing model moved with it, which remained in DPH, and how were the resulting institutional boundaries later bridged?

Caseloads: the ratio on paper is only the beginning

Caseload has become a recurring HSH oversight issue because a contractual staffing ratio does not by itself establish the amount or type of service residents actually receive. City documents show changing service-intensity targets and, importantly, distinguish ordinary case-management staffing from the additional clinical capacity needed for residents with higher acuity.

1:25

Adult PSH enhancement target

HSH reported investments intended to lower adult PSH case-management ratios to approximately one case manager for 25 tenants.

1:20

Family / TAY and newer HSH planning

HSH reported a maximum 1:20 target for TAY and family PSH. A 2024 City financing document also states that HSH's then-current services ratio was 1:20 for the PSH project being underwritten, while the underlying RFQ had specified 1:25.

A ratio is not a service-frequency requirement. A 1:20 or 1:25 caseload describes assigned workload. It does not establish whether every resident must be contacted weekly, monthly or according to assessed need. Nor does it show whether funded positions were filled.

The February 2024 HSH/provider presentation to the Homelessness Oversight Commission identifies inability to recruit, retain and right-size staffing as a housing-stability challenge. It also identifies needs beyond ordinary case management, including onsite licensed clinicians, harm-reduction specialists, peer staff and additional front-desk capacity. The same presentation describes PHACS, site-based nursing and other DPH services as clinical resources operating within PSH.

Funded ≠ filled

A contract can fund enough positions to satisfy a ratio while vacancies increase the caseload carried by staff actually working. Where records permit, this project will distinguish funded FTE → required FTE → filled FTE → actual caseload.

Case management ≠ clinical capacity

A building can meet its case-management ratio and still require nursing, behavioral-health, substance-use or other clinical services. PHACS and other DPH overlays are therefore tracked separately rather than counted as ordinary HSH case management.

Resident autonomy and voluntary services

HSH and supportive-housing providers themselves identify “balancing resident autonomy and voluntary services” as a challenge in PSH. That makes autonomy an operational and records question—not merely a philosophical one. A resident may decline a particular service while remaining housed and engaged in other ways; unsuccessful contact, an unavailable service and an explicit refusal are different factual states.

Contact attempted
→
Contact made
→
Need identified
→
Service offered
→
Accepted / declined / no response
→
Referral / delivery / follow-up
A resident's right to decline a service does not, by itself, explain why a service was not received.
Different state

Offered and declined

The record establishes that contact occurred, an identifiable service was offered, and the resident chose not to accept that service at that time.

Different state

No response / unsuccessful contact

This does not establish refusal. It may mean the resident could not be reached or did not respond to that attempt.

Different state

Accepted but unavailable

A resident may want assistance while a referral, appointment, bed, clinical service or staff resource is unavailable or pending.

Different state

No documented attempt

Absence of a documented service cannot automatically be translated into resident choice. The underlying case record, referral system and provider documentation matter.

Evidence rule for this project: do not silently translate “no service” into “refused service,” and do not translate “refused service” into “system failure.” Where possible, preserve the actual disposition: attempted contact, successful contact, offer, acceptance/refusal, availability, referral, delivery, follow-up and outcome.

File 25134 — working chronology

Complaint filed

File 25134: Minh Cantarutti v. Department of Homelessness and Supportive Housing.

Committee proceedings

The Education, Outreach & Training Committee considered jurisdiction and recommended Sunshine Ordinance findings.

SOTF finding

The full Task Force voted 10–0 finding violations of §§ 67.21, 67.26 and 67.27.

Order and reconsideration

The Order of Determination was approved; a reconsideration request followed and was granted.

Reconsideration hearing

File 25134 appeared as Item 14 with an approximately 80-page packet. Final disposition remains to be confirmed through minutes/transcript/audio review.

The requests inside the dispute

RequestWhat the current record indicatesStatus
#25-10128City mobile-device records connected to Jan. 17–18, 2024 activity. The packet describes call/text logs, an MDM screenshot and revised/redaction-log materials.Further records alleged
#26-105Pedro Rincon / San Bruno Avenue records. The June packet describes an HSH production of roughly 55 documents, including operational/outreach materials.Production documented
#26-134Supplemental request concerning text-message content, voicemail material, archived communications and related records.Completeness unresolved

Note: the June materials appear to contain an inconsistency concerning which request is described as “controlling.” This dossier preserves that ambiguity pending verification against the original request chain.

Questions another researcher can test

Records completeness

Did the identified phone/text records, SF HEART Touchpoint/activity records, field documentation, schedules/duty rosters, Encampment Master Log entries, and inter-agency communications exist? If so, were they searched, retained, produced, or withheld?

NextRequest publication

Why did public-facing request pages appear to show records as unavailable while HSH represented that responsive documents had been released through NextRequest? Was this configuration, publication status, later removal, or something else?

Withholding and redactions

What exemption-by-exemption explanations or responsive-record logs were supplied, and do they account for each category identified by the requester?

June 3 outcome

What did SOTF ultimately decide after granting reconsideration? The audio and final minutes/transcript should be checked before drawing conclusions.

What could be mapped — and what is missing?

The public-interest question is larger than any single records request: can San Francisco's street-response activity be followed geographically from an initial call or observation, through outreach and encampment operations, into shelter or service linkage, and—where applicable—to a later critical incident? City materials show that HEART reports include neighborhood-segmented call volume, dispositions/outcomes and response times; HSOC coordinates multi-agency encampment operations and uses shared operational data. That makes a reproducible map conceivable, but not yet complete.

Layer 1 • documented

HEART street response

Potential fields: neighborhood/geography, 311/911 source, ticket type, response, needs assessment, disposition/outcome, response time, requests for assistance.

City documentation says HEART monthly reporting aggregates these measures and segments information by neighborhood.

Layer 2 • documented

HSOC / ERT operations

Potential fields: encampment location, operational schedule, outreach activity, shelter resources/offers, partner-agency activity, resolution activity and follow-up.

HSOC materials describe coordinated call intake, shared data, encampment assessment, scheduling and multi-agency field operations.

Layer 3 • incomplete

Service pathway

Research question: can street contacts be reliably linked to subsequent outreach, referrals, shelter offers, placements or other services without conflating different people or events?

Linkage requires compatible identifiers, dates, locations and definitions. The existence of separate datasets does not establish that they can safely or reliably be joined.

Layer 4 • currently missing

Critical Incident Reports

Potential downstream layer: where a qualifying serious incident later occurs in the homelessness-response system, CIR information could provide an outcome/safety layer. Whether CIR data can actually be linked to HEART/HSOC/service records remains an open evidentiary question.

The dossier should not imply that every street contact leads to a CIR, or that CIRs necessarily contain fields permitting person-level or event-level linkage.

Conceptual chain to test

311 / 911 / observation → HEART / HSOC response → outreach / encampment operation → referral / shelter / service pathway → critical incident, if one occurs → outcome

The missing-link question: Which fields allow these stages to be connected, and which records are unavailable, unverified, withheld, or simply maintained in incompatible systems?

Why this matters for mapping: without the missing or inaccessible layers, a public map could show where calls and operations occurred while still being unable to test what happened afterward. The gap itself should be displayed rather than filled with assumptions.

Unreviewed evidence: audio

“There are known knowns… there are known unknowns… [and] unknown unknowns.”
— Donald Rumsfeld, 2002. Included here as an organizing metaphor, not evidence in the case.

The audio archive is a priority because testimony and member questioning may establish facts that are invisible in the written packet. Until that work is complete, “not found in the packet” should not be read as “not in the SOTF record.”

Related transparency record

This investigation can be expanded carefully beyond File 25134. Candidate strands include the Civil Grand Jury's findings concerning HSH and the history of requests for HSH Critical Incident Reports, including interactions involving the Mayor's Office. Those connections should be added only after the underlying primary documents are assembled and sourced.

Next research phase

Build the cross-case chronology

HSH → SOTF → Civil Grand Jury → Critical Incident Reports → Mayor's Office. Each assertion should link to its primary source, with agency positions, complainant allegations and official findings visually distinguished.

SOTF File 25134 — direct record links

These links go directly to the official SOTF materials used in the working chronology. They are also embedded into the relevant dates elsewhere on this page.

ProceedingOfficial recordWhy it matters
Jan. 27, 2026 — Education, Outreach & Training CommitteeOPEN ITEM 5 PACKET ↗Contains HSH's Jan. 8 response and the underlying #25-10128 request; committee-stage record for File 25134.
Mar. 4, 2026 — full Sunshine Ordinance Task ForceOPEN ITEM 11 PACKET ↗Official File 25134 complaint packet for the full Task Force proceeding.
June 3, 2026 — reconsideration / Item 14OPEN ITEM 14 PACKET ↗Reconsideration materials, later submissions and supporting records.

Additional direct links—Order of Determination, May 6 reconsideration record, meeting minutes and audio—will be added here as each official source is verified.

Primary source library

This section is the beginning of the dossier's permanent source index. Wherever possible, later versions will link individual claims to the exact underlying document, page, audio segment, request page or agency response.

SourceWhat it establishesLink
SOTF File 25134 — June 3, 2026 Item 14 packetComplaint summary, procedural history, reconsideration materials, HSH/requester submissions and supporting documents.VIEW OFFICIAL PDF ↗
City announcement launching HEART — May 30, 2023HEART mission, 311/911 role, service-linkage functions and planned monthly reporting, including neighborhood segmentation.VIEW SF.GOV ↗
Coordinated Response Division annual reportOperational context for HEART and HSOC, including call categories, outreach/service linkage and HSOC shelter-preference data.VIEW OFFICIAL PDF ↗
HSH Five-Year Strategic FrameworkHSH creation; DAH described as a DPH-created low-threshold PSH program later managed by HSH.VIEW OFFICIAL PDF ↗
DPH / Civil Service Commission packet — 2012–13Contemporaneous Health Worker III role at Star Hotel; interdisciplinary HUH case management and historical staffing evidence.VIEW OFFICIAL PDF ↗
HOC — Building Greater Stability in Permanent Supportive HousingPSH acuity, staffing challenges, service-enhancement ratios, resident autonomy/voluntary services, PHACS and other clinical supports.VIEW OFFICIAL PDF ↗
HSH OCOH implementation update — Feb. 2023Case-management enhancement investments and 1:25 adult / maximum 1:20 TAY-family targets.VIEW OFFICIAL PDF ↗
1979 Mission service-plan evaluation — May 2024States an HSH 1:20 service ratio for the project while noting the underlying RFQ's 1:25 requirement.VIEW OFFICIAL PDF ↗

Source links point to the original City-hosted material. More sources will be added as each part of the evidence record is verified.

Update log

DateChange
Sept. 23, 2026Added DPH→HSH/DAH institutional history, six-building continuity, PSH caseload and clinical-capacity framework, resident-autonomy/voluntary-services section, and supporting primary-source links.
Sept. 22, 2026Established permanent ongoing-dossier format; added evidence-status framework, File 25134 chronology, request map, HEART/HSOC/service/CIR mapping framework, primary-source library and update log.

Future revisions replace this same HTML file. The public URL can therefore remain unchanged while the evidence record develops.