Establishing secure connection…Loading editor…Preparing document…

Cooperative Research and Development Agreement

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

COOPERATIVE RESEARCH AND DEVELOPMENT AGREEMENT

This Cooperative Research and Development Agreement (the "Agreement") is entered into as of by and between Party A Name: , an entity type: , having its principal place of business at ; and Party B Name: , an entity type: , having its principal place of business at . Each of Party A and Party B is sometimes individually referred to herein as a "Party" and collectively as the "Parties."

RECITALS

WHEREAS, Party A possesses expertise and facilities in ; and Party B possesses expertise in ;

WHEREAS, the Parties desire to collaborate on the research and development of (the "Project") pursuant to the terms and conditions set forth herein to evaluate technical approaches, exchange information, and develop resulting intellectual property.

WHEREAS, the Parties intend for this Agreement to define the scope of collaboration, allocation of rights to background and developed intellectual property, responsibilities for costs, confidentiality obligations, and procedures for publication and commercialization.

NOW, THEREFORE, in consideration of the mutual covenants set forth below, the Parties agree as follows:

1. DEFINITIONS

1.1 "Background Technology" means technology, know-how, data, inventions, and materials that a Party owns or controls prior to the Effective Date or independently of the Project, as identified in Annex A: Background Technology. Each Party shall list such items in the field below.

1.2 "Developed Technology" or "Joint Inventions" means inventions, discoveries, designs, processes, data, software, and other intellectual property conceived, reduced to practice, or authored in the course of performance of the Project pursuant to Section 3.

2. PURPOSE AND SCOPE

2.1 Purpose. The Parties shall collaborate to carry out the Project described in the Statement of Work attached as Annex B. The collaboration shall be limited to the tasks, deliverables, and milestones set forth therein.

2.2 Project Duration. The term of the Project shall commence on the Effective Date and continue until , unless earlier terminated in accordance with Section 10.

3. STATEMENT OF WORK; PERFORMANCE

3.1 Statement of Work. The detailed tasks, responsibilities, schedule, milestones, and deliverables are set forth in Annex B. Each Party shall perform its responsibilities in accordance with Annex B and industry standards of professional care.

3.2 Key Personnel. Each Party shall identify key personnel assigned to the Project and shall not replace such personnel without prior written notice to the other Party. Key personnel for Party A: ; for Party B: .

4. FUNDING; COSTS; PAYMENT

4.1 Funding Commitment. Each Party's funding obligations and cost sharing are set forth in Annex C. Party A agrees to contribute: USD; Party B agrees to contribute: USD.

4.2 Invoicing and Payment. Costs incurred shall be invoiced monthly in sufficient detail. Payments are due within days of invoice receipt. Overdue amounts shall bear interest at the lesser of 1.5% per month or the maximum permitted by law.

5. INTELLECTUAL PROPERTY

5.1 Ownership of Background Technology. Each Party retains exclusive ownership of its Background Technology, and no transfer of ownership is intended by this Agreement except as expressly set forth herein.

5.2 Ownership of Developed Technology. Unless otherwise expressly agreed in writing, (a) inventions and other intellectual property that are conceived or reduced to practice solely by employees or contractors of one Party in performance of the Project shall be owned exclusively by that Party; and (b) inventions conceived or reduced to practice jointly by employees or contractors of both Parties shall be jointly owned by the Parties as tenants in common, subject to the joint ownership provisions set forth in this Section 5.

5.3 Patent Prosecution and Expenses. Owners of Joint Inventions shall consult in good faith regarding prosecution and maintenance of patent rights. Unless otherwise agreed, prosecution costs for patents claiming Joint Inventions shall be shared equally; each Party may file and prosecute patent applications in its own name for its respective ownership interest provided the filing Party consults the other Party and gives the other Party reasonable opportunity to participate and contribute to prosecution costs.

5.4 License Grants. Subject to confidentiality obligations and other terms, each Party hereby grants to the other a non-exclusive, non-transferable, royalty-free license to use its Background Technology solely to the extent necessary to perform the Project. Any further licenses for commercialization shall be negotiated in good faith and set forth in a written license agreement.

6. CONFIDENTIALITY

6.1 Definition. "Confidential Information" means non-public information disclosed by one Party to the other in connection with the Project, including technical data, trade secrets, designs, know-how, prototypes, and business information, whether disclosed orally, visually, in writing, or electronically.

6.2 Obligations. The receiving Party shall (a) maintain Confidential Information in strict confidence using at least the same degree of care it uses to protect its own confidential information but in no event less than reasonable care; (b) not use Confidential Information except to perform the Project; and (c) not disclose Confidential Information to third parties except to employees, contractors, or advisors who have a need to know and who are bound by obligations of confidentiality at least as protective as those herein.

