Start With Your Story — The Mission in One Breath

• Give us the one-sentence summary of this mission—what you need to achieve and why it matters now.
• Who owns the payload(s) and who will be the primary point of contact on your team during campaign execution?
• Is this a single-satellite launch, a rideshare slot, or part of a constellation deployment? Options: Single dedicated launch, Rideshare (multiple payloads), Constellation batch deployment, Secondary payload on a primary mission, Other
• How would you rank this mission's priority for your organization? Options: Critical — cannot slip, High — serious impact if delayed, Medium — manageable with minor penalties, Low — flexible
• What’s the single biggest worry you have today about getting this mission done on time?

Why This Orbit, Right Now?

• If you ended up in a nearby but different orbit, what would break or change for your mission?
• What is the primary target orbit or set of candidate orbits for deployment? Options: Low Earth Orbit (LEO), Sun-synchronous orbit (SSO), Medium Earth Orbit (MEO), Geostationary Transfer Orbit (GTO), Geostationary Orbit (GEO), High Earth Orbit / HEO, Lunar transfer / cislunar, Interplanetary / escape
• Please specify required altitude(s), inclination(s), and RAAN constraints (provide ranges or fixed values).
• What orbital tolerances are mission-critical (select all that apply)? Options: Altitude +/- (km) — specify below, Inclination +/- (deg) — specify below, RAAN window, Local time of ascending node (LTAN) / beta angle, Phasing relative to constellation slots, Delta-v margin after separation
• How would you describe the operational consequences if insertion misses your tolerance by: a) small amount, b) moderate, c) large? Tell us examples and impacts.

The Schedule That Defines Your Career

• If the launch date slips past your preferred window, who inside or outside your organization feels the immediate pressure and why?
• What is your preferred launch timeframe and how fixed is it? Options: Fixed date / firm window, Flexible within a 2–4 week window, Flexible within 1–3 months, Flexible within 6+ months, Targeted to fiscal or regulatory deadline
• List the earliest acceptable date and the absolutely latest date you can accept (include reasons for hard cutoffs).
• Do you have hard blackout dates or mission-dependent time constraints (e.g., constellation phasing, regulatory windows)? Options: Yes — list below, No
• How much schedule slip are you prepared to tolerate before the mission becomes commercially or operationally unacceptable? Options: 0 days — must not slip, Up to 7 days, Up to 30 days, 1–3 months, More than 3 months
• When a slip happens, how is the decision made to accept delay vs. escalate to alternatives (who signs off and which criteria are used)?

Payload — The Things That Break Plans

• What payload constraint do you suspect will be the most contentious during integration—and why might others underestimate it?
• Provide key payload parameters: total mass, center-of-gravity envelope, and primary dimensions.
• Which of the following payload interfaces and environmental requirements apply to your hardware? Options: Standard separation system (e.g., P-POD, ESPA), Custom dispenser / adapter, Pressurized or fueled stages, Specific thermal control during processing, Cleanroom class requirement, Shock/vibration sensitivity above typical levels
• Does your payload require special handling or hazardous processing (propellants, pyros, batteries above certification limits)? Please be specific. Options: No hazardous processing, Watch-listed batteries / high-energy, Propellant or pressurants, Pyrotechnic devices, Other (specify below)
• Who on your team will own integration engineering and what are their past experiences with flight integration on this vehicle class?
• Are there expected late changes to the payload manifest or mass properties we should plan for? If so, how often and how late? Options: No late changes expected, Minor tweaks (mass/power) possible, Significant changes possible up to months before launch, Manifest still undecided

Success Signals — How You'll Know We Nailed It

