University–Industry Collaboration: Defining Problems, Responsibilities and Deliverables

Begin with a problem both partners can describe

A useful collaboration starts with a shared account of the problem and the value of investigating it. An institution may seek new knowledge and student learning, while an industry partner may seek a better process or evidence for a product decision. These purposes can coexist, but they should be stated openly.

Write a short problem statement covering the current situation, the unanswered question, relevant users and the decision that the research might inform. Identify what is outside scope. If the company requires a routine service with a predetermined specification, discuss whether a service agreement is more appropriate than describing the activity as collaborative research.

Assess feasibility before promising outcomes

Check whether the necessary expertise, facilities, information and time are available. Ask which assumptions must hold for the project to proceed. Access to company data, specialist equipment or field sites should be confirmed through the appropriate institutional process.

Distinguish an intended research outcome from a guaranteed commercial result. Research may establish that a proposed solution is ineffective or infeasible. A credible plan explains how such findings will be evaluated and used, without promising a product, patent or market benefit that the study cannot ensure.

Make roles and contributions specific

Identify who will lead the research, supply materials, maintain equipment, recruit participants, analyse data and review outputs. Specify staff time and in-kind contributions alongside financial support. Clarify what happens if a promised resource becomes unavailable.

Establish a small governance arrangement with named contacts, a review schedule and a route for escalating disagreements. Institutional signatories should have the necessary authority. A researcher's enthusiasm or an informal exchange of emails should not substitute for an approved commitment where an agreement is required.

WIPO describes collaboration agreements as instruments for clarifying the objectives and responsibilities of parties involved in joint work, including relevant intellectual property arrangements. The exact agreement should reflect the actual project and institutional circumstances. ^[1]

Define deliverables and review criteria

Describe each deliverable in a form that can be reviewed: a technical report, validated dataset, prototype specification or training resource. State the expected content, limitations and review process. Avoid treating every draft as a completed output or every disagreement as a failure to deliver.

For an exploratory study, acceptance may depend on completing the agreed methods and explaining the findings accurately. It should not require the evidence to support a preferred answer. Plan how feedback will be consolidated and how substantial changes will affect cost, schedule and scope.

Discuss publication, data and intellectual property early

Identify existing materials each party brings into the project and the permissions needed to use them. Discuss ownership and use of new outputs, confidentiality, publication review, attribution and potential commercialisation. Address the position of students and external contributors explicitly.

These matters depend on applicable law, institutional policy and negotiated terms. The UK Lambert guidance offers models for university–business collaboration but is designed for English law; its wording should not be treated as a ready-made agreement for another jurisdiction. ^[2] Obtain qualified review for the actual agreement.

Data permission is a separate practical question. A partner's ability to provide a dataset does not by itself establish that every proposed research use or onward disclosure is permitted. Confirm relevant permissions, security arrangements and research ethics requirements before access begins.

Test the plan with an illustrative scenario

Imagine an education institution and a software company proposing a study of a learning platform. The company wants information about use, while the researchers want to investigate how students interpret feedback. Before collecting data, the partners should agree the study questions, participant arrangements, access controls and reporting boundaries.

They should also decide how findings that are commercially inconvenient will be handled. An agreed review process can address legitimate confidential information while protecting the accuracy and independence of the research record. This hypothetical example illustrates planning decisions; it does not describe an existing CARE partnership.

Manage changes and close the work

Use review meetings to compare progress with commitments and record decisions. When a change is proposed, consider its effects on research quality, resources, permissions and the agreed outputs. Keep the revised plan and approvals together so that team members act on the same understanding.

At completion, confirm delivery, financial obligations, custody of materials, access to outputs and any continuing restrictions. Discuss whether the evidence supports a further project rather than assuming that a collaboration must expand.

• Can both parties explain the research question and limits?
• Are contributions and decision rights documented?
• Have student, publication and data interests been considered?
• Is there a workable route for changes and disagreements?
• Are exit and continuing responsibilities clear?

A strong partnership gives each participant a dependable understanding of the work, the uncertainty involved and the responsibilities they have accepted.