Quick Snapshot: Your Fleet & Priorities

• How many vessels are in your active fleet today and what range of sizes/classes are they? Options: 1-2, 3-5, 6-10, 11-20, 21+
• Which of the following best describes your typical itinerary complexity? Options: Short regional loops (same ports), Regional with varied ports, Multi-country itineraries (dozens of jurisdictions), Global/worldwide itineraries
• Who on your leadership team feels the most immediate pressure when operations go wrong (title or role)? Options: VP Marine Operations, Fleet Operations Director, Head of Revenue Management, Port Operations Manager, COO, Other
• What outcome would make this discovery conversation feel immediately valuable to you? Options: Clear pilot scope, Risk mitigation plan, ROI estimate, Decision timeline, Other
• What legacy systems are currently core to voyage planning, crew scheduling, or POS on your vessels? Options: In-house legacy system, Third-party maritime ERP, Separate crew/HR system, Multiple disconnected systems, Paper/manual processes, Other

What Keeps You Up at Night?

• If a single operational failure could be prevented this year, which would you choose—and why would that one matter more than the others? Options: Port detention for compliance, Crew scheduling violations, Significant onboard revenue leakage, Major itinerary disruption/stranding, Other
• Tell me about the last time that risk actually materialized—what happened, how long did it take to recover, and what was the human cost?
• How often do near-miss incidents (e.g., close calls with port compliance or missed manifests) occur across your fleet? Options: Weekly, Monthly, Quarterly, Rarely, Never tracked
• Who internally bears the reputational fallout when a compliance or scheduling failure happens, and how does that pressure show up in day-to-day decisions?
• How long have you been managing these risks with your current processes, and what incremental fixes have you tried?

When Compliance Isn't Optional

• Imagine a new port-state audit comes tomorrow—what gap in your documentation or workflow would expose you most? Options: Incomplete manifests, Missing safety documentation, Non-standard regulatory mappings, Crew certification mismatches, Other
• Which jurisdictions cause the most friction for you—by name, and why do they stand out?
• How are regulatory changes (IMO, flag-state, local port rules) currently tracked and pushed into shipboard operations? Options: Central compliance team, Ad-hoc emails/manual updates, Shared docs/spreadsheets, Automated updates from vendor, Other
• When a regulatory requirement changes, what is the typical time from notice to shipboard implementation on average? Options: Days, Weeks, Months, Varies widely, Not measured
• What would 'regulatory peace of mind' look like for you—what evidence would make you confident you're protected?

Where Revenue Slips Through the Cracks

• How confident are you that current onboard POS and inventory processes capture all guest spend accurately? Options: Very confident, Somewhat confident, Doubtful, We believe we are losing a lot
• Where do you suspect the largest sources of onboard revenue leakage occur (select all that apply)? Options: Point-of-sale reconciliation, Inventory shrinkage, Third-party vendor settlements, Incorrect guest folios, Uncaptured ancillary sales, Other
• Can you share an example of a recent reconciliation or audit where revenue unexpectedly differed from expectations—what was the delta and root cause?
• How tightly integrated are your reservation/CRM systems with shipboard POS and manifests today? Options: Fully integrated, Partially integrated, Loosely connected via files, Not integrated / manual handoffs
• If you could remove one recurring revenue headache overnight, which would it be and why?

The Human Side: Crew, Unions, and Adoption

• What part of introducing new onboard systems do crews resist most—and what stories do you hear from the frontline?
• Which stakeholders must be won over for a pilot to succeed (select all that apply)? Options: Master/Captain, Chief Officer/Operations, Head of IT, Crew supervisors/leads, Union representatives, Shore-side operations, Finance/Revenue
• How have past technology rollouts affected crew morale or operational tempo, and how long did it take for adoption to stabilize? Options: Weeks, Months, A year+, Never stabilized, Not tracked
• What training formats have worked best for your crews (select all that apply)? Options: Onboard instructor-led, Remote instructor-led, Microlearning modules, Printed quick-guides, Shadow/training rotations, Other
• If crew pushback were removed, what positive changes would you expect to see first—and how would that feel operationally?

Connectivity, Outages and the Sea