• If you were writing the post-launch headline that makes your stakeholders breathe easy, what would it say?
• Which measurable orbital metrics will you use to accept or reject the mission on day-of-separation? Options: Altitude within X km, Inclination within X deg, RAAN/time-of-day, Delta-v budget remaining, On-orbit attitude and power functional checks, Successful communication within X hours
• Specify the numeric acceptance bands and the time after separation you consider definitive (e.g., altitude +/- 20 km within 6 hours).
• Who is the formal acceptance authority for on-orbit success (role/title) and do insurers or partners get a veto?
• What are your minimum acceptable post-deployment operational milestones and timelines (e.g., comms, power, payload commissioning)?
• What contingency acceptance paths would you consider (e.g., slight rephasing, on-orbit manoeuvre) versus calling the mission a failure? Options: Allow minor on-orbit correction, Require meeting ground acceptance within timeframe, Invoke insurance/compensation, Other — describe

Risk, Insurance, and What Keeps Underwriters Awake

• What single element of the mission would you most want an underwriter to focus on if you could choose one?
• Which types of insurance coverage do you require or prefer for this mission? Options: Launch/physical loss, In-orbit indemnity, Third-party liability, Delay-in-start-up (DSU), No insurance required / self-insured
• Will an insurer or technical advisor need access to vehicle performance data, and do you have preferred formats or thresholds they expect? Options: Yes — full telemetry access requested, Yes — summarized reliability data, No — not required at this stage, Unsure — need guidance
• Describe any prior claims, unresolved anomalies, or reliability concerns from previous programs that insurers have flagged.
• What level of indemnification or liability allocation would be a deal-breaker for you? Options: Full indemnity to provider, Shared indemnity, Limited indemnity with cap, No indemnity — unacceptable
• If a mission anomaly occurs, what escalation and communication cadence do you expect between your team, the launch provider, and insurers?

Stakeholders, Approvals, and the Red Lines That End Conversations

• Who has the final authority to abort or greenlight a launch attempt, and what triggers their decision in your view?
• Which internal and external stakeholders must sign off before we proceed to integration and launch (select all that apply)? Options: Mission Director, Program Manager, Chief Engineer, Legal/Contracts, Finance, Insurance underwriter, Government/regulator, Range authority
• How do you prefer to receive status and decisions during the campaign (e.g., daily standup, dashboard, executive summary)? Options: Daily operational call, Automated dashboard, Weekly executive summary, Ad-hoc alerts for exceptions, Combination
• Are there contractual red lines or non-negotiable terms (e.g., manifest flexibility, liability caps, data rights) we should know now? Options: Manifest flexibility required, Specific liability cap required, Data access restrictions, None — open to negotiation, Other (specify)
• If you anticipate a cross-organizational conflict during the campaign, what’s the most effective way for us to help resolve it? Options: Escalate to executive sponsors, Facilitate technical working group, Bring in neutral third-party mediator, Document tradeoffs and proceed
• How will your procurement, legal, and insurance teams be involved during negotiation and campaign execution (names/roles and typical response times)?

Integration, Range, and The Operational Dependencies

• What is the single operational dependency that, if unresolved, will derail your launch campaign?
• How and when will your hardware be shipped, stored, and staged for integration (options or constraints)? Options: Direct ship to provider integration facility, Ship to customer staging facility then deliver, Multiple split shipments, Tight cold-chain or humidity control required
• What telemetry, ground-station, or tracking support must be in place at T+0 to validate separation and early operations?
• Do you require on-site presence of your engineers or a remote/observer model during integration and launch operations? Options: Full on-site team, Minimal on-site (POC + 1 engineer), Remote participation with live feeds, Hybrid schedule
• Are there range approvals, export controls, or regulatory certifications we need to coordinate together? Options: Range approvals, ITAR / export licensing, Frequency allocation/coordination, Hazardous materials permits, None/handled
• What staffing or vendor constraints (e.g., contractor availability, security clearances) could limit our campaign schedule?

Tradeoffs — Where Would You Bend to Save the Date?

