SOP-201

Confidentiality Agreements, Clinical Trial Agreements and Budgets

Number
SOP-201
Category
Start-up and Regulatory
Edition
Reference Edition 1.3
Approx. pages
8

[YELLOW] the site fills in. [DEFAULT: green] a value the site may keep or change.

On this page

1. Purpose

This SOP describes how [SITE NAME] reviews, negotiates, approves and signs confidentiality agreements (CDAs) and clinical trial agreements (CTAs), builds and negotiates study budgets, and invoices and reconciles study payments. ICH E6(R3) expects the financial aspects of the trial and the arrangements between parties to be documented in agreements, and lists them among the essential records that should be in place before the trial starts.

2. Scope

This SOP applies to all CDAs, CTAs (including master agreements, work orders and amendments), budgets and payment terms for clinical studies at [SITE NAME], whether the counterparty is a sponsor, a CRO acting for a sponsor, or a sponsor-investigator. It covers agreements with the site's own service providers only where they are study-specific; general vendor oversight is in SOP-105.

Out of scope: the Medicare coverage analysis, which must be finished before the budget is final (SOP-202); participant payment processing (SOP-310). This SOP describes operating steps. It is not legal advice; [SITE NAME] confirms legal and contracting positions with [LEGAL COUNSEL]. Terms flagged in step 5.3.4 go to [LEGAL COUNSEL] when the Site Director decides legal review is needed. Where a sponsor, CRO or IRB requirement is stricter than this SOP, the site follows the stricter requirement.

3. Responsibilities

RoleResponsibilities
Site DirectorOwns the contracting and budget process. Approves budgets and negotiation positions. Decides when to use outside counsel. Signs agreements on behalf of [SITE NAME] when authorized under 5.6.
Principal Investigator (PI)Reviews the CTA for terms that bind the investigator personally (protocol compliance, publication, record retention, financial disclosure). Signs as investigator where the CTA requires an investigator acknowledgment ("read and understood"). Reviews the budget for clinical accuracy of procedures and investigator time.
Finance / Contracts LeadLogs and tracks agreements. Performs the first review against F-201-01. Builds the budget. Negotiates within limits set by the Site Director. Sets up the payment schedule, invoices invoiceable items and reconciles payments.
Regulatory CoordinatorFiles executed agreements, amendments and budget documents in the ISF (SOP-204). Tells the Finance / Contracts Lead when IRB fees are incurred.
Lead CRCConfirms visit and procedure counts, staff time and screen-fail patterns used in the budget. Reports invoiceable events (screen fails, unscheduled visits, re-consents, SAE reports) to the Finance / Contracts Lead.
Quality LeadChecks that terms on monitoring access, audit, inspection and record retention match site SOPs.

4. Definitions

TermDefinition
Confidentiality agreement (CDA)An agreement, also called a non-disclosure agreement (NDA), that governs the site's use and protection of the sponsor's confidential information, usually signed before the protocol is shared.
Clinical trial agreement (CTA)The contract between the site (and sometimes the investigator) and the sponsor or CRO that sets out the terms for conducting a study.
Master agreementA CTA framework with a sponsor or CRO that applies to multiple studies, with each study added by a work order or study addendum.
BudgetThe schedule of payments attached to the CTA, including per-visit or per-participant fees, fixed fees and invoiceable items.
Schedule of assessments (SoA)The protocol table of visits and procedures; the basis for the per-visit budget.
InvoiceableA payment the site must request by invoice because it is not triggered by EDC data (for example screen-fail fees, IRB fees, unscheduled visits, archiving).
HoldbackA percentage of each payment withheld by the sponsor until study close-out conditions are met.
Subject injury clauseThe CTA terms that state who pays for diagnosis and treatment of injuries caused by the IP or by protocol procedures.
IndemnificationA contractual promise by one party to cover the other's losses from defined claims.
OverheadThe site's indirect cost rate applied to direct study costs.

5. Procedure

5.1 Logging and tracking

5.1.1
The Finance / Contracts Lead logs every CDA, CTA, amendment and budget in [CONTRACT TRACKER] with counterparty, protocol, version received, date received, status, next action and owner.
5.1.2
The Finance / Contracts Lead keeps every version exchanged (redlines and clean copies) in [CONTRACTS FOLDER] with the date and sender in the file name, so the negotiation history can be reconstructed.

5.2 Confidentiality agreements

