Quick Alignment Check — Who's in the Room?

• Who from your team is leading this collaboration and what are their titles?
• Which role on your side will be the final decision-maker for IP and commercial terms? Options: General Counsel / Chief Legal Officer, Head of IP / Patent Counsel, CTO / Head of Engineering, VP, Business Development, CEO / Founder, Procurement, Board-level approval required, Other
• Who from the partner side is driving this project (names and titles) and how do they typically make decisions?
• Which internal teams should we engage early to avoid surprises? Options: Legal, IP/Patent, R&D / Engineering, Product Management, Business Development / BD, Regulatory / Compliance, Procurement, Finance, Other
• Have you used external counsel for similar joint development agreements before? If so, who and what was their role?
• Who will own day-to-day communications with our team (name, role, contact info)?

Who's Actually Calling the Shots?

• If a senior executive and your IP team disagree, whose position has historically carried the day? Options: IP team, Business leadership (CEO/COO), General Counsel with executive backing, Board-level decision, Varies by deal
• Do you have defined approval thresholds (e.g., dollar value, exclusivity breadth, patent scope) that automatically trigger board or C-suite sign-off? Options: Yes — board-level for thresholds, Yes — C-suite for thresholds, Yes — specific thresholds exist, No formal thresholds, Unsure
• Describe a recent internal decision conflict over a deal—how long did it take to resolve and what was the outcome?
• Who has veto authority on commercialization, exclusivity, or assignment provisions? Options: General Counsel, Head of IP, CEO / Founder, Board, Regulatory / Compliance lead, No single veto — collective approval
• What level of negotiation authority has been delegated to the deal lead (e.g., sign term sheet, finalize contract, recommend only)? Options: Full authority to sign, Authority to sign term sheet only, Recommend with required approval, Limited day-to-day authority, No negotiation authority — must escalate

Deadlines That Can't Move — Where's the Pressure Coming From?

• Imagine engineering hits a critical milestone while we're still negotiating the JDA — what is the worst realistic consequence for your business?
• Which external or internal deadlines are driving urgency on this deal? Options: Product launch date, Regulatory submission, Funding round / investor commitment, Customer contractual milestone, Partner's internal roadmap, Patent filing window, Other
• Which of those deadlines are absolutely fixed versus ones that can be shifted with stakeholder alignment? Options: All fixed, Some fixed, some negotiable, Mostly negotiable, Unsure / need to confirm
• How much runway do you have before missing a technical window becomes irrecoverable? Options: Less than 2 weeks, 2–6 weeks, 6–12 weeks, 3 months or more
• Have you paused development previously because legal terms weren’t in place? Tell us what happened and how it affected momentum.
• Would interim protections (tight NDA, short-term interim license, scoped carve-outs) help keep engineering moving while we finalize the JDA? Options: Yes — interim license, Yes — tightened NDA and safeguards, Possibly — depends on scope, Prefer to wait for full JDA, Unsure

Non-Negotiables & Red Lines — Tell Us What You Won't Compromise

• If we proposed a typical split of foreground ownership, what part of that proposal would immediately make you uncomfortable and why?
• Which of the following are absolute deal-breakers for your organization? Options: Loss of ownership of foreground, Partner gets exclusive commercialization rights, Broad license to our background IP, Unrestricted publication rights for partner, Assignment to third parties without consent, Weak termination/transition rights, Other
• For each non-negotiable you flagged, explain the real-world harm you'd expect if it were breached.
• Do you require field-of-use, territory, or customer-segment carve-outs? If yes, specify which and why. Options: Global rights acceptable, Specific countries only, Industry vertical carve-outs, Existing customers only, No carve-outs required, Other
• How flexible are you on licensing scope if we can implement stronger governance, audit, or revenue-share protections? Options: Very flexible, Somewhat flexible, Not flexible, Unsure / depends on terms
• What mitigations would make you comfortable compromising on an otherwise non-negotiable point (examples: escrow, enforced contribution records, step-in rights)?

Trust, Past Scars, and Hidden Risks