6.3 Exceptions. Confidential Information shall not include information that is: (a) known to the receiving Party prior to disclosure; (b) publicly available without breach of this Agreement; (c) rightfully received from a third party without restriction; or (d) independently developed by the receiving Party without use of the disclosing Party's Confidential Information.

7. PUBLICATION

7.1 Review and Approval. Either Party may publish results of the Project. Prior to submission for publication, the publishing Party shall provide the other Party with a copy of the proposed manuscript or abstract and a written request for review. The receiving Party shall have days to review and request redaction or delay for patent filing or protection of Confidential Information. Any agreed delay for patent filing shall not exceed days.

8. REPRESENTATIONS; WARRANTIES; NO OTHER WARRANTIES

8.1 Each Party represents that it has the full corporate power and authority to enter into this Agreement and to perform its obligations hereunder. Each Party further represents that its Background Technology and performance under this Agreement will not knowingly infringe third party intellectual property rights.

8.2 EXCEPT AS EXPRESSLY SET FORTH HEREIN, THE PARTIES DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

9. INDEMNIFICATION; LIMITATION OF LIABILITY

9.1 Indemnification. Each Party (the "Indemnitor") shall indemnify, defend and hold harmless the other Party and its officers, directors, employees and agents (the "Indemnitees") from and against any third-party claims arising out of the Indemnitor's gross negligence, willful misconduct, or breach of its representations and warranties under this Agreement.

9.2 Limitation of Liability. Except for liability arising from a Party's gross negligence, willful misconduct, breach of confidentiality, or indemnification obligations, in no event shall either Party be liable to the other for any indirect, incidental, special, consequential, or punitive damages, and each Party's aggregate liability for claims under this Agreement shall not exceed the amount of direct damages equal to the total funding actually paid by the Parties hereunder during the twelve (12) months preceding the claim.

10. TERM AND TERMINATION

10.1 Termination for Convenience. Either Party may terminate this Agreement for convenience upon days' prior written notice to the other Party. Termination shall not relieve either Party of obligations incurred prior to the effective date of termination.

10.2 Termination for Cause. Either Party may terminate this Agreement upon written notice if the other Party materially breaches any provision of this Agreement and fails to cure such breach within days after receiving written notice specifying the breach.

11. INSURANCE

Each Party shall maintain insurance coverage customary for its industry and sufficient to cover liabilities that may arise from the performance of the Project, including commercial general liability and employer's liability insurance where applicable.

12. NOTICES

All notices required or permitted under this Agreement shall be in writing and shall be delivered personally, by certified mail (return receipt requested), or by nationally recognized overnight courier to the addresses set forth below, or to such other address as either Party shall designate by notice to the other Party.

13. AMENDMENTS; WAIVER; ASSIGNMENT

13.1 Amendment. No amendment or modification of this Agreement shall be valid unless in writing and signed by authorized representatives of both Parties.

13.2 Waiver. No failure or delay by either Party in exercising any right shall operate as a waiver of that right. A waiver must be in writing to be effective.

13.3 Assignment. Neither Party may assign or transfer this Agreement or any rights or obligations hereunder without the prior written consent of the other Party, except that either Party may assign to an affiliate or in connection with a merger or sale of substantially all of its assets provided the assignee assumes the assigning Party's obligations hereunder.

14. GOVERNING LAW; DISPUTE RESOLUTION

This Agreement shall be governed by and construed in accordance with the laws of the State or jurisdiction of , without regard to conflict of laws principles. The Parties shall first attempt to resolve disputes through good-faith negotiation. If the Parties are unable to resolve a dispute within sixty (60) days, either Party may pursue any remedy available at law or in equity.

15. ENTIRE AGREEMENT; SEVERABILITY; COUNTERPARTS

15.1 Entire Agreement. This Agreement, including all Annexes and Exhibits attached hereto, constitutes the entire agreement between the Parties with respect to the subject matter hereof and supersedes all prior and contemporaneous understandings and agreements.

15.2 Severability. If any provision of this Agreement is held to be invalid or unenforceable, the remainder of the Agreement shall remain in full force and effect and the Parties shall negotiate in good faith to replace the invalid provision with a valid provision that achieves, to the extent possible, the economic, legal and commercial objectives of the invalid provision.

15.3 Counterparts. This Agreement may be executed in counterparts, each of which shall be deemed an original and all of which together shall constitute one and the same instrument. Signatures delivered by electronic transmission shall be binding.

ANNEXES

The following Annexes are attached and incorporated by reference: Annex A — Background Technology; Annex B — Statement of Work; Annex C — Budget and Payment Schedule. Confirm attached annexes:

Party A:

By:

Title:

Date:

Party B:

By:

Title:

Date:

Enter text✕

What a Cooperative Research and Development Agreement Is

A Cooperative Research and Development Agreement (CRADA) is a written contract used by a federal laboratory and one or more nonfederal parties to collaborate on research and development. It defines the project scope, contributions, intellectual property rights, publication and confidentiality rules, and how inventions or data will be managed. CRADAs enable sharing of facilities, personnel, and technical expertise while preserving each party's rights described in the agreement. They are commonly used to translate government research into commercial applications while documenting responsibilities and risk allocation.

Why a CRADA Matters for Collaborative R&D

A CRADA clarifies roles, protects confidential information, and sets expectations for IP ownership and commercialization. For both government labs and industry partners, it reduces ambiguity about resource use, publication timing, and invention reporting, supporting predictable outcomes and lawful technology transfer.

Why a CRADA Matters for Collaborative R&D

Who Typically Uses Cooperative Research and Development Agreements

Common signatories include federal laboratories, universities, startups, and established companies that require shared access to government research capabilities and technical staff.

  • Federal laboratories and their technology transfer offices seeking to move inventions toward practical use.
  • University research offices and principal investigators collaborating with industry partners.
  • Private companies and startups that need lab facilities, specialized equipment, or co-funded research relationships.

These agreements balance collaboration benefits with legal protections for data, inventions, and publication rights, making them appropriate where structured IP and confidentiality terms are needed.

Roles That Sign a CRADA

Lab Tech Transfer Officer

A technology transfer officer negotiates terms on behalf of the federal lab, coordinates internal approvals, and ensures compliance with agency policies and invention-reporting obligations.

Corporate R&D Executive

An R&D or business leader from the commercial partner defines project goals, funding or in-kind support, and negotiates IP rights and commercialization commitments with the laboratory.

Core Elements to Include in a Professional CRADA

A clear CRADA includes defined technical scope, contributions, intellectual property rules, publication controls, confidentiality protections, and termination conditions tailored to the collaboration's goals and regulatory context.

Parties

Full legal names and organizational details for each party, including responsible office or division, and a designated point of contact for contracting and technical coordination.

Scope of Work

A precise description of tasks, deliverables, milestones, performance metrics, and schedules so each party understands responsibilities and expected technical outcomes.

Contributions

Describe funding amounts, in‑kind resources, personnel assignments, equipment access, and any material transfers provided by each party to support the research.

Intellectual Property

Define background IP, foreground inventions, ownership, patent prosecution responsibilities, licensing terms, and any rights retained by the federal laboratory under statute.

Confidentiality

Identify confidential information categories, disclosure limitations, permitted disclosures, duration of confidentiality obligations, and procedures for marking and handling sensitive data.

Publication & Reporting

Set review periods for manuscripts, invention disclosure timing, reporting obligations, and any approval procedures required before public release of results.

Step-by-Step: How to Prepare and Execute a CRADA

Follow these steps to draft, review, and finalize a CRADA with clear approvals and documented IP handling.

  • 01
    Draft SOW: Develop a detailed Statement of Work with milestones and deliverables.
  • 02
    Identify Contributions: Document funding, personnel, equipment, and material support provided by each party.
  • 03
    Negotiate IP Terms: Agree on background rights, ownership of inventions, and licensing arrangements.
  • 04
    Obtain Approvals: Secure signatures from authorized officials and complete agency internal reviews.

How a Typical CRADA Workflow Progresses

A CRADA usually moves from initial inquiry through negotiation, internal approvals, execution, and project management. Each step involves specific offices and documentation.

  • Initial Inquiry: Partner contacts the lab's technology transfer office to discuss capabilities and interests.
  • Proposal & SOW: Parties draft the Statement of Work and resource commitments for review.
  • Review & Approval: Legal, contracting, and technical offices review for compliance and risk.
  • Execution: Authorized signatories execute the agreement and begin collaborative activities.

Digital Workflow Settings Recommended for CRADAs

Configure your e-signature workflow to reflect review order, required authentications, and document attachments before sending the CRADA for execution.

Field Configuration
Signature Order Sequential signing with lab approvals first
Authentication Email + SMS code or enterprise SSO
Attachments Attach SOW, budget spreadsheet, and supporting annexes
Retention Enable automatic archival and audit trail export

Technical Considerations for eSigning a CRADA

Use an eSignature platform that supports strong authentication, audit trails, and secure storage when handling government-related agreements.

  • Authentication: Support for email, SMS, and SSO
  • Integrations: Connect with NetSuite, Salesforce, or Google Workspace
  • File Types: Accept PDF, DOCX, and structured form exports

