Tell Us About Your Program

• What is the program or contract name and a one-line objective we should keep front of mind?
• What is your role and how involved will you be in day-to-day decisions for this engagement? Options: VP/R&D, CTO/Head of Tech, Program Manager, Director/Principal Investigator, Procurement/Contracts, Other
• What triggered the need for an external research partner today? Options: Contract requirement / accreditation, Internal R&D gap, Competitive bid/subcontract need, Timeline risk on internal effort, Regulatory/test need, Other
• How urgent is this work on a scale of practical priority? Options: Must deliver to next contract milestone (critical), High priority within 3 months, Planned within 3–6 months, Exploratory—no immediate deadline
• Which technical areas best describe the work you expect (pick all that apply)? Options: Materials science, Autonomous systems/controls, Energy storage/power, Biosciences/assay development, Advanced computing/ML, Systems integration, Other
• Have you tried to solve this internally or with other partners before? Briefly describe what happened.

What’s Kept You Up at Night About This Program?

• If this program misses its goals, what will the real cost be—for the budget, the timeline, and for the team’s credibility?
• What are the single biggest technical unknowns or failure modes that keep you worried?
• Which of these failure modes is most likely to happen based on prior evidence? Options: Scale-up/manufacturability, Test reproducibility, Materials performance, Integration with existing systems, Data quality/validation, Regulatory/compliance
• How do past program overruns or technical surprises still influence how you evaluate outside partners?
• On a scale from 1–5, how much psychological pressure is there to deliver—are leaders watching daily, weekly, or only at milestones? Options: 1 - Low (leaders see milestones only), 2 - Low–moderate, 3 - Moderate (regular updates), 4 - High (leadership checks frequently), 5 - Very high (daily/near-daily scrutiny)
• How do you emotionally weigh the choice between a fast hopeful prototype and a slower, risk‑reduced experiment?

Who Will Be Cheering—or Blaming—When This Delivers?

• Who are the stakeholders who must be convinced for this to move from pilot → funded program → deployment? Options: Program Manager, VP/Director of R&D, Procurement/Contracts, Regulatory/Compliance Lead, Manufacturing/Operations, External customer/Prime contractor, Other
• Who has final authority to select a research partner and sign the SOW or contract? Options: Program Manager, VP/Director, Procurement/Contracts, Legal with stakeholder sign-off, Other
• Which internal teams will need to provide inputs, samples, or access during the pilot? Options: Systems engineering, Manufacturing, IT/security, QA/regulatory, Logistics, None / fully external
• How often have key stakeholders shifted priorities mid‑program in the past 24 months? Options: Never, Rarely, Occasionally, Often, Almost always
• Tell us about one example where stakeholder misalignment cost time or budget—what happened and what would you change?
• How important is having a named technical lead from our side stay for the program duration? Options: Essential, Important but negotiable, Preferable, Not important

Is the Timeline Real—or a Hopeful Target?

• Was the project timeline set to win a bid, meet a contract milestone, or to reflect technical de‑risking needs? Options: Set to win a bid, Set to meet contract milestone, Set based on technical de‑risking needs, Mixed/uncertain
• Which dates are truly immovable (e.g., government deliverable, regulatory deadline)?
• How much contingency is budgeted for schedule slips? Options: None, Small (≤10%), Moderate (10–25%), Significant (>25%)
• When your teams have missed schedules previously, what was the primary cause? Options: Technical complexity, Staffing turnover, Procurement delays, Scope creep, Regulatory/clearance delays, Other
• If a pilot today revealed a new, costly risk, what is the decision path for buying more time or money?
• How would missing the next milestone change your organization’s next steps or funding posture?

Intellectual Property, Data & Controls — Where Are You Willing To Compromise?

• If forced to choose, would you prioritize retaining broad commercialization rights or getting faster, more open collaboration during pilot work? Options: Retain full commercialization rights, Shared/licensing model acceptable, Faster collaboration with limited IP rights, Undecided
• Which IP frameworks are acceptable to you (pick all that apply)? Options: Client retains all IP, Joint ownership, Client exclusive license, Non-exclusive license, Background IP retained by each party, Other
• Are there data residency, export control, or classification constraints we must meet? Options: ITAR/EAR, Controlled Unclassified Information (CUI), FDA/regulatory data constraints, GDPR/personal data, No special constraints, Other
• What contract terms feel like instant deal‑killers to you on IP or publication rights?
• How do you prefer raw experimental data be delivered and archived? Options: Raw datasets + metadata, Curated reports with appendices, Both raw and curated, Only summary reports
• Have you previously negotiated a sponsored research arrangement—what lessons should we know up front?