• When connectivity degrades at sea, what single capability failing worries you most? Options: Voyage plan sync, Crew scheduling updates, POS reconciliation, Regulatory document submission, Real-time support/escalation
• How frequently do you experience partial or full system outages while a vessel is underway? Options: Weekly, Monthly, Quarterly, Rarely, Never tracked
• Which resilience strategies do you currently use for low-connectivity operations? Options: Local offline caches, Staged batch syncs, Manual paper backups, Satellite redundancy, None
• Describe a time when a connectivity failure created a regulatory or passenger-facing problem—what broke down and how was it resolved?
• What level of at-sea availability (percentage) would you require from a vendor before you’d accept fleet rollout? Options: 99.9%, 99.5%, 99%, 95-98%, Depends on offline capabilities

Decision Signals & Pilot Success Criteria

• If the pilot goes perfectly, what three measurable signals would convince you to expand to the fleet?
• Which of these will be deal-closers for you at the end of pilot evaluation (select all that apply)? Options: Regulatory sign-off, Data migration integrity, Crew adoption > X%, Demonstrated revenue lift, Operational SLA met, Other
• Who has final authority to greenlight a fleet rollout, and what concerns do they typically raise?
• What acceptance tests (functional or scenario-based) should be included in the pilot to meaningfully prove readiness? Options: Voyage plan accuracy, Manifest/regulatory submission, Crew schedule compliance, POS reconciliation, Offline failover scenarios
• How will you quantify ROI for the pilot—what financial or operational levers will you measure? Options: Reduced detention risk (costs avoided), Incremental onboard revenue, Crew scheduling efficiency (hours saved), Operational incident reduction, Other

Risk, Budget, and Timeline Reality Check

• What's the realistic window for running a single-vessel pilot and making a fleet decision? Options: 4-8 weeks, 2-3 months, 4-6 months, 6-12 months
• Which constraints could stop this project before a pilot starts (select all that apply)? Options: Budget approval, IT/security sign-off, Union agreements, Vessel availability, Data access from legacy systems, Other
• When you imagine things go wrong during a pilot, what single failure mode would most likely derail the initiative? Options: Integration failure, Crew rejection, Data migration errors, Connectivity blackouts, Commercial disagreement
• What internal communication cadence and governance will you need during the pilot to feel informed but not overwhelmed? Options: Weekly steering, Bi-weekly updates, Monthly executive summaries, As-needed incident calls
• How much budget range is realistically available for a pilot and initial integration effort (ballpark)? Options: <$50k, $50k-$150k, $150k-$500k, $500k+

What Success Feels Like—and The Small Steps to Get There

• If this program reduces one category of stress for you personally, which would you choose and why (compliance, revenue, crew, or other)? Options: Compliance, Revenue, Crew management, Operational predictability, Other
• What small, low-risk first step would make you comfortable moving from conversation to a scoped pilot? Options: Data readiness assessment, Technical integration feasibility, Pilot timeline proposal, Stakeholder alignment workshop, Other
• Who else should we involve in the next meeting to accelerate decisions (names/roles)?
• What would make you say 'this vendor understands our world' within the first pilot month—concrete behaviors or evidence?
• Finally, what concerns would you like us to address proactively before a pilot kickoff?

• Pre-Work Alignment — Current State & Success Metrics
• Single-Vessel Pilot Scenario — Diagnosis → Proof → Validation
• Multi-Port Compliance Scenario — Regulatory Proof
• Low-Connectivity & Offline Operations Scenario — Resilience Validation
• Trade-offs & Go/No-Go Decision Workshop

