Your CRO Has Your Data. Now What?
A small biotech outsources most of what it does, and each relationship hands over data that is the company's core asset. What to establish before you outsource, how to manage access across organizational boundaries, and why study close is the moment that matters most.
A small biotech outsources most of what it does — the CRO runs the trial, the CDMO makes the product, the central lab holds the samples, a consultant has admin access to a system. Each relationship involves handing over data that is the company's core asset, under agreements usually negotiated for scope and price rather than for data control. Your obligations for that data don't transfer with the work, and the moment that matters most is study close, when everyone's attention has moved on.
This is the final piece in our series on pharmaceutical technology risk. Earlier articles covered what acquirers examine in IT due diligence, what a partner's security questionnaire is really asking, and the cost of downtime in manufacturing. This one is about the data that leaves your building every time you outsource — and what it takes to keep it yours.
See where your regulated environment actually stands.
Fifteen questions, about five minutes, scored on screen with a remediation roadmap emailed to you.
Who is actually responsible?
The framing point. Outsourcing the activity does not outsource the sponsor's responsibility for data integrity and record retention. A regulator asking about trial data asks the sponsor, not the CRO.
ICH E6(R3), the Good Clinical Practice guideline, is explicit on this: a sponsor may transfer trial-related activities to a service provider, but "the ultimate responsibility for the sponsor's trial-related activities, including protection of participants' rights, safety and well-being and reliability of the trial data, resides with the sponsor." The CRO runs the trial; the sponsor owns the answer if something is wrong with the data.
What that means practically for a company with no internal systems of its own is that the sponsor still has to know where the data sits, who can touch it, and how it comes back. You can outsource the work; you cannot outsource the question. If you cannot answer "where is our trial data right now" without sending an email to a vendor, you have outsourced the responsibility along with the work — and a regulator will notice the difference.
What do you actually need to know about each relationship?
This is the inventory most companies don't have. For each outsourced relationship, you should be able to answer six questions without picking up the phone:
- What data they hold. Not "clinical data" — the specific datasets: subject records, lab results, manufacturing batch records, stability data, draft regulatory submissions.
- Where it physically sits. Which data centre, which region, which cloud tenant. "In our system" is not an answer; "Azure West Europe, tenant X" is.
- Who at their organization can access it. Named roles, not "our team." How many people, and what level of access — read, write, admin.
- Which subprocessors they use. The CRO's hosting provider, their backup provider, any analytics tool that touches the data. These are parties with access to your data that you did not choose.
- How it comes back to you. The mechanism and the format at the end of the relationship.
- In what format. This is where it goes wrong. Data returned in a proprietary export nobody can read is technically returned and practically lost. A CSV of a clinical database is not the database. A PDF of a batch record is not the record. The format question is the one nobody asks until it is too late.
What should the agreement say?
Practical rather than legal — and this is general guidance, not legal advice; have your counsel review the specifics. The provisions that matter for data control are:
- Data ownership stated explicitly. The data is yours, the vendor holds it on your behalf, and nothing in the agreement transfers ownership.
- Return and deletion obligations with a defined timeframe. Return within a set number of days of termination; deletion after confirmed return, with a certificate of destruction.
- Format requirements for returned data. Specify the format — structured, documented, in a standard or openly documented schema — not "the vendor's standard export." If the only reader is the vendor's software, you have not gotten your data back.
- Subprocessor disclosure and approval. The right to know who they use and to object to a new one. A subprocessor is a party with your data that you did not choose.
- Audit rights. The right to verify how the data is handled, directly or through a designated auditor.
- Incident notification with a window. Notification of a security incident affecting your data within a defined period — not "promptly," which is unenforceable.
- Retention obligations that survive termination. The vendor's obligation to preserve records for the regulatory retention period, and to hand them to you or a successor if they cannot.
The pharmaceutical industry page covers the broader regulatory context these provisions sit inside. The point here is that data control terms are not standard procurement clauses — they need to be negotiated, and the time to do it is before the contract is signed, not at study close.
Access management across organizational boundaries
This is the operational risk that follows the contract. CRO staff have accounts in your systems; your staff have accounts in theirs. People leave both organizations, and nobody tells the other side. An account that belonged to a CRO project manager who left eight months ago is still active in your document system because nobody knew to remove it.
Periodic access review is the control, and it has to cross the organizational boundary. On a schedule that matches the risk, review every external account with access to your systems: is the person still on the project, do they still need the access, is the access level still appropriate. Send the list to your counterpart at the vendor and ask them to confirm. Offboarding at the other end is invisible to you unless you ask — the vendor's HR process does not notify you when their employee leaves, and it should not have to. The review is your control, not theirs.
The same applies in reverse. Your staff with admin access to a vendor's system should be tracked and removed when the project ends. A stale admin account in a CRO's environment is an access path to your data that you forgot existed.
What happens at study close?
This is the centerpiece, and it is the moment nobody plans for. Everyone's attention moves to the next study. The closeout meeting covers deliverables and final invoices, not data. The data has to come back in a usable form, be retained for a period that usually outlives the relationship, and be retrievable and readable at the end of it.
The period matters. Clinical trial records are retained for years — the obligation is defined in the applicable regulations and in ICH E6, and it routinely exceeds the length of the CRO relationship. A study that closes this year may need records available a decade later. The CRO you used may not exist by then, may have changed systems, or may not be able to read its own eight-year-old export. The difference between having received the data at close and being able to read it in eight years is the difference between meeting the obligation and failing it.
Plan the close before the study starts. Decide where the data will live once it comes back, who will hold it, what format it will be in, and how it will remain readable. A data return that is tested at close — can we open it, can we read it, does it match what they held — is the only kind that counts. An untested return is a promise.
What if the relationship ends badly?
The uncomfortable case. A dispute over scope or payment, a termination for cause, or a CRO that goes out of business or is acquired. What leverage exists to get your data back, and why it depends almost entirely on what the agreement said before the relationship soured.
When a relationship ends badly, goodwill is gone and the only thing that governs is the contract. If the data return terms were a one-line obligation to "return data upon termination," you have a right but no mechanism — no specified format, no timeframe, no fallback if the vendor cannot or will not cooperate. If the terms specified the format, the timeframe, and the right to recover the data directly in the event of non-performance, you have something enforceable. The time to establish data return terms is before you need them — and the moment you need them is the moment the relationship is already under strain, which is too late to negotiate.
Where does your own infrastructure fit?
Brief and honest. Even a company that outsources everything needs somewhere authoritative to hold what comes back — with access control, backup, and retention that meets the regulatory obligation. That place should be yours, not a shared folder in a partner's environment.
This is not a call to build a data centre. It is a call to own the authoritative copy. When the data returns from the CRO, it lands in an environment you control, with access you manage, with backups you have tested, and with retention you can demonstrate. A shared folder in the CRO's tenant that you happen to have access to is not that. The cybersecurity and data protection controls that govern your own environment are the same ones that should govern the authoritative archive of everything that came back.
A checklist for each outsourced relationship
- 1.What data do they hold? Be specific — the datasets, not a category.
- 2.Where does it sit? The data centre, region, and tenant. Get the answer in writing.
- 3.Who has access? Named roles and access levels. Get the list at the start and review it on a schedule.
- 4.Which subprocessors? Every third party that touches your data, disclosed and acknowledged.
- 5.What's the return format and timeline? A documented, openly readable format and a defined number of days.
- 6.What's the deletion obligation? Deletion after confirmed return, with a certificate of destruction.
- 7.Who reviews access and how often? A named person on your side, on a defined cadence, across the organizational boundary.
- 8.Where does it live once it's back? An authoritative environment you control, with backup and retention that meets the obligation.
What each outsourced relationship holds, and what to establish before you sign
| Relationship type | Data they hold | The risk at close | What to establish upfront |
|---|---|---|---|
| CRO | Trial data, subject records, case report forms, statistical outputs | Data returned in a proprietary format nobody can read; records needed years later are inaccessible | Return format in an open, documented schema; retention handoff plan; access review cadence |
| CDMO | Manufacturing batch records, stability data, process validation data | Batch records held by a vendor who has moved systems or ceased trading | Return of records in readable form; retention obligation that survives termination; documented archive destination |
| Central lab | Sample data, lab results, reference ranges | Sample chain-of-custody gaps; results locked in the lab's LIMS | Defined return of raw and reported data; sample disposition documented; format specified |
| Consultants with system access | Admin credentials, configuration data, access to your systems | Stale accounts after the engagement ends; configuration knowledge not documented | Time-bound access; offboarding at engagement end; configuration documented before the engagement closes |
| Cloud platform vendors | Hosting of your authoritative data and applications | Vendor lock-in; data not portable; exit without a migration path | Data portability terms; defined export in standard formats; exit assistance obligation |
The obligation outlives the relationship
The relationship ends; the obligation doesn't. The companies that handle this well decided where the data would live before they sent any of it out — and treated the return, the format, and the retention as part of the scope, not an afterthought at close.
Photo: Rows of white archive boxes on wooden shelves on Unsplash.
Frequently asked questions
Don't see your question? Email info@isectra.com and we'll answer it directly.

Santiago runs IT environments for pharmaceutical manufacturers. He writes about the operational reality of regulated IT — the work, the obligations, and what actually happens when the contract ends.
Get the next post in your inbox.
Signal, once or twice a month. No spam — just the posts worth reading.
Let's see what your IT could feel like.
A senior engineer will review your environment and respond within 24 hours. No sales script, no obligation.

