Borrow-or-Refer Protocol¶
Routing protocol — instantiates Tool-Repertoire Bias Counterbalancing
Routes a case to borrowed capability, referral, or escalation when the local repertoire cannot fit it, so tool limits never become the boundary of responsibility.
A Borrow-or-Refer Protocol is the standing agreement that when the local toolset does not fit a case, the answer is to reach outside it — borrow a capability, refer to another owner, or escalate — rather than to force the case into whatever the local tools can do. Its defining move is converting a fit failure into an outbound route: it takes a "this doesn't fit us" verdict and turns it into a specific, pre-negotiated hand-off with a named recipient, rather than letting the case dead-end at the edge of what the team happens to own. The protocol carries a lightweight fit gate — enough to decide keep or send — and a wired set of external paths so that sending is a real, frictionless option and not a bureaucratic cliff.
Example¶
A hospital's dermatology clinic owns a set of procedures — biopsies, excisions, cryotherapy — and, like any specialty, tends to see incoming referrals as instances of its own repertoire. A patient arrives with a spreading rash the referring GP labeled "possible eczema." Under the old habit, the clinic would biopsy and treat topically, because that is what it can do.
The Borrow-or-Refer Protocol inserts a keep-or-send gate before the procedure menu opens. The intake dermatologist checks the restated need — "recurrent whole-body rash with joint pain and fatigue" — against the clinic's actual fit, and the pattern reads systemic, not dermatological. Rather than defaulting to a biopsy the clinic can perform, the protocol routes: a same-week rheumatology referral, plus a note borrowing the lab's autoimmune panel the dermatology clinic doesn't order itself. The case leaves the clinic better served than any local tool could have managed. Crucially, the protocol makes the referral the easy path — a pre-agreed slot and template — so that "send" competes fairly with "just biopsy it."
How it works¶
- Run a keep-or-send gate. A deliberately light fit check: does the local repertoire preserve enough of the restated need to legitimately keep the case, or not? The gate is binary in intent — its output is a routing decision, not a fit score.
- Wire the external paths in advance. Borrow (use another team's tool/credential), refer (hand ownership to a better-fit owner), or escalate (raise to someone who can source capability). Each path is pre-negotiated so it is genuinely available under time pressure.
- Guarantee a landing. A referral is not complete until a named recipient has accepted; the protocol forbids "sent into the void" hand-offs.
Tuning parameters¶
- Gate sensitivity — how poor the local fit must be before the case is routed out. Loose triggers over-refer and erode local competence; tight triggers keep misfit cases that should have left.
- Path breadth — how many borrow/refer/escalate destinations are pre-wired. More destinations serve more misfits but cost relationship upkeep and can fragment accountability.
- Hand-off weight — a warm accepted transfer versus a lightweight pointer. Warm hand-offs prevent dropped cases but are slower; light ones are fast but risk the void.
- Reversibility — whether borrowed capability keeps the case local (borrow) or moves ownership entirely (refer). Borrowing preserves continuity; referral gets true expertise but hands away control.
When it helps, and when it misleads¶
Its strength is that it stops tool limits from silently becoming the limit of responsibility — the failure where a case outside the local menu is treated as not-our-problem. It is the archetype's guarantee that "we can't grip this" resolves into "so here is who can," a discipline close in spirit to a clinician's obligation to work within and refer beyond their scope of practice.[n1]
Its failure mode is over-referral: a team that routes every slightly-awkward case outward hollows out its own competence and buries partners in dumped work — the mirror image of forcing everything to fit locally. It can also produce accountability gaps when a hand-off lands nowhere. The guarding discipline is to require an accepting recipient for every route and to feed patterns of frequent referral back as a signal that the local repertoire itself may need to grow.
How it implements the components¶
referral_or_borrowed_tool_path— its core: the pre-wired, guaranteed-landing routes (borrow, refer, escalate) that carry a misfit case to a better-fit owner or capability.tool_fit_gate— the keep-or-send check applies a fit gate, but only to the depth needed to make a routing decision: keep locally, or send outward.
It routes cases and decides keep-or-send, but it does not maintain the standing register of what didn't fit and why — that record of residual cases is non_grippable_residual_register, held by its nearest twin, the Residual Case Log; the log remembers the misfits, this protocol moves them. It also does not score fit across candidate representations (outcome_validity_check, the Representation Fit Scorecard).
Related¶
- Instantiates: Tool-Repertoire Bias Counterbalancing — supplies the outbound path so local tool limits don't cap responsibility.
- Consumes: Residual Case Log surfaces the recurring misfits that need routing.
- Sibling mechanisms: Residual Case Log · Favored-Tool Pause Rule · Representation Fit Scorecard · Alternative-Tool Red Team · Problem-First Intake Template · Tool Repertoire Inventory · Tool-Mismatch Postmortem
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Routes a case to borrowed capability, referral, or escalation when the local repertoire cannot fit it, so tool limits never become the boundary of responsibility, making its operative form a bounded selection, routing, admission, or allocation among eligible alternatives.
Independent corroboration: The frozen evidence defines Borrow-or-Refer Protocol as 'Routes a case to borrowed capability, referral, or escalation when the local repertoire cannot fit it, so tool limits never become the boundary of responsibility', so its operative form is Decision, Gate & Allocation.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Medicine & Healthcare
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Referral when local competence or capability is insufficient is a canonical clinical-care coordination practice.
Related originating lineages:
- Law & Governance — Licensure and scope-of-practice rules formally bound when work must move beyond local competence.
- Organizational & Management Science — Service organizations generalize borrowed capacity, escalation routes, and accepted handoffs while retaining case ownership.
- Public Administration & Policy — Public case-management systems institutionalize referral networks and responsibility for unresolved needs.
Review resolution: The AMA Code makes referral or consultation an explicit professional response when another practitioner has the knowledge and skills a case needs. That canonical scope-of-competence practice makes medicine primary; organizational and public-service handoffs and legal scope rules independently shape the generalized protocol.
Attribution caveat: Clinical referral supplies the clearest named professional practice; the page generalizes it into a borrow-or-refer rule for any capability-limited team.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
- AMA Code of Medical Ethics — Consultation, Referral, and Second Opinions — Authoritative medical ethics guidance directs physicians to consult or refer to professionals with the knowledge, skills, and license required for the needed service.
Notes¶
[n1] Scope of practice — the professional boundary defining what a practitioner is trained, credentialed, and permitted to do, paired with a duty to refer beyond it. The protocol generalizes that borrow-or-refer duty to any team whose repertoire has an edge. ↩