• Customer to provide historical connectivity logs and a list of critical shipboard functions that must remain available offline.
• Identify integration endpoints and data handoffs required to run the pilot.
• Surface and document major trade-offs and mitigation plans.
• Vendor to produce a pilot acceptance test script mapped to the agreed KPIs.
• Customer to deliver the canonical dataset for the chosen pilot voyage and grant access to integration endpoints.
• Schedule the pilot execution window and assign sign-off approvers for each validation checkpoint.
• One-Sentence Current State for Compliance
• Validate that the platform can produce a compliant multi-port package for the sample itinerary.
• Agree on expected risk reduction and time savings with supporting assumptions.
• Document required integrations and owner responsibilities for compliance data flows.
• Customer to provide regulatory checklists for the selected ports and any recent port detention reports.
• Vendor to map each required regulatory document to the system output and deliver a sample compliance package.
• Assign a regulatory SME to be available during the compliance pilot runs for rapid clarifications.
• Current State: Connectivity Profile & Consequences
• Confirm the platform's offline capabilities meet the customer's minimum operational requirements.
• Agree on SLAs, recovery objectives, and incident escalation responsibilities for at-sea outages.
• Establish a connectivity simulation test plan to run during the pilot to validate resilience.
• Introductions & Meeting Objectives
• Vendor to deliver an offline-mode test script and conflict-resolution demo using customer sample data.
• Schedule a simulated outage test during the pilot with agreed success criteria.
• Recap of Agreed Current State, Consequences, and Future-State
• Arrive at a documented go/no-go decision for the single-vessel pilot.
• Secure resource commitments, pilot timeframe, and sign-off owners for execution.
• Ensure all trade-offs and residual risks are explicitly captured with mitigation owners.
• If GO: Vendor to prepare pilot statement of work and acceptance criteria appendix for signature.
• If GO: Customer to confirm resource allocation and provide final access credentials/data by agreed date.
• If NO-GO: Document blockers, owner assigned to each blocker, and target remediation dates for re-review.
• A single-sentence current-state definition is documented and agreed.
• Consequences are quantified with at least two supporting metrics (cost, time, risk).
• Future-state outcome(s) and success metrics for the Solution Experience are agreed.
• Data, artifacts, and SME owners required for scenario walkthroughs are identified with delivery dates.
• Customer to provide sample voyage manifests, recent port incident reports, crew roster examples, and connectivity logs.
• Vendor to prepare a KPI baseline template for the identified consequences (cost/day of detention, rework hours, revenue leakage).
• Assign a single pilot owner from customer side and a vendor engagement lead.
• Recap Current State & Consequence (30s One-liners)
• Confirm an execution-ready single-vessel pilot design tied to specific customer pain points.
• Agree on numeric KPI targets and acceptance criteria for the pilot.
• One-Sentence Current State (Diagnosis)
• Regulatory Mapping Walkthrough
• Pilot Process Map (Shipboard + Shoreside Flow)
• Scenario Outcome Summaries (Single-Vessel, Multi-Port, Offline)
• Offline Workflow Demonstration
• Sync & Conflict Resolution Mechanics
• Live/Simulated Data Proof Points
• Sample Compliance Package Creation
• Risk vs Reward & Trade-off Matrix
• Quantify Consequences
• SLA Expectations & Recovery Scenarios
• Quantify Detention Risk & Time Savings
• Resource & Timeline Commitment
• KPI Modeling: Baseline vs Projected
• Define Future-State Outcomes (One Sentence)
• Select Scenarios & Data/Artifacts Required
• Acceptance Criteria & Validation Checkpoints
• Decision & Next Steps
• Integration & Responsibility Matrix
• Incident Escalation & Crew Enablement
• Documentation & Communication Plan
• Validation & Regulatory Sign-off Plan
• Pre-work & Ownership

• Legacy Booking Data Migration
• Shipboard Offline Data Sync Engine
• Guest Manifest Import and Shore Sync
• Port Call Document Exchange Connector
• Automated Compliance Certificate Generation
• Crew Certification and Visa Record Management
• Onboard POS Integration and Revenue Reconciliation
• Inventory and Stores Reconciliation Module
• Port Health and Safety Submission Package
• Voyage Routing Optimization Engine
• Real-Time Safety Incident Reporting Module
• Passenger Onboard Account Settlement Module

Legacy Booking Data Migration

• Do you require migration of legacy booking and guest records into the new platform for the pilot vessel? Options: Yes, No
• Which legacy sources hold your booking and guest data? Options: Proprietary Reservation System, Third-party CRS/CRS Export, Onboard PMS, Flat files / Spreadsheets, Other
• Approximately how many guest/booking records need migration for the pilot vessel? Options: Less than 5,000, 5,000–25,000, 25,000–100,000, More than 100,000
• What are the primary data quality concerns we should address (duplicates, inconsistent IDs, missing documents)?
• Do you need historical transaction detail (payments, refunds, onboard purchases) migrated or only core booking and guest profile fields? Options: Core booking & profiles only, Include transaction history, Selective recent history (e.g., 2 years), Unsure - need guidance
• What are your acceptance criteria for successful migration (record counts match, reconciliation reports, sample verification)?

Shipboard Offline Data Sync Engine