What Will ‘Success’ Actually Look Like to Your Team?

• Imagine the pilot is complete and you are thrilled—what measurable signals led to that feeling?
• Which of the following acceptance criteria must be met for you to consider the pilot successful? Options: Specific performance thresholds met, Reproducible test results, Scalability demonstration, Passing independent accredited tests, Clear path to commercialization, Other
• What tests, standards, or accreditation bodies do we need to demonstrate compliance with? Options: ISO standards, Third‑party accredited lab, Government/regulatory test protocol, Pharma-specific assays / GLP, Custom client protocol, None specified
• Who signs off on the Go/No‑Go after the pilot, and what evidence do they require? Options: Program Manager, VP/Director, Technical review board, External customer/prime, Other
• What downstream outcomes matter most after pilot success—licensing, internal scale-up, handoff to manufacturing, or sale to a prime? Options: License/IP transfer, Internal scale-up to production, Tech transfer to manufacturer, Handshake to prime contractor, Spin-out / commercialization
• How would you like lessons learned and failure modes documented during the program? Options: Weekly technical notes, Structured lessons-learned deliverable, Real-time issue tracker access, Final consolidated report, Combination

Hidden Gates: Facilities, Security and Practical Constraints

• Do you expect work to be done in our facilities, yours, or a mix—and what is the real barrier to each option? Options: All in our facilities, All in your facilities, Hybrid (both), Undecided
• Which accreditations or lab certifications are required for this work? Options: ISO 17025, GLP, Biosafety level (specify), NIST traceability, DoD/government accreditation, None required, Other
• What security clearances or background requirements must on-site staff meet? Options: Public trust / policy, Secret, Top Secret/SCI, No clearance needed, Facility access only
• Are there chain-of-custody, sample handling, or disposal rules we should plan for?
• Do you have constraints on shipping samples internationally or between facilities? Options: Yes—export controls apply, Yes—biosamples restricted, No constraints, Unsure / need to check
• Would you want joint site visits and walkthroughs before the SOW is finalized? Options: Yes—essential, Helpful but not necessary, No

Money, Contracts and Continuity—The Practical Tradeoffs

• If the program discovers additional work is required to meet success signals, who would fund the incremental scope? Options: Client will fund, Jointly decide funding, Contingent on re-bid, Unclear / need approval
• Which commercial models are acceptable to you for a pilot? Options: Fixed-price pilot, Milestone-based payments, Time & materials with cap, Hybrid (T&M + milestone), Other
• What payment terms and invoicing cadence do you typically accept? Options: Net 30, Net 45, Net 60, Upfront deposit + milestones, Government-specific terms
• How important is having staffing continuity (named PIs or technical leads committed for the program duration)? Options: Mandatory, Very important, Nice to have, Not necessary
• What procurement or contracting hurdles should we expect (e.g., flow-down clauses, FAR/DFARS requirements)?
• Have you worked with CRO-style research contracts before and what contract clause caused the most negotiation time?

The One Critical Question (Pilot Focus & Next Steps)

• What is the single critical technical question the pilot must answer to justify continued investment?
• What would be the minimum viable set of experiments or milestones that would convincingly answer that question?
• What is your target pilot duration and are there immovable windows for tests or samples? Options: 2–4 weeks, 4–8 weeks, 2–3 months, 3–6 months, Flexible
• What deliverables do you need at pilot close to make a Go/No‑Go decision (e.g., raw data, independent report, prototype, test certificate)? Options: Raw datasets + metadata, Independent accredited test certificate, Prototype and build instructions, Technology transfer package, Executive summary + recommendations
• What would make you say ‘we should start this pilot next week’—what factors must align?
• What's the best next step right now to move this conversation forward? Options: Schedule technical deep-dive, Request draft SOW and budget, Facility walkthrough, Pilot proposal within 2 weeks, Other

• Solution Experience Kickoff — Problem & Success Signals
• Failure Modes & Acceptance Criteria Workshop
• Pilot Feasibility Plan — Experiments & De-risking Milestones
• Technical Feasibility Review — Tools, Data & Staffing
• Pilot Approval & Governance Gate

