1---2name: draft-markup-jda-biopharma-device3task_id: intellectual-property/draft-markup-of-joint-development-agreement4description: Combined issue log, redline commentary, and strategic cover memo for a joint development agreement in a biopharma-device collaboration, evaluated against client instructions, IP schedule, licensing policy, and prior deal terms.5activates_for: [planner, solver, checker]6metadata:7 source: https://skillmd.com/skills/finchipaiorg/draft-markup-jda-biopharma-device8---910# Skill: Draft Markup of Joint Development Agreement1112## 2. Failure modes the skill is correcting1314- Marking up the agreement as if it were a generic collaboration agreement, without integrating the client’s licensing policy, the background-IP schedule, and the prior deal terms into a single comparison set15- Missing deviations from negotiated commercial positions because the draft is read clause-by-clause instead of against the whole source bundle16- Treating joint ownership, field restrictions, sublicensing, and use-rights as standard boilerplate rather than policy-driven terms that may need bespoke overrides17- Overlooking the allocation of regulatory control, data ownership, and development-cost responsibility that is often decisive in a biopharma-device collaboration18- Producing commentary that identifies an issue but does not state severity, explain the clause interaction, or spell out the downstream business, regulatory, or litigation consequence19- Offering only stylistic redlines that are fragile in export, instead of changes that remain intelligible in plain text and can be reviewed line-by-line20- Drafting a memo that summarizes concerns but does not give concrete negotiating direction or operational next steps2122## 3. Legal frameworks / domain conventions that apply2324- The agreement should be tested against the client’s licensing policy first where policy is more specific than market practice, especially on field-of-use limits, sublicensing, ownership of improvements, and permitted downstream use25- The prior deal term sheet functions as the negotiated commercial benchmark; departures from it should be identified, explained, and, if material, treated as active negotiation points26- Background IP must be ring-fenced with precision so that each party’s pre-existing technology, know-how, and platform rights are excluded from joint ownership except to the extent expressly licensed27- Joint development in a regulated product context should allocate control over regulatory strategy, submissions, data use, adverse-event reporting support, and related costs28- Default rules on joint ownership may not match the parties’ intended exploitation model; the draft should confirm whether the agreement overrides default co-ownership consequences under the governing law29- Clinical, technical, and regulatory data rights should be allocated expressly, because use of those materials often determines both approval strategy and post-development commercialization30- Where the source documents identify governing law, statutory authority, regulatory regime, or policy language, the commentary should anchor conclusions to that authority rather than to abstract market custom3132## 4. Analytical scaffolds3334- Source-set reconciliation:35 1. client instructions36 2. background-IP schedule37 3. licensing policy38 4. prior deal / term sheet39 5. current draft JDA40 Compare each operative provision against this full set before drafting a change41- Policy-first IP review:42 - background IP43 - foreground / project IP44 - improvements45 - joint inventions46 - license scope47 - sublicensing48 - exclusivity or field restrictions49 - post-termination rights50- Regulatory and development control review:51 - who owns the development plan52 - who controls filings and submissions53 - who bears costs54 - who controls data, reports, and communications with regulators55- Deviation analysis:56 - identify where the draft departs from prior deal economics or allocation of rights57 - state whether the departure is intentional, acceptable with revision, or a negotiation risk58- Issue-log discipline:59 - assign an ordinal severity to each issue60 - tie the issue to the relevant clause and to the source document(s) it conflicts with61 - explain the practical consequence if uncorrected62- Redline discipline:63 - make each substantive edit readable from plain text alone64 - pair each edit with a short rationale comment so the business and legal reason is visible65- Negotiation memo discipline:66 - translate the markup into a concise risk assessment67 - identify must-have positions versus points that can move68 - recommend who should act and what should happen next6970## 5. Vertical / structural / temporal relationships7172- If the source materials involve more than one party, review each party’s rights, obligations, and asymmetries separately before drafting any joint allocation73- If the draft contains multiple schedules or exhibits, cross-check the main agreement against each schedule to ensure definitions, ownership, and licensing terms are consistent74- If the agreement contemplates phased development, clinical testing, validation, regulatory filing, and commercialization, confirm that rights and controls shift coherently across stages rather than remaining fixed by default75- If the draft addresses pre-signing conduct, in-term development, and post-termination exploitation, treat those as distinct temporal buckets and test each bucket for survivability and residual rights76- If the collaboration spans both product and data rights, keep the vertical relationship clear: technical work may generate data, data may support filings, and filings may drive commercialization rights7778## 6. Output structure conventions7980- Produce one combined working document that contains:81 1. a severity-ranked issue log82 2. the redlined agreement with inline plain-text change markers and short rationale comments83 3. a strategic cover memo84- Use a defined severity scale at the start of the issue log and apply it consistently to every entry85- For each issue-log entry, include:86 - clause / topic87 - severity88 - source conflict or deviation89 - proposed fix90 - consequence if not fixed91- For each substantive redline, make the change explicit in text using a robust convention that survives export, and include a brief rationale immediately nearby92- The cover memo should state overall risk posture, non-negotiable positions, negotiable items, and the preferred bargaining sequence93- End with a Recommended Actions section that assigns an action, a responsible role, and a timing anchor tied to the drafting or negotiation milestone94- Cite controlling legal authority or policy authority whenever a legal conclusion depends on a rule, statute, regulation, or defined policy requirement95- Keep the writing operative: every section should advance the markup, not merely describe the exercise