• What's the one collaboration mistake you would do anything to avoid repeating in this JDA?
• Have you had IP disputes with partners before? Select the outcome that best matches your experience. Options: Yes — litigation, Yes — settled contractually, Yes — internal remediation without public dispute, No prior disputes, Prefer not to say
• How do those past experiences shape the people and safeguards you want involved now?
• Which operational controls do you already use to reduce collaboration risk? Options: Contribution logs / provenance records, Code repos with contributor agreements, Publication review committee, Escrow or source-code escrow, Audit rights for partner, Maintained background IP register, Employee invention assignment policies, Other
• Where do you feel most vulnerable today—technical leakage, mis-attribution of contributions, commercialization surprises, or something else?
• Would you accept a joint audit process or independent third-party review to resolve disputed contributions? Options: Yes, Maybe — with defined scope, No, Unsure

Technical and Legal Reviewers — Who Needs to Sign Off?

• Who on your technical team would reject IP language that doesn't map to how your engineers actually build, and why?
• Please list specific reviewers we should expect from legal and technical teams (name, role, domain expertise, best contact).
• What review cycles and turnaround times do those reviewers typically require? Options: 1-week turnaround, 2-week turnaround, 3–4 weeks, Formal legal redline + commentary, Technical proof-of-concept validation required, Patentability or prior-art assessment, Other
• Do you have internal templates, prior JDAs, or playbooks we should review before drafting?
• Who maintains the authoritative records for your background IP and prior art (patent counsel, R&D lead, knowledge management, other)? Options: Patent counsel / external patent firm, Head of IP / in-house, R&D lead / engineering, Knowledge management or KM system, Other
• Are there external regulators, third-party licensors, or grantors whose approval will be required for IP allocation or publication?

Decision Path: How We Get to Yes (or No)

• What could cause this deal to unexpectedly fail at the final contract stage?
• Which documents will the decision-maker expect to see before giving approval? Options: Term sheet / commercial summary, IP landscape and risk memo, Contribution matrix (background vs foreground), Draft JDA, Budget impact analysis, Risk register, Reference agreements
• Walk us through your ideal timeline from term sheet to signature — list gates, dates, and who signs at each gate.
• What negotiation cadence accelerates approval in your experience? Options: Weekly touchpoints with stakeholders, Bi-weekly negotiation cycles, Ad-hoc rapid sessions as issues arise, Single intensive negotiation window, Monthly checkpoints
• Which concessions are you prepared to make to accelerate execution, and which must remain off the table?
• Who should receive a short executive briefing summarizing IP and commercial risk once we have a draft? Options: General Counsel, Head of IP, CTO, CEO / Founder, VP, Business Development, Board member, Other

Next Steps — Small Wins to Keep Momentum

• If we could secure only one commitment from you today that would materially advance this deal, what would it be?
• Which immediate next steps would you prefer we start with? Options: Share existing background IP register, Provide key stakeholder contacts, Schedule a 60‑minute kickoff workshop, Share prior JDAs / templates, Commission a quick IP landscape memo (2–3 weeks), Execute or update an NDA
• When are your key stakeholders available for a 60‑minute kickoff in the coming weeks? Please provide date ranges and time-zone preferences.
• What materials would make that kickoff most productive (pick examples we should prepare)? Options: Contribution matrix template, IP checklist and decision map, Sample JDA clauses, Draft term sheet, High-level risk summary, Other
• Who must be on the invite list (names and roles), and who is optional?
• How would you like us to handle sensitive attachments and background IP disclosures? Options: Secure portal upload, Encrypted email, Provide after signed NDA, Only discuss in workshop — no attachments yet, Other

Where Are We Starting From?

• In one or two sentences, describe the core technology, product, or scientific area this co-development will touch.
• Which internal assets do you expect to contribute to the project? (select all that apply) Options: Issued patents, Pending patent applications, Trade secrets / know‑how, Source code repositories, Datasets, Trained ML models, Hardware designs / schematics, Clinical or experimental data, Process documentation, Other (please specify)
• Which internal teams primarily own or maintain those assets? (select all that apply) Options: R&D / Engineering, Product Management, Legal / IP, Data Science / ML, Manufacturing / Ops, Clinical / Regulatory, Business Development / BD, IT / DevOps, Other (please specify)
• How mature are the contributing assets you listed? Options: Research-stage (lab notebooks, proofs of concept), Prototype / internal demo, Beta / limited external testing, Production / deployed capability, Other / mixed maturity
• Give one concrete example (name, file ID, repo path, or patent number) of an asset we must explicitly protect or track.

