License Agreement by and Between The Broad Institute Inc
What this License Agreement covers and how it is used
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.
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.
Step-by-step: completing the License Agreement
-
01Assemble parties: Confirm legal names and authority for each party.
-
02Define the grant: Specify rights, territory, field of use, and exclusivity.
-
03Set commercial terms: Detail fees, royalties, milestones, and payment schedule.
-
04Execute and record: Obtain signatures, notarize if required, then archive executed copy.
Typical eSignature workflow for executing this agreement
-
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
| 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
| 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
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
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
Frequently asked questions about execution and validity
-
Can this agreement be signed electronically?
Yes. Electronic signatures are generally enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and state UETA laws, except where a specific statutory exception applies.
-
Is a notary required to validate signatures?
Not usually for a license agreement, but certain transactions (transfer of real property, some POAs) may require notarization or recording; check state requirements.
-
How should I confirm signer identity?
Use reasonable authentication matched to transaction risk: email link for low risk, SMS or multi‑factor for moderate risk, and KBA or ID proofing for high‑risk transactions.
-
What records should be retained?
Keep signed PDFs, audit trails, and related exhibits for the agreement term plus at least three years; follow industry retention rules such as 45 CFR §164.530(j) for HIPAA records.
-
Can I use remote online notarization (RON)?
Possibly. RON is permitted in most states but rules vary; confirm the state's RON statute and notary requirements before relying on remote notarization.
-
Who can sign for an institution?
Only signatories with delegated authority should sign. Document the delegation (board resolution or signed authorization) to prevent disputes about enforceability.