Ensure the platform can produce a tamper-evident audit trail, meet agency security requirements, and offer optional BAAs or advanced signer authentication for regulated collaborations.

Typical Timelines and Deadlines in a CRADA

Timelines vary by project, but common deadlines include negotiation periods, milestone submissions, invention disclosures, and periodic progress reports.

Negotiation Period:

30–90 days from initial proposal to signed agreement in many cases

Milestone Reporting:

Interim technical reports typically submitted quarterly or per SOW schedule

Invention Disclosure:

Prompt reporting upon conception per agency rules and SOW terms

Publication Review:

Labs often require a 30–90 day review before public release

Annual Reviews:

Yearly program reviews or audits as specified in the agreement

Key Project Milestones for a CRADA

Use a milestone ladder to track project initiation, major deliverables, IP events, and closeout tasks during the collaboration.

01

Project Kickoff

Formally start collaboration and confirm resources and contacts

02

Midpoint Review

Assess progress, validate milestones, and adjust SOW if needed

03

Invention Reporting

Document any potentially patentable outcomes and notify lab offices

04

Project Closeout

Deliver final reports, reconcile deliverables, and settle IP arrangements

Common Mistakes When Preparing a CRADA

  • Vague scope leading to unmet expectations or disputes.
  • Unclear IP terms causing ownership or licensing conflicts.
  • Insufficient confidentiality protections for sensitive data.
  • Missing internal approvals or improperly authorized signatures.

Risks and Consequences of an Improper CRADA

IP Loss: Disputes over ownership or licensing
Regulatory Noncompliance: Violation of agency rules or export controls
Confidentiality Breach: Loss of trade secrets or protected data
Funding Disputes: Unclear contributions leading to repayment claims
Publication Conflict: Delayed or restricted dissemination of results
Contract Voidance: Improper authorization can render agreement unenforceable

Security and Compliance Essentials for CRADA Documents

Encryption: TLS 1.2/1.3; AES-256 at rest
Audit Trail: Tamper-evident signing history
HIPAA: BAA available where required
21 CFR Part 11: Support for FDA-regulated records
ESIGN / UETA: Compliant electronic signature framework
Certifications: SOC 2 Type II and ISO 27001

Real-World eSignature Use in Complex Agreements

These customer examples illustrate how eSignature platforms support complex document workflows that include external approvals and integration with enterprise systems.

Optica Ventures LLC

Brian Fitzgibbons described streamlined execution with a simple interface.

  • The team reduced turnaround times on partner agreements.
  • The solution helped the company execute documents efficiently across internal and external stakeholders while maintaining compliance and clear audit trails.

Xerox

Kodi-Marie Evans highlighted integration with enterprise systems for signature workflows.

  • Integration reduced manual entry and reconciliation.
  • Built-in API connectivity enabled automated routing and record keeping, allowing teams to get signatures on complex documents in supported formats without repetitive manual processes.

Practical Tips for Accurate and Efficient CRADA Completion

Adopt these practices to reduce delays, preserve rights, and keep the collaboration compliant and auditable.

Use a Detailed SOW
Attach a scope of work that breaks tasks into milestones, deliverables, and acceptance criteria to avoid scope disputes later.
Clarify IP and Licensing
Define background and foreground IP clearly, assign prosecution responsibility, and state preferred licensing terms to prevent later ambiguity.
Document Approvals
Track internal agency approvals and authorized signatories; missing approvals are a leading cause of invalid contracts.
Preserve Audit Trails
Use an eSignature platform that retains tamper-evident audit logs and attachments for compliance and potential patent prosecution needs.

How a CRADA Differs from Other Collaborative Agreements

Compare CRADAs with standard NDAs, sponsored research agreements (SRAs), and licensing agreements to choose the correct instrument for collaboration.

Agreement Type CRADA NDA SRA License
Purpose joint r&d confidentiality only funded research ip commercialization
IP Ownership shared or negotiated no ip transfer sponsor often gets rights licensor retains ip
Funding in-kind or financial none sponsor funds work licensing fees
Publication Controls yes, negotiated n/a yes, often limited n/a

eSignature Pricing and Feature Comparison for CRADA Workflows

Select an eSignature provider that supports required security, audit trails, and integrations. Pricing models and features vary; signNow appears first in the table for vendor comparison.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial 7-day free trial Varies by vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes (Business Premium) Yes Yes Yes Varies
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No
Envelope Cap No cap 100 envelopes/user/year Varies Varies Varies

Frequently asked questions about executing CRADAs

Answers to common practical and compliance questions when preparing, signing, or managing a Cooperative Research and Development Agreement.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users