If Your Tech Were an Open Book, What Would You Lose?

• If our partner gained unrestricted rights to anything built on your platform, what single commercial vulnerability would hurt you most?
• Which background IP do you consider mission‑critical and therefore off‑limits for broad partner use? (select all that apply) Options: Core patents / patent families, Key trade secrets, Customer data or datasets, Proprietary ML models, Hardware design blueprints, Regulatory dossiers / clinical data, Other (please specify)
• Are any of those background assets already subject to licenses or encumbrances that could limit how you allocate rights to a partner? Options: Yes, No, Unsure
• If you answered Yes or Unsure, list the licenses, counterparty names, or obligations that might constrain us (license IDs, sponsor agreements, cloud provider terms, etc.).
• How would losing exclusivity over the assets you listed change your go‑to‑market or competitive position?

What Are We Walking Into — Risk First?

• What prior‑art or clearance issues would make the joint output legally unusable or expose you to third‑party claims?
• Has any IP clearance, FTO (freedom‑to‑operate), or prior‑art search been done for the proposed scope? Options: Completed — no major issues, Completed — issues identified, In progress, Planned but not started, No search performed
• If a search has been done or is in progress, summarize key findings or provide reference IDs (patent families or search report IDs).
• Are there known third‑party patents, standards‑essential patents, or licensors that read on the planned work? Options: Yes — listed below, No known issues, Unsure / need review
• List any identified third parties, patent families, or standards obligations that concern you (owner, family, why it matters).

Who Decides If It's Yours?

• If a dispute over ownership arises, who in your organization will make the final call and do they have budget authority to implement remedies?
• Which internal stakeholders must we align with early on for IP allocation decisions? (select all that apply) Options: General Counsel / CLO, Head of IP / Chief Patent Counsel, CTO / VP Engineering, VP Business Development, Chief Product Officer, Chief Commercial Officer, Research Director, Finance / Budget owner, Other (please specify)
• Which external advisors or governance bodies (institutional tech transfer office, sponsoring agency, investor committee) will need to review the JDA or IP terms? Options: Technology transfer office, University sponsor, Venture investor counsel, Government sponsor, None, Other (please specify)
• How long do your decision‑makers typically need to review and approve IP allocations or licensing language? Options: 48–72 hours, 1–2 weeks, 2–4 weeks, 1–2 months, Longer / depends on matter
• Describe a past situation where internal stakeholders disagreed on IP ownership and how it was resolved.

Where Will New Work Live — The Technical Lineage?

• Exactly where in your architecture, pipelines, or workflows will partner contributions be introduced (modules, repos, datasets, instruments)?
• Will partner code or models be integrated directly into production systems, or kept in isolated sandboxes/repos? (select one) Options: Integrated into production, Kept in segregated sandbox, Containerized with restricted runtime, Hybrid / some integration, some sandbox
• Do you require provenance metadata for every contribution (author, timestamp, dataset version, experimental run), and if so, at what granularity? Options: Yes — per commit/experiment, Yes — per release/batch, Useful but not mandatory, No
• Who will own day‑to‑day maintenance and patching of integrated partner contributions after deployment? Options: Internal team, Partner, Shared ops rotation, Third‑party managed service, Undecided
• List any CI/CD, ELN, LIMS, or audit systems we must integrate with for traceability (repo names, tool names, or contact points).

How Much Freedom Are You Willing To Share?

• Would you prioritize guaranteed commercialization upside (revenue, milestones) or preserving exclusive control over your background technology? Options: Prioritize commercialization upside, Prioritize exclusive control, Seek balanced split, Undecided / need guidance
• Which IP allocation model would you prefer as a starting point? (select all that reflect acceptable starting positions) Options: Background retained; narrow license to partner, Joint ownership of foreground with commercialization carve‑outs, Sole ownership of foreground by one party, Exclusive field‑limited licenses, Cross‑licensing of related background, Revenue/share based commercialization rights, Undecided — want options
• What commercialization controls are non‑negotiable for you (fields, territories, sub‑licensing approvals, OEM restrictions)?
• How tolerant are you of the partner sublicensing or selling components that incorporate jointly developed IP? Options: Not tolerant at all, Tolerant with approval and restrictions, Open if revenue share applies, Depends on field/territory, Undecided
• Would you be open to time‑limited exclusive rights or trial exclusivity in exchange for stricter background protections? Options: Yes, Maybe — depends on terms, No

