Start by naming the strategic target

• How would you briefly describe the strategic goal for this co-development?
• Which business metrics will demonstrate success for this collaboration within 12 months? Options: Revenue attributable to collaboration, Time to market for a joint feature, Regulatory milestone achieved, Cost reduction or cost avoidance, New customer wins, Other
• Who is the decision owner for whether the resulting IP can be commercialized, and which roles must sign the JDA? Options: General counsel/Head of legal, Head of IP/Patent counsel, VP Business Development, CTO/Head of Engineering, CFO/Procurement, Other
• How soon do you need a signed agreement to keep the engineering schedule on track, within 2, 4, or 8 weeks? Options: Within 1 week, Within 2 weeks, Within 4 weeks, Within 8 weeks, No immediate deadline
• Tell me about a past collaboration where IP ownership caused friction, what happened and what the measurable impact was?

What success looks like, and what failure actually costs

• If this project misses its primary strategic objective, what is the direct business consequence for your product roadmap or commercial plan?
• Which single commercialization milestone would make you consider walking away from the project? Options: Ownership of core algorithm, Exclusive commercialization rights in a market, Freedom to sell to key customers, Right to publish or not publish, Other
• Estimate the value tied to success, choose the category that matters most to your leadership Options: Revenue uplift, Faster regulatory approval, Competitive differentiation, Lower development cost, Strategic partnership access
• Who outside legal must sign off on commercialization rights and licensing scopes, and how fast can they review a term sheet? Options: IP counsel only, IP and commercial legal, IP, commercial legal, and business unit lead, Executive sign-off required
• If the deal slips past your technical window, what downstream costs or missed opportunities occur that we should quantify now?

Map your background IP and non-negotiables

• Walk me through the pieces of existing technology, patent families, datasets, or know-how you view as non-negotiable to retain control over.
• Which artifact types in that portfolio are relevant to this project, for example patent filings, source code, datasets, lab notebooks, or prototypes? Options: Issued patents, Pending patent applications, Source code repositories, Annotated datasets, Lab notebooks or experiment logs, Prototypes or hardware
• How many active patent families, pending applications, or registered copyrights relate to the relevant technology, choose the best range Options: None, 1 to 3, 4 to 10, More than 10, Unclear / need to audit
• Are any background assets subject to third-party licenses, open-source obligations, or encumbrances that could limit how you grant rights? Options: No known encumbrances, Open-source components with copyleft terms, Third-party license restrictions, Existing exclusive licenses, Unknown, needs review
• Is there any single background asset you cannot under any circumstances license to a partner? Options: Yes, specific asset(s) cannot be licensed, No, everything is potentially licensable, Unsure, needs internal approval

Where ownership disputes tend to start, and what to watch for

• Which parts of your architecture or experiment data do you expect will be ambiguous between background and foreground? Options: Model training data, Core algorithm modules, Hardware interface code, Sensor calibration techniques, Test datasets and metrics, Other
• How do you currently decide inventorship or contributor credit when two teams jointly produce a technical result? Options: Patent counsel determines inventorship, Engineering documents determine contributions, Joint review between teams, No set process today
• What publication constraints does your organization require, for example review periods, regulatory clearance, or patent filing holds? Options: Standard internal review period, Patent filing before publication required, Regulatory clearance needed, No publication restrictions, Other
• Have you previously seen a clause or term in a JDA that created operational friction, and which clause was it?
• What single ambiguity in ownership or licensing would make you pause development immediately?

Alternatives you're weighing, including internal options