• Ensure a contingency plan and escalation path are in place before pilot start.
• Document necessary lab, security, and data requirements to execute the pilot.
• Ensure each milestone's success is directly tied to reducing the stated consequence and proving the future state.
• Seller to deliver a Pilot Experiment Matrix (experiments, success thresholds, measurement plan) within 3 business days.
• Customer to confirm experimental constraints (e.g., sample limits, access windows) and approve the milestone sequence.
• Reserve required lab time and instrumentation for the first milestone and confirm security/clearance needs.
• Draft a preliminary pilot budget and resource list for customer review.
• Confirm Lab & Facility Fit
• Confirm lab and instrument availability and any constraints that would affect execution.
• Agree a defensible data capture, validation, and custody process for pilot evidence.
• Establish staffing assignments and a continuity plan to avoid knowledge loss.
• Introductions & Meeting Objectives
• Seller to confirm instrument reservation times and calibration schedules.
• Assign named personnel (primary and backup) for each experiment and publish contact list.
• Define and publish the data schema, storage location, and access controls for pilot results.
• Customer and seller to agree contingency cost cap and decision triggers for invoking contingency.
• Recap: Current State, Consequence, Future State
• Obtain formal approval to execute the pilot with agreed scope, metrics, and milestones.
• Establish governance structure, reporting cadence, and decision owners for go/no-go gates.
• Ensure commercial and legal items that block execution are identified and either resolved or scheduled for resolution.
• Customer to sign the pilot SOW and release initial funding or formal go-ahead.
• Seller to publish the Pilot Execution Plan (schedule, owners, experiment matrix) and calendar invites for milestone reviews.
• Legal/commercial owners to resolve any outstanding IP or licensing items flagged before the first milestone.
• Set the first milestone review date and required evidence package to be delivered.
• Produce a single-sentence Current State statement agreed by customer and seller.
• Document measurable consequences (cost, time, risk) tied to the current state.
• Agree a one-sentence Future State (outcome) the pilot must validate.
• Confirm the critical technical question that the pilot will answer and required pre-work.
• Owner to publish the agreed one-sentence Current State to the shared workspace.
• Customer to provide data to quantify consequence (costs, schedule impacts, failure rates) within 3 business days.
• Seller to draft the one-sentence Future State and circulate for confirmation.
• Assign owners and deadlines for pre-work items (documents, samples, access).
• Review Current State, Consequence, and Future State
• Create a prioritized failure-mode list mapped to program impact.
• Produce measurable pass/fail acceptance criteria for top failure modes.
• Agree on measurement methods and required evidence for validation.
• Customer validates that passing the defined metrics equates to achieving the future state.
• Seller to produce a Failure Mode Matrix (mode, consequence, likelihood, acceptance metric) and share within 48 hours.
• Customer to confirm or adjust ranked priorities for failure modes.
• Assign owners for each measurement method and note any required third-party instrumentation or lab needs.
• Define data format and storage location for evidence collected during the pilot.
• Restate Critical Question & Top Failure Modes
• Produce an experiment matrix where each test maps to a failure mode and an acceptance metric.
• Agree a milestone schedule with explicit go/no-go criteria.
• Experiment Matrix: Test -> Metric -> Expected Outcome
• Review Pilot Plan & Milestones
• Craft one-sentence Current State
• Instrumentation, Calibration & Data Capture Plan
• Brainstorm Failure Modes
• Staffing & Continuity Plan
• Quantify the Consequence
• Commercial & Legal Pre-checks (IP, Licensing, Budget)
• Define De-risking Milestones & Go/No-Go Gates
• Prioritize by Impact and Likelihood
• Governance, Reporting Cadence & Escalation
• Resource, Lab, Security & Data Needs
• Define one-sentence Future State (Outcome)
• Define Measurable Acceptance Criteria
• Risk Controls & Contingency Resources
• Final Validation & Sign-off Question

• Fabricate Functional Prototype
• Run Accredited Environmental Tests
• Perform ISO/IEC 17025 Chemical Analyses
• Execute Autonomous Systems Field Trials
• Build Pilot Production Line
• Perform Accelerated Life Testing
• Execute GMP‑Compliant Assay Runs
• Assemble and Validate Sensor Integration
• Perform Materials Characterization (SEM/XRD)
• Deliver Manufacturing-Ready Engineering Drawings
• Produce Technology Transfer Package
• Run Failure Reproduction Test Campaign

Fabricate Functional Prototype