Where Are the Legal Landmines Hiding?

• Which existing agreements or obligations could unexpectedly grant others rights over your background or newly created IP?
• Do you have sponsored research, grant, or collaborative agreements that mandate publication or grant license rights to sponsors? Options: Yes — list below, No, Unsure — need review
• Do any engineers, contractors, or advisors operate under consulting agreements or invention assignment carve‑outs that might affect ownership? Options: Yes — details below, No, Unsure
• Are there export control, sanctions, privacy, or regulatory constraints that could limit the scope of licensing or cross‑border commercialization? Options: Export control restrictions, Data privacy constraints, Regulatory approvals required, Sanctions issues, None known, Unsure
• List contract names, counterparty contacts, or clause locations we must review immediately (license IDs, sponsor agreements, consultant contracts).

How Will We Prove Who Built What?

• If ownership is challenged, will your current records (commits, lab notebooks, JIRA tickets) likely persuade a court or arbitrator? Options: Yes — strong evidence, Partial — some gaps, No — insufficient records, Unsure
• Which contribution‑tracking systems are already in use and where (select all that apply)? Options: Git / code repos (please list), Electronic Lab Notebooks (ELN), JIRA / issue trackers, LIMS / experiment systems, Data catalogues / provenance stores, Spreadsheets / ad hoc logs, None
• Describe how inventor attribution and contribution declarations are currently documented (forms, workflows, frequency).
• Would you implement a lightweight, auditable contribution ledger or enhanced commit metadata if we provided templates and a simple workflow? Options: Yes — mandatory, Yes — if low friction, Maybe — need details, No
• Who, within your organization, will be responsible for producing evidence during negotiations or a dispute? Options: Head of IP, General Counsel, VP Engineering, Project Manager, Designated evidence custodian, Other (please specify)

What's the Fastest Way This Deal Breaks?

• What specific IP drafting or governance mistakes have caused you to walk away from deals in the past?
• What term or condition is an absolute non‑negotiable for you to proceed with this collaboration?
• Which concessions (if any) would you be willing to trade to preserve your core background rights? Options: Limited commercialization exclusivity for partner, Revenue share or milestones, Time‑limited exclusivity, Wider grantback rights, None — no tradeoffs
• How flexible is your technical timeline if IP terms require deeper legal review (select one)? Options: Can pause for legal work, Can delay by weeks, Timeline is tight — cannot delay, Unsure
• List the internal redlines we must surface immediately to prevent surprises (budget, security, regulatory, IP).

Imagine a Year From Now: What IP Success Actually Looks Like

• Fast‑forward 12 months: what are three measurable IP outcomes that would make this collaboration a clear success for you?
• What ongoing governance structures would make you comfortable after signing (select all that appeal)? Options: Joint IP steering committee, Quarterly technical and IP reviews, Shared contribution ledger with audit rights, Independent IP escrow, Pre‑agreed commercialization milestones, None / ad hoc
• How long should licensing or ownership arrangements remain in effect before mandatory review (select one)? Options: Project lifetime, 1–3 years after termination, 5–10 years, Perpetual unless renegotiated, Other (please specify)
• What post‑termination rights would let you continue development without undue risk (e.g., license back, retained background, source access)?
• Would a pre‑agreed dispute resolution path (mediation then arbitration) increase your willingness to accept tighter IP compromises? Options: Yes — strongly preferable, Maybe — depends on forum and rules, No — prefer court litigation

Quick Orientation — Who's in the Room and What’s Urgent?

• Please introduce yourself, your title, and your primary responsibility for this joint development project.
• Which best describes your organization? Options: Startup / Scaleup, Mid-market company, Large enterprise, University or research institute, Contract manufacturer / supplier, Other
• Who is the ultimate decision-maker for IP allocation, publication approvals, and escalation on your side? Options: General Counsel / Head of Legal, Head of IP / Chief IP Counsel, CTO / Head of Engineering, VP of Business Development, Board or C-suite collective, Other
• Which internal teams must be involved in pre-deployment readiness and ongoing governance (pick all that apply)? Options: R&D / Engineering, Legal / IP, Regulatory / Compliance, Product / Commercial, Security / Privacy, Quality / Manufacturing, IT / DevOps, Other
• How soon does engineering expect to resume active development under this collaboration (be realistic)? Options: Immediately / already resuming, Within 2 weeks, Within 1 month, 1–3 months, 3+ months, Unsure
• Briefly list prior JDAs, collaboration templates, or publication policies you’ve used that are relevant here (names, dates, what worked/didn’t).