• If we had to compromise to keep the current launch date, what would you consider giving up first? Options: Orbit precision, Additional payload testing, Late manifest flexibility, Cost increase to expedite, Launch slot in favor of a later dedicated mission, Other — explain
• How do you emotionally weigh trading technical margin for schedule certainty—what keeps you awake when that decision arrives?
• What non-negotiables must remain in place even if we accelerate the timeline (safety, insurance, acceptance criteria)?
• Have you made similar tradeoffs on past missions? What was the outcome and what did you learn?
• If we propose an accelerated integration path, what approvals would we need from your side and how fast can those be obtained? Options: Immediate (same day), Within 3 business days, Within 1–2 weeks, Longer — depends on review

If Everything Went Perfect — The Day-After Vision

• Imagine the mission was flawless. Describe the first three operational checks you’d run and how quickly you'd expect them to complete.
• What downstream business or operational milestones depend on a timely, successful insertion (e.g., commercial service start, constellation spacing, science observation schedule)?
• How would a successful on-time mission change your program’s risk profile or negotiating power with insurers and partners?
• What follow-up support would you want from us in the first 30–90 days post-separation to feel comfortable handing the spacecraft to ops? Options: Detailed telemetry replay and analysis, On-orbit commissioning assistance, Weekly mission-status calls, Warranty / post-launch support window, None — internal team handles it
• Are there future missions or a broader program we should be aware of that influence decisions on margins, data sharing, or testing now? Options: Yes — expanding constellation, Yes — technology demonstrator series, No immediate follow-ons, Unsure

• Mission Scenario Alignment
• Vehicle-Choice Tradeoff Workshop (Scenario Modeling)
• Schedule Confidence & Mitigation Planning
• Mission Assurance Proof Session
• Executive Decision & Mutual Validation

• Agreement on any additional qualification work or telemetry items required before progressing to Solution Scope.
• Agree a schedule confidence percentage (e.g., 90% on-time) and the residual risk tolerances.
• Define and assign a prioritized mitigation plan that raises schedule confidence to the target level.
• Identify required contractual schedule remedies and insurance conditions to be included in the mutual commit stage.
• Confirm gate owners and the evidence list for each decision point.
• Seller to produce a revised Gantt with mitigation-induced schedule deltas and confidence bands.
• Legal and insurance to draft suggested schedule remedy and manifest-flex language for review.
• Program leads to populate the decision gate evidence checklist and assign owners.
• Recap of Agreed Future-State & Acceptance Criteria
• Each acceptance criterion has a defined verification method, schedule for evidence, and an assigned owner.
• Customer validates that the provided proofs and heritage data close their primary concerns about insertion accuracy and residual risk.
• Introductions & Objectives
• Seller to deliver a verification matrix document with owners and timelines.
• Seller to share raw telemetry examples and post-launch orbit determination report templates.
• Customer to confirm any extra verification evidence required and timelines for delivery.
• Decision Recap
• Secure executive confirmation that the Solution Experience proved the future-state and that assumptions are valid.
• Authorize progression to Solution Scope with an agreed timeline and open item list.
• Assign owners and deadlines for the top commercial and insurance items that remain open.
• Seller to circulate a formal Decision Record capturing agreed current-state, consequence, future-state, vehicle choice, mitigations, and open items.
• Schedule Solution Scope kickoff meeting and circulate preparatory materials.
• Assign owners to the top 3 open commercial/insurance risks with deadlines for resolution before Mutual Commit.
• Produce and agree a single-sentence current-state describing what is breaking today.
• Quantify the top consequence metrics (cost, schedule, risk) so urgency is explicit.
• Define and agree the one-sentence future-state (measurable outcome) to prove during the experience.
• Identify top 3 constraints and assign owners for follow-up scenario inputs.
• Capture and circulate the finalized current-state, consequence numbers, and future-state statements.
• Customer to provide any missing cost / insurance escalation data within 48 hours for modeling.
• Seller to schedule vehicle and schedule modeling sessions and assign analysts.
• Re-state Mission Acceptance Criteria
• Produce a ranked short-list of vehicle candidates mapped to probability of achieving the future-state.
• Surface the primary risk drivers per vehicle and the most effective mitigations.
• Obtain customer validation that scenario assumptions are accurate and outcomes are actionable.
• Agree next steps for deeper technical trade or a firm vehicle selection gateway.
• Seller to deliver detailed scenario model outputs and sensitivity plots within 3 business days.
• Seller to attach independent actuarial reliability reports and reference launches for shortlisted vehicles.
• Customer to confirm vehicle shortlist decision criteria and any mandatory vehicle exclusions.
• Baseline Campaign Schedule & Critical Path
• Verification Matrix Walkthrough
• Schedule Risk Quantification
• Open Risks & Commercial Impacts
• Vehicle Options & Independent Metrics
• Crisp Current-State Statement
• Mitigation Controls & Operational Changes
• Consequence Quantification
• Customer Validation Exercise
• Scenario Modeling: Insertion Outcome vs Vehicle
• Failure-Mode Case Studies
• Authorize Next Steps & Timeline
• Contractual Remedies & Insurance Levers
• Flight Heritage & Data Proof
• Mitigation Controls Mapping
• Future-State Definition
• Wrap-up & Action Owner Confirmation
• Validation Exercise
• Decision Gate Tree & Owners
• Top Constraints & Risk Drivers
• Customer Validation & Confirmation
• Validation & Next Steps

