Post-Acute Placement Coordination Log

This template tracks each post-acute referral from submission through acceptance, denial, or placement, along with payor status and any delay reason. It is meant to give care coordinators a single place to record the current state of a discharge placement. Use it to follow skilled nursing, rehab, long-term care, home health, or other post-acute options. It is not a clinical charting template; it is an operations log for care transitions.

Use it whenever a patient needs a post-acute placement decision and the discharge plan depends on outside facility acceptance or insurance review. It is especially useful when multiple referrals are sent, responses are pending, or the discharge date is blocked by placement delays. If the patient is going home with no placement coordination needed, this log is usually unnecessary. It is also less useful for one-off, fully confirmed transfers with no follow-up work.

A care coordinator, case manager, discharge planner, or utilization review lead should usually own the log. The DRI should be clear so one person is accountable for updating referral status, following up on blockers, and closing the loop when placement is confirmed. Other contributors, such as social work, nursing, or payer liaison staff, can add updates as needed. The key is that ownership stays explicit so items do not sit in a non-blocking state without action.

Update it as soon as a referral is sent, a facility responds, a payor decision changes, or a delay is identified. In active discharge planning, the log should be reviewed at least daily and often more frequently for critical cases. If your team uses a Kanban-style workflow, keep the number of active pending placements visible so work does not pile up unnoticed. The recurrence is operational rather than fixed; the template is designed for continuous tracking until placement is resolved.

A common mistake is logging vague status updates like 'waiting' without naming the blocker, the next follow-up step, or the current DRI. Another issue is mixing unrelated clinical notes into the log, which makes it harder to see the placement workflow. Teams also sometimes mark every item as critical, which hides the truly urgent cases. The best logs keep each checklist item or task atomic, independently verifiable, and tied to a clear next action.

Yes. You can add fields or task types for facility name, referral date, payor authorization status, bed availability, transport needs, and expected discharge date. Many teams also customize it by service line, such as SNF, inpatient rehab, behavioral health, or home health. Keep the core workflow intact so the log still shows referral, acceptance, delay, and closure clearly. Customization should improve visibility, not turn the template into a catch-all note dump.

No. This template is best used as an operational coordination layer, not as a replacement for the EHR, referral platform, or payer portal. It helps the team see the status of placement work across systems and identify what still needs action. If you integrate it with your existing tools, use it to mirror the current state and surface blockers, not to duplicate every document. The value is in coordination and follow-through.

Ad-hoc follow-up is easy to start but hard to audit, prioritize, and hand off. A structured log makes pending referrals visible, clarifies who owns the next step, and reduces the chance that a placement delay gets lost in a message thread. It also makes it easier to spot patterns such as repeated payor denials or facilities that respond slowly. If your team needs repeatable discharge coordination, a template is much easier to manage than scattered messages.