• Will the ship operate with prolonged low- or no-connectivity windows that require robust offline sync? Options: Yes - frequent multi-hour outages, Occasional short outages, Mostly connected (rare outages)
• Which data domains must be supported offline and synchronized later? Options: POS transactions, Crew schedules, Passenger manifests, Inventory counts, Compliance documents, Safety incidents
• What is the maximum amount of data (daily MB/GB) you expect to queue onboard between sync windows? Options: Less than 100MB, 100MB–1GB, 1GB–10GB, More than 10GB
• How should sync conflicts be resolved when shore and ship edits collide? Options: Last-write-wins (auto), Manual review and merge, Field-level merge rules, Custom business rules
• Do you require end-to-end encryption, certificate pinning, or specific compliance (e.g., PCI) for offline sync payloads? Options: Yes - PCI/Encryption required, Encryption only, No special requirements
• Describe any bandwidth throttling or scheduled sync windows (e.g., only sync at night or when on satellite band X).

Guest Manifest Import and Shore Sync

• What are the source systems for guest manifests (CRS, tour operator feeds, onshore check-in systems)? Options: CRS/Reservation System, Onshore Check-in Portal, Third-party tour operator, Manual uploads/CSV
• How frequently must manifest changes flow to shore (real-time, hourly, on-departure, daily)? Options: Real-time, Near real-time (minutes), Hourly, Daily, On specific events only
• What matching rules should be used for manifest reconciliation (PNR, passport number, guest ID)? Options: PNR/Booking ID, Passport/National ID, Name + DOB, Custom mapping
• Are there data privacy or retention constraints for passenger PII (GDPR, national privacy laws)? Options: Yes - GDPR applies, Yes - other national rules, No special constraints, Unsure
• What are acceptable success criteria for manifest sync (record count parity, checksum validation, reconciliation report)?
• How should duplicate or split bookings be handled during import? Options: Automatic dedupe with rules, Flag for manual review, Merge into a primary record, Custom logic

Port Call Document Exchange Connector

• Which ports/authorities do you exchange documents with for the pilot itinerary (list of port authorities or countries)?
• Which delivery methods are required by your port partners (SFTP, API, email/web portal upload, EDIFACT, IATA format)? Options: SFTP, REST API, Email/Portal Upload, EDIFACT/XML, Other
• What document types must be exchanged automatically (crew lists, passenger manifests, cargo declarations, health declarations)? Options: Crew lists, Passenger manifests, Cargo/baggage docs, Health declarations, Custom forms
• Do ports require field-to-field mapping or format transformation (e.g., CSV→XML) for accepted documents? Options: Yes - extensive transformations, Minor mapping required, No - standard formats supported
• What SLAs or delivery windows must we meet for document submission before arrival? Options: 24+ hours, 12 hours, 6 hours, 2 hours or less, Per-port varying requirements
• Should the connector support automated retries, delivery receipts, and audit logs for regulatory compliance? Options: Yes - full audit & receipts, Basic retries only, No - minimal logging

Automated Compliance Certificate Generation

• Which certificate types must be auto-generated for the pilot vessel (e.g., ISM, MARPOL declarations, crew work hour attestations)? Options: ISM/ISM-related, MARPOL/Environmental, Crew work-time attestations, Voyage-specific customs/immigration, Other
• What authoritative data sources will populate certificates (ship registry, crew records, fuel logs, voyage plan)? Options: Ship registry, Crew certification DB, Fuel/consumption logs, Voyage plan system, Other
• Do certificates require digital signatures from named authorities or shore approvers? Options: Yes - digital signature required, Yes - manual sign then upload, No signature required
• What template/format requirements exist for certificates (PDF with structured fields, XML, agency-specific forms)? Options: Agency-specific PDF, Structured PDF with fields, XML/EDI, Other
• What acceptance tests must pass for certificate validity (data source reconciliation, signature verification, port-accepted format)?
• Do you need a certificate expiration/renewal workflow and notifications tied to crew or vessel records? Options: Yes - automated notifications, Manual tracking preferred, Not required for pilot

Crew Certification and Visa Record Management