• Receive and inspect payload shipments
• Perform vibration and thermal vacuum testing
• Integrate payload to separation adapter
• Payload fairing encapsulation and closure
• Install rideshare dispenser and payload mounts
• Install telemetry, power, and command harnesses
• Propellant loading for vehicle stages
• Vehicle transport to pad and erection
• Execute terminal countdown and liftoff
• Arm and operate flight termination system
• Execute payload separation and deployment
• Post-launch orbit determination and confirmation
• Upper-stage deorbit or disposal burn execution

Receive and inspect payload shipments

• Will you or the launch provider arrange and pay for payload shipping and logistics? Options: Customer arranges and pays, Provider arranges and charges customer, Shared arrangement / other
• How many shipments and discrete line-items (e.g., primary + spares + test articles) will arrive for this manifest? Options: 1, 2-3, 4-10, More than 10
• What are the required delivery windows or hard arrival dates (ISO date ranges)?
• Does any shipment contain hazardous materials, cryogens, batteries, or specialized packaging that requires special handling? Options: Lithium batteries, Pressurized gas or cryogenics, Classed hazardous material, No special handling, Other
• What inspection and acceptance evidence must be performed on receipt (visual, mass properties, functional checkout, serial-number verification)?
• Who is designated as the receiving authority (customer rep, third-party integrator, provider) and what are their contact & availability windows?

Perform vibration and thermal vacuum testing

• Is qualification-level testing required or only acceptance-level (flight unit) testing? Options: Qualification + acceptance, Acceptance only, No environmental testing required
• Which test levels and profiles apply (random sine, shock, TVAC soak, thermal cycle profiles)? Provide reference test spec numbers if available.
• Will the flight unit be tested, or will a structural/flight-representative test article be provided? Options: Flight unit to be tested, Engineering/test article provided, Not applicable
• Do you require provider witness or third-party witness of testing and/or raw data delivery? Options: Provider witness, Customer witness, Third-party witness, No witness required
• Are there special fixturing, thermal harnessing, or qualification instrumentation needs (accelerometers, thermocouples, EM sensors)? Options: Standard instrumentation, Customer-supplied instrumentation, Custom fixtures required, None
• What are your pass/fail acceptance criteria and required test deliverables (report format, raw data, signed certification)?

Integrate payload to separation adapter