• Who else, including internal teams, are you actively considering to manage JDA strategy and IP ownership? Options: External specialty law firm, Large generalist law firm, Internal legal team handling it, Technical consulting partner, Hybrid internal plus external
• Which external capabilities or track record are you prioritizing in that comparison, for example domain experience, dispute history, or drafting speed? Options: Domain experience (semiconductor, pharma, software), Proven dispute defense record, Speed of delivery, Cost or pricing model, Governance and program-level support
• What would have to be true about your current internal approach for you to keep it rather than hire outside counsel? Options: Internal team can meet technical complexity, Internal team can meet timelines, Cost of external counsel not justified, Internal team has prior JDA precedent
• Has anyone on your team proposed solving IP ownership without an outside vendor, and who would lead that effort? Options: Yes, legal would lead, Yes, engineering would lead, No one has proposed DIY, Proposal is under discussion
• What would change in the RFP, scope, or timeline that would make you stop the vendor search and stay with your incumbent?

Approval gates and timeline realities that break deals

• Who within your organization must approve the JDA, and which of those approvals historically take the longest? Options: Legal/IP only, Legal plus business unit lead, Legal, business unit, and finance, C-suite approval required
• How long does each approval typically take, from legal to IP to business to executive sign-off? Options: Less than 1 week, 1 to 2 weeks, 2 to 4 weeks, More than 4 weeks
• Are there budget or procurement processes that will gate fee approval or outside counsel hiring? Options: Yes, procurement gating, Yes, budget cycle gating, No formal gating, Unknown
• If approvals cannot be secured within your target window, would you proceed with technical work under an interim agreement? Options: Yes, with interim NDA and limited license, No, must have a signed JDA, Depends on specific protections
• Which single internal stakeholder's objection would block the project?

Operational readiness, data access, and technical constraints

• Which integration, data access, or lab access constraints, if unresolved, would prevent us from delivering the scoped IP assessment on schedule?
• Which third-party systems, APIs, or hosted platforms must we connect to, and who currently owns those credentials and endpoints? Options: Internal API endpoints, Cloud data storage (S3, blob), On-prem lab systems, Vendor-managed platforms, Other
• How many dedicated engineering, legal, or data staff can you commit to structured working sessions per week? Options: 0 - ad hoc participation, 1 to 2 people, 3 to 5 people, More than 5 people
• Is the data and experimental evidence we will need stored, labeled, and owned by someone who can grant access within the project timeline? Options: Yes, ready to share, Partially ready, needs preparation, No, significant clean up required, Unknown
• Are there regulatory approvals, export controls, or security reviews that could pause knowledge transfer? Options: Yes, regulatory approvals required, Yes, export control considerations, Yes, security review required, No known regulatory gating
• If we require API access or export approvals that you cannot provide, can the engagement proceed under a reduced scope or remote evidence review? Options: Yes, reduced scope acceptable, No, cannot proceed without access, Depends on which assets are restricted

Interim protections and your minimum risk posture

• What interim protections do you require before engineers begin work with a partner, for example NDA, interim license, or limited-use data agreement? Options: Mutual NDA, Interim limited license, Source code escrow, Data use agreement, None required
• Which party typically drafts initial NDAs or interim licenses in your deals, and how long do those close? Options: We draft and close quickly, Counterparty drafts and closes slowly, Neutral template preferred, No standard approach
• Would you accept a narrowly scoped interim license that protects background IP while enabling necessary collaboration work? Options: Yes, Maybe with amendments, No
• How important is immediate signature versus negotiated terms, ordered by priority: speed, scope, enforceability? Options: Speed, Scope, Enforceability
• Is lack of an interim NDA or protection a deal-breaker for starting technical work? Options: Yes, cannot start without interim protection, No, we can start with limited disclosures, Depends on the partner

Clear acceptance criteria and the next steps that shorten the timeline

• If the initial IP memo and term sheet meet your expectations, what internal action would move you to sign a JDA within one week?
• Which three measurable acceptance criteria should we include, for example clear foreground ownership of X modules, a license scope for Y uses, and approval windows under Z days?
• What budget or fee approval exists for JDA legal work today, and which engagement model do you prefer: fixed fee, capped hours, or time and materials? Options: Fixed fee, Capped hours, Time and materials, No budget approved yet
• How do you prefer to receive the deliverables, IP memo, annotated term sheet, draft JDA, or all three at once? Options: IP memo first, Annotated term sheet first, Draft JDA first, All deliverables together
• Realistically, when can you commit to a short kick-off workshop with engineers, inventors, and legal stakeholders: within 1 week, within 2 to 4 weeks, or later? Options: Within 1 week, Within 2 to 4 weeks, In more than 4 weeks, Not yet sure

