Loading...
operations

Shelter Bed Inventory and Nightly Occupancy Log

A nightly operations checklist for shelter staff to verify bed availability, record occupancy counts, log turnaways and bed holds, and confirm HMIS data entry — giving directors accurate data for planning and federal reporting.

Trusted by frontline teams 15 years of frontline software

Built for: Nonprofit And Social Services · Government And Public Administration · Healthcare And Human Services

Overview

The Shelter Bed Inventory and Nightly Occupancy Log is a structured nightly checklist designed for emergency shelter operations. It guides on-duty staff through the end-of-night sequence: physically verifying available beds by type, recording the final occupancy count, logging any bed holds for temporarily absent residents, documenting turnaways with reason codes, and confirming that all client data has been entered into HMIS before the shift closes.

Use this template every night the shelter operates, regardless of occupancy level. Low-census nights are just as important to document as overflow nights — funders and CoC leads use the full dataset to calculate utilization rates and justify continued investment. The checklist is especially valuable during Point-in-Time count periods, grant audits, and any night when a licensing or oversight body may request same-day census data.

This template is not the right tool for intake screening, client case notes, or incident reporting — those require separate workflows. It is also not a substitute for HMIS data entry; it is a verification gate that confirms HMIS entry happened. Shelters with multiple buildings or campuses should clone the template and configure one instance per location rather than combining all units into a single checklist, which makes physical verification harder to trace.

A common pitfall is treating this as a paperwork formality rather than an operational control. When staff complete it from memory instead of a physical walk-through, bed hold and turnaway data degrades quickly, and the cumulative reporting errors can create compliance exposure during federal audits.

Standards & compliance context

  • HUD Continuum of Care and Emergency Solutions Grant programs require participating shelters to report nightly bed utilization through HMIS; the HMIS verification step in this checklist supports that obligation.
  • The turnaway log aligns with HUD's requirement to document unmet need, which feeds into CoC system performance metrics and Point-in-Time methodology.
  • Bed hold documentation supports accurate unduplicated client counts, which are required for HUD Annual Performance Report submissions and state-level ESG reporting.
  • Some state licensing bodies require shelters to maintain a nightly census record for a defined retention period — typically two to seven years — making consistent checklist completion part of licensure compliance.
  • Shelters receiving FEMA Emergency Food and Shelter Program funds may be subject to audit of nightly occupancy records; a completed log series provides the documentary evidence auditors request.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

How to use this template

  1. Clone the template and rename it with your shelter name and location so staff can distinguish it from other site instances.
  2. Review each checklist item against your shelter's current bed configuration and intake policies, adding or removing items to match your actual unit types and local reporting requirements.
  3. Assign the nightly DRI — typically the on-duty supervisor — at the start of each shift so responsibility is established before the intake window closes.
  4. At the end of the intake window, complete each item in sequence: conduct a physical walk-through of the sleeping area, record counts by bed type, log any holds and turnaways with reason codes, and verify HMIS entry.
  5. Mark any item that cannot be completed as blocked and add a note explaining the reason — for example, a wing that is temporarily closed — so the record is accurate rather than silent.
  6. At shift handoff, pass the completed log to the incoming supervisor and flag any open items or anomalies that require follow-up before the next nightly cycle.

Best practices

  • Conduct a physical walk-through of every sleeping area before recording bed counts — never estimate from the intake log alone, as late arrivals and informal swaps routinely create discrepancies.
  • Record each turnaway as a separate checklist note with time, reason, and referral destination so the data is usable for grant reporting without additional reconstruction.
  • Treat the HMIS verification step as a blocking item — do not mark the checklist complete until data entry is confirmed, not just assumed.
  • Keep bed hold entries time-stamped with an expected return date so the next shift knows when a held bed becomes available for reassignment.
  • Assign a single template owner — typically the program manager — who reviews the checklist structure quarterly and updates it whenever bed configuration or policy changes.
  • Clone a separate template instance for each physical building or wing rather than combining all units into one checklist, so walk-through accountability is traceable by location.
  • Archive completed nightly logs in a location accessible to the shelter director and data coordinator so discrepancies can be investigated without reconstructing the record from memory.

What this template typically catches

Issues teams running this template most often surface in practice:

Bed count recorded from the intake log rather than a physical walk-through, causing the reported census to differ from the actual floor count
Bed holds not documented, resulting in held beds being reassigned and the original resident losing their placement on return
Turnaways logged as a single aggregate number without reason codes, making the data unusable for grant reporting or capacity planning
HMIS verification step skipped on busy nights, creating a backlog of missing entries that surfaces only during audits
Overflow mats or temporary units omitted from the bed count because they are not part of the permanent bed inventory, understating actual occupancy
Checklist completed by the incoming shift from the outgoing shift's verbal report rather than an independent walk-through, propagating errors across multiple nights
No record of which staff member completed the checklist, making it impossible to follow up on discrepancies after the fact

Common use cases

