Set Equipment Sharing Rules Before the First Urgent Request

The best time to decide who may lend equipment is before another building asks for it urgently. Under pressure, a vague “share when possible” instruction leaves staff negotiating ownership, local reserves and transport on the same call. A small set of operating rules lets them spend that call deciding whether a particular loan can actually work.

Write asset management rules for decisions rather than an exhaustive policy for every imaginable item. The aim is a repeatable path from request to answer. The multi-facility equipment management guide provides the wider operating context; this article focuses on what the two buildings need to agree before making their first move.

Name the people who can say yes

Start by separating a request from an offer. A requester describes the equipment need and the required arrival window. A lending contact confirms whether a specific unit is a candidate. An authorized approver decides whether the building may release it. Those roles may overlap in a small operation, but staff should know when they do.

Build a contact table by role, including backup coverage. For a hypothetical weekend request, the usual maintenance director may be unavailable while an administrator can authorize the loan and a receiving supervisor can accept delivery. A table with only the director's name would turn an otherwise feasible loan into a search for permission.

The central team can maintain the rules and help resolve disputes. Avoid making central approval the default for every routine move unless the operator wants that control and can provide responsive coverage. Authority that exists only during office hours needs an explicit after-hours alternative.

Decide what a request must contain

A request should carry enough information for the lender to make a decision without collecting resident details. Use the equipment category, distinguishing specifications for responsible staff to assess, destination, needed arrival window, expected duration or review date, and the name of the receiving contact.

If the duration is uncertain, say so. An honest review date is better than an invented return promise. If no one is available to receive the delivery, that is a missing condition rather than a reason to send the equipment and hope someone finds it.

A proposed rule card might read:

• The requesting building names a contact who will receive and acknowledge the unit.
• The lending building identifies a specific unit and confirms its local availability.
• Responsible staff resolve permission, suitability, cleaning and maintenance requirements before release.
• Both buildings agree on transport, included accessories and the next review date.
• A named person owns any unresolved exception.

Treat this card as an operator-designed workflow. It does not replace staff judgment or the terms applying to particular equipment.

Protect the right to decline

A sharing program needs a legitimate “no.” A unit can be visible in a storage room yet be held for an anticipated need, awaiting a check, or restricted by ownership terms. Staff should not need to disclose clinical details to explain that it is unavailable.

Use concise reasons such as local reserve, readiness unresolved, permission unresolved, transport unavailable, or no matching unit. Add a useful review time when one exists. Do not turn reason codes into a ranking that penalizes buildings for protecting appropriate local availability.

In a hypothetical example, Building A requests a transfer today. Building B has a visible candidate but cannot confirm readiness until tomorrow. The correct outcome may be a declined transfer for today's window and an agreed follow-up, while Building A uses another authorized option. Leaving the request “pending” without a deadline would be less useful than a clear answer.

Set an escalation that preserves responsibility

Escalation should resolve a specific question. If the dispute concerns a protected reserve, involve the operator's designated reserve owner. If it concerns equipment compatibility, send it to the responsible clinical or technical staff. If it concerns transport, ask the logistics owner to establish a feasible plan.

A regional operations leader should not be asked to provide clinical clearance simply because they are the most senior person on the call. Naming a decision owner means matching the person to the question.

Agree how to handle an unanswered request as well. A requesting building needs an approved alternative when its response window expires. Do not make repeated unanswered calls a prerequisite to obtaining necessary equipment through the operator's usual process.

Review rules using actual exceptions

At the first review, ask which requests required extra calls and why. A missing backup contact suggests a coverage change. Repeated transport failures suggest a narrower sharing region. A category with unresolved terms may need to stay outside the pool until the authorized owner resolves them.

Cross-building visibility can make equipment candidates easier to identify. Norra's room-level equipment visibility supports that discovery, while lending permission and acceptance remain human decisions. Rules become useful when staff know what to do after finding a candidate, including when the right answer is to leave it where it is.