• Do you need a single breadboard prototype or multiple iterated prototypes? Options: Single prototype, Multiple iterations (2-3), Multiple iterations (4+), Undecided
• What are the primary objectives for the prototype (select all that apply)? Options: Functional validation, Form/fit assessment, User evaluation, Manufacturability study, Regulatory submission, Other
• What fidelity is required for the prototype (mechanical, electrical, software)? Describe required performance targets.
• What materials, finishes, or vendor-supplied components must be used or avoided?
• Do you require documentation and deliverables (e.g., BOM, assembly instructions, test reports)? Options: BOM and cost estimate, Assembly instructions, Functional test report, None/just hardware
• What is the target delivery timeline for the prototype effort? Options: 2-4 weeks, 4-8 weeks, 8-12 weeks, 12+ weeks

Run Accredited Environmental Tests

• Which accredited environmental standards or test methods are required? Options: MIL-STD-810, IEC 60068, ASTM, Customer-specified protocol, Other
• What sample types and quantities will you provide for testing? Options: Prototype units, Production samples, Materials only, Subassemblies, Specify in free text
• Which environmental conditions must be exercised (temperature, vibration, shock, humidity, salt fog, EMI/EMC)? Options: Temperature, Vibration, Shock, Humidity/condensation, Salt fog/corrosion, EMI/EMC, Other
• Is an accredited test report/certificate required for procurement or regulatory submission? Options: Yes, certificate required, Report only (non-accredited), No formal report required
• Are there packing, handling, or fixture constraints for the test samples (e.g., explosive, classified, sterile)? Options: Yes - special handling, No special handling, TBD (will advise)
• What is the expected schedule window for testing and how will test failures be handled (retest, modify, cancel)?

Perform ISO/IEC 17025 Chemical Analyses

• Which chemical analyses or assays under ISO/IEC 17025 accreditation do you require? Options: Contaminant quantification, Material composition, Residual solvents, Potency/assay, Other
• What sample matrix and quantity are available (solid, liquid, gas; mass/volume)?
• Are chain-of-custody, cold chain, or traceability controls required for samples? Options: Yes - chain-of-custody required, Cold chain required, No special requirements
• Do results need to be accompanied by method validation, uncertainty, and LOQ/LOD reporting? Options: Yes - full validation metrics, Yes - basic uncertainty, No, summary results only
• Is pre-approved SOP/method required or should the lab propose methods? Options: We will provide SOP/method, Lab to propose validated method, Hybrid (we provide references)
• What turnaround time do you require for analysis and certified reporting? Options: 48-72 hours, 1-2 weeks, 2-4 weeks, Flexible

Execute Autonomous Systems Field Trials

• What autonomy function(s) must be validated during field trials (navigation, perception, control, swarm/cooperative behaviors)? Options: Navigation/localization, Perception/object detection, Control/stability, Path planning, Swarm/cooperative
• What operating environment and constraints apply (urban, rural, maritime, GPS denied, classified airspace)? Options: Urban, Rural, Maritime, Indoor/GPS-denied, Restricted/controlled airspace, Other
• How many vehicles/platforms and what configuration (fully integrated, sensor-only payload, software-in-the-loop)?
• What safety, regulatory, or range approvals are required before trials (NOTAM, flight waivers, range access)? Options: Flight waivers/NOTAM, Range safety briefings, Regulatory approvals needed, None/applicant will advise
• What data products and telemetry must be collected and delivered (raw sensor logs, annotated video, performance metrics)? Options: Raw sensor logs, Annotated video, Performance metrics, Health/diagnostics logs, Other
• What are success criteria and acceptable failure modes for the field trial?

Build Pilot Production Line

• What annualized throughput or batch size is the pilot line expected to achieve? Options: <100 units/month, 100-1,000 units/month, 1,000-10,000 units/month, Custom/describe
• Which production processes must be included on the pilot line (assembly, soldering, coating, CNC, molding, test/QA)? Options: Manual assembly, Automated assembly, Soldering/SMT, Molding/overmolding, CNC/precision machining, In-line test/QA
• What quality standards or certifications must the pilot line meet (ISO 9001, AS9100, GMP)? Options: ISO 9001, AS9100, GMP, Customer-specific QMS, None
• Will the pilot line require supplier-managed components or fully in-house fabrication? Options: In-house fabrication, Supplier-managed subassemblies, Hybrid
• What staffing model do you expect for the pilot (operator count, engineers, QC)?
• What is the target timeline from line design to first article availability? Options: 4-8 weeks, 8-16 weeks, 16-24 weeks, 24+ weeks