• Which separation adapter/interface is planned (provider standard, legacy flight-proven adapter, or custom adapter)? Options: Provider standard adapter, Legacy/flight-proven adapter, Custom adapter required, Unknown / to be decided
• Have you provided detailed mechanical drawings and mass/inertia properties for adapter interface verification? Options: Yes - complete dataset, Partial data provided, No - will provide, N/A
• Specify mechanical attachment details required: bolt pattern, preload torque, alignment dowels, and maximum allowable interface loads.
• Who will design, manufacture, and supply the adapter and its qualification evidence (customer, provider, third party)? Options: Customer supplies, Provider supplies, Third-party supplier, To be determined
• Are there electrical/pneumatic/command lines across the adapter that require umbilicals or separation sequencing? Options: Yes - electrical, Yes - pneumatic/pyro, Yes - both, No
• What verification activities are required post-integration (mass properties measurement, functional check, separation test)?

Payload fairing encapsulation and closure

• Does the payload fit within the selected fairing volume and clearance margins (provide dimensions and envelope sketches)? Options: Yes - cleared, No - requires review, Unknown - need fit check
• What cleanliness/contamination control class is required for encapsulation (e.g., ISO Class 5/7) and special contamination constraints? Options: ISO Class 5, ISO Class 7, Standard cleanroom, No special cleanliness
• Are there time or environmental constraints between closure and launch (max allowable time on-pad, humidity/temperature limits)?
• Will encapsulation require customer attendance or witness, and do you require photography/telemetry during closure? Options: Customer witness required, Photo/video only, No witness required
• Are there special pyrotechnic, hold-down, or explosive bolt constraints or no-fire zones near the payload that affect closure operations? Options: Yes - pyros present, Yes - prohibited items, No special constraints
• What contamination protection or purge requirements exist during encapsulation and transport to pad (nitrogen purge, desiccant, sealed shipping)? Options: Nitrogen purge, Desiccant/sealed, No purge required, Other

Install rideshare dispenser and payload mounts

• What rideshare dispenser type and mechanical configuration is planned (provider standard dispenser, ESAM, custom stack)? Options: Provider standard dispenser, ESAM / multi-payload dispenser, Custom dispenser, Unknown
• How many secondary payloads and their individual mass ranges will be attached to the dispenser? Options: 1-3, 4-10, 11-30, More than 30
• Are there specific deployer interfaces (spring-based, separation nut, clamp-band) or constraints per payload? Options: Spring pusher, Clamp-band, Separation nut, Custom
• Do you require sequencing/release timing control for multiple dispensers or prioritized deployments? Options: Yes - sequencing required, No - simultaneous OK, TBD
• Will payloads require isolation from dispenser structural loads (dynamic isolators, dampers) or special mounting hardware? Options: Isolation required, Standard mounts acceptable, Custom mounting required
• Who is responsible for supply, inspection, and certification of the dispenser and mounts (customer, provider, third-party)? Options: Customer, Provider, Third-party supplier, Shared

Install telemetry, power, and command harnesses

• What telemetry downlink channels, data rates, and modulation types are required during ascent and separation? Options: S-band, UHF, X-band, Custom
• What power interfaces and nominal voltages/currents are required for payload support during ground ops and on-vehicle?
• Are redundant command paths or safe-mode command sequences required for pre- and post-separation operations? Options: Yes - redundancy required, No redundancy required, Partial redundancy
• List connector types and pinouts or provide harness interface control documents (ICDs) and harness routing constraints.
• Who will perform harness installation and harness verification testing (continuity, channel checks)? Options: Provider team, Customer team, Third-party integrator, Mixed
• Are EMI/EMC, grounding, or shielding requirements specified for your payload harnesses? Options: Yes - EMI/EMC required, No special requirements, TBD

Propellant loading for vehicle stages

