lev-os Field of Use Restriction Clause
Drafts a narrow, enforceable licensing clause that limits exploitation rights to a defined field while preserving licensor control outside that field. U.S.-focused; cross-border enforcement may require localization. [VERIFY]
Prerequisites
Before drafting, confirm:
- Grant model defined — IP type, exclusive/non-exclusive, term, royalty logic, territory.
- Portfolio data collected — patent IDs, software modules/versions, know-how, related IP.
- Business boundaries set — industries, customer types, channels, geographies, prohibited markets.
- Source documents available — draft agreement, SOW, schedules, prior licenses.
- Enforcement preferences — audit cadence, reporting format, cure policy, remedy priorities.
- Jurisdiction selected — governing law, venue/forum, injunctive relief requirements.
Quick Start
Gather inputs across five dimensions, then assemble clause sections in order:
| Input | Capture | Drives |
|---|---|---|
| Field scope | Industry, use case, geography, customer type, channel | Field of Use definition and negative examples |
| IP scope | Patent IDs, software versions, process assets | Covered subject-matter precision |
| Commercial rights | Grant type, exclusivity, sublicensing | Reservation-of-rights language |
| Compliance controls | Reporting cadence, records, audit access | Audit and reporting mechanics |
| Enforcement posture | Cure tolerance, injunction needs, termination triggers | Remedies and transition provisions |
Clause Assembly
Draft sections in this order:
- Definitions —
Licensed Property,Field of Use,Permitted Applications,Restricted Fields, plus technology-specific terms from patents/specs. - Grant — Confer rights only within
Field of Use; reserve all rights outside; tie term/milestones to any scope evolution. - Sublicense/assignment — Scope limits, mandatory field-of-use flow-down notices, licensor approval where required.
- Use controls — Prohibit direct/indirect exploitation outside scope; explicit anti-circumvention for affiliates, contractors, distributors.
- Derivatives — Restrict derivative use consistent with field intent; address improvements and new IP ownership.
- Compliance — Licensee records by product/application/customer; periodic reports; audit rights with access scope and notice.
- Remedies — Cure rules (if any), material breach termination, injunction, enhanced royalties/profits, IP clawback where lawful.
- Post-termination — Immediate cessation, return/destruction of materials, ongoing confidentiality and field restrictions.
- Governing law and disputes — Chosen forum plus carve-out for expedited injunctive relief.
- Survival — Confidentiality, indemnity, continuing restraint obligations.
Validation Checklist
Before finalizing:
- No operative verb (
sell,use,offer,distribute,import) permits off-scope commercial activity - All cross-references resolve; terminology uniform across definitions and obligations
- Reporting fields tie to royalty and audit triggers
- Survival clause covers confidentiality, indemnity, and continuing restraints
- Grant language and exclusion language are consistent (no contradictions)
Pitfalls
- Ambiguous scope — Prefer objective controls over subjective standards; ambiguity defeats enforcement.
- Software licenses — Split field definitions by platform, module, deployment model, and customer class.
- Liquidated damages — Use only if demonstrably tied to anticipated loss and proportionate.
- Anti-circumvention gaps — Cover affiliates, contractors, distributors, and value-chain intermediaries explicitly.