Communication between the operating room and sterile processing works best when both teams can act on the same information. “We need it soon” and “we are working on it” may be true, but neither statement explains what is needed, what is ready, or who will provide the next update.
A useful OR-SPD handoff identifies the item, the current status, the unresolved need, and the person responsible for the next action. It gives each department information it can use without turning every request into a series of repeated calls.
This article offers a practical communication structure for local adaptation. It does not change clinical decision-making authority, processing requirements, or the facility's escalation procedures.
Why information quality matters across departments
The OR and SPD see different parts of the same workflow. One team may be thinking about a scheduled procedure while the other is resolving an item discrepancy or waiting for a required process to finish.
Neither view is complete by itself. A productive conversation connects them with specific facts.
AHRQ's TeamSTEPPS handoff tool emphasizes transferring information and responsibility, with an opportunity to clarify and confirm. Applied to OR-SPD work, that means a request should have a receiving owner and an understood next action.
The goal is not a longer message. It is a message that reduces uncertainty for the person receiving it.
Begin with a shared description of the item
Departments sometimes use different names for the same set, device, or service. Before discussing urgency, confirm what is being requested through the facility's approved identifiers.
A nickname can be convenient inside one team and ambiguous outside it. When several similar items exist, include the detail needed to distinguish them.
If the request remains unclear, resolve identification first. Repeating a completion estimate for the wrong item does not help either department.
Leaders can support this by maintaining consistent naming in the systems both teams use. A communication problem may begin in a preference card, inventory record, or informal list rather than in the conversation itself.
Define useful status language together
Words such as “done,” “ready,” and “almost” can mean different things. SPD may be referring to one processing stage while the receiving team interprets the same word as authorization for use.
Agree on status descriptions that match the approved workflow. Identify which status means the required release process is complete and which statuses still involve unresolved work.
Do not create a parallel status system in a personal spreadsheet if the organization already has a controlled tracking process. Clarify the existing system with the people responsible for it.
Use training examples to test the language. Ask staff from both departments what they would do after receiving each message. Different interpretations are a signal that the wording needs work.
A five-part handoff structure
The following is an original communication template. Adapt it through local policy and keep patient information inside authorized systems.
| Part | Question to answer |
|---|---|
| Item | Which set or device are we discussing? |
| Need | What does the receiving team need to know or decide? |
| Status | What is confirmed about the item's current condition in the workflow? |
| Dependency | What must happen before the next status can be confirmed? |
| Owner and update | Who is responsible, and when will another update occur? |
This structure separates a requested time from a confirmed status. It also gives staff a way to communicate uncertainty honestly.
For example, an estimated update time can be useful even when a completion time is not yet known. The key is to label the estimate accurately and deliver the promised update.
Use a check-back for consequential messages
AHRQ describes check-back as a closed-loop exchange: the receiver repeats the message and the sender verifies that it was understood. In a busy department, this can be adapted to confirm the requested item, current status, and next action.
A check-back should be brief. It is not necessary to repeat every sentence of a routine conversation.
Use it when misunderstanding would affect an assignment, escalation, or planning decision. The sender should correct any mismatch immediately rather than assuming the receiver will infer the intended meaning.
The point is shared understanding, not a scripted performance. Train the skill with realistic examples so staff can use it naturally.
Hypothetical example: an urgent set request
An OR staff member requests a set for an upcoming case. SPD confirms the exact set, but an unresolved discrepancy prevents the team from giving a reliable completion time.
A useful message might read:
Training example: The requested set is identified. A discrepancy is under review, so readiness is not yet confirmed. The SPD lead owns the follow-up and will update the OR coordinator at the agreed time. Please use the clinical escalation process for any scheduling decision.
The receiving person confirms the set and understands that the update time is not a promise of release. The authorized teams then handle any clinical planning or alternative arrangements.
This example is intentionally about information, not a workaround. Urgency does not change the device's required processing or release criteria.
Make incoming handoffs useful too
Communication should not flow only from SPD to the OR. Information arriving with used items, changed requests, or unusual circumstances can affect what the receiving team needs to do next.
Ask both departments which information the approved process requires and how it should be transmitted. Identify the owner for missing or unclear information.
Do not ask staff to reconstruct important details from memory at the end of a shift if the information can be recorded appropriately when the event occurs. Use the authorized system and protect patient privacy.
Review one real workflow together without turning the meeting into a debate about which department causes more problems. The useful question is where information stops moving reliably.
Build a predictable route for changes
Case schedules, priorities, equipment availability, and assignments can change. Decide how those changes reach the people who need them and who acknowledges receipt.
A message sent to one person's phone may not reach the covering staff member. A change mentioned in a meeting may not reach the evening shift. These are routing problems that a clearer process can address.
Use a designated role or approved channel where practical, with a backup for absence or downtime. The handoff should not depend on knowing which individual happens to be available.
When a change alters a previous estimate, update the affected team promptly. Explain the new information and the next action rather than silently allowing an outdated expectation to stand.
Keep the escalation path visible
Staff should know which concerns they can resolve directly and which need a supervisor, educator, infection prevention specialist, or clinical leader.
Publish the approved escalation route in a usable location. Include coverage for off-hours and situations where the first contact is unavailable.
Practice an example during orientation: a request is unclear, status cannot be confirmed, or an urgent disagreement remains unresolved. Ask staff to show who they contact and how they record the outcome.
The purpose is timely resolution. Escalation should not require a person to become more confrontational before the system responds.
Reduce repeated status calls by improving visibility
Repeated calls can indicate that colleagues do not trust or cannot access the current information. Before telling people to stop calling, investigate what they are missing.
Check whether the tracking system is updated at meaningful points, whether terms are understood, and whether the receiving team knows when another update will occur.
If a new communication routine is introduced, measure whether it reduces uncertainty rather than only counting fewer calls. Calls may decrease because information improved, or because staff stopped asking questions. Those are different outcomes.
Ask both departments for feedback. A process that saves SPD time by shifting confusion to the OR has not solved the shared problem.
Debrief the process after a difficult handoff
Choose a specific event and reconstruct the information available at each point. Keep the discussion factual and follow the organization's quality and privacy procedures.
Ask what each person understood, which message changed the plan, and where an assumption entered the conversation. Identify the earliest point where a clearer exchange could have helped.
Then agree on one correction. It might be a naming change, a required field, a backup contact, or a clearer distinction between an estimate and a confirmed status.
Avoid ending with “communicate better.” That phrase does not tell anyone what to do differently tomorrow.
Give SPD input before new work arrives
Some handoff problems begin well before the day of a procedure. Equipment purchases, new services, inventory changes, and scheduling decisions can introduce requirements that the processing team has not had an opportunity to evaluate.
Healthcare Purchasing News's reporting on SPD participation in hospital decisions highlights firsthand concerns about excluding processing expertise. The local action is to identify which planning decisions need SPD involvement and establish a route for that input.
Ask for a concrete place in the workflow: review before purchase, notice before a new service, or an agreed discussion of processing capacity. A defined contribution is easier to sustain than a general request to be included more often.
Try a small communication improvement
Choose one recurring handoff, such as an unresolved set question or a shift-to-shift status update. Define the information both sides need and test an approved template over a limited period.
Before starting, decide what you will observe. Useful questions include whether the item was clearly identified, whether responsibility was acknowledged, and whether the promised update occurred.
Review the findings with both teams. Keep the parts that helped and simplify the parts that created extra work without improving understanding.
This is a suggested improvement method, not a required timetable or a claim that one template can resolve every OR-SPD relationship problem.
Teach students how to ask a clear question
New technicians may hesitate because they do not want to interrupt an experienced colleague. Give them a simple structure: what item they are discussing, what they know, what remains unclear, and what help they need.
Practice with fictional examples. Have the listener explain what they understood and what information was missing.
The exercise teaches precision without expecting the student to make decisions beyond their training. It also helps the preceptor see whether the learner can distinguish a fact from an assumption.
For more on developing that foundation, read what makes a great sterile processing instructor.
Make the backup channel part of the agreement
Electronic tracking and messaging systems can become unavailable. Ask how each department will communicate during an outage and which record will preserve the decisions made during that period.
Use the organization's approved downtime process. A private messaging group created in the moment can leave the next shift without access to important updates.
When the system returns, identify who reconciles outstanding requests and confirms which estimates or statuses remain current. The end of an outage does not automatically close the work created during it.
Practice this handoff in a brief tabletop discussion. The exercise should reveal missing ownership and access questions before staff have to solve them under time pressure.
Frequently asked questions
What is the most important part of an OR-SPD handoff?
Shared understanding of the item, current status, and next responsible action. The details vary, but neither side should leave the exchange relying on an unspoken assumption.
Should every message include a completion time?
Only communicate an estimate you have a basis for, and label it as an estimate. When readiness cannot be predicted, agree on an update time and explain the unresolved dependency.
Can urgency justify bypassing required processing?
No. Use the approved escalation process to address the operational or clinical planning problem. Communication should make constraints clear, not hide them.
What if another department uses different terminology?
Compare definitions using concrete examples and agree on language that matches the authorized workflow. Update the relevant references through the responsible owner.
How can leaders tell whether the change worked?
Review the quality of the information, acknowledgment of responsibility, and follow-through. Include feedback from both departments rather than relying on a single volume measure.
Make the next handoff specific
You can begin with one habit: before ending a consequential conversation, confirm who owns the next action and when another update is expected. That small change makes responsibility visible.
For teams exploring help with education or department workflows, contact Aseptic Technical Solutions about consulting. Bring one recurring communication problem and the steps you have already tried so the discussion can focus on a practical next move.
