Question 1

How does Cairnsplice create an inspection-ready audit trail for CRO studies?

Accepted Answer

Cairnsplice brings study issues, decisions, owners, due dates, and supporting evidence into an issue register and activity log. Teams can preserve the context behind an action and produce audit-ready evidence exports; it helps organize inspection preparation but does not replace your SOPs or formal inspection processes.

Question 2

How does Cairnsplice support ICH-GCP oversight across sponsors, CROs, and sites?

Accepted Answer

It helps distributed teams operationalize oversight by connecting milestones, quality signals, deviations, owners, and follow-up actions in one visible workflow. Cairnsplice supports sponsor and CRO oversight practices; it does not replace ICH-GCP responsibilities, approved SOPs, or the judgment of the accountable quality team.

Question 3

Is Cairnsplice 21 CFR Part 11 compliant, and what does the customer still need to validate?

Accepted Answer

Cairnsplice is designed to support operational controls relevant to regulated clinical work, but this page is not a certification or formal regulatory determination. Your organization must validate the configured system for its intended use, document procedures and controls, and confirm the appropriate Part 11 position with its quality and regulatory teams.

Question 4

How do you protect evidence integrity and preserve the context behind each quality decision?

Accepted Answer

The issue register keeps the decision, responsible owner, timing, status, and related evidence together, while the activity log preserves the operational history around changes and follow-up. That context supports a coherent evidence export; your team remains responsible for source records, access practices, and the integrity of the underlying evidence.

Question 5

How are protocol deviations and related corrective actions assigned, escalated, and closed?

Accepted Answer

Teams can record a deviation or quality issue, assign an accountable owner, set a due date, and track corrective actions through review and closure with supporting evidence. Escalation and closure practices are scoped to your workflow, roles, and SOPs, so the configured process supports—not replaces—your quality system.

Question 6

Who owns each action when a study involves sponsor, CRO, site, vendor, and quality teams?

Accepted Answer

Each action has an explicit owner, due date, status, and study context, making handoffs visible across sponsor, CRO, site, vendor, and quality teams. Cairnsplice clarifies accountability and follow-through; the participating organizations still define responsibilities, delegation, and oversight in their agreements and procedures.

Question 7

What integrations and import/export options fit our existing clinical-operations workflow?

Accepted Answer

Integration and data-movement choices are tailored to the systems, evidence sources, and controls already used by your team. During a demo, we can map the right connection or scoped import/export approach for your workflow and confirm what can be supported—without assuming a named integration or a one-size-fits-all setup.

Question 8

How long does onboarding take for a CRO or multi-site study team?

Accepted Answer

There is no fixed implementation promise: timing depends on study complexity, site count, current workflows, data preparation, and validation expectations. We use the discovery process to scope the control loop, owners, evidence model, and rollout plan for your team before confirming an onboarding path.

Question 9

How is pricing structured for single studies, multi-site CROs, and enterprise quality teams?

Accepted Answer

Pricing is tailored to the scope of oversight: the studies and sites involved, participating teams, workflow requirements, and any implementation or validation support. We do not publish a fixed one-size-fits-all model here; a demo lets us confirm the operating shape and provide a scoped commercial proposal.

Question 10

Where is study data hosted, and how do you handle data residency requirements?

Accepted Answer

Hosting and residency requirements are reviewed as part of scoping, alongside your region, study obligations, security expectations, and validation needs. We will confirm the applicable deployment and data-handling options for your situation during a demo rather than make a blanket regional or residency guarantee.

The questions quality teams ask before the study starts.

Bring us the workflow behind the question.