Establishing secure connection…Loading editor…Preparing document…

License Agreement by and Between The Broad Institute Inc

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!
License Agreement by and Between The Broad Institute Inc

What this License Agreement covers and how it is used

A License Agreement by and Between The Broad Institute Inc is a legally binding contract through which The Broad Institute, as licensor, grants specified rights to a licensee to use intellectual property, research materials, software, or proprietary methods. Typical clauses define the grant scope (exclusive or nonexclusive), territory, permitted fields of use, sublicensing rights, term and termination, fees or royalties, confidentiality, representations and warranties, indemnification, and dispute resolution. The agreement often attaches technical exhibits, usage restrictions, and data‑handling requirements that reflect funding and regulatory obligations.

Why a clear license agreement matters for institutions and partners

A clear, well‑drafted license agreement allocates rights and risks, ensures compliance with funder or sponsor conditions, preserves patent and data rights, and supports commercialization or collaborative research. Properly structured terms reduce ambiguity about permitted uses, revenue sharing, and post‑termination obligations.

Why a clear license agreement matters for institutions and partners

Who typically prepares or signs this agreement

Various organizational roles encounter or complete license agreements depending on the transaction and institution.

  • Tech transfer and licensing offices handling IP commercialization and compliance for research institutions.
  • Corporate legal and business development teams negotiating commercial or co‑development licenses.
  • Principal investigators or lab managers supplying technical exhibits and compliance confirmations.

Each party should involve legal, finance, and subject‑matter experts early to confirm scope, downstream obligations, and any export or biosecurity restrictions.

Representative signatory roles

Tech Transfer Officer

Typically a university or institute employee who evaluates IP, negotiates license scope and royalties, verifies assignment chain, and signs on behalf of the institution under board authorization or delegated authority.

Licensee Executive

A corporate signatory (CEO, VP Business Development, or authorized agent) who confirms commercial intent, payment terms, and operational readiness to comply with usage restrictions and reporting obligations.

Security and compliance items to track

Encryption: AES-256 at rest
Transport: TLS 1.2/1.3
Audit Trail: Signed event logs
HIPAA: BAA available
21 CFR Part 11: Compliant options
Retention: Tamper-evident records

Step-by-step: completing the License Agreement

Follow these essential steps to prepare, review, and execute a license agreement with The Broad Institute Inc.

  • 01
    Assemble parties: Confirm legal names and authority for each party.
  • 02
    Define the grant: Specify rights, territory, field of use, and exclusivity.
  • 03
    Set commercial terms: Detail fees, royalties, milestones, and payment schedule.
  • 04
    Execute and record: Obtain signatures, notarize if required, then archive executed copy.

Typical eSignature workflow for executing this agreement

A standard electronic execution flow reduces turnaround and preserves an auditable record of consent.

  • Upload document: Prepare final PDF version for signature placement.
  • Place fields: Add signature, date, and initial fields where required.
  • Route to signers: Send in role order or via signing link.
  • Archive and export: Save signed PDF with certificate of completion.

Recommended digital workflow settings

Adjust settings to balance signer friction and authentication strength.

Field Configuration
Authentication Email link | SMS code optional
Template Save as reusable template
Bulk send Enable for mass distribution
Storage Archive as PDF/A with audit trail

Technical and integration considerations for eSubmission

Choose a platform that supports required authentication, audit trails, and your document formats.

  • Integrations: Salesforce, NetSuite, Google Workspace
  • File formats: PDF, DOCX, HTML supported
  • Authentication: Email, SMS, or advanced options

Confirm the platform can export a tamper-evident signed PDF and retain accessible logs to meet audit and compliance needs.

Comparing eSignature vendor pricing and basic capabilities

High-level vendor comparison for processing license agreements; signNow is listed first per platform preference requirements.

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 No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes (BAA available) Yes (BAA available) Yes (BAA available) No No
Envelope Cap No cap 100 envelopes/user/year Varies by plan Varies by plan Varies by plan

Primary legal risks and common contract penalties

Breach Damages: Monetary remedies
Injunction: Court order to stop use
Termination: Loss of rights and repayment
Indemnity: Cost to defend claims
Reputational Risk: Funding and collaboration harm
Tax Exposure: Withholding or reporting issues

Common preparation mistakes to avoid

  • Using informal or multiple inconsistent versions of the agreement leads to ambiguity about the binding terms and effective date.
  • Failing to confirm the signatory's authority or corporate delegation can leave the agreement unenforceable against the intended party.
  • Overbroad grant language without defined field of use or territorial limits can unintentionally permit undesired commercial activity.
  • Neglecting to attach technical exhibits or data handling addenda causes implementation delays and compliance gaps during audits.

Real-world examples of electronic execution and integration

Institutions and companies use digital workflows to accelerate licensing and maintain auditable records.

Optica Ventures — COO

Optica streamlined external licensing processes with digital signatures.

  • Integration with common systems mattered for adoption.
  • "The interface is simple and easy-to-use for our team; more importantly, it is just as easy for our customers." — Brian Fitzgibbons, COO, Optica Ventures LLC

Xerox — NetSuite Director

Xerox integrated eSignatures into ERP workflows to automate contract routing.

  • API and NetSuite connectivity reduced manual steps.
  • "airSlate SignNow provides us with the flexibility needed to get the right signatures on the right documents, in the right formats, based on our integration with NetSuite." — Kodi‑Marie Evans, Director of NetSuite Operations, Xerox

Practical tips for accurate, efficient completion

Adopt consistent templates and review checklists to reduce negotiation cycles and signature errors.

Standardize templates
Keep a single institutionally approved template with modular exhibits; changes should be tracked and approved by counsel.
Use clear definitions
Define terms like "Net Sales," "Field of Use," and "Sublicense" to avoid future disputes and simplify financial reporting.
Record authority
Document corporate approvals and signing authority in the file to support enforceability and audit trails.
Preserve evidence
Retain executed PDFs and access logs to demonstrate intent and attribution under ESIGN (15 U.S.C. ch. 96) and applicable state law.

Frequently asked questions about execution and validity

Answers to common questions about signing, authentication, and enforceability for a license agreement with The Broad Institute Inc.


Need help? Contact support

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