03 · What You Need to Know
Different Requirements Are Not Always Conflicting Requirements
Start by writing down exactly what each institution requires
Researchers sometimes encounter what appears to be a conflict because two institutions use different terminology, forms, workflows, or administrative processes.
Institution A might say that data must be stored on an "approved institutional platform." Institution B might say that identifiable data cannot be transferred outside its secure environment. Those requirements are different, but they are not necessarily contradictory. A research arrangement might satisfy both by keeping identifiable data at Institution B and transferring only appropriately de-identified information to Institution A.
Before escalating a conflict, convert each instruction into a precise requirement: who must do what, to which activity or information, at what stage, and under what authority?
A genuine conflict exists when complying with one requirement would breach another
Two requirements become genuinely incompatible when you cannot satisfy one without violating the other.
For example, imagine one institution requires identifiable interview recordings to be transferred to the lead university, while the host institution's binding data agreement prohibits identifiable recordings from leaving its secure system. If neither requirement can be modified, the project has a genuine governance conflict.
By contrast, if one institution requires five years of record retention and another requires a minimum of three years, retaining the records for five years may satisfy both, provided no other requirement imposes a maximum retention period or requires earlier destruction.
Different requirements
The institutions ask for different things, but both requirements can still be satisfied.
Conflicting requirements
Compliance with one requirement would make compliance with the other impossible or impermissible.
Identify where each requirement comes from
Not every institutional instruction has the same source or force.
A requirement may arise from legislation, regulation, an ethics decision, institutional policy, sponsorship arrangements, a research contract, funding conditions, a data-sharing agreement, professional standards, site authorization, or an administrative preference.
This distinction matters. A department's preferred template may be negotiable. A legal prohibition may not be. A contractual term may require amendment. An ethics condition may need review by the ethics committee before the research team can change the approved procedure.
The current UK Policy Framework for Health and Social Care Research illustrates this layered structure. It expressly operates alongside legislation and other standards and assigns different responsibilities to investigators, sponsors, funders, research sites, employers, regulators, and care providers rather than treating one organization as universally controlling every research decision.
Ask what each institution actually has authority over
An institution can legitimately impose requirements within areas for which it has responsibility. That authority is not necessarily unlimited.
Your home university may govern your employment, research-integrity obligations, institutional data systems, and sponsorship arrangements. A hospital hosting the research may control access to its premises, clinical records, staff, information systems, and local resources. A collaborating laboratory may control its facilities and safety requirements.
This is why responsibility for research conducted outside your own institution should be mapped rather than assigned entirely to either the home or host organization.
When several institutions are involved, the relevant question is not simply, "Which institution is senior?" It is, "Which institution has legitimate responsibility for this particular activity?"
The lead institution does not automatically override participating institutions
Calling one organization the lead institution can clarify coordination, but it does not necessarily give that institution authority over everything another organization controls.
A lead university cannot ordinarily authorize access to another hospital's confidential records merely by declaring that the study has institutional approval. Likewise, a participating hospital cannot necessarily change a project-wide protocol on behalf of the sponsor and all other sites.
As the UK Policy Framework emphasizes, responsibilities should be clearly designated, communication pathways should be explicit, and research sites retain responsibilities for activities occurring through their sites.
The broader governance principle is that several institutions can share responsibility without having identical authority.
The stricter requirement does not automatically win
"Follow whichever rule is stricter" sounds safe, but it is not a universal conflict-resolution principle.
Sometimes satisfying the more demanding requirement does satisfy both. If one institution requires stronger encryption than another, using the stronger permitted standard may solve the problem.
But stricter is not always compatible. One institution might require data to be retained while another valid requirement requires destruction. One may require disclosure that another prohibits. One may require a procedure that falls outside the ethically approved protocol.
Severity therefore cannot substitute for authority analysis.
Do not solve ethics-related conflicts by changing the protocol informally
If resolving an institutional disagreement requires changing the approved research design, recruitment, consent process, participant information, data handling, intervention, or another ethically relevant aspect of the study, the change may require ethics review or another formal modification before implementation.
The UK Policy Framework specifically states that changes to research proposals or protocols should be submitted to research ethics committees and other relevant approval bodies when review is expected or required, and approved changes should then be introduced consistently across relevant sites.
A compromise between administrators therefore does not automatically amend an ethics-approved protocol.
Contracts and collaboration agreements should help prevent conflicts
Multi-institution research works more smoothly when responsibilities are allocated before data collection begins.
Agreements can identify which institution is responsible for ethics submissions, data storage, security, access, intellectual property, financial management, participant complaints, reporting, publication, research-integrity concerns, and other relevant functions.
This does not guarantee that disagreements will never occur. It does give the institutions an agreed starting point for resolving them.
Where responsibilities have never been documented, apparent policy conflicts can expose a more fundamental governance problem: nobody established which institution had authority over the issue in the first place.
Escalate the issue through the responsible governance channels
Researchers should not be left to privately adjudicate genuine institutional conflicts that exceed their authority.
Depending on the issue, resolution may require the principal investigator, research governance office, sponsor, institutional legal counsel, privacy or data-protection office, research-integrity office, ethics committee, contract manager, funder, or another responsible body.
The escalation pathway should match the issue. A data-sharing conflict belongs with the people responsible for data governance and the relevant agreement. An ethics condition belongs with the ethics process. A site-access dispute belongs with the institution controlling the site.
Document the resolution
Once the institutions agree on a solution, document it appropriately.
This may require an amended agreement, revised protocol, ethics modification, updated data-management plan, revised site authorization, written institutional clarification, or another formal record.
An email saying "we discussed this and it should be fine" may be sufficient for a minor administrative clarification. It is a poor substitute for formal amendment when the underlying governance document itself needs to change.
Watch Out
Do not quietly follow whichever institution gives you the answer you prefer. If two legitimate requirements cannot both be satisfied, proceeding under one while ignoring the other can turn an administrative disagreement into research non-compliance.