Emergency Shelter Supervisor — End-of-Night Census Close
The on-duty supervisor uses the checklist to walk each dormitory wing, record final bed counts by type, confirm all holds are logged, and verify HMIS entry before signing off for the night. The completed log becomes the authoritative record for that date's census.
CoC Data Coordinator — HMIS Audit Preparation
A Continuum of Care data coordinator pulls the prior 90 nights of completed logs to reconcile nightly HMIS entries against the physical census records before a HUD monitoring visit, using the checklist archive to identify and correct any gaps.
Shelter Director — Capacity Expansion Justification
A shelter director exports six months of turnaway log data from completed checklists to document unmet demand in a funding proposal, demonstrating consistent overflow on specific nights of the week and supporting a request for additional beds.
Multi-Site Nonprofit — Standardized Nightly Reporting Across Locations
A nonprofit operating three shelter sites clones the template once per location, allowing regional leadership to compare nightly occupancy rates across sites using a consistent data structure rather than reconciling three different ad-hoc formats.
Family Shelter Intake Coordinator — Unit-Type Bed Tracking
An intake coordinator at a family shelter uses a customized version of the template with separate checklist items for single-adult beds, family units, and ADA-accessible rooms, ensuring each category is verified independently and preventing a surplus in one type from masking a shortage in another.

Frequently asked questions

Who is responsible for completing this checklist each night?

The designated nightly DRI is typically the on-duty shelter supervisor or intake coordinator. The template is structured so one staff member can complete it end-to-end, but larger shelters may split HMIS data-entry verification to a separate data-entry clerk. Assign the DRI at shift handoff so accountability is clear before the shift begins.

What time of night should this checklist be run?

Most shelters complete the occupancy count after the final intake window closes — commonly between 10 PM and midnight — so the numbers reflect the true overnight census. If your shelter has a hard lights-out policy, tie checklist completion to that cutoff. Avoid running it mid-evening when late arrivals could change the count.

How does this template support HUD CoC and ESG federal reporting requirements?

HUD Continuum of Care and Emergency Solutions Grant programs require shelters to report nightly bed utilization and unduplicated client counts through HMIS. This checklist includes a verification step confirming that all entries are recorded in HMIS before the shift closes, creating an auditable paper trail that aligns with HUD's bed and unit inventory reporting standards. It does not replace HMIS itself but ensures the data pipeline stays intact nightly.

What is a 'bed hold' and why does the template track it separately?

A bed hold reserves a specific bed for a current resident who is temporarily absent — at a hospital, detox facility, or overnight employment — so the bed is not reassigned. Tracking holds separately from available beds prevents double-counting capacity and ensures the occupancy number reported to funders reflects actual sleeping guests, not theoretical capacity. Failing to log holds is one of the most common sources of census discrepancy.

How should turnaways be documented in this checklist?

Each turnaway entry should capture the approximate time, the reason (no beds available, policy violation, medical referral, etc.), and whether the individual was referred to another shelter or service. This data feeds into Point-in-Time count methodology and helps directors identify patterns — such as consistent overflow on specific nights — that justify capacity expansion requests to funders.

Can this template be adapted for a low-barrier or family shelter with different bed types?

Yes. The checklist items referencing bed counts can be duplicated and relabeled by unit type — single adult beds, family units, ADA-accessible beds, overflow mats — so each category is verified independently. This prevents a common pitfall where a single aggregate count masks a shortage in one specific bed type while another shows surplus.

How does nightly completion of this checklist help with operational planning?

When completed consistently, the log builds a historical dataset that reveals occupancy trends by day of week, season, and local event calendar. Shelter directors can use this data to schedule staffing, pre-position supplies, and negotiate overflow agreements with partner agencies before a crisis night rather than during one.

What is the biggest pitfall teams run into with this type of checklist?

The most common failure is completing the checklist from memory rather than a physical walk-through of the sleeping area. Staff should physically verify each wing or room before marking bed counts — not estimate from the intake log — because late arrivals, no-shows, and informal bed swaps frequently create discrepancies between the intake record and the actual floor count.

Does this template integrate with HMIS software?

The template does not connect directly to HMIS platforms such as Apricot, Clarity, or ServicePoint, but it includes a verification step that prompts staff to confirm HMIS entry is complete before closing the checklist. This makes the checklist a quality-control gate on top of HMIS rather than a replacement for it. Teams can add a link to their HMIS login in the task notes for faster handoff.

How often should the checklist structure itself be reviewed and updated?

Review the checklist items at least quarterly and whenever your shelter changes its bed configuration, intake policy, or funder reporting requirements. A checklist that no longer matches the physical layout or current policy creates compliance risk and erodes staff trust in the process. Assign a specific staff role — typically the program manager — as the template owner responsible for keeping it current.

Go deeper on the topic

Related concepts
  • A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
  • A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
  • A frontline employee app is a phone-first application that gives hourly, field, and deskless workers access to their schedule, pay, announcements, training,...
  • A frontline worker is any employee whose job happens away from a desk — on a production floor, in a patient room, behind a store counter, in a customer's...
Related guides

Ready to use this template?

Get started with MangoApps and use Shelter Bed Inventory and Nightly Occupancy Log with your team — pricing built for small business.

Get Started