operations

Perioperative Daily Add-On Case Triage Log

Track same-day add-on surgery requests, urgency classification, and OR slot assignment in one perioperative log. Use it to keep the coordinator, surgeon, and OR desk aligned on what can be scheduled now and what is blocking.

See it in MangoApps Get Started

Trusted by frontline teams 15 years of frontline software

Built for: Hospitals · Ambulatory Surgery Centers · Perioperative Services

Overview

The Perioperative Daily Add-On Case Triage Log is a task template for capturing same-day surgery requests, classifying urgency, and assigning an operating room slot or escalation path. It is built for the perioperative coordinator or OR desk team that needs a single record of what was requested, who owns the next step, and whether the case is blocking the day’s flow.

Use this template when add-on cases arrive outside the planned schedule and must be sorted quickly against staffing, room availability, anesthesia readiness, and clinical priority. It works well for emergency cases, urgent inpatient add-ons, and late-day requests that may fit into a turnover window. The log helps separate normal requests from important or critical ones without inflating priority on every entry.

Do not use it as a substitute for the master OR schedule, a surgical consent record, or a clinical chart. It is also not the right tool for long-range block planning or elective booking. If your site does not need same-day triage, this template will add noise rather than clarity. The value is in making each add-on request independently verifiable, easy to assign, and easy to review after the shift ends.

Standards & compliance context

This template supports documentation discipline consistent with perioperative quality and patient-safety workflows by preserving the triage rationale and assignment trail.
If your organization follows emergency prioritization or surgical scheduling policies, use the local clinical escalation rules to set urgency and slot assignment.
The log should complement, not replace, the medical record, informed consent process, or anesthesia documentation required by your facility.
If the case involves safety-sensitive delays or transfer decisions, record the reason for deferral so the review trail is clear for internal audit.

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. Create a new log entry for each add-on request and record the patient, service line, requesting clinician, and time received.
2. Classify the case urgency as normal, important, or critical based on the documented clinical need and your local escalation rules.
3. Assign a DRI for the next action, such as the perioperative coordinator, charge nurse, anesthesia lead, or surgeon office contact.
4. Record the current OR slot decision, including assigned room, pending slot, deferred status, or blocked status with the reason.
5. Update the entry after each verification step, then close it with the final disposition and any follow-up needed for the next shift.

Best practices

Write each checklist item as a single, independently verifiable action so the coordinator can answer yes, no, or N/A without interpretation.
Keep priority limited to normal, important, and critical so the log reflects real urgency instead of routine noise.
Record the blocking reason separately from the request itself so capacity issues, staffing gaps, and clinical delays are easy to distinguish.
Assign one clear DRI per entry and avoid shared ownership, which slows escalation when the case needs a decision now.
Capture the time of request, time of triage, and time of slot assignment to make handoffs auditable across shifts.
Use a verification step before marking a case scheduled, especially when anesthesia, bed placement, or equipment readiness may still change the plan.
Close out deferred requests with a specific next review point so they do not disappear into an unresolved backlog.

What this template typically catches

Issues teams running this template most often surface in practice:

The request arrives without a clear urgency classification, which delays assignment and creates avoidable back-and-forth.

The log shows a case as scheduled, but the verification step for anesthesia, staffing, or equipment was never completed.

Multiple people act as the DRI, so no one owns the next escalation when the room opens unexpectedly.

Critical priority is overused for routine add-ons, which makes real urgent cases harder to identify.

A case is marked blocked without naming the blocking condition, so the team cannot tell whether the issue is clinical, staffing, or capacity-related.

Deferred cases are left open without a follow-up time, which causes them to be rediscovered late in the day.

Common use cases

Charge Nurse Managing Emergency Orthopedic Add-Ons

A charge nurse uses the log to triage fracture repairs, classify urgency, and assign the next available room while coordinating anesthesia and transport. The record keeps the decision path visible when multiple urgent cases compete for the same slot.

Perioperative Coordinator Handling Late-Day General Surgery Requests

A coordinator logs incoming add-on requests from the surgical office, checks room turnover windows, and marks each case as scheduled, pending, or deferred. This helps the team avoid informal promises that cannot be supported by the actual OR plan.

Ambulatory Surgery Center Reviewing Same-Day Cancellations and Fill-Ins

An ASC team uses the template to capture replacement cases when a scheduled patient cancels and a surgeon wants to fill the gap. The log shows whether the case is blocking, what verification is still needed, and who owns the final call.

Hospital OR Desk Tracking Transfer-Driven Add-Ons

When a patient transfers in with an urgent surgical need, the desk team records the request, urgency, and readiness checks in one place. That makes it easier to coordinate bed status, equipment needs, and room assignment without losing the original request details.

Frequently asked questions

What is this template used for?

This template is used to record add-on surgery requests as they arrive, classify clinical urgency, and assign or defer an operating room slot. It gives the perioperative coordinator a single place to capture who requested the case, what the case needs, and whether it is blocking the day’s schedule. It is especially useful when requests come in by phone, secure message, or hallway conversation and need to be normalized into one triage log.

Is this meant for every scheduled case or only add-ons?

It is for add-on cases only, not the full elective schedule. Use it when a case arrives outside the planned block and must be triaged against current OR capacity, staffing, and clinical urgency. If you need a master schedule or block calendar, that should be a separate template.

Who should run this log?

The perioperative coordinator, charge nurse, or OR desk lead typically owns the log, with the surgeon or anesthesia lead providing clinical input when needed. The DRI should be clear for each entry so there is no ambiguity about who is making the next move. If your site uses a different escalation path, the template can be customized to match it.

How often should it be used?

This is a daily workflow template used whenever add-on requests come in during the operating day. In many facilities, it is updated continuously and reviewed at set checkpoints such as shift change, room turnover, or midday huddles. If your volume is low, you can still keep it open for the full day so nothing is lost between calls.

Does this help with clinical urgency and compliance decisions?

Yes, it creates a consistent record of the urgency classification and the reason a case was accepted, delayed, or declined. That matters when you need to show that triage decisions were based on documented clinical priority rather than informal preference. It is not a substitute for clinical judgment, but it does make the decision trail easier to review.

What are the most common mistakes when using it?

The biggest mistake is logging the request without a clear urgency classification or without naming the DRI for follow-up. Another common issue is treating every add-on as critical, which makes prioritization less useful and can hide true time-sensitive cases. It also helps to record whether the case is blocking or non-blocking so the team knows what must happen before the next assignment.

Can we customize it for our hospital or service line?

Yes, and customization is usually necessary. You can add service line fields, surgeon preference notes, anesthesia requirements, bed status, or transfer source if those affect triage at your site. Keep the core fields intact so the log still supports fast, consistent decisions across different services.

How does this compare with handling add-ons by email or chat?

Email and chat are useful for communication, but they are weak as a system of record because details get buried and decisions are hard to audit later. This template turns those scattered requests into a structured log with a clear status, assignment, and next action. That reduces handoff errors and makes it easier to review what happened during a busy day.

Related templates

Tasks

Surgical Block Time Utilization Monthly Review

Monthly review of surgical block utilization by surgeon and service against release thresholds. U...

Tasks

OR Coordinator Surgical Implant Bill-Only PO Reconciliation

Reconcile bill-only implant usage from surgical cases against purchase orders and chargemaster ch...

Tasks

OR Coordinator Daily Case Posting Reconciliation

Daily reconciliation checklist for OR case postings against surgeon office submissions. Use it to...

Tasks