• Which propellant types and stage(s) require loading during this campaign (LOX, LH2, RP-1, hypergolic, storable, other)? Options: LOX/LH2, RP-1/LOX, Hypergolic, Storable bipropellant, Other
• What is the planned fueling timeline and T-0 relative fueling window (hours before launch)?
• Are there cryogenic boil-off, conditioning, or replenishment needs during hold/recycle scenarios? Options: Yes - active replenishment, No - passive allowed, TBD
• Does fueling require special permits, range approvals, or insurer sign-offs beyond standard range notices? Options: Yes - extra permits/approvals, No - standard approvals only, Unknown
• Who supplies and certifies propellant, and who bears cost and transfer liability (provider, customer, fuel vendor)? Options: Provider supplies and certifies, Customer supplies, Third-party vendor, Shared arrangement
• What safety constraints or exclusion zones must be maintained during fueling (shoreline, inhabited areas, transit closures)?

Vehicle transport to pad and erection

• What transport method will be used (horizontal/vertical road transporter, rail, barge) and are any route permits required? Options: Road trailer - horizontal, Road trailer - vertical, Rail, Barge/sea transport, Other
• Are there bridge, overpass, or corridor restrictions that require special escort, temporary infrastructure, or schedule windows for transport? Options: Yes - restrictions apply, No restrictions, Unknown - to be surveyed
• What are lift/erection requirements at pad (crane capacity, lift fixtures, personnel certifications)?
• What environmental or weather constraints drive the transport and erection schedule (wind limits, precipitation, temperature)?
• Who is responsible for vehicle transport insurance, escort permits, and route scheduling? Options: Provider, Customer, Third-party logistics, Shared
• Are there hold points or inspection checkpoints during transport that require documentation or customer sign-off? Options: Yes - sign-off required, No hold points, TBD

Execute terminal countdown and liftoff

• Who will be the official countdown director and what go/no-go decision authorities must be present for T-0?
• What is the planned T-0 window length and allowable launch window constraints (instantaneous, minutes, orbit-plane constraints)? Options: Instantaneous, ±5 minutes, ±15 minutes, Other
• What predefined hold reasons and clear re-start criteria must be captured in the countdown plan (weather, telemetry, range safety, payload readiness)?
• Do you require live telemetry access, secure video, or a private comms bridge during terminal countdown? Options: Full live telemetry + video, Telemetry only, Video only, No live access required
• What abort/recycle procedures are acceptable and who is authorized to call a scrub or recycle?
• Are there contractual schedule remedies or credits tied to missed launch commitments during terminal operations? Options: Yes - remedies defined, No remedies, TBD / under negotiation

Arm and operate flight termination system

• What FTS architecture applies to this mission (range-controlled, vehicle-integrated, redundant channels)? Options: Range-controlled FTS, Vehicle-integrated FTS, Hybrid/redundant FTS, Unknown
• When must the FTS be armed relative to T-0 and what interlocks or safing conditions exist?
• Are there third-party or range authority tests, certifications, or witness requirements for FTS prior to launch? Options: Range witness required, Third-party certification required, No external witness
• Who owns the FTS and associated liability during arming and operation (provider, range, customer)? Options: Provider owns, Range owns, Shared responsibility
• What verification and end-to-end testing evidence is required for FTS (simulation, functional tests, telemetry)?
• Are there specific insurer or regulator constraints tied to FTS operation that affect arm timing or safing procedures? Options: Yes - insurer/regulator constraints, No special insurer constraints, Unknown

• Statement of Work (SOW)
• Launch Services Agreement (LSA) / Master Launch Agreement
• Insurance Endorsement & Certificate
• Indemnification & Liability Annex
• Manifest & Schedule Flexibility Addendum
• Schedule Remedies & Performance Credits
• Acceptance Gates & Mission Completion Criteria
• Payment Schedule & Financial Security
• Change Control & Modification Procedure
• Payload Integration Agreement
• Export Control & Compliance Certification (ITAR/EAR)
• Range Safety & Regulatory Approvals
• Telemetry, Data Rights & Post-Launch Reporting
• Termination, Force Majeure & Contingency Plan
• Dispute Resolution & Governing Law
• Signatory Authority & Governance Matrix
• Third-Party Vendor & Subcontractor Consent
• Performance Bond / Parent Guarantee