• Technical and Legal Working Sessions Kickoff and Evidence Intake
• Component-Level Background IP Mapping
• Foreground Candidate Identification and Technical Attribution
• Publication, Confidentiality, and Inventorship Constraints Workshop
• Ownership Allocation Decisions and Evidence Standards

• Schedule a follow-up legal redline session to convert provisional allocations into contract language.
• Produce inventor and contributor lists for top-priority candidates.
• Prepare evidence packages for the allocation workshop, including timestamps and authorship metadata.
• Review applicable publication policies and sponsor obligations
• Agreed publication constraints matrix with embargo windows and review timelines per candidate.
• List of immediate interim protections required to preserve commercial rights.
• Documented approval process for any academic or public disclosures.
• Produce a publication constraints matrix that maps candidates to embargo periods and approval steps.
• Prepare and submit proposed interim patent or confidentiality filings where agreed.
• Draft a publication review workflow and notification template for contributor use.
• Recap evidence collected and outstanding gaps
• Provisional ownership allocation ratified for each prioritized foreground candidate.
• Defined evidence standards and a list of remaining deliverables needed for legal sign-off.
• Clear list of contract clauses and governance points to include in the term sheet and draft JDA.
• Produce an ownership allocation summary document mapping each candidate to provisional owner, evidence status, and required next deliverables.
• Collect outstanding evidence items to meet the defined evidence thresholds for legal sign-off.
• Draft term sheet language and clause list reflecting the agreed allocations and submit for legal review.
• Confirm engagement scope and success criteria
• Finalized list of stakeholders with decision rights and contact points.
• Prioritized document and evidence intake checklist for each component.
• Confirmed schedule for component-level workshops and secure file exchange method.
• Distribute the document and evidence intake checklist to all stakeholders for upload to the secure folder.
• Schedule component-level mapping sessions and send calendar invites with prepared component lists.
• Collect initial contributor declarations or inventor name lists to enable inventorship tracking.
• Provision access to version control snapshots and lab notebook extracts for review.
• Recap component scope and available materials
• Complete background IP map for the component with referenced evidence links.
• Prioritized list of evidence gaps that could affect ownership allocation.
• Named follow-up investigations and deadlines to close critical gaps.
• Collect and attach missing evidence items identified in the session to the component folder.
• Produce a component background IP map document for review in the allocation workshop.
• Initiate targeted investigations for high priority gaps, such as retrieving commit histories or lab notebook entries.
• Confirm foreground identification criteria
• Prioritized list of foreground candidates with technical descriptions and initial attribution hypotheses.
• Named evidence needed per candidate to support or refute the attribution hypothesis.
• Gather version control commits, design files, and test results that map to each prioritized candidate.
• Identify stakeholders and decision rights
• Map publication risk against prioritized foreground candidates
• Present allocation recommendation per candidate
• Review development activities and outputs against criteria
• Walk component design and development history
• Map declared background ownership and third-party encumbrances
• Agree evidence thresholds and sign-off criteria
• Document technical boundaries and contribution lines for each candidate
• Surface components, modules, and technical interfaces
• Define embargo periods, redaction rules, and approval timelines
• Decide interim confidentiality and filing actions
• Establish document and data intake checklist
• Prioritize candidates for ownership allocation
• Record contract implementation items and next steps
• Identify and prioritize evidence gaps
• Agree next-step investigations
• Agree timeline, milestones, and communication rules

• IP Framework Walkthrough