5.2.1
The Finance / Contracts Lead reviews the CDA within [DEFAULT: 3 business days] of receipt against the CDA items on F-201-01 and the site's positions in [CONTRACT PLAYBOOK] (a separate, uncontrolled business document not shared with sponsors). At minimum the Finance / Contracts Lead checks:
  • the parties are correct ([SITE LEGAL NAME], not an individual staff member, unless the sponsor requires the PI to sign as well)
  • disclosure is permitted to IRBs, regulators and staff who need to know, and as required by law
5.2.2
Standard CDAs that pass every item and match [CONTRACT PLAYBOOK] may be signed by an authorized signatory (5.6) without further review. CDAs with deviations go to the Site Director.
5.2.3
Staff do not open or forward confidential protocol materials until the CDA is executed, unless the sponsor states in writing that a CDA is not required.

5.3 Clinical trial agreement review

5.3.1
When the CTA arrives, the Finance / Contracts Lead confirms the site has a go decision under SOP-200 and that the protocol version referenced is the version under review.
5.3.2
The Finance / Contracts Lead reviews the CTA against every item on F-201-01 and against the site's positions in [CONTRACT PLAYBOOK] (a separate, uncontrolled business document not shared with sponsors). This SOP sets the review process only; the site's negotiating positions and fallbacks are kept in [CONTRACT PLAYBOOK] and not in this SOP. The review covers at least these topics, with the control checks shown:
  • Parties and roles. Correct legal entity, investigator named, CRO acting as agent identified, payment entity identified.
  • Scope and protocol. Protocol identified by number and version; amendments handled by written amendment.
  • Indemnification and insurance. Terms reviewed against [CONTRACT PLAYBOOK]; the sponsor's insurance certificate is received; the site's insurance obligations match what the site carries.
  • Subject injury. The language matches the consent form (5.3.6). Under the Medicare Secondary Payer rules, a sponsor that agrees to pay for injury care is a primary payer for that care, so the site bills the sponsor, not Medicare, for it (SOP-202).
  • Confidentiality. Carve-outs for IRB, regulators, participant consent and law.
  • Publication and intellectual property. Terms reviewed against [CONTRACT PLAYBOOK]. Results posting on ClinicalTrials.gov is the sponsor's obligation.
  • Data protection and HIPAA. The sponsor receives participant data under the HIPAA authorization in the consent form (45 CFR 164.508). Coded data only; no direct identifiers unless the authorization allows it. Any state privacy law terms are noted on F-201-01. Whether a Business Associate Agreement is appropriate is decided under SOP-400.
  • Monitoring, audit and inspection access. The site permits monitoring, audits and regulatory inspection with direct access to source records; the notice period for an FDA inspection matches SOP-702.
  • Record retention. The retention period meets 21 CFR 312.62(c) or 812.140(d) and any longer sponsor period, the CTA states who pays for storage and for how long, and the sponsor must notify the site when records may be destroyed (SOP-402).
  • Payment terms, holdback and termination. Stated in the CTA and recorded in [ACCOUNTING SYSTEM] under 5.7.3; positions are in [CONTRACT PLAYBOOK].
  • Participant care after termination. The site may give participants appropriate follow-up care for their safety.
  • Safety reporting. The site's safety reporting duties match the protocol and the reviewing IRB's reporting policy. The CTA states who submits IND safety reports to the IRB: the sponsor on the investigator's behalf, with written confirmation to the site of each submission, or the site. 21 CFR 312.66 requires the investigator to report unanticipated problems to the IRB; FDA's December 2025 investigator safety reporting guidance (Investigator Responsibilities: Safety Reporting for Investigational Drugs and Devices, section VI) states FDA considers IND safety reports to be unanticipated problems (SOP-501 Serious Adverse Event and Expedited Safety Reporting, 5.10.4; SOP-502).
  • Financial disclosure. The investigator and Sub-Is provide financial disclosure information (21 CFR 54) and update it during the study and for one year after completion.
  • Debarment. Each party represents it is not debarred; the site screens staff and providers under SOP-704 Research Misconduct and Fraud Reporting.
  • Governing law and dispute resolution. Acceptable to the Site Director.
  • Anti-bribery and transparency. Standard compliance language; payments to investigators may be reported by the manufacturer under the federal Open Payments program.
