Establishing secure connection…Loading editor…Preparing document…

Research and AI Document

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

RESEARCH AND AI COLLABORATION AGREEMENT

Parties and Recitals

This Research and AI Collaboration Agreement (the Agreement) is entered into as of (Effective Date) by and between:

Principal Investigator / Client Name:

Service Provider / AI Research Entity:

WHEREAS, Client desires to engage Provider to conduct research and development activities relating to artificial intelligence models, data analysis, prototypes, or related deliverables as described herein; and

WHEREAS, Provider has represented that it possesses the technical capability, personnel, facilities, and expertise necessary to perform the research services and to develop the specified AI outputs; and

WHEREAS, the parties wish to set forth the terms and conditions under which such research, development, testing, and delivery shall occur.

Scope of Work

Payment Terms

Term and Termination

Term Commencement: This Agreement commences on and continues until unless earlier terminated in accordance with this section.

Either party may terminate this Agreement for material breach if the breaching party fails to cure such breach within the notice period set forth above following written notice. Termination shall not relieve either party of obligations accrued prior to termination, including payment for services performed and deliverables accepted.

Confidentiality

Definition: "Confidential Information" means non-public technical and business information disclosed by a disclosing party to the receiving party, including but not limited to datasets, model architectures, training procedures, source code, non-public results, and business plans, whether disclosed orally, in writing, electronically, or by inspection.

Obligations: The receiving party shall (a) protect Confidential Information with at least the same degree of care it uses to protect its own confidential information but no less than reasonable care; (b) use Confidential Information solely for performance of this Agreement; and (c) not disclose Confidential Information to any third party except to employees, contractors, or advisors who have a need to know and who are bound by confidentiality obligations no less protective than those herein.

Exclusions: Confidential Information does not include information that (i) is or becomes publicly available without breach of this Agreement; (ii) is rightfully received from a third party without restriction; (iii) is independently developed without use of the other party's Confidential Information; or (iv) is required to be disclosed by law, provided that the disclosing party is given prompt written notice and, if feasible, an opportunity to seek protective measures.

Intellectual Property and Data Rights

Pre-Existing Materials: Each party retains all right, title and interest in any technology, software, or data that existed prior to the Effective Date and that is disclosed during performance of this Agreement.

Deliverables and Model Outputs: Unless otherwise agreed in writing below, the parties agree that:

Client receives assignment of IP in deliverables (subject to Provider pre-existing rights)

Provider retains ownership and grants Client a non-exclusive, worldwide, royalty-free license to use deliverables for internal research and business purposes

Warranties, Indemnity, and Limitation of Liability

Each party represents that it has the authority to enter into this Agreement. Provider warrants that services will be performed in a professional manner consistent with industry standards. EXCEPT AS SPECIFICALLY SET FORTH HEREIN, PROVIDER MAKES NO OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Indemnity: Each party shall indemnify and hold harmless the other party from claims arising out of its negligent acts or willful misconduct in connection with this Agreement. Neither party shall be liable for indirect, incidental, consequential, punitive, or special damages, and aggregate liability shall be limited to the total amounts paid under this Agreement during the prior twelve (12) months, except for claims arising from breach of confidentiality, willful misconduct, or intellectual property infringement.

Governing Law and Dispute Resolution

The Agreement shall be governed by and construed in accordance with the laws of the governing jurisdiction specified above without regard to its conflicts of law principles. The parties agree to attempt to resolve disputes in good faith through negotiation prior to initiating any formal proceeding.

Entire Agreement and Amendments

This Agreement, including any exhibits, statements of work, or attachments expressly incorporated herein, constitutes the entire agreement between the parties with respect to the subject matter and supersedes all prior and contemporaneous agreements, proposals, or representations, whether written or oral. No amendment shall be effective unless in writing and signed by authorized representatives of both parties.

Notices

Miscellaneous Provisions

Assignment: Neither party may assign this Agreement without the prior written consent of the other party, except to a successor in interest in connection with a merger or sale of substantially all assets.

Severability: If any provision is held unenforceable, the remainder of the Agreement will remain in full force and effect.

Client:

By:

Date:

Provider:

By:

Date:

Enter text✕

What the Research and AI Document Is