If We Don’t Lock This Down, What Breaks at 2am?

• What would keep you awake at 2am about contribution tracking, publication review, or regulatory exposure if these aren’t confirmed before engineering continues?
• Have you previously experienced a breach, dispute, or surprise arising from poorly tracked contributions or premature publication? Options: Yes — major dispute, Yes — minor issue resolved, No
• If a partner asserted ownership over technology built on your background IP, what would the likely business impact be? Options: Severe — threatens product/commercial roadmaps, Moderate — manageable but costly, Minor — limited impact, Unclear / depends on details
• Describe any specific past incident where a publication, missing audit trail, or unclear license harmed a patent filing, regulatory approval, or commercial negotiation.
• Which outcomes are non-negotiable for you before engineering continues (e.g., ability to independently commercialize, publication approval delays, exclusivity carve-outs)?

Where Does the Valuable IP Actually Live — and Where Will They Touch It?

• Which of the following asset types do you consider strategically core and likely to be touched by the partner? Options: Source code / firmware, Hardware designs / schematics, Data sets / training data, Assay or protocol know-how, Prototypes / tooling, Patents / patent applications, Trade secrets / processes, Other
• List the specific components, modules, datasets, or processes that you believe must remain protected or clearly designated as background IP — please name them and explain why.
• Are any of these assets already licensed, encumbered, or subject to third-party obligations (open-source licenses, vendor agreements, sponsored research terms)? Options: Yes — multiple encumbrances, Yes — single encumbrance, No known encumbrances, Unsure — need to confirm
• How do you currently distinguish background (pre-existing) from foreground (project-created) in practice — documentation, contribution records, or informal memory? Options: Formal contribution ledger / log, Commit history + ticket linkage, Lab notebooks / ELN, Email/meeting notes, Informal memory / verbal, Other
• Give one specific example where the line between background and foreground is ambiguous in this project and why that ambiguity worries you.

Who Holds the Keys — Decision Rights, Reviewers, and Publication Controls

• If an engineer proposes a conference paper or a code release tomorrow, who on your side has the authority to delay or block publication and would they actually act? Options: General Counsel / IP lead, CTO / Technical lead, Regulatory lead, Commercial lead, No single owner / collective decision, Other
• Describe your desired publication review workflow (steps, reviewers, maximum review time) and any absolute veto rights you require.
• How many reviewers and which disciplines must sign off on any public disclosure (pick all that should be required)? Options: Legal / IP, Technical author, Regulatory / Compliance, Business / Commercial, Partner’s review, Other
• What maximum turnaround time is acceptable for publication review that won’t stall engineering (pick one)? Options: 24–48 hours, 3–5 business days, 1–2 weeks, Longer — acceptable for high-risk publications
• What escalation path do you want if reviewers disagree (e.g., arbitration, neutral technical committee, expedited legal decision)? Options: Internal final sign-off by GC/IP lead, Joint technical committee, Third-party independent reviewer, Pre-defined arbitration, Other

Are Your Systems Ready to Prove Who Built What (and When)?

• Can you produce a tamper-evident, timestamped record today that links contributions to individuals and tickets/requirements? Options: Yes — full traceability across systems, Partial — some systems have traceability, No — mostly manual or missing, Unsure
• Which tools and repositories hold the project artifacts we must be able to audit (choose all that apply)? Options: Git (GitHub/GitLab/Bitbucket), Issue trackers (JIRA, Azure Boards), Confluence / Docs, ELN / LIMS, CI/CD logs, S3 / object storage, Other
• Do you use practices that strengthen provenance (commit signing, signed-off-by, issue → commit linkage, mandatory code reviews, time-stamped lab notebook entries)? Options: All in use, Some in use — list which, None currently, Planning to adopt
• How long are audit logs, commit histories, and lab notebooks retained under your retention policy? Options: Less than 1 year, 1–3 years, 3–7 years, 7+ years, Policy varies / unsure
• If we needed to create a joint contribution ledger, who on your team would operate and maintain it (role and backup)?