• How many crew records will be in scope for the pilot vessel (approximate headcount)? Options: Less than 100, 100–300, 300–800, 800+
• Which crew credentials and visa types must be tracked (STCW, medicals, visas, work permits)? Options: STCW, Medical Certificates, Visas/Permits, Flag-state endorsements, Other
• Do you require automated expiry alerts and escalation for soon-to-expire credentials? Options: Yes - email & SMS alerts, Yes - email only, No alerts required
• Should the module validate credentials against external registries or flag-state APIs? Options: Yes - external validation, Optional, No
• What access controls are needed for crew data (who can view/edit sensitive fields)? Options: Ship master & HR, Crew admin only, Shore HR & Ops, Role-based granular access
• Do you need audit trails and signed attestations for visa/crew certification uploads? Options: Yes - full audit & attestations, Basic upload logs, No

Onboard POS Integration and Revenue Reconciliation

• Which onboard POS systems or vendors are used on the pilot vessel? Options: Vendor A, Vendor B, Vendor C, Proprietary/Legacy, Other
• Do POS transactions need to be processed offline and reconciled later, or must they be real-time to shore? Options: Offline with later reconciliation, Real-time sync required, Hybrid (critical items real-time)
• Which revenue types must be reconciled (retail, F&B, excursions, spa, casino)? Options: Retail, F&B, Excursions/shore tours, Spa/amenities, Other
• What currencies and payment methods must be supported (multi-currency, multi-gateway, onboard account charges)? Options: Single currency, Multi-currency, Multiple payment gateways, Guest onboard account only
• What are your reconciliation expectations (daily batch, end-of-voyage, immediate balancing)? Options: Daily batch, Per sail/event, End-of-voyage only, Real-time balancing
• How should refunds, chargebacks, and split payments be handled in reconciliation? Options: Automatic matching & posting, Flag for manual review, Central finance handles outside system

Inventory and Stores Reconciliation Module

• What inventory categories must be tracked for the pilot ship (provisions, retail, consumables, spare parts)? Options: Provisions/food, Retail/shops, Consumables/housekeeping, Spare parts, Other
• How are current stock counts maintained today (manual counts, barcode scans, POS decrements)? Options: Manual cycle counts, Barcode/RFID scans, POS automatic decrement, ERP integration
• What cadence of stock reconciliation do you require (daily, weekly, per-port, on-demand)? Options: Daily, Weekly, Per-port arrival/departure, On-demand
• Do you need automated reorder notifications tied to consumption thresholds or shore replenishment windows? Options: Yes - automated reorder, Yes - thresholds only, No - manual ordering
• Should inventory values integrate with finance/ERP for cost-of-goods and variance reporting? Options: Yes - full integration, Export-only reports, No integration required
• Are there special handling rules (cold chain, hazardous materials, controlled substances) that affect reconciliation workflows? Options: Cold chain items, Hazardous materials, Controlled substances, None of the above

Port Health and Safety Submission Package

• Which health and safety submissions are required by ports on your itineraries (passenger health forms, crew health declarations, vaccination lists)? Options: Passenger health declarations, Crew health declarations, Vaccination/medical lists, PCR/test results, Other
• Which authorities receive submissions and in what formats (port health portal, email, API)? Options: Port health portal, Email/attachment, API/structured feed, Other
• What lead time do ports require for health submissions prior to arrival? Options: 48+ hours, 24 hours, 12 hours, Less than 12 hours
• Do you require automated validation of health data (e.g., valid test result formats, valid vaccination codes)? Options: Yes - strict validation, Basic validation, No validation required
• Should health submissions be linked to passenger/crew manifests and certificates for traceability? Options: Yes - link to manifests, Optional, No link required
• What retention period and audit capabilities are needed for health submission records? Options: 12 months, 24 months, Per regulation, Custom/unsure

Voyage Routing Optimization Engine

• What primary optimization objectives do you want (fuel consumption, ETA adherence, emissions reduction, berth window compliance)? Options: Fuel consumption, ETA accuracy, Emissions reduction, Berth/port window adherence, Crew rest optimizations
• Which constraints must the engine respect (draft limits, speed restrictions, berth availability, environmental zones)? Options: Draft limits, Speed restrictions, Port berth windows, Emission control areas (ECA), Other
• Do you require integration with external data feeds (weather routing, currents, AIS, tide tables)? Options: Weather routing, Ocean currents, AIS/traffic, Tide tables, None
• What level of planner control do you want vs. automated suggestions (fully automatic, planner approves suggestions, planner-only recommendations)? Options: Fully automatic, Planner approval required, Advisory suggestions only
• What acceptance metrics define a successful optimization (fuel % saved, ETA variance hours, berth adherence rate)?
• Will optimized plans need to be exported to voyage plan documents and shared with ports/agents? If so, specify required formats.