The Research and AI Document is a formal agreement and record used to define project scope, data sources, consent terms, intellectual property allocation, security controls, and governance for research projects involving artificial intelligence. It consolidates data use, model training authorization, and risk mitigation steps so stakeholders can document permitted uses, retention requirements, and audit procedures. The form clarifies responsibilities for data custodians, principal investigators, and technology vendors and supports reproducible workflows and compliance reviews where human-subjects or regulated data are involved.

Why this document matters for projects

The Research and AI Document reduces ambiguity about data rights, privacy safeguards, and permitted model uses while documenting compliance obligations; it helps align stakeholders and preserves an auditable record of decisions under ESIGN and UETA where electronic execution applies.

Why this document matters for projects

Who typically prepares and signs this document

Researchers, data stewards, legal and procurement teams, and technology vendors commonly prepare and sign this document to set permissions and responsibilities for AI development.

  • Academic research teams documenting IRB approvals, consent scope, and controlled data access for model development and evaluation.
  • Corporate AI groups setting data provenance, IP assignments, usage limits, and vendor responsibilities for production models.
  • Legal and compliance staff reviewing retention schedules, consumer disclosures, and regulatory language before execution and archival.

Institutional review boards, compliance officers, cloud service providers, and contracting officers also rely on the document when approving data access, model deployment, or vendor engagements.

Step-by-step: prepare and execute the document

Follow a structured sequence to prepare, approve, sign, and archive the Research and AI Document to maintain compliance and an auditable trail.

  • 01
    Prepare: Identify datasets, approvals, and stakeholders before drafting.
  • 02
    Draft: Document scope, rights, privacy, IP, and security controls.
  • 03
    Review: Get legal, IRB, and security sign-offs.
  • 04
    Execute: Collect signatures, record audit trail, and distribute copies.

Core components every Research and AI Document should include

A comprehensive document groups scope, data handling, IP terms, security measures, privacy provisions, and governance to reduce legal and operational risk.

Scope

Define project scope including permitted datasets, approved model architectures, allowed outputs, geographic and temporal limits, exclusions for sensitive data, and the authorization period to ensure clarity on what the agreement permits and forbids.

Data Use

Specify rights to access, preprocess, label, and retain data; permitted secondary uses such as model improvements; obligations for de-identification, re-identification risk mitigation, and restrictions on resale or transfer to third parties.

Privacy

List consent requirements, whether HIPAA protections apply, FERPA considerations for educational data, data minimization practices, and responsibilities for breach notification and compliance with applicable U.S. privacy laws.

Security

Describe technical and organizational controls, encryption in transit (TLS 1.2/1.3) and at rest (AES-256), access control, incident response, and any SOC 2 or ISO 27001 attestations relied upon.

IP & Rights

Allocate ownership of model weights, training derivatives, and improvements; specify license grants for use, explicit redistribution limits, attribution, and downstream commercialization rights or revenue-sharing arrangements.

Governance

Set change-control procedures, audit rights, model validation requirements, periodic reviews, designated data steward contacts, and escalation paths for policy exceptions or compliance audits and reporting.

Typical digital execution flow

Electronic execution commonly follows upload, field placement, signer delivery, signature capture, and archival, with an audit trail for future review and compliance.

  • Upload: Upload the final approved document as PDF or DOCX.
  • Fields: Place signature, initial, date, and conditional fields.
  • Send: Add signer emails or generate secure links.
  • Archive: Store signed copy and export audit log.

Configure your online signing workflow

Map approval order, authentication level, and conditional routing to match institutional and project requirements before sending for signature.

Field Configuration
Signing Order Sequential or parallel signer order configured per role
Authentication Email, SMS OTP, or KBA depending on risk
Conditional Fields Show or hide fields based on answers
Notifications Email reminders and completion notices to stakeholders

Technical requirements for eSigning platforms

Use a platform that supports required file formats, strong authentication, audit logging, and exportable records when executing Research and AI Documents electronically.

  • Formats: PDF, DOCX, Excel supported
  • Integrations: Salesforce, NetSuite, Teams, Google Workspace
  • Security: TLS 1.2/1.3 and AES-256

Typical timing and milestone deadlines

Track approvals, execution dates, and retention start points; align milestones with IRB, sponsor, and institutional reporting requirements.

IRB Approval (if applicable) prior to data access:

Obtain before collecting any human-subjects data.

Data Sharing Window and Access Period:

Specify start and end dates for dataset access.

Retention Start and End Dates:

Record retention clocks as MM/DD/YYYY; tie to effective date.

Annual Review and Audit Schedule:

Conduct yearly compliance reviews and document outcomes.

Reporting to Sponsors and Funders:

Meet funder reporting timelines specified in grant terms.

Common preparation mistakes to avoid

  • Vague or undefined permitted uses can lead to disputes over model deployment, causing costly remediation, contract renegotiation, or halting production systems while parties clarify rights.
  • Insufficient de-identification or undocumented techniques risk exposing PHI, potentially triggering HIPAA breach obligations and notification requirements under 45 CFR §164.404.
  • Using inconsistent legal entity names across documents can invalidate signatures, complicate tax reporting, and delay payments or onboarding.
  • Relying on weak signer authentication increases repudiation risk; high-value or regulated projects should use stronger identity proofing methods.

Principal legal and operational risks

HIPAA Fines: Civil and criminal penalties under HIPAA.
Contract Damages: Breach remedies and indemnities.
Regulatory Enforcement: State attorneys general actions possible.
Data Subject Claims: Privacy lawsuits and statutory penalties.
Tax Reporting: Backup withholding if incorrect TIN.
Operational Delay: Project suspension or remediation costs.

Real-world examples and outcomes

Practical examples illustrate how standardized Research and AI Documents reduce administrative friction and support compliance across sectors.

Optica Ventures — Brian Fitzgibbons

Optica Ventures used a standardized research agreement to streamline investor diligence and partner data sharing across multiple early-stage collaborations.

  • Automation sped external approvals and reduced back-and-forth.
  • "The interface is simple and easy-to-use for our team; more importantly, it is just as easy for our customers." Standardized documentation cut turnaround time and reduced administrative queries during due diligence.

Fertility Centers of Illinois — John Butler

A healthcare provider standardized consent and data-sharing language for clinical AI projects to ensure patient privacy and regulatory compliance.

  • BAA and security controls were formalized.
  • "The airSlate SignNow team has been exceptional, responsive, the API has been great, and we're extremely happy that we chose airSlate SignNow as a company." This reduced manual handling and ensured consistent audit trails for patient consent and research approvals.

Roles that typically sign or approve

Lead Researcher

The principal investigator responsible for study design and protocol adherence. The PI verifies informed consent scope, coordinates IRB submissions, approves permitted uses, and confirms the Research and AI Document matches sponsor and institutional obligations before signature.

Data Custodian

The data steward manages dataset access, implements de-identification, documents provenance and lineage, enforces retention schedules, and responds to data subject or audit inquiries while coordinating technical controls with legal and security teams.

Practical tips to reduce errors and delays

Adopt these practices to improve accuracy, speed approvals, and maintain a defensible audit trail for research and AI work.

Use Clear, Narrow Permitted Uses
Avoid broad 'research purposes' clauses. Enumerate specific training, validation, or benchmarking activities. Narrowing permitted uses reduces disputes, enables targeted consent, and clarifies downstream commercialization or sharing limits for auditors and enforcement authorities.
Standardize Names and Entities
Use legal entity names consistently across agreements, tax forms, and invoices. Mismatched names can trigger backup withholding, invalidate signatures, or delay contracting. Cross-check with payroll and vendor records to prevent administrative friction.
Document De-identification Methods
Describe de-identification steps, algorithms, and re-identification risk assessments. Maintain reproducible records of transformations applied to datasets to support compliance with HIPAA guidance and internal risk reviews.
Choose Proper Authentication Strength
Match signer authentication to transaction risk—email for low-risk approvals, SMS or KBA for moderate risk, and advanced authentication for high-value or regulated data to reduce repudiation risk.

Comparing eSignature vendors for Research and AI Document execution

Compare pricing, bulk capabilities, HIPAA support, and audit features when selecting an eSignature vendor for executing Research and AI Documents.

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 plan Varies by plan Varies by plan Varies by plan
Bulk Send Yes (Business Premium) Yes Yes Yes Limited
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Frequently asked questions and quick answers

Answers to common questions about electronic execution, compliance, retention, and authentication for Research and AI Documents.


Need help? Contact support

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