Night-Shift Swap Checklist: 12 Handover Checks | Yihu

Download a blank 12-check administrative worksheet for night-shift roster changes, midnight boundaries and staff acknowledgement. Preview Yihu drafts without a mic; keep patient data in clinical channels.

Download the blank 12-check worksheet ↓

Preview privacy before you try

The linked preview uses preset material, needs no login or microphone, and keeps edits only in the open page. Reloading resets edits. Optional read-aloud uses the browser’s voice service; usage analytics require consent.

Keep private originals in approved tools. In the app, on-device recognition and the destination’s storage, sync and access rules are separate steps. Review the installed version before using a source-described workflow. Read the data-flow guide

US listing verified; availability depends on your storefront. No Mac or self-signing for store installation. Bring your workspace address and account; the optional speech model is about 950 MB.

Verify the swap against the approved roster before drafting the handover; a sent message does not confirm acceptance

After a last-minute night-shift swap, use the hospital’s existing approved system to check the current roster version, full start and end dates and times, role coverage and approval scope. Then prepare only necessary non-patient administrative notes for authorized staff to check through the established process. A chat acknowledgement, transcript or visible phone draft alone cannot establish that the swap took effect or the handover finished. For patient condition, orders, medication or urgent care, use the hospital’s required clinical handover and escalation channels, not this page or Yihu.

Scope: administrative checks after a roster change, not clinical handover

Use this checklist to ask whether the swap was approved, who covers which interval, and which administrative items still need confirmation. With the required permissions and models, Yihu can help prepare speech text, retain voice notes and prepare drafts in compatible workbenches you provide. It is not a hospital rostering, electronic health record, medication-checking, identity-verification or e-signature system. It does not find cover, approve swaps or notify receiving staff automatically.

Check hospital rules and the relevant people’s permission before recording. If recording is not authorized, use an existing approved recording method instead. Do not put patient names, bed numbers, record numbers, conditions, medical images, staff contact details or full rosters into unapproved devices or workbenches. Even with on-device recognition, the destination’s storage, synchronization and access remain separate checks.

Twelve checks after a last-minute shift swap

Check Where to verify Minimum conclusion to retain If still uncertain
Current roster version The hospital’s designated approved roster source Checked version and applicable dates A chat screenshot does not replace the current roster; confirm at the source
Original and revised shifts Original roster and authorized change record Which role and interval changed Do not overwrite the arrangement with the latest spoken message
Midnight boundaries Complete dates, times and applicable time zone in the source Separate start and end dates Clarify “tonight” or “tomorrow morning”; do not infer or convert them yourself
Early or late arrival Approved arrangement and original handover window Coverage interval and any unresolved gap Do not assume the adjacent shift will cover it
Role coverage Existing staffing and role rules Whether required roles have authorized coverage Do not use this checklist to assess credentials or safe staffing ratios; refer to the responsible lead
Swap approval Explicit decision in the established approval channel Authorized version and scope A proposal, forwarded message or “seen” is not approval
Outgoing and receiving staff Actual identity and feedback in an approved channel What each person confirmed administratively Do not confirm for someone else or use voiceprint/name text as identity verification
Open administrative items Original record and accessible item references Item, already agreed owner and agreed time Leave unagreed fields awaiting confirmation; do not infer owners or deadlines
Conflicts and negation Authorized original text and current draft Retain “not yet approved” and “do not swap” restrictions Keep conflicting versions visible rather than choosing the more confident wording
Draft and destination Current approved workbench, account and preview Intended destination and content scope Stop if the destination is unclear or refuses insertion; do not bypass it
Sending and acknowledgement Original sending record and explicitly associated receiving feedback Separate visible draft, sent message and confirmed scope No feedback means awaiting confirmation; a service receipt is not a person taking over
Uncertainty and duplication Original record, request and existing handoff attempt Known step and remaining uncertainty Check the original destination first; do not resend to “complete evidence” or duplicate staffing arrangements

Preparing a draft with Yihu

  1. Check approved records first. Verify the roster version and change reference only within your authorized scope. Ask the responsible person if access is missing; do not borrow accounts or export the full staff list.
  2. Prepare only necessary administrative text. Separate checked arrangements, items awaiting confirmation and the next checking person/channel. Record owners and times only when already agreed. Do not rewrite a suggestion as approval.
  3. Review critical wording. Compare dates, start/end times, roles, quantities and negation. Recording order is not event order, and completed transcription does not establish factual accuracy.
  4. Check the destination and previous attempts. Explicit note insertion is bound to the workbench/page captured when notes opened. Stop and verify if the destination changes. Not every page supports insertion; a visible draft is not a sent message.
  5. Send and acknowledge through the original process. Authorized staff act in hospital-approved tools. Receiving staff confirm only what they actually checked. Leave missing confirmations open; completing a checklist does not create legal acknowledgement.
  6. Stop on uncertain outcomes. Each note retains a one-handoff marker. Failed or uncertain handoffs do not automatically retry or become another staged copy. Check existing destination content before an authorized person chooses the next step. New operations do not prove old ones and may create duplicates.

Direct insertion has a 3,000 Swift Character limit; longer notes use the existing Markdown attachment-staging path. This is not permission to split or rename content to bypass the one-handoff boundary. Staging is not upload, sending, approval or acceptance. Copy and paste can also create copies and duplicates; do not assume everything stays on-device or that deleting one copy retracts all others.

Download the blank checklist

Instructions: /samples/p33-clinical-shift-handover/README.md · English: /samples/p33-clinical-shift-handover/checklist.en.json · 中文:/samples/p33-clinical-shift-handover/checklist.zh.json

This is a blank manual worksheet with no real staff or patient information. It is not a roster import file and does not submit approvals, call hospital systems or save your entries. Before saving a completed copy, check its storage location and access permissions. Reference authorized records without copying sensitive content. Blank fields mean unfilled, not passed, not applicable or complete.

Frequently asked questions

Does a chat reply saying “received” approve a swap?

No. Check whether the established approval covers the current version, role and interval. Sending and receiving feedback are separate. “Received” does not automatically establish approval or actual attendance.

Is a shift name enough when the night shift crosses midnight?

If the interval is unclear, verify the start date, end date, exact times and applicable time zone in the original roster. Do not ask Yihu to guess which date “tonight” means or change roster dates using the phone’s message-receipt time.

Can I record patient handover and pass it to a workbench?

This page does not recommend that use. Patient condition, orders and medication handover belong in the hospital’s required clinical systems and staff processes. This page covers authorized non-patient administrative preparation only, not clinical checking or compliance certification.

Can Yihu swap shifts, fill coverage gaps or verify staff credentials?

This page claims none of those capabilities. Yihu is not a roster or credentialing system; it does not automatically change schedules, approve cover or guarantee staffing. Refer unresolved coverage to the hospital’s designated lead.

Does a draft or service receipt prove the handover finished?

A draft supports only the corresponding visible state. A service receipt supports only its service-record boundary. Actual sending, staff acceptance and subsequent handling each require their own evidence. This checklist is not a new app audit log and provides neither legal certification nor a substitute for actual acknowledgement.

The page reloaded during handover. Should I send again?

Stop and check the original destination and existing records. Reloads or network errors do not prove that the original action never happened. Do not clear markers, change summaries or create requests to manufacture proof of the old action. Urgent matters use the hospital’s established escalation channel.

Continue reading

Voice notes and explicit handoff · Scope of multi-person confirmation · Dates and time zones · Get started · Privacy

Product capability references: current source overview, note handoff boundaries. The earlier handoff description is historical context, not proof of current store-edition features. Check the store and installed version before use; a source merge does not establish installed-version parity.