5.3.3
The PI reviews the CTA for investigator obligations and confirms in [CONTRACT TRACKER] or by email that they have read and accept them.
5.3.4
The Finance / Contracts Lead marks each item on F-201-01 as acceptable, escalated to the [CONTRACT PLAYBOOK] owner, or not applicable. Items the playbook owner cannot resolve go to the Site Director, who decides whether to accept, negotiate further, involve [LEGAL COUNSEL], or decline the study.
5.3.5
The Finance / Contracts Lead sends redlines to the sponsor or CRO with brief explanations and records each round in [CONTRACT TRACKER].
5.3.6
Before signature, the Finance / Contracts Lead confirms that the subject injury, confidentiality, data use, participant payment and costs language in the final CTA matches the IRB-approved or submitted consent form. Any inconsistency is resolved before signature by changing the CTA, the consent form, or both.

5.4 Budget build

5.4.1
The Finance / Contracts Lead builds the budget from the final protocol schedule of assessments, not from the sponsor's proposed budget. The sponsor's budget is compared against the site build after the site build is done.
5.4.2
For each visit, the Lead CRC and Finance / Contracts Lead list every procedure and assign:
  • the site cost (internal cost or vendor price) or the site's research rate
  • staff time: CRC, PI or Sub-I, and other staff, in minutes, at the site's loaded hourly rates
  • whether the item is paid by the sponsor or, if the site bills insurance, billed as routine care per the coverage analysis (SOP-202)
5.4.3
The budget includes fixed and invoiceable fees as applicable. Typical items:
  • start-up fee (feasibility, regulatory packet, CTA and budget negotiation, SIV preparation)
  • IRB fees: initial, continuing review, amendments, closure, if the site pays them rather than the sponsor
  • pharmacy or IP management: set-up fee, per-dispensing fee, IP destruction, temperature monitoring
  • screen-fail fee per screen-failed participant
  • re-consent fee per participant per new consent version
  • unscheduled visit fee
  • SAE reporting fee per SAE
  • advertising and recruitment costs (per SOP-300, IRB-approved materials only)
  • participant stipends and travel reimbursement (SOP-310), as pass-through
  • monitoring visit and audit preparation fees beyond a stated number
  • specimen processing and shipping, dry ice, courier
  • protocol amendment fee (administrative work per amendment)
  • record storage and archiving per year, and retrieval fees
  • close-out fee
  • equipment purchases or rental the protocol requires
  • out-of-pocket items at cost plus overhead where the CTA allows
5.4.4
The Finance / Contracts Lead applies overhead at [OVERHEAD RATE] percent to direct costs, unless the sponsor's budget template builds it into fee lines, in which case the line amounts must carry it.
5.4.5
The Finance / Contracts Lead compares the site build with the sponsor offer line by line, records the gaps on F-201-01, and prepares a counter-proposal using the priorities in [CONTRACT PLAYBOOK].
5.4.6
Budget items must be consistent with the coverage analysis (SOP-202): an item the sponsor pays for is never also billed to a participant or insurer, and an item planned to be billed to insurance as routine care is not also in the sponsor budget.
5.4.7
The PI or Lead CRC confirms that the final budget covers every protocol procedure and reflects realistic staff time.
5.4.8
The Site Director approves the final budget before the CTA is signed and records the approval on F-201-01.

5.5 Amendments

5.5.1
When a protocol amendment adds or changes procedures or visits, the Lead CRC alerts the Finance / Contracts Lead, who checks the budget impact and requests a budget amendment before the site performs the new procedures, where the timeline allows.
5.5.2
CTA amendments follow the same review, approval and signature steps as the original.

5.6 Who may sign

5.6.1
Only the following may sign agreements on behalf of [SITE NAME]: [AUTHORIZED SIGNATORIES, e.g., CEO, SITE DIRECTOR]. The authorized signatory list and any dollar limits are kept in [SIGNATURE AUTHORITY POLICY] and updated by the Site Director.
5.6.2
The PI signs as investigator only where the agreement requires the investigator's acknowledgment or personal obligations. A PI who is not an authorized signatory does not sign on behalf of the company.
5.6.3
CRCs, Regulatory Coordinators and other staff do not sign CDAs, CTAs or budgets.
5.6.4
Electronic signatures through the sponsor's or the site's e-signature platform are acceptable. The Finance / Contracts Lead obtains a fully executed copy with all signatures and dates.

5.7 Execution and filing