Regulators, Export Controls, and Third-Party Strings Attached — The Hidden Constraints

• Which external rules or regimes could instantly restrict commercialization or sharing of jointly developed outputs? Options: FDA / EMA / other medical regulators, EAR / ITAR (export controls), GDPR / data protection laws, HIPAA / patient data rules, Grant or sponsor obligations, Competition / antitrust constraints, Other
• Are any aspects of this collaboration subject to government funding, sponsored-research terms, or pre-existing grants that require publication or impose IP terms? Options: Yes — government funding, Yes — corporate sponsor terms, No, Unsure — need to check
• What third-party software, libraries, or datasets are likely to be embedded in the joint deliverable (list key licenses if known)?
• Do you have any absolute restrictions on what can be exported or shared with the partner (e.g., no cross-border transfer of training data, no ITAR-controlled tech)? Options: Yes — strict export controls, Yes — partial restrictions, No, Unsure
• Have regulators or auditors previously flagged issues in similar projects that we should explicitly address now? Options: Yes — multiple flags, Yes — single flag, No, Unsure / need to check

When You Need to Show Your Work — Auditability, Acceptance, and Enforcement

• Imagine an external auditor or judge asks for proof of who contributed key IP — how confident are you that you could provide convincing evidence today? Options: Very confident, Somewhat confident, Low confidence, Not confident at all
• Which artifacts do you rely on to prove inventorship or contribution (choose all that apply)? Options: Signed invention disclosures / lab notebooks, Commits linked to tickets, Design documents with authorship, Meeting minutes / review logs, Emails confirming contributions, Other
• How frequently would you prefer joint audits or reviews of contribution records and compliance (pick one)? Options: Quarterly, Bi-annually, Annually, On milestone completion only, Ad-hoc / when triggered
• If gaps exist, which remediation options would you consider acceptable (reconstruction of records, contributor statements, escrowed artifacts, procedural fixes)? Options: Reconstruction + statements, Escrow of artifacts, Process and tooling upgrade only, Legal remedies / indemnities, Combination, Other
• What immediate next steps would you like us to take together (select and add owners/timelines): run a systems gap analysis, draft contribution ledger template, map publication workflow, or schedule a 2-hour readiness workshop? Options: Systems gap analysis, Draft contribution ledger template, Map publication workflow, Schedule 2-hour readiness workshop, Prepare regulatory constraints memo, Other
• Who on your team should we schedule the readiness workshop with (name, role, and preferred availability windows)?

Quick Check: Where We’re Starting

• Who are the primary people (name + role) we should include when validating contribution records and governance?
• Which of these best describes your organization’s current readiness to support contribution audits? Options: We have detailed contribution logs and version control history, We have partial records but gaps exist, We rely on individual memory and ad hoc notes, We have no formal contribution records
• How do your engineers currently tag or attribute code, designs, or lab results that derive from background IP? Options: Automated commit metadata (SCM), Manual contribution forms, Lab notebooks / ELN entries, No consistent method, Other
• If we had one hour with your IP and engineering leads, what would you want us to learn first?

If Your Joint IP Was Put Under a Microscope Tomorrow…

• What would be the single biggest factual issue that could make ownership of a jointly developed innovation ambiguous?
• How confident are you that your background IP is identified with sufficient granularity to separate it from future foreground? Options: Very confident, Somewhat confident, Not confident, Unsure
• Tell us about a past internal or external dispute (if any) where contribution attribution was challenged—what went wrong?
• Which evidence would you consider decisive in a dispute over joint ownership? Options: Time-stamped repository commits, Signed contribution declarations, Design documents with dates, Lab notebook entries, Meeting minutes/emails, Other

Who Owns the Story? Lining Up Background vs. Foreground