• Non-Disclosure Agreement (NDA)
• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Service Level Agreement (SLA) — At-Sea Availability
• Pilot Agreement & Timeline
• Pricing & Payment Schedule
• Data Migration & Ownership Agreement
• Acceptance Criteria & Sign-off
• Governance & Fleet Rollout Decision Framework
• Integration & API Interface Agreement
• Security, Privacy & Data Processing Agreement (DPA)
• Training & Change Management Commitment
• Support, Escalation & Incident Response Plan
• Change Order & Scope Management
• Termination, Exit & Data Return Plan
• Regulatory Compliance & Liability Addendum

• Success Signals Validation Meeting
• Pilot Lessons Learned Retrospective
• Continuous Improvement & Governance Setup
• Enhancement Backlog Prioritization & Roadmap Alignment
• Executive Outcomes & Commercial Closeout

• Confirm resourcing plan and risk mitigations for the roadmap timeline.
• Publish a distributed 'pilot playbook' summarizing decisions, workarounds, and permanent process changes.
• Schedule small-workshop follow-ups for each major theme to design the fix and acceptance tests.
• Purpose & Scope of Governance
• Create a live shared channel and ticketing workflow for issues and enhancements with agreed access permissions.
• Define SLAs and escalation matrix so incidents have deterministic response and ownership.
• Establish a governance roster and meeting cadence for continuous improvement decisions.
• Provision the shared communication channel, invite stakeholders, and publish channel guidelines.
• Configure ticketing templates and severity definitions in the vendor/ops ticket system.
• Publish governance charter with roster, meeting schedule, and decision rights.
• Backlog Intake Review
• Produce a prioritized backlog and a time-phased roadmap for features, fixes, and compliance items.
• Agree acceptance criteria and QA gates for inclusion in the fleet rollout.
• Introductions & Objectives
• Publish the prioritized backlog and roadmap with owners, timelines, and acceptance criteria.
• Schedule sprint/resolution slots for critical fixes and compliance items before fleet cutover.
• Arrange a technical handoff session for items with complex integration dependencies.
• Executive Summary of Outcomes
• Obtain executive sign-off to proceed with the agreed commercial path for fleet rollout or remediation plan.
• Agree any contract amendments or commercial reconciliations required to support scaling.
• Schedule executive checkpoints and confirm high-level milestones for the next phase.
• Execute required contract amendments or purchase orders to enable fleet rollout.
• Publish an executive one-page decision memo and distribute to stakeholders.
• Confirm kickoff date and invite governance/implementation leads to the kickoff meeting.
• Confirm which success signals are met and which require remediation prior to fleet rollout.
• Assign clear owners, timelines, and acceptance criteria for any remediation work.
• Document an explicit go/no-go decision or conditional approval for fleet expansion.
• Publish a one-page validation report mapping each success signal to measured outcome and acceptance status.
• Create remediation tickets for unmet signals with owners, acceptance tests, and target dates.
• Schedule a re-validation checkpoint after remediation work is complete.
• Set Intent & Safe Space
• Produce a prioritized list of lessons learned mapped to concrete changes (process, tech, training).
• Identify knowledge gaps and assign owners to update runbooks, training, and operational playbooks.
• Agree on methods to capture and distribute retrospective outputs to all fleet stakeholders.
• Create and assign updates to operational runbooks and crew training modules based on prioritized lessons.
• Recap of Success Signals
• Value & Effort Scoring
• Shared Channel Design
• Chronological Walkthrough
• Financial & Commercial Reconciliation
• Risk & Compliance Snapshot
• Roadmap Drafting
• What Went Well
• Escalation Matrix & SLAs
• Metrics Review (Data-backed)
• What Could Be Improved
• Decision & Commitments
• Triage & Backlog Workflow
• Resource & Risk Alignment
• Gap & Impact Analysis
• Root Cause Themes & Prioritization
• Acceptance Criteria & QA Gates
• Reporting Cadence & KPIs
• High-level Next Steps & Milestones
• Remediation Options & Trade-offs
• Documenting and Handover
• Governance Roster & Decision Rights
• Decision & Next Steps