Perform Accelerated Life Testing

• Which accelerated stressors are required (temperature cycling, HALT, vibration, humidity, UV)? Options: Temperature cycling, HALT, Vibration, Humidity, UV/solar exposure, Other
• What end-of-life criteria or failure thresholds define test completion?
• How many samples and what lot distribution will be provided for ALT? Options: 1-3 samples, 4-10 samples, 10+ samples, Specify in free text
• Do you require environmental chamber traceability, calibrated sensors, and time-temp logs with the report? Options: Yes - full calibration traceability, Basic logging only, No requirements specified
• Should results include Weibull/MTTF modeling or statistical life projections? Options: Yes - Weibull/MTTF, No - pass/fail only, Discuss options
• What turnaround and contingency plan do you expect if units fail early in ALT?

Execute GMP‑Compliant Assay Runs

• What assay type and throughput are required (ELISA, PCR, potency, stability)? Options: ELISA, qPCR/RT-PCR, Potency assay, Stability testing, Other
• Do samples require controlled chain-of-custody, biosafety level handling, or controlled substances licensing? Options: Chain-of-custody required, Biosafety handling required, Controlled-substance license required, No special requirements
• Are validated methods and GMP documentation (batch records, SOPs) required to accompany results? Options: Yes - full GMP documentation, Method validation only, No, research-grade reporting
• What release criteria and acceptance ranges will you accept for assay outcomes?
• What sample volumes/quantities and stability/storage conditions apply?
• What turnaround time is required and is on-site inspection or audit requested? Options: 48-72 hours, 1-2 weeks, 2-4 weeks, On-site audit required

Assemble and Validate Sensor Integration

• Which sensors and interfaces must be integrated (camera, lidar, IMU, chemical sensor, CAN, Ethernet)? Options: Camera, Lidar, IMU/INS, Chemical sensor, CAN/LIN, Ethernet/ROS
• What validation tests are required (latency, accuracy, calibration, environmental robustness)? Options: Latency/performance, Accuracy/calibration, Thermal/vibration robustness, EMI susceptibility, Other
• Do sensors require custom firmware, drivers, or middleware integration (ROS nodes, SDKs)? Options: Custom firmware, Driver integration, Middleware/ROS nodes, No software work required
• What are the acceptance criteria for integrated sensor performance?
• Will integration require mechanical housings, connectors, or environmental sealing? Options: Yes - enclosures/sealing, Standard connectors only, TBD
• What deliverables are required (calibration reports, source code, validation test logs)? Options: Calibration reports, Source code/artifacts, Validation test logs, Integration documentation

Perform Materials Characterization (SEM/XRD)

• Which characterization techniques are required (SEM, XRD, EDS, TEM, AFM)? Options: SEM, XRD, EDS, TEM, AFM, Other
• What sample preparation constraints exist (coating, cross-sectioning, vacuum compatibility)?
• How many specimens and from which lot(s) will be submitted? Options: Single specimen, 3-5 specimens, 6-20 specimens, 20+ specimens
• Do you require quantitative phase analysis, particle size distribution, or elemental mapping? Options: Phase analysis (XRD), Particle size distribution, Elemental mapping (EDS), Topography (AFM/TEM)
• Is an accredited or traceable report required, including instrument calibration details? Options: Yes - accredited/traceable report, Standard lab report, No report required
• What timeline is required for characterization and are destructive methods acceptable? Options: 48-72 hours, 1-2 weeks, 2-4 weeks, Destructive methods acceptable, Destructive methods not acceptable

Deliver Manufacturing-Ready Engineering Drawings

• What drawing standards and formats are required (GD&T per ASME Y14.5, CAD format: STEP, SolidWorks)? Options: ASME Y14.5 (GD&T), ISO drawing standards, STEP files, Native CAD (SolidWorks, Creo), Other
• Which parts require drawings versus assembly-level drawings and tolerances?
• Do you require supplier-ready packaging, fabrication notes, and critical-to-quality callouts? Options: Yes - supplier-ready, Fabrication notes only, No packaging/notes required
• Should drawings include manufacturing process recommendations (surface finish, heat treat, coatings)? Options: Yes - include recommendations, No - drawings only, Discuss per-part
• What release process do you require for drawings (e.g., engineering review, signoff by customer)? Options: Vendor release after internal QA, Customer signoff required, Iterative review cycle desired
• What is the target delivery schedule for full drawing package and bill of materials? Options: 2-4 weeks, 4-8 weeks, 8-12 weeks, Custom