• What’s your working definition of 'background IP' and how was that definition agreed internally?
• Where do you expect the biggest gray areas to appear when we map background to foreground? Options: Algorithm improvements, Hardware integrations, Data/ML models, Regulatory filings, Process optimizations, Other
• Which internal teams are most protective of background IP (rank up to 3)? Options: R&D/Engineering, Product, Legal/IP, Business Development, Regulatory, Other
• Have you previously licensed any background IP that could restrict commercialization under a JDA? If yes, summarize the constraints. Options: Yes, with significant restrictions, Yes, minor restrictions, No prior licenses, Unsure
• Please attach or describe any particularly sensitive background assets that must never be co-owned or sublicensed (names or identifiers).

How Would You Spot a Contribution Before It’s Too Late?

• If a new technical contribution appears in a sprint, what process triggers its capture as a candidate 'foreground'? Options: Automatic SCM tagging rule, Engineer fills a contribution form, Weekly design review captures changes, No process exists, Other
• Who currently has authority to declare that a work product is a joint contribution rather than internal work? Options: Engineering manager, CTO, Legal/IP lead, Project lead, Cross-party governance committee, No one designated
• How quickly can your team produce provenance (who, when, what, why) for a piece of code or experiment result? Options: Within hours, Within days, Within weeks, Cannot reliably produce provenance
• Describe any tools or templates you already use for contribution capture (e.g., CLA, DCO, contribution log, ELN).
• What would reduce friction for engineers in capturing contributions—short checklist, auto-metadata, incentives, training, or something else? Options: Short checklist, Automated metadata capture, Monetary/project incentives, Training and templates, Other

When Enforcement Matters: What Would You Actually Do?

• Imagine the partner begins using a jointly developed component in a commercial product in a way you didn’t expect—what’s the first thing you would want to happen?
• Which enforcement paths would you consider realistic and acceptable (pick all that apply)? Options: Formal dispute resolution/mediation, Injunctive relief, Monetary damages only, Mutual audit and cure period, Renegotiation of license terms, Termination rights
• How risk-averse is your board/legal leadership about entering a JDA where enforcement would require litigation? Options: Very risk-averse, Moderately risk-averse, Comfortable if evidence is strong, Unsure
• What financial or business outcomes would push you to escalate to outside counsel or litigation (thresholds/examples)?
• If enforcement relied on audit rights, what frequency and scope would you require to feel protected? Options: Quarterly full audit, Annual compliance audit, Ad hoc on reasonable suspicion, Limited to specific modules/data, Other

How Tight Do You Need the Gatekeepers?

• Who should sit on any joint governance committee (roles, not people) to balance speed and control? Options: Legal/IP lead, CTO/Head of Engineering, Product lead, Business development, Compliance/Regulatory, Other
• If governance actions require unanimous approval, what practical problems do you foresee?
• Which decisions must be reserved to senior leadership rather than delegated (pick all that apply)? Options: IP ownership re-allocation, Commercialization carve-outs, Publication approvals, Third-party licensing, Termination for convenience, Other
• How much day-to-day autonomy should the engineering teams have inside the governance framework? Options: Full autonomy within guardrails, Limited autonomy with checkpoints, Tightly controlled by governance, Depends on module
• What cadence and meeting format would you prefer for governance check-ins? Options: Weekly standups, Biweekly working group, Monthly steering committee, Quarterly executive review, On-demand meetings for issues

What Does Acceptance Actually Look Like?

• How do you define 'accepted' for jointly developed deliverables—technical spec, test pass, clinical endpoint, or other? Options: Technical performance spec, Automated test suite pass, Regulatory approval milestone, Business KPI met, Other
• Who must sign off on an acceptance—engineering lead, product owner, governance committee, or legal? Options: Engineering lead, Product owner, Governance committee, Legal/IP lead, Other
• What objective evidence would satisfy you that a jointly developed feature meets acceptance? Options: Test reports, Third-party validation, User acceptance feedback, Regulatory sign-off, Deployed production metrics
• If a deliverable meets technical criteria but raises IP overlap concerns, how should acceptance be handled? Options: Block acceptance until IP cleared, Accept with reservation and mitigation plan, Accept and address later, Escalate to governance committee
• Describe a past acceptance process (internal or external) that worked well—what made it effective?

If We Built the Perfect Audit Trail, What Would It Prove?