• You confirm the proposed background/foreground allocation for the reviewed scenarios removes the ownership ambiguity that was delaying engineering.
• Confirm the current state and its cost to your team
• Provide the two highest-priority co-development scenarios, including referenced background assets and any publication or supplier constraints within 3 business days.
• Present the two highest-priority co-development scenarios
• You agree the proposed licensing scopes preserve the commercialization freedoms and exclusivity you require for those scenarios.
• Deliver a written mapping of background/foreground allocation and draft license term bullets for each reviewed scenario within 5 business days.
• Prepare a draft approval matrix and governance checkpoint language for internal review within 5 business days.
• You accept the governance checkpoints and publication controls as adequate to prevent unintended disclosures and to enable timely approvals.
• Apply the proposed background/foreground separation to Scenario A
• Confirm the internal decision-maker list and required approval timelines for IP and commercialization terms within 3 business days.
• Apply the proposed separation to Scenario B and compare outcomes
• Walk through licensing scopes and commercialization rights
• Review governance, approval checkpoints, and publication controls
• Validate alignment
• Confirm next commitments and timelines

• IP Framework Walkthrough
• IP Framework Walkthrough Deck
• IP Framework Solution Brief

• meeting
• slides
• document

• Prepare IP-focused Term Sheet
• Draft Joint Development Agreement
• Negotiate JDA Terms with Counterparty
• Draft IP Allocation and Ownership Clauses
• Draft Background and Foreground IP Schedules
• Draft License Grants and Scope Limitations
• Draft Commercialization and Exploitation Rights
• Draft Confidentiality and Data Rights Provisions
• Draft Publication and Academic Collaboration Clauses
• Create Governance and Steering Committee Charter
• Draft Termination, Transition, and Survivability Provisions
• Draft Patent Prosecution and Inventorship Protocols
• Draft Regulatory Compliance and Data Privacy Clauses
• Prepare Enforcement, Remedies, and Dispute Resolution Clauses

Prepare IP-focused Term Sheet

