Loading...
operations

ED Boarding Hours Tracking Log

Track each ED boarding event from admit decision to actual transfer, so you can quantify delay, spot bottlenecks, and escalate capacity issues consistently.

Fill it now — Free Get Started
Customize with AI →

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Hospitals · Emergency Medicine · Health System Operations

Overview

The ED Boarding Hours Tracking Log is a per-patient workplace form for recording the operational milestones of an emergency department boarding event. It captures the admit decision time, bed request time, actual transfer time, calculated boarding minutes, and any escalation to the capacity team. The template also includes fields for delay reason and delay notes so teams can explain why a transfer took longer than expected.

Use this template when your team needs a consistent record of boarding burden across shifts, units, or facilities. It is useful for ED operations, bed management, and quality review because it turns an individual delay into structured data that can be reviewed later. The log is especially helpful when there is a local threshold for when boarding should be escalated.

Do not use this template as a general patient chart or a substitute for clinical documentation. It is not meant to collect broad medical history, diagnosis details, or unnecessary PII. If your workflow only needs aggregate counts, a per-patient log may be more detailed than necessary. Keep the form focused on the minimum necessary fields, and use conditional logic so delay details only appear when a boarding threshold is exceeded.

Standards & compliance context

  • Limit collection to the minimum necessary information and avoid unnecessary PII in line with data minimization principles.
  • If the log is used in a health setting, keep access restricted and use patient identifiers only as needed for operations and audit trail purposes.
  • Use clear field labels, required-vs-optional markers, and accessible validation to support WCAG 2.1 AA usability for staff completing the form.
  • If the form is adapted for employee or patient intake workflows, add disclosure language explaining what happens after submission and who can view the record.

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

What's inside this template

Log Entry Details

This section identifies the boarding event and keeps each record tied to the right date, unit, and admission status.

  • Log Date (required)

    Date the boarding event is being recorded.

  • ED Location or Unit (required)

    Select the emergency department or site where boarding occurred.

  • Patient Record Reference (required)

    Enter the internal patient or encounter reference used by your organization. Do not enter SSN or other unnecessary PII.

  • Admission Status (required)

    Select whether the patient was admitted and boarded in the ED.

Boarding Timepoints

This section captures the timestamps needed to calculate boarding minutes and compare delay patterns consistently.

  • Admit Decision Time (required)

    Time the decision to admit was documented.

  • Bed Request Time (required)

    Time the inpatient bed request was placed.

  • Actual Transfer Time (required)

    Time the patient physically left the ED for the inpatient bed or receiving unit.

  • Boarding Minutes

    Calculated as actual transfer time minus admit decision time.

Delay and Escalation

This section explains why the transfer was delayed and whether the case was escalated for capacity review.

  • Did boarding exceed your escalation threshold?

    Check this if the boarding time met or exceeded the local threshold for escalation.

  • Primary Delay Reason

    Select the main reason for the boarding delay.

  • Delay Notes

    Briefly describe the operational issue if additional context is needed.

  • Escalated to Capacity Team

    Indicate whether the case was escalated for bed management or throughput review.

Review and Submission

This section records who submitted the entry and any notes needed for handoff, validation, or audit trail.

  • Submitter Role (required)

    Select your role for audit trail purposes.

  • Submission Notes

    Optional notes for audit trail or data quality review.

How to use this template

  1. Create one log entry for each boarded patient and enter the log date, facility unit, patient record reference, and admission status.
  2. Record the admit decision time, bed request time, and actual transfer time using the same time standard across all users.
  3. Let the form calculate boarding minutes from the timepoints, or enter the value only if your workflow requires manual verification.
  4. If boarding exceeds your local threshold, mark the threshold field, select the delay reason, and add concise delay notes with the operational cause.
  5. Indicate whether the case was escalated to the capacity team, then submit the form with your role and any review notes needed for handoff or audit.
  6. Review submitted entries on a regular cadence to identify repeated delay patterns and update staffing, bed flow, or escalation rules.

Best practices

  • Use a date picker for log_date and time fields for all timepoints so entries stay consistent and easy to compare.
  • Define the boarding threshold in the form instructions so every submitter applies the same rule.
  • Keep delay_reason as a controlled list with an optional notes field instead of relying on free text alone.
  • Use conditional logic to show delay_notes and escalated_to_capacity_team only when boarding exceeds the threshold.
  • Limit patient_record_reference to the minimum necessary identifier and avoid adding extra PII in submission notes.
  • Standardize whether boarding_minutes is system-calculated or manually entered, and do not mix both methods in the same workflow.
  • Review the log by shift or day so unresolved cases are still fresh enough to validate.

What this template typically catches

Issues teams running this template most often surface in practice:

Missing one of the three core timepoints, which makes boarding_minutes impossible to trust.
Using inconsistent time formats across submitters, which creates false delay patterns in review.
Recording a delay reason without enough notes to explain the operational cause.
Marking every field required, which slows completion and leads to poor-quality entries.
Capturing extra patient details in notes when the log only needs a reference identifier.
Forgetting to mark whether the case was escalated to the capacity team.
Entering transfer time late from memory instead of at the point of transfer.

Common use cases

ED charge nurse shift log
A charge nurse records each boarding event during the shift so unresolved transfers can be handed off cleanly to the next team. The log preserves the timepoints and escalation status without relying on verbal recall.
Bed management capacity review
A bed management coordinator uses the log to review which delays are tied to bed availability, transport, or unit readiness. The structured fields make it easier to compare patterns across services.
Hospital quality and throughput review
An operations analyst uses the entries to identify recurring boarding bottlenecks and prepare a review for leadership. The form keeps the review grounded in actual transfer data rather than anecdotal reports.
Multi-facility transfer coordination
A health system with several facilities uses the facility_unit field to separate boarding patterns by site or unit. That makes it easier to see whether delays are local, systemic, or shift-specific.

Frequently asked questions

What is this template used for?

This template records the key timepoints for a single emergency department boarding event: admit decision, bed request, and actual transfer. It helps teams measure boarding minutes, document delay reasons, and capture whether the case was escalated to the capacity team. Use it when you need a per-patient audit trail rather than a high-level dashboard.

Who should fill out the log?

It is usually completed by ED charge nurses, unit coordinators, bed management staff, or another designated operations role that can verify the timepoints. The submitter should be someone who can confirm the source of each timestamp and add notes about delays. If your workflow spans multiple teams, assign one owner for final submission to avoid duplicate entries.

How often should this log be completed?

Complete one entry for each boarding event as it happens or at the end of the shift while details are still fresh. If you wait until later, boarding minutes and delay reasons become harder to verify. For reporting, teams often review the log daily, weekly, or by shift depending on volume.

What counts as boarding in this log?

Boarding starts after the admit decision is made and continues until the patient is actually transferred to the inpatient bed or receiving unit. The template is designed around those operational milestones, not around triage, registration, or discharge steps. If your organization uses a different definition, adjust the timepoint labels so the log matches your policy.

What should we do if the transfer is delayed?

Use the delay reason and delay notes fields to capture the operational cause, such as bed unavailable, transport delay, isolation needs, or staffing constraints. If the delay crosses your threshold, mark boarding_exceeded_threshold and note whether it was escalated to the capacity team. The goal is to make the delay explainable and reviewable, not just measurable.

Does this template need to follow any privacy rules?

Yes. Because it includes a patient record reference, keep the log limited to the minimum necessary information and avoid adding extra PII in notes. Use your internal patient identifier or reference code rather than free-form identifiers when possible. Limit access to staff who need it for operations, quality review, or escalation.

Can we customize the threshold and fields?

Yes. Most teams customize the boarding threshold to match local policy and may add fields for unit, shift, transport mode, or receiving service. Keep the form lean and use conditional logic so extra delay fields only appear when a threshold is exceeded. That keeps the log easier to use and improves data quality.

How is this better than tracking boarding in email or chat?

Email and chat are hard to search, inconsistent, and usually miss one or more timestamps. A structured log gives you a repeatable field set, cleaner validation, and a usable audit trail for review. It also makes it easier to compare cases and identify recurring bottlenecks across shifts or units.

Related templates

Forms

ED Boarding Hours Tracking Log

Track each ED boarding event with admit decision time, bed request time, transfer time, and delay...
Forms

ED Left Without Being Seen Rate Daily Tracking Log

Track ED left-without-being-seen counts by hour, note likely trigger windows, and record interven...
Forms

Perioperative Daily Add-On Case Triage Log

Perioperative Daily Add-On Case Triage Log template for tracking urgent case requests, triage rat...
Forms

SPD Decontamination Area Daily Log

Use this daily log to record sterile processing decontamination area PPE checks, water temperatur...
Forms

SPD Supervisor Daily Productivity and Turnover Log

Track daily sterile processing output, turnover timing, staffing variance, and follow-up actions ...
Inspections

Active Shooter Run Hide Fight Drill Evaluation

Use this Active Shooter Run Hide Fight Drill Evaluation template to document how staff announce t...
Sop

Code Blue Activation

Code Blue Activation SOP template for cardiopulmonary arrest response, from arrest confirmation t...
Hr Policy

Anti-Harassment & Anti-Discrimination Policy

Anti-Harassment & Anti-Discrimination Policy template for defining prohibited conduct, reporting ...

Go deeper on the topic

Related concepts
  • Standard Operating Procedure
    A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
  • Workforce Management
    Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
  • Daily Huddle
    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...
  • Deskless Worker
    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 —...
Related guides

Ready to use this template?

Get started with MangoApps and use ED Boarding Hours Tracking Log with your team — pricing built for small business.

Get Started
Customize with AI →