• What are the non-negotiable data points you need in an audit trail to prove provenance? Options: Author identity, Timestamped commits, Linked design documents, Test results with signatures, Approval emails/records, Other
• How much historical depth should your audit trail include (start date/back to first commit)? Options: Full history back to origin, Past 2 years, Past 12 months, From project kickoff only, Unsure
• Who should be allowed to access audit records, and what privacy or confidentiality controls do you require? Options: Legal/IP only, Engineering + Legal, Designated governance members, External auditors with NDA, Other
• Would a neutral third‑party custodian or escrow of contribution records increase your confidence? Why or why not? Options: Yes, increases confidence, No, internal control is enough, Maybe—depends on cost and terms, Unsure
• What formats or integrations are essential for your audit trail (e.g., Git history, ELN exports, signed PDFs)? Options: Git/SCM history, ELN exports, Automated build logs, Signed PDFs, Database change logs, Other

Publication, Patents, and Regulatory: Who Gets the Loudest Voice?

• What publication or patenting priorities would you want the JDA to protect for your side? Options: First-to-publish academic credit, Commercial patent priority, Trade secret preservation, Regulatory filing timelines, Freedom to file independently
• How sensitive are you to partner-initiated publications or filings that could undermine commercialization? Options: Extremely sensitive, Moderately sensitive, Not very sensitive, Unsure
• Describe an ideal review window for publications or patent filings by the partner that involve joint work. Options: 30 days, 45 days, 60 days, Case-by-case via governance, No review required
• If a publication or filing could jeopardize a commercial strategy, what remedies would you expect to be negotiated? Options: Delay publication, Redaction of sensitive parts, Joint authorship/assignment changes, Prevent filing entirely, Other
• How do regulatory obligations (data retention, approvals) constrain how you want governance and validation to work?

Getting Real About Change & Exit

• If the collaboration ends, what outcome would make you feel the separation was 'clean' regarding IP and commercialization rights?
• Which of these post‑termination rights do you consider essential to retain? Options: Perpetual license to foreground for internal use, Right to continue development independently, Option to purchase partner’s commercialization rights, Continued access to contribution records, None of the above
• How long would you expect obligations like publication review, audit access, or royalty reporting to survive termination? Options: 1 year, 2 years, 5 years, Perpetual for critical modules, Depends on module
• What practical barriers do you foresee to separating engineering teams or codebases after exit? Options: Tightly integrated code, Shared databases, Cross-trained personnel, Insufficient documentation, Other
• Have you experienced fringes of an exit where your team couldn’t use work they helped create? If yes, briefly describe.

Remedies, Risks, and Tolerances — Tell Us the Limits

• What level of commercial exposure (lost revenue, market share impact) would you tolerate before taking legal action over IP misuse? Options: Low (any measurable impact), Moderate (defined threshold), High (material business harm), Only existential threats
• Which of the following remedies feel acceptable to your leadership in IP disputes? Options: Injunctions, Monetary damages, Contractual license adjustments, Mandatory audits and oversight, Mediated settlements
• Are there corporate policies or external commitments (investor conditions, grants, government contracts) that would limit your options for enforcing IP rights? Options: Yes—investor/board constraints, Yes—government/grant restrictions, No limiting policies, Unsure
• How important is predictability of dispute outcomes versus flexibility to pursue aggressive remedies? Options: Predictability is king, Balance both, Prefer aggressive remedies, Unsure
• If we recommended a technically enforceable but operationally heavy control (e.g., escrow + mandatory audits), would you accept it if it reduced legal risk? Options: Yes, accept operational cost, Maybe—need to evaluate cost, No, too burdensome, Unsure

Practical Next Steps — What Will Make This Real?

• Which of these immediate actions would you like us to prioritize after this discovery? Options: Gap analysis of contribution records, Drafting contribution capture templates, Designing governance committee charter, Creating acceptance criteria templates, Setting audit and review cadence
• Who should receive our initial findings and proposed term sheet (roles/email list)?
• What is your ideal timeframe for having governance and validation rules in place before the next engineering milestone? Options: Immediately (within 2 weeks), Short (2–4 weeks), Moderate (1–2 months), Longer than 2 months
• What would convince your leadership to invest in stronger governance now rather than later? Options: Clear ROI or cost avoidance, Case studies of disputes avoided, Board/director insistence, Regulatory requirement, Other
• Finally, what keeps you personally awake about governance and validation in this collaboration?