• Who in your organization must sign the term sheet (title and role) and who will be the day-to-day point of contact for redlines?
• Which commercial outcomes should the term sheet prioritize for your technology (exclusive licensing, field-limited rights, joint ownership, revenue share)? Options: Exclusive license in defined field, Non-exclusive license, Joint ownership with defined fields, Revenue-share arrangement, Other (explain)
• How should background IP be listed on the term sheet: as a summarized catalogue by patent family and code repository, or as a full schedule with provisional application numbers and source-control paths? Options: Summarized catalogue (patent families + repos), Full schedule with application numbers and repo paths, Hybrid (summary plus key entries), Undecided
• When do you need the final term sheet delivered relative to your engineering milestone (for example, before first prototype delivery or before first public data release)? Options: Before prototype delivery, Before public data release, Before pilot manufacturing run, Within a specified number of business days
• Provide the specific deliverables you expect from the term sheet (for example, a redline-ready PDF, annotated commercial term table, and an issues log tied to JIRA ticket IDs).
• Identify the top three IP risks (for example, published manuscripts that may preclude patenting, third-party standard-essential patents, supplier-supplied components with restrictive licenses).
• Estimate the number of patent families and code repositories that must be referenced in the term sheet (provide counts for patent families and git repository URLs or names).
• Specify any fixed commercial thresholds that must be included in the term sheet (for example, minimum annual purchase volumes, milestone payments tied to clinical endpoints, or royalty bands tied to net sales).
• Confirm the acceptance evidence that will validate the IP-focused term sheet is complete (for example, signed PDF of term sheet, a cleared redline log, and your authorized signer's written approval). Options: Signed PDF of term sheet, Cleared redline log + approval email, Both signed PDF and cleared redline log, Other (describe)

Draft Joint Development Agreement

• Who should be the internal approver for the draft JDA (title and legal escalation contact) and which external stakeholders require review (for example, head of R&D, export compliance officer)?
• Which technical artifacts will form part of the JDA schedules (for example, lab notebooks, design files, bill of materials, protocol versions)? Options: Lab notebooks, Design files / CAD, Bill of materials (BOM), Clinical or test protocols, Software repositories, Other
• How do you want foreground ownership allocated for deliverables such as prototype hardware assemblies, firmware commits (by commit IDs), and new process SOPs?
• When must the draft JDA be ready to circulate to the other party relative to your product timeline (for example, prior to first pilot run or before filing a provisional patent)? Options: Prior to first pilot run, Before filing a provisional patent, Before public disclosure, Other timeline
• Provide any mandatory clauses that must appear in the JDA for your industry (for example, FDA-specific cooperation on regulatory filings, export control language for controlled tech, or confidentiality tied to clinical data standards).
• Identify any non-negotiable IP positions you require in the JDA (for example, sole ownership of improvements to your background patents, right to sublicense to affiliates, or retention of prosecution control).
• Specify documents or repository evidence you will provide to support the JDA drafting (for example, invention disclosure forms, copies of pending patent applications, commit hashes from source control).
• Confirm the acceptance evidence that will validate delivery of the draft JDA (for example, a redline-ready Word doc with tracked changes and a corresponding issues register). Options: Redline-ready Word doc with tracked changes, Issues register with assigned owners, Both documents, Other (describe)

Negotiate JDA Terms with Counterparty

• Who on your team will lead negotiations and who is authorized to accept commercial compromises (title and approval threshold)?
• Which negotiation channels do you prefer for exchanging redlines and comments (for example, marked-up Word, collaboration platform, or in-person working sessions)? Options: Marked-up Word, Collaboration platform with comment history, In-person working sessions, Video conferencing + shared doc
• How many negotiating rounds do you target before escalation is required (for example, two rounds then legal escalation to GC)? Options: 1 round, 2 rounds, 3 rounds, Open-ended
• When negotiating technical ownership points such as inventorship on patent applications or authorship on manuscripts, which internal teams must be present in calls (for example, head inventor, lead engineer, compliance officer)?
• Provide the timeline constraints that will limit negotiations (for example, patent filing deadlines, regulatory submission dates, or manufacturing ramp milestones).
• Identify acceptable interim protections while negotiations continue (for example, mutual non-assert covenants, scoped work pauses, or escrow of source code commits). Options: Mutual non-assert covenant, Scoped work pause, Escrow of source code commits, Interim confidentiality addendum, Other
• Specify any negotiation topics that must be reserved for executive-level approval (for example, IP assignment, exclusive commercialization rights, or indemnity caps).

Draft IP Allocation and Ownership Clauses

• Which model of IP allocation do you prefer to start from: strict background-retained with licensed foreground, joint ownership by contribution, or contribution-weighted ownership with defined evidentiary standards? Options: Background retained + licensed foreground, Joint ownership by contribution, Contribution-weighted ownership with evidence standards, Undecided / need guidance
• How should inventorship and contribution be evidenced for hardware and software artifacts (for example, signed invention disclosure forms, git commit diffs, lab notebook entries with timestamps)? Options: Signed invention disclosure forms, Git commit diffs with issue IDs, Lab notebook entries with timestamps, Test protocol logs, Combination of above
• Who will maintain the single source of truth for contribution evidence (for example, a shared repository, a designated legal folder, or a project management board)? Options: Shared code repository, Design document repository, Legal document folder, Project management board, Other
• When allocating ownership of jointly-developed firmware or algorithm improvements, what thresholds must be met to trigger sole ownership (for example, >50% of inventive contribution by commits or specific claim language drafted)?
• Provide any industry-specific constraints on ownership allocation we should reflect (for example, academic publication rights that limit assignment, or supplier agreements that prohibit assignment of improvements).
• Identify any patent prosecution controls you require tied to ownership (for example, sole prosecution control for inventions claiming your background tech, or joint prosecution committee).

Draft Background and Foreground IP Schedules

• Which specific patent families, provisional filings, software repositories, and material specifications must be listed on the background IP schedule (please list application numbers and repository names or provide a spreadsheet)?
• How granular should foreground schedules be: per-artefact (each prototype ID, each commit hash, each experiment protocol) or by project milestone (alpha, beta, production)? Options: Per-artefact (prototype ID, commit hash, protocol), By project milestone, Hybrid approach
• Who will be responsible for maintaining and updating the schedules during development and how often (for example, weekly updates by project manager tied to sprint reviews)? Options: Weekly by project manager, After each sprint, Monthly by legal team, On-demand as artifacts change
• What evidence will validate acceptance of the background and foreground schedules (for example, an agreed Excel schedule, repository snapshots, and signed acknowledgements)? Options: Agreed Excel schedule with signatures, Repository snapshot archive (tarball) + hash, Signed acknowledgements from both parties, Combination of above
• Specify any exclusions from the schedules (for example, third-party open-source components, supplier-provided toolchains, or pre-existing datasets).
• Indicate whether publication or academic collaboration artifacts must be redacted from schedules and, if so, which manuscript IDs or conference submissions are affected.

Draft License Grants and Scope Limitations

• Which license model do you need for background IP used by the other party: royalty-free internal-use, paid field-limited license, or per-product royalty-bearing license? Options: Royalty-free internal-use, Field-limited paid license, Per-product royalty-bearing license, Other (describe)
• How should sublicensing be handled for software and hardware blueprints (for example, permitted to affiliates, permitted with reporting, or prohibited)? Options: Permitted to affiliates, Permitted with reporting/consent, Prohibited, Permitted under specific commercial terms
• Who will define the field-of-use definitions for licenses (for example, product categories, end markets, or regulated use cases like clinical diagnostics)?
• Specify any quantitative scope limits required (for example, maximum units per year, geographic exclusions, or channel restrictions tied to SKU lists).
• Identify required compliance checks for licensed software components (for example, open-source license scans, export-control screening, or FIPS cryptography requirements). Options: Open-source license scan, Export-control screening, FIPS compliance check, Other

Draft Commercialization and Exploitation Rights

• Which commercialization rights do you require for jointly-developed products (for example, exclusive rights in defined territory, co-marketing rights, or first-refusal on manufacturing)? Options: Exclusive rights in territory, Co-marketing rights, First refusal on manufacturing, Non-exclusive commercialization
• How should revenue split or royalty tiers be structured against commercial milestones such as regulatory approval, first commercial sale, and attainment of sales thresholds?
• Who must approve pricing and distribution partners for jointly commercialized products (for example, head of BD, head of sales)?
• Specify any carve-outs that must exist for internal use, research use only, or continued independent development by your teams.
• Indicate the metrics you will use to measure successful commercialization (for example, units sold, signed distributor agreements, or recorded net sales). Options: Units sold, Distributor agreements signed, Recorded net sales, Other

Draft Confidentiality and Data Rights Provisions

• Which data types require the strictest controls (for example, raw clinical trial data, material composition files, source code, or customer usage telemetry)? Options: Raw clinical data, Material composition files, Source code, Customer telemetry, Other
• How should dataset ownership and access be handled for shared test datasets, annotated images, and training sets for models (for example, joint access, licensed access, or segregated read-only mirrors)? Options: Joint access, Licensed access, Segregated read-only mirrors, Third-party data escrow
• Who will retain copies of confidential source code and where will they be stored (for example, your secure repository, an escrow, or a mutually accessible encrypted bucket)? Options: Your secure repository, Escrow, Mutually accessible encrypted bucket, Other
• When may datasets or technical reports be shared outside the project team and what approval workflow is required (for example, legal sign-off plus data steward approval)?
• Specify retention and destruction schedules for confidential materials such as lab notebooks, raw data files, and prototype hardware at project end.

Draft Publication and Academic Collaboration Clauses

• Which publication channels are relevant for your work (for example, peer-reviewed journals, conference proceedings, or preprint servers) and which require embargo handling? Options: Peer-reviewed journals, Conference proceedings, Preprint servers, Patent-first embargo required
• How long of a review period do you require for manuscripts or abstracts before submission to protect patent filing opportunities (for example, 30 days, 60 days)? Options: 15 days, 30 days, 45 days, 60 days, Custom
• Who will be responsible for coordinating author lists and acknowledgements tied to student contributors, inventors, and corporate scientists?
• Specify any data redaction or anonymization standards that must be applied before publication (for example, removal of patient identifiers per HIPAA, or masking of supplier part numbers).
• Identify scenarios where publication must be blocked entirely (for example, if filing a patent would be prejudiced or if material contains export-controlled technical data).

Create Governance and Steering Committee Charter

• Who from your organization must sit on the steering committee (role names such as head of R&D, head of IP, VP of BD) and who will be an alternate?
• Which decision rights should the charter reserve for the steering committee (for example, approving prosecution strategy, authorizing sublicenses, or pausing work streams)? Options: Approve prosecution strategy, Authorize sublicenses, Pause work streams, Adjudicate disputes
• How often should the steering committee meet and what artifacts should be pre-circulated (for example, sprint reports, IP logs, and financial burn charts)? Options: Weekly, Bi-weekly, Monthly, Quarterly
• Provide the escalation path from project team to steering committee to executive decision-makers for disputed IP claims or commercialization disagreements.

• Non-Disclosure & Data Authorization Agreement
• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Fee Schedule & Payment Terms
• Approval & Escalation Protocol
• Background IP Access & Interim Protections Addendum

• Technical Health Check
• Commercial Metrics Review (day 60 to 90)
• Bilateral Obligations Audit (around day 90)
• Roadmap Alignment Review (quarterly ongoing)

• Circulate the quarterly monitoring checklist that specifies metric reporting cadence and formats tied to Engagement Scope targets.
• Schedule a verification checkpoint to confirm remediation items are closed and evidence accepted.
• Restate documented obligations and acceptance criteria
• Produce a documented audit outcome that records pass/conditional/fail per contractual obligation for the initial period.
• Agree a timebound remediation plan that converts any conditional or failed obligations to compliant status within a defined window.
• Publish the bilateral obligations audit report listing each obligation, its status, required evidence, and remediation dates.
• Provide missing evidence packages for any items marked conditional or failed within the agreed remediation timeline.
• Review product and commercialization roadmap updates
• Lock in the next quarter's prioritized commercialization and development activities with named owners and dates.
• Reduce the open risk items list by agreeing on closures and setting follow-up verification for remaining items.
• Publish the updated roadmap excerpt showing prioritized activities, owners, and quarter targets.
• Update the risk register with agreed closure dates and required evidence for each remaining open item.
• Confirm integration and environment go-live
• Confirm the shared development environment is accessible and any critical defects are assigned remediation owners with dates.
• Verify interim IP protection measures are operational and evidence capture workflows are active.
• Publish the prioritized defect list with mitigation steps and target resolution dates.
• Deliver a checklist of interim IP evidence items required per workstream for daily capture.
• Schedule a follow-up technical sync for any blockers unresolved within 7 days.
• Present commercialization and milestone metrics
• Agree a remediation plan that addresses the primary causes of any shortfall in on-time milestone completion rate and royalty reporting accuracy.
• Confirm the evidence and reporting format required to demonstrate metric remediation to satisfaction of the parties.
• Reconcile commercial reports and deliver a corrected royalty payment ledger within 10 business days.
• Produce a milestone recovery schedule showing tasks, owners, and new target dates aligned to Engagement Scope targets.
• Provide the standardized evidence package template for commercialization events and payment submissions.
• Co-review risk register and IP-use incidents
• Review commercialization license activity and payments
• Triage active defects and incidents
• Present evidence for each obligation
• Confirm prioritized activities and owners
• Formal acknowledgment and pass/fail recording
• Diagnose root causes for metric gaps
• Validate interim IP protections and evidence capture
• Agree corrective actions and timelines
• Open technical blockers and resolution timing
• Agree remediation plan for any unmet obligations
• Agree monitoring cadence and evidence requirements