A Collaboration Brief

#Describe the problem and proposed use

A collaboration brief is a short document that supports an informed discussion about possible work. It is not proof of readiness or an agreement to proceed. Begin with the problem: who is affected, where the difficulty occurs, what happens now and why the consequences matter to care or service delivery.

Next, describe the proposed approach and its intended use. Identify the users, setting, task and boundaries. Explain what would change in the current workflow and what would remain unchanged. Avoid promotional claims and separate the proposed mechanism of improvement from outcomes that have actually been demonstrated.

#Summarise evidence and practical requirements

Set out the evidence supporting the proposal, including its source, relevance and main limitations. Distinguish published findings, local observations and assumptions. State where benefit, safety or feasibility remains uncertain. If evidence concerns a different population or setting, explain why its applicability needs examination rather than presenting it as directly transferable.

Describe the resources and arrangements that would be required: staff roles, time, systems, data, permissions and oversight. Identify who would own key decisions and how affected people would contribute. Include important dependencies and constraints, such as unresolved access or integration requirements, without implying that approval or capacity is already available.

#Make the next decision explicit

List the questions that need answers before any commitment. Group them around evidence, safety, ethics, operational delivery and responsibility where useful. Propose a proportionate next step, such as clarifying the need or assessing feasibility. Explain what that step would establish and which questions it would leave unanswered.

Close with the decision being requested, the people authorised to make it and the information they still need. Record scope exclusions, possible reasons not to proceed and how the brief will be updated. Use plain language and define necessary technical terms so that readers from different roles can challenge the same assumptions.

#Common misunderstandings

A collaboration brief is not a sales pitch, a clinical recommendation or proof that an approach works. Its purpose is to help people examine a proposed use together, including reasons not to proceed. A clear description of a problem does not establish that the proposed solution is necessary or better than current practice.

Supporting evidence also needs context. Findings from one setting or patient group may not apply elsewhere, and technical performance alone does not establish benefit in care. Practical considerations, such as staff workload, accessibility and responsibility for follow-up, are part of the assessment rather than details to resolve later.

Unresolved questions are not a weakness to hide. Naming them helps collaborators distinguish what is known from what remains uncertain. Likewise, agreement to discuss or explore an idea is not approval to introduce it into care. The brief should make that distinction visible without implying endorsement from anyone involved.

#Questions worth asking a clinician

• What clinical problem does this collaboration brief address, and how does it affect patients?
• How would the proposed approach fit into current care, and who might benefit?
• What evidence supports the proposed approach, and how relevant is it to patients like me?
• What risks, limitations or unanswered questions should we discuss before using this approach?
• How will clinicians and patients help define success and evaluate whether the collaboration improves care?