• Statement of Work (SOW)
• Master Services Agreement (MSA)
• Non-Disclosure Agreement (NDA)
• IP and Licensing Agreement
• Payment & Milestone Schedule
• Staffing Continuity & Key Personnel Commitment
• Governance, Escalation & Change Control
• Acceptance Criteria & Test Protocols
• Security, Facility Access & Accreditation Addendum
• Data Management, Delivery & Technology Transfer
• Export Controls & Regulatory Compliance
• Insurance, Indemnity & Liability Schedule
• Audit & Progress Reporting Rights
• IP/Deliverable Escrow Agreement

• Outcome Verification Workshop
• Final Technology Transfer & Documentation Handoff
• Lessons Learned & Process Improvement Retrospective
• Open Issues Triage & Follow‑On Work Planning
• Executive Closeout & Strategic Review

• Create backlog entries for all triaged items in the agreed tracking tool with owners and due dates.
• Ensure the customer receives a complete, usable transfer package that enables independent follow-on work.
• Assign definitive owners for post-handoff support and training and agree a training schedule.
• Resolve any outstanding IP/licensing record items required for handover.
• Deliver the finalized documentation package to the agreed secure repository and confirm receipt.
• Schedule and run the committed training sessions and capture attendance and feedback.
• Log any residual documentation gaps and assign rapid-closure owners with deadlines.
• Retrospective Objectives & Rules
• Document an evidence-backed lessons learned report covering technical, operational, and contractual elements.
• Prioritize a small set of high-impact process improvements with owners and deadlines.
• Agree on how lessons will be shared internally and with program stakeholders.
• Publish a formal lessons learned report including root-cause notes, suggested fixes, and owners.
• Update internal playbook/SOPs where agreed and notify teams of mandatory changes.
• Schedule a check-in to review progress on improvement actions in 30/60/90 days.
• Review Open Issue Log
• Agree a prioritized, risk‑ranked backlog of open issues with remediation owners and target dates.
• Define candidate follow-on projects with clear objectives and preliminary budgets to enable rapid proposal creation.
• Establish criteria for closing issues and criteria for escalation into funded follow-on work.
• Introductions & Objectives
• Draft preliminary statements of work for follow-on scope candidates and circulate for budgetary review.
• Schedule focused technical deep-dive sessions for the top three high-risk items.
• Executive Summary of Outcomes
• Receive executive acknowledgement of program outcomes and a decision on pursuing follow-on work or scale-up.
• Complete commercial closeout checklist including final payments and contract records.
• Confirm commitments for continuity, escalation contacts, and sponsor-level owners for follow-on initiatives.
• Issue the executive sign-off document and archive in contract records.
• Finalize any remaining commercial closeout items (invoices, change orders) and confirm payment schedule.
• Schedule a strategic kickoff for approved follow-on work and assign executive sponsors.
• Confirm which deliverables meet the agreed success signals and record formal acceptance where appropriate.
• Produce a prioritized remediation list for any gaps with owners and dates.
• Ensure both parties have the same understanding of current state, consequences, and next steps.
• Publish an acceptance record listing accepted deliverables and any conditional items, with signatures.
• Create remediation tasks for each gap, assign owners, and set target completion and re-test dates.
• Share raw data packages and provenance notes referenced during the walkthrough to the customer's secure repository.
• Handoff Overview & Scope
• Current State Statement
• Documentation Package Review
• Business Impact & Cost/Consequence Review
• Prioritization & Risk Assessment
• Synopsis of Project Timeline & Outcomes
• Technical Triage of Top Risks
• Risk/Continuity & Key Personnel Commitments
• Consequence Framing
• What Went Well (Evidence-Based)
• Training & Knowledge Transfer Plan
• What Didn’t Work & Root Cause Analysis
• Data Formats, Access & Long‑term Storage
• Commercial Closeout Items
• Define Follow-On Scope Candidates
• Success Signals & Acceptance Criteria Review
• Prioritize Improvements & Assign Owners
• Decision: Immediate Fix vs Phase Work
• Strategic Roadmap & Decision on Next Steps
• Evidence Walkthrough (Data & Artifacts)
• IP, Licensing & Records Review
• Gap Analysis & Root Cause Notes
• Update Playbook and Next Steps
• Action Plan & Backlog Creation
• Handoff Acceptance & Checklist Sign-off
• Final Sign-offs & External Communications