5.7.1
The Finance / Contracts Lead sends the fully executed CTA and budget to the Regulatory Coordinator, Site Director and PI, and records the execution date in [CONTRACT TRACKER].
5.7.2
The Regulatory Coordinator files the executed CTA, budget, insurance certificate and amendments in the ISF (SOP-204) and records the executed CTA on F-205-01. Study procedures do not start until the CTA is executed (SOP-205).
5.7.3
The Finance / Contracts Lead sets up the study in [ACCOUNTING SYSTEM] with the payment schedule, invoiceables list, holdback percentage, payee details and sponsor invoice address.

5.8 Invoicing, tracking and reconciliation

5.8.1
The Lead CRC reports invoiceable events to the Finance / Contracts Lead at least [DEFAULT: monthly], using visit logs, screening logs (F-303-01) and SAE tracker (F-501-01) as support.
5.8.2
The Finance / Contracts Lead issues invoices for invoiceables per the CTA terms, keeps a copy with the supporting evidence, and tracks each invoice in [ACCOUNTING SYSTEM] until paid.
5.8.3
At least [DEFAULT: quarterly], the Finance / Contracts Lead reconciles for each study:
  • completed visits in the site's visit log and EDC against payments received from the sponsor or payment vendor
  • invoices issued against payments received
  • holdback withheld against the CTA percentage
  • participant payments disbursed (SOP-310) against pass-through reimbursements received
5.8.4
The Finance / Contracts Lead follows up unpaid amounts older than the CTA payment term plus [DEFAULT: 30 days], escalates unresolved items to the Site Director, and records follow-up in [CONTRACT TRACKER].
5.8.5
At close-out (SOP-601), the Finance / Contracts Lead performs a final reconciliation, invoices close-out and archiving fees, requests release of holdback, and records the final financial status on F-601-01.
  • F-201-01 Contract and Budget Review Checklist
  • F-205-01 Study Activation Checklist
  • F-303-01 Screening and Enrollment Log
  • F-501-01 SAE Reporting Tracker
  • F-601-01 Study Closeout Checklist
  • Appendix B Central and Site Responsibility Matrix (Model N only)
  • SOP-103 Staff Qualification, Training and Training Records
  • SOP-104 Conflict of Interest and Financial Disclosure
  • SOP-105 Oversight of Service Providers and Vendors
  • SOP-200 Study Feasibility and Selection
  • SOP-202 Medicare Coverage Analysis and Research Billing Compliance
  • SOP-204 Essential Documents and the Investigator Site File
  • SOP-205 Site Qualification, Initiation and Study Activation
  • SOP-301 Informed Consent Process and Documentation
  • SOP-310 Participant Payments and Reimbursement
  • SOP-400 Participant Privacy and HIPAA in Research
  • SOP-402 Record Retention, Archiving and Destruction
  • SOP-501 Serious Adverse Event and Expedited Safety Reporting
  • SOP-502 Unanticipated Problems and Reportable New Information
  • SOP-601 Study Closeout
  • SOP-702 FDA Inspections and Remote Regulatory Assessments
  • SOP-704 Research Misconduct and Fraud Reporting
  • SOP-902 Network Study Feasibility, Allocation and Central Contracting (Model N only)

7. References

ReferenceTitle
ICH E6(R3) Annex 1, 2.5.1Compliance with Protocol (investigator agreement)
ICH E6(R3) Annex 1, 3.5Financing
ICH E6(R3) Annex 1, 3.6Agreements
ICH E6(R3) Annex 1, 3.14Insurance/Indemnification/Compensation to Participants and Investigators
ICH E6(R3) Appendix CEssential Records for the Conduct of a Clinical Trial
21 CFR 54Financial Disclosure by Clinical Investigators
21 CFR 312.62Investigator Recordkeeping and Record Retention
21 CFR 312.66Assurance of IRB Review
FDA Guidance (December 2025)Investigator Responsibilities: Safety Reporting for Investigational Drugs and Devices
21 CFR 812.140Records (devices)
45 CFR 164.508Uses and Disclosures for Which an Authorization Is Required
42 U.S.C. 1395y(b)Medicare Secondary Payer
42 U.S.C. 1320a-7b(b)Anti-Kickback Statute (Model N payments between entities)
42 CFR 403 Subpart ITransparency Reports and Reporting of Physician Ownership or Investment Interests (Open Payments)

Independent Site SOP Library. Licensed CC BY-NC 4.0 by the American Institute for Medical Research (AIMR), with added permission for any site's internal use (license terms). Not legal advice: each adopting site confirms state law, IRB and sponsor requirements with its own counsel and owns every step it approves.