1
PLAYBOOK TEMPLATES

Joint Development Agreement (JDA)

A JDA sets forth terms for collaborative product or technology development, addressing ownership, confidentiality, and IP outcomes. This playbook highlights best practices for defining contributions, milestones, and dispute resolution.

License Scope

Why This Matters: Clear scope provisions protect against unauthorized exploitation or unintended limitations, reducing the risk of disputes and revenue loss by ensuring mutual understanding of rights.

Negotiation strategy

If you're the Company A:

Ensure the license scope is clearly defined to protect proprietary interests. Specify the territory and field of use to prevent unauthorized exploitation.

If you're the Company B:

Negotiate for a broad license scope to maximize usage rights. Ensure sublicensing rights are included to allow flexibility in business operations.

Essential elements

1

Licensed IP

Intellectual property covered.
2

Territory

Geographic area of use.
3

Field of Use

Specific application area.

Action framework

ACCEPT

Propose edits if the scope is too restrictive or unclear.

EDIT

Reject if the scope does not align with strategic goals.

ADD

Add language to clarify sublicensing rights.

PRO TIP

Always align the license scope with long-term business objectives to avoid future limitations.

Real-world examples

FAVORABLE

Preferred License Scope

"The Licensor hereby grants to the Licensee a non-exclusive, worldwide license to use the Licensed IP solely within the Field of Use."
NEUTRAL

Standard License Scope

"The Licensor grants a license to the Licensee, subject to specified territorial and field of use restrictions."
UNFAVORABLE

Overly Restrictive License Scope

"The Licensor grants a limited license to the Licensee, with significant territorial and field of use limitations."

Alternative scenarios & positions

High-Risk Projects

In high-risk projects, ensure the license scope includes indemnification clauses to mitigate potential liabilities.

Global Expansion

For global expansion, negotiate for a worldwide license to avoid regional restrictions that could hinder growth.

Joint Ventures

In joint ventures, ensure the license scope allows for sublicensing to partners to facilitate collaboration.

Access all other DocJuris Playbooks

Launch in days, not months

Unlike complex CLMs with long implementations and steep learning curves, DocJuris is built for speed and simplicity. We integrate with your workflow—whether connecting to a CLM or uploading agreements manually—so you're up and running in days, not months.
WEEK 1
CLM Readiness and Design
Our CX team works with you to understand your contracting challenges, prioritize key workflows, and identify the biggest impact areas. We build a tailored implementation plan that fits your needs.
WEEK 2
Install Module
We connect DocJuris to your contract repositories, set up admin and user accounts, and ensure your environment is ready for success.
WEEK 3
Deliver & Test
Your team builds initial playbooks, reviews existing clause libraries, and trains the DocJuris agent to align with your internal standards and negotiation positions.
WEEK 4
Launch
We support you in rolling out DocJuris to a pilot group or your full organization—with launch materials, training, and hands-on support to drive adoption from day one.

Not another CLM

Tackle everything your team needs using existing IT without expensive consultants, outrageous user licensing fees, or complex coding. DocJuris takes on the heavy lift and delivers your requirements with its people, process, and technology.

See how DocJuris can automate your legal, procurement, and sales operations.

Request demo
© 2025 DocJuris, Inc. All rights reserved. Patent Pending.
DocJuris is not a law firm or a substitute for an attorney or law firm. We cannot provide any kind of advice, explanation, opinion, or recommendation about possible legal rights, remedies, defenses, options,selection of forms or strategies.