Hospital discharge planners search "shelter bed available tonight", street outreach teams text colleagues "any beds open at Crossroads", and people in crisis search "family shelter open near me". The coalition or HMIS system usually knows the answer in real time, but the public web surface is a static directory or a phone tree. The data is fresh inside the coalition's database, but the rendered web pages don't reflect it.

SleekRank reads the coalition's bed-availability feed (an HMIS export, a REST endpoint from the bed-management app, or a Google Sheet that shelter staff update at intake) and maps each shelter to /shelter-availability/{slug}/. Tag mappings handle shelter name and neighborhood. Selector mappings render current bed counts (open beds, total beds, bed type breakdown), intake hours, population served, and a feed-as-of timestamp. List mappings render bed-type detail (single male, single female, family, youth, severe weather) and accessibility features.

Hope House Mission becomes /shelter-availability/hope-house-mission/. The Crossroads Family Shelter becomes /shelter-availability/crossroads-family-east-oakland/. Both pages share one template, one feed, and one cache window short enough to keep bed counts useful, with a visible timestamp so readers know exactly how fresh the number is.

Bed availability is one of the rare datasets where a 30-minute lag changes the outcome. A discharge planner placing a homeless patient at 9pm needs to know whether Hope House has a bed right now, not whether it had one at 5pm. The HMIS or coordinated-entry system usually knows the answer in real time, but the public web surface is a static directory built once a year.

A per-shelter corpus that reads the bed-availability feed on a short cache window, renders the count as crawlable HTML, displays a visible timestamp, and degrades gracefully to a phone CTA when the feed is stale solves the problem at the data layer. The coalition keeps maintaining its bed-availability source for coordinated entry; SleekRank renders the same source as public pages. The downstream impact is measured in beds filled, transport calls saved, and outreach hours redirected to the people who need them.

Every minute of accuracy on a per-shelter page is a person not left in the cold while a worker calls around to find an opening that's been filled for an hour.