• Launch Outcomes Review — Executive & Operations
• Telemetry & Orbit Determination Deep Dive
• Lessons Learned & Continuous Improvement Workshop
• Insurance, Liability & Contract Closeout
• Ongoing Issues & Enhancements Governance (Standing)

• Agree on documentation packaging and deadlines for insurer and legal reviews.
• Provide payload teams with recommended early-orbit commissioning steps or delta-v plans if required.
• Archive raw telemetry, analysis artifacts, and configuration snapshots to the shared channel with access permissions.
• If root cause indicates hardware or process failure, trigger formal anomaly investigation with timeline.
• Framing: Review Success Signals & Consequences
• Produce a prioritized, actionable lessons-learned backlog with owners and timelines.
• Agree on measurable metrics to track improvement efficacy (e.g., schedule variance reduction, telemetry completeness).
• Commit to a communications plan that transparently shares relevant lessons with the customer and critical partners.
• Create a prioritized improvement backlog in the shared channel and tag owners within 5 business days.
• Assign 30/60/90-day deliverables for the top three high-impact improvements.
• Prepare a one-page lessons-learned summary for the customer and publish to the shared customer channel.
• Schedule follow-up checkpoint to review progress against improvement metrics in 30 days.
• Contractual Milestone & Remedy Review
• Confirm insurance triggers and the evidence required for any potential claim.
• Decide whether to initiate claims or contractual remedies and assign owners for notifications.
• Introductions & Objectives
• Submit required claim/notice communications to underwriters and counterparties within contractual timeframes.
• Assemble and deliver the insurer-required mission data package (telemetry, orbit products, anomaly logs).
• Legal to prepare any contract amendments, settlements, or acknowledgements required for closeout.
• Log residual liabilities and remediation commitments in the shared governance tracker.
• Review Open Issues & Status
• Ensure all launch-related issues are actively tracked and progressing to closure.
• Prioritize and schedule enhancements that materially reduce operational or mission risk.
• Maintain a single, customer-accessible channel for status, artifacts, and decisions.
• Update the shared issue tracker weekly with current statuses, owners, and expected close dates.
• Publish an enhancements roadmap showing priorities, owners, and milestones to the customer channel.
• Confirm owners and schedule for the next governance meeting.
• Escalate any stale or blocked high-priority issues to executive sponsors for resolution.
• Confirm which success signals were met and which were not with clear evidence.
• Identify and assign owners for immediate mitigations and customer communications.
• Decide whether further technical deep dives or insurer/legal notifications are required.
• Publish an executive launch outcome brief to customer and internal stakeholders within 24 hours.
• Open and assign issue tickets for each anomaly with initial mitigation plans.
• Schedule the Telemetry & Orbit Determination Deep Dive within 48 hours if data indicates deviation.
• Notify insurance and legal teams if contractual or coverage triggers may apply.
• Pre-reads & Data Availability Check
• Validate telemetry integrity and confirm whether the achieved orbit meets acceptance criteria.
• Identify root causes for any observed deviations with data-backed evidence.
• Define and schedule the technical artifacts (reports, data exports) needed by customers, insurers, and internal teams.
• Deliver a consolidated telemetry and orbit determination analysis report within 72 hours.
• Timeline Mapping & Root Causes
• Success Signals vs Actual Outcomes
• Enhancement Backlog Prioritization
• Telemetry Integrity & Timeline Review
• Insurance Coverage Assessment
• Impact Quantification
• Schedule & Timeline Variances
• Evidence & Documentation Requirements
• Trajectory & Orbit Determination Results
• Risk Register & Mitigation Updates
• Customer Feedback & Satisfaction Check
• Orbit Insertion Accuracy
• Improvement Brainstorm & Prioritization
• Separation & Payload Health Assessment
• Determine Claims & Notification Timeline
• Define Experiments, Owners, and Metrics
• Root Cause Analysis of Deviations
• Anomalies and Immediate Impacts
• Residual Liability & Closeout Actions
• Cadence, Owners, and Next Deliverables