A Quick Snapshot of Your Safety World

• Which best describes your organisation? Options: Part 121 airline, Part 135 operator / charter, MRO / CAMO, Airport operator, Business aviation operator, Other
• How many operational bases/locations do you run? Options: 1, 2–5, 6–20, 21–50, 50+
• Roughly how many aircraft or operational units are in scope for SMS? Options: 1–5, 6–20, 21–50, 51–200, 200+
• Who owns day-to-day SMS operations today (role/title)? Options: Director of Safety, Accountable Executive, Quality Manager, Operations Lead, Shared/No single owner, Other
• When was your last formal SMS gap assessment? Options: Within 3 months, 3–12 months, 1–2 years, 2+ years, Never done one
• Which SMS software or tools are you currently using (if any)?
• How would you describe your current reporting culture? Options: Strong and active, Functional but inconsistent, Weak — low trust, Non-existent / passive
• Approximately how many voluntary safety reports do you receive per month? Options: 0–10, 11–50, 51–200, 201–500, 500+

If an Auditor Pulls the Thread, What Unravels?

• If an auditor asked for your top three recurring SMS weaknesses, what would you hear back from your team?
• Which types of audit non-conformities have shown up most often in past inspections? Options: Policy & documentation, Risk assessment gaps, Investigation quality, Training records, Safety assurance evidence, Data/reporting inconsistencies, Other
• How current and accurate is your risk register across bases and fleets? Options: Fully up-to-date, Mostly current with gaps, Patchy by base/fleet, Outdated / unreliable
• When your team gets a recurring finding, how long does it typically take to close it? Options: <1 month, 1–3 months, 3–6 months, 6–12 months, 12+ months / unresolved
• Who leads audit remediation and how is accountability tracked?
• How do repeated findings affect your operational leadership and crew confidence?

Why Don't People Tell Us What They See?

• If frontline staff could describe the reporting process in one sentence, what would you be worried they might say?
• Which barriers most often stop people from reporting hazards or near-misses? Options: Fear of reprisal, Reporting forms are too complex, No feedback after reporting, Takes too long during shifts, Perception it's just paperwork, Lack of trust in follow-up, Other
• Through what channels can crews currently submit reports? Options: Mobile app, Web portal, Paper forms, Phone/hotline, Via supervisors, Email, Other
• Do you offer confidential and/or anonymous reporting options today? Options: Both confidential and anonymous, Confidential only, Anonymous only, Neither
• What does your feedback loop look like after a report is submitted—how do reporters hear back and how quickly? Options: Immediate acknowledgement + updates, Acknowledgement + occasional updates, Delayed updates, No consistent feedback
• Can you share an example of a near-miss or hazard that wasn’t reported until it recurred? What happened?

What Would Audit‑Ready Look Like in Your Shoes?

• If an auditor asked you to show 'audit-ready' SMS evidence tomorrow, what single thing would make you feel confident?
• Which measurable success signals matter most to you (pick all that apply)? Options: Monthly reporting rate target, Risk register accuracy percentage, Average time to close investigations, Number of repeat findings, Audit readiness score, Frontline engagement index
• Which one of the above is the non-negotiable priority for the next 12 months? Options: Monthly reporting rate target, Risk register accuracy, Time to close investigations, Reduce repeat findings, Audit readiness score, Frontline engagement index
• What measurable baseline and target would you set for that priority (be specific)?
• Who across Safety, Ops, and IT must sign off on acceptance criteria for success? Options: Accountable Executive, Director of Safety, Head of Ops, Head of Maintenance/MRO, IT Lead, HR/People, Other
• What time horizon would make achieving those targets realistic for your organisation? Options: Immediate (1–3 months), Near term (3–6 months), Medium (6–12 months), Longer term (12+ months), Unsure

Where Could Technology Actually Stop Creating Work and Start Creating Trust?

• If your safety software could only do one thing to rebuild trust with crews, what should it be?
• Which software features would move the needle for you (select up to five)? Options: Simple mobile reporting, Anonymous reporting, Closed-loop feedback to reporter, Integrated risk register, Investigation workflow tracking, Dashboards for leadership, Multi-base role controls, Two-way integration with maintenance/CMMS, Audit evidence packaging
• Which integrations are must-haves for day one? Options: Maintenance/CMMS, Flight Ops / Dispatch, Crew rostering, HR / training records, EFB/flight data, None / no integrations required, Other
• What are your data residency, security or compliance constraints we should know about? Options: On-prem required, Cloud acceptable, Hybrid preferred, Must meet SOC2, Must meet ISO27001, Other / specialised
• Who needs day‑one access to the platform and at what permission level?
• How do you prefer crew-facing reporting be delivered—native mobile app, mobile web, SMS, or other? Options: Native mobile app, Mobile web portal, SMS/text-based, Paper-to-digital option, Hybrid

What Would We Be Committing To — Beyond the License?

• If you signed an agreement, what hidden expectation or internal constraint would most likely derail progress?
• What capacity do you have internally to support implementation (pick the closest)? Options: Dedicated FTE(s) for SMS roll-out, Shared resource across functions, Contractor support only, Very limited/no capacity
• What budget runway is realistically available for this initiative this year? Options: Fully funded, Partially funded, Budget request pending, No budget allocated yet
• What governance cadence would you require for commercial and deployment decisions? Options: Weekly steering, Bi-weekly, Monthly, Ad-hoc as needed
• What specific acceptance criteria must we meet for you to consider the engagement a success?
• How will you measure ROI or business impact from a successful SMS implementation? Options: Fewer audit findings, Reduced incident rates, Faster investigation closure, Improved crew engagement, Operational resilience metrics, Other

Ready to Run or Need a Safety Net?

• What single failure mode in your environment worries you most during deployment (integration, data quality, adoption, regulator scrutiny)?
• How available is the data we’d need to integrate (reports, HR lists, maintenance records)? Options: All data readily available, Most available with some effort, Partial / manual extraction needed, Significant data gaps
• Which security or auditor requirements must the solution satisfy before go‑live? Options: SOC2 Type II, ISO27001, FAA/regulator-specific controls, Local data sovereignty, Other / bespoke
• Is your regulator or internal auditor already engaged in the readiness conversation? Options: Actively engaged, Aware but not engaged, Not engaged, Unsure
• What communications and change plan exists to prepare crews and leadership for launch? Options: Detailed plan ready, High-level plan, Informal communications only, No plan yet
• What training approach will work best for your teams? Options: Hands-on classroom, Train-the-trainer, Self-paced e-learning, Blended approach
• Realistically, when could you commit to a phased roll-out start date? Options: Immediately, Within 1–3 months, 3–6 months, 6–12 months, Undecided

Quick safety snapshot — a few facts to get us started

• What single safety metric do you rely on most to understand current performance? Options: Hazard reports per 100 employees/month, Near‑miss reports, Open risk register items, Number of audit findings, Investigation cycle time, Other
• Which platform or combination of tools do you currently use to capture safety reports and artifacts? Options: Homegrown/Excel, Paper forms / email, Commercial SMS software, Maintenance/flight ops system with links, No consistent tool, Other
• Roughly how many safety reports (hazards, occurrences, near misses) do you receive in an average month? Options: 0–10, 11–50, 51–200, 201–500, 500+
• Who formally owns the risk register and signs off on risk acceptance decisions? Options: Accountable Executive, Safety Director/Manager, Quality/Compliance, Operations leadership, Shared committee, No single owner
• How do front‑line employees most commonly submit reports today? Options: Mobile app, Web form, Paper form returned to supervisor, Email, Phone/dispatch, Anonymous hotline, Other

Tell me where it actually hurts — the surprises and the recurring headaches

• If an auditor showed up tomorrow and pulled the worst examples, what three specific gaps would they highlight first?
• Which of these issues causes the most day‑to‑day friction for your team? Options: Low reporting rates, Slow investigations, Outdated risk register, Poor root cause quality, Action items left open, Lack of executive visibility, IT/data silos
• How often do you hear staff dismiss safety processes as ‘paperwork’ rather than protection? Options: Always, Often, Sometimes, Rarely, Never
• Share a recent incident where a known hazard was not acted on — what happened and what was the impact?
• How do these recurring gaps typically make you feel as a safety leader? Options: Frustrated/overworked, Worried about exposure, Motivated to change, Helpless/blocked by org, Other
• On average, what is your report → investigation → closure timeline today? Options: <7 days, 7–30 days, 1–3 months, 3–6 months, Not tracked

Are we just tolerating risk? — where legacy habits cost you

• What practices are you keeping simply because ‘we’ve always done it this way’ rather than because they demonstrably reduce risk?
• Which SMS artifacts are actually current and used in decision making? Options: Safety policy, Risk register, Hazard logs, Investigation reports, Corrective action logs, Training records, None of the above
• Do you have a single source of truth for safety data, or is information scattered across teams? Options: Single integrated SMS platform, Partially centralized (some systems), Scattered across spreadsheets/paper, No idea
• How often is the risk register formally reviewed and by which governance body? Options: Weekly — operational review, Monthly — safety committee, Quarterly — senior leadership, Annually, Never
• Where do you find duplicate, conflicting, or stale records today — give one concrete example.
• If you could immediately retire one legacy process that generates noise but little safety value, what would it be?

If auditors gave you a standing ovation — the concrete signals of an excellent SMS

• Imagine a regulator declared your SMS ‘best practice’ — what three visible behaviors or documents would prove it?
• Which of the following success signals would you want to show during an audit? Options: High reporting culture (reports/head), Timely closed investigations, Accurate, current risk register, Evidence of corrective action effectiveness, User adoption metrics, Regulator-ready dashboards
• What constraints—budget, IT, people, contract, or culture—would most limit achieving that vision? Options: Budget, IT/integration, Staff/time, Union/staff resistance, Regulatory ambiguity, Other
• Who needs to be visibly changed or convinced in your organization for that ideal to stick? Options: Accountable Executive, Operations leadership, Maintenance leadership, Frontline supervisors, IT, HR/Training, Union reps
• How would you prefer to present evidence in an audit—live dashboards, narrative packs, or packaged exports? Options: Live dashboards with drilldown, Narrative summaries with attachments, Packaged files and document folder, Hybrid approach
• Name one metric or KPI you would celebrate publicly each month if the pilot succeeded.

What’s standing in the way (even if it feels small) — hidden blockers and soft limits

• What small, often ignored gap today has the biggest chance of becoming a formal finding tomorrow?
• How would you rank the importance of cultural issues versus technical issues in blocking SMS progress? Options: Mostly cultural, Mostly technical, Equally both, Unsure
• Which of these are active blockers for change right now? Options: No anonymous reporting, Insufficient investigation owners, Lack of integration with maintenance/OPS, Insufficient training/time, No executive dashboard, Data ownership disputes, Other
• How often do IT/security reviews delay safety tool rollouts in your organisation? Options: Rarely, Sometimes, Often, Always, Not applicable
• Who typically champions SMS improvements internally, and who tends to resist? Give names/roles if possible.
• If you could remove one blocker in the next 90 days, which would it be and why?

Plumbing, people & proof — mapping where data, roles, and flows must work

• If your safety data had to flow end‑to‑end without manual handoffs, where would it break first?
• Which systems currently hold safety‑relevant data (select all that apply)? Options: Maintenance tracking (AMMS), Flight ops/crew scheduling, Homegrown SMS/Excel, Third‑party SMS, HR/training systems, Safety bulletin boards/email, None
• Which integrations are non‑negotiable for you to consider a solution? Options: Maintenance system, Crew scheduling, Flight data monitoring, HR/training, Email/phone reporting, ERP/finance, Other
• Who will own day‑to‑day activities: reporting intake, investigations, and risk register upkeep? Options: Safety team, Operations, Maintenance, Quality, Cross‑functional committee, Other
• What access controls, multi‑base role requirements or separation‑of‑duty rules are absolute musts for your organisation?
• How would you prefer anonymous reports handled operationally compared with confidential identified reports? Options: Separate anonymous stream with limited access, Same workflow with redaction options, Supervisor filters before investigation, Unsure — need guidance

Readiness & next steps — what would make you comfortable to move forward

• What would make you say 'yes' to a pilot and mean it — not a tentative 'let’s see'?
• Which pilot scope feels both meaningful and realistic for your team? Options: Single base / single fleet, Multiple bases / single fleet, MRO only, Entire ops for a single discipline, Other
• What success criteria must be achieved to consider a pilot accepted? Options: Increase in usable reports, Reduced investigation turnaround, Risk register updated and current, Integration proven with key systems, User adoption threshold met, Regulator/auditor feedback positive
• How soon could you allocate people and IT support for a discovery or pilot phase? Options: Immediately, Within 1 month, 1–3 months, 3–6 months, Unsure
• Who should be at the table for the next conversation (roles or names)? Options: Accountable Executive, Safety Director/Manager, Operations Lead, Maintenance Lead, IT/Security, HR/Training, External auditor/consultant
• What reservations or hard constraints should we surface now so we can address them proactively?

Start Here — Tell Us About Your World

• Who are you in the organisation and which functions will be directly involved in SMS decisions? Options: Director of Safety / SMS Owner, Accountable Executive / CEO, Operations (COO, Ops Manager), Maintenance / MRO Lead, Quality Manager, IT/Integrations Lead, HR / Training, Regulatory Affairs, Other
• Which operating model best describes your organisation today? Options: Part 121 airline (multi-base), Part 135 operator / charter, MRO organisation, Airport authority, Business aviation operator, Other
• Roughly how many operational bases and fleets (types) will the SMS need to support? Options: Single base / single fleet, Single base / multi-fleet, Multi-base / single fleet, Multi-base / multi-fleet, Unsure / need to confirm
• Who will be our primary contact for technical integrations and data access?
• How soon do you want to have a working pilot or first deployment (phased)? Options: Immediately / <1 month, 1–3 months, 3–6 months, 6–12 months, No timeline yet

Are You Comfortable Leaving Safety to Hope?

• When staff encounter hazards today, how often do you believe a report actually gets submitted? Options: Most of the time, About half the time, Rarely, Almost never, Don't know
• Tell us about a recent example where a frontline report changed (or failed to change) an operational decision—what happened and how did that feel for the team?
• Which of these barriers best explain why people might not report hazards here? Options: Fear of reprisal, Cumbersome process / time pressure, Unclear benefits / nothing changes, Preference for informal channels, Language or accessibility issues, Other
• How would you describe the emotional climate around reporting—are people proud to report, indifferent, defensive, or worried? Options: Proud / proactive, Generally positive, Indifferent, Defensive / protective, Worried / fearful, Varies by team
• If reporting culture were a dial from 0 (dead) to 10 (everyone reports, no hesitation), where are you and how did you land on that number?

What Does Your SMS Actually Say vs. What It Does?

• When auditors come in, which recurring findings or gaps keep showing up in longer reports? Options: Risk register gaps, Incomplete investigations, Training records issues, Policy not implemented, Insufficient reporting rates, Other
• How accurate and current is your risk register today—does it reflect active operational hazards or a historical list? Options: Highly current and operational, Mostly current with some stale items, Mostly historical / needs overhaul, We don’t maintain a formal risk register, Unsure
• Where do you currently store SMS artifacts (reports, RCA, risk register, SOPs) and who controls access? Options: Shared network drive, Safety-specific software, Email / folders, Document management system (DMS), Paper binders, Mixed / other
• Share an example of a time a documented procedure didn’t match the operation on the ground—what broke, and who had to fix it?
• How frequently do you run internal safety assurance checks or mock audits, and what typically derails them? Options: Monthly, Quarterly, Biannually, Annually, Rarely / never

If You Could Fix One Safety Headache Overnight

• What single outcome would change your day-to-day experience the most if it were guaranteed tomorrow?
• Which measurable success signals matter most to you? Pick the top three. Options: Increased voluntary reporting rate, Up-to-date risk register, Reduced time-to-close investigations, Audit-ready evidence trail, Improved front-line satisfaction with SMS, Reduced incident recurrence
• What targets would you set for those signals in the next 6–12 months?
• How would regulators and auditors recognize improvement—what artefacts or behaviours would convince them? Options: Complete and current risk register, Documented investigation workflows with closure evidence, Training and promotion records, Anonymous reporting options with response logs, Governance meeting minutes and actions
• If we achieved those targets, who in your organisation would call that a success—and who might still be unconvinced?

Who Would Notice If It Worked?

• Are your decision-makers aligned on what ‘good’ looks like for SMS, or do different functions expect different outcomes? Options: Fully aligned, Mostly aligned with a few differences, Significant misalignment, No alignment / each team has its own view
• Who holds authority to approve changes to SOPs, integrations, and training curricula? Options: Accountable Executive, Director of Safety, Ops Lead, Quality/MRO Lead, IT Lead, Collective body / steering group, Other
• When you evaluate vendors, which of these weighs heaviest in a buying decision? Options: Aviation operational experience, Ease of use for front-line, Integration capabilities with existing systems, Support and implementation services, Regulatory evidence and templates, Cost
• Describe previous procurement or deployment experiences—what made them smooth or painful for stakeholders?
• Who do we need buy-in from to run a pilot, and what approvals would they require?

What’s Standing Between Today and Deployment?

• If systems and people could talk honestly, what obstacle would they name first as the reason deployment stalls? Options: Lack of data access / siloed systems, Insufficient IT resources, People capacity / time constraints, Regulator readiness concerns, Cultural resistance, Budget approvals
• Which of these data sources must we integrate to make the platform valuable on day one? Options: Flight ops (FOQA/ORM) data, Maintenance records / AMOS, Training / rosters, Crew scheduling, HR (competence/roles), Existing safety reporting system, Other
• What access constraints or security requirements should we plan for (e.g., air-gapped systems, SSO, role-based controls)?
• Who will be responsible for ownership of deployable artefacts—data feeds, integrations, user provisioning, communications? Options: IT/Integrations Lead, Director of Safety, Ops Manager, Quality/MRO Lead, Third-party integrator, Other
• How would regulators/auditors want to see readiness controls demonstrated during handover? Options: Tested reporting flows with logs, Audit trail of investigations, Governance sign-off documents, Training completion records, Live access to risk register

Let’s Map a Realistic First Win

• What would you accept as a minimally scoped pilot that proves value—what must it include and what can be excluded?
• Which user group should be in the pilot to surface the most meaningful signals (e.g., line crew, maintenance, ramp, ops control)? Options: Line crew / flight crew, Maintenance technicians, Ramp / ground ops, Ops control / dispatch, Quality / safety teams, Mixed group
• What acceptance criteria will you use to decide whether to expand after the pilot (pick up to three)? Options: Increase in reports submitted, Time-to-investigation closure reduced, Risk register updated with actionable items, Positive front-line feedback, No major integration issues, Regulatory confidence
• What training and communication channels will you use to introduce the pilot and sustain engagement? Options: In-person briefings, E-learning modules, Tooltips / in-app guidance, Team huddles / safety meetings, Email campaigns, Union/rep engagement
• What resources (internal or external) can you commit to run a 3-month pilot—roles and approximate FTE/time allocation?

Start Here — Tell Us Who You're Protecting

• Which best describes your organization? Options: Part 121 airline/operator, Part 135 operator / charter, MRO / Maintenance organization, Airport authority, Business aviation operator, Other
• Who in your organization will be most accountable for SMS decisions and sign-offs (name/role or team)?
• How many operational bases or hubs do you operate that will need distinct SMS roles or configurations? Options: Single base, 2–5 bases, 6–15 bases, More than 15
• Describe the teams involved in evaluating safety software and processes (safety, operations, IT, HR, legal — who else?).
• What timeline are you working toward for achieving audit-ready SMS capability? Options: Immediately / in 1 month, 1–3 months, 3–6 months, 6–12 months, No fixed timeline

Are You Comfortable With Your 'Safe Enough' Story?

• When you step back, what part of your current SMS gives you the least confidence that it will withstand a focused regulator audit?
• How often do safety reports get closed with clear corrective actions and measurable outcomes? Options: Almost always, Often, Sometimes, Rarely, Never
• Which of these do you suspect is happening in your program today? Options: Under-reporting of hazards, Stale or unreviewed risks, Investigations without closure, Lack of training follow-through, Data not reaching decision-makers
• Tell us about a recent moment that made you worry your SMS is more paperwork than protection (what happened and how it felt).
• How long have you tolerated the issues above before deciding they must change? Options: Under 3 months, 3–12 months, 1–3 years, Multiple years, I don't feel we've tolerated them — we're proactive

When the Audit Door Opens, What Worries You Most?

• If a regulator walked in tomorrow, which single documentation or evidence gap would most likely trigger a finding? Options: Risk register accuracy, Investigation closure notes, Training records, Reporting confidentiality controls, SMS governance minutes, Other
• Have you had repeat findings from past audits? If so, describe the finding, how long it's recurred, and attempted fixes.
• Which audit standard is your primary target for compliance? Options: FAA Part 5, ICAO Annex 19, IS-BAO, IOSA, National regulator standard, Multiple / Other
• How do audit readiness activities show up in your day-to-day operations today (scheduled reviews, random spot checks, internal audits, none)? Options: Regular internal audits, Ad-hoc reviews, Pre-audit checklist only, No formal readiness activities
• What would acceptance by your regulator/auditor look like—describe the concrete artifacts and behaviors they'd want to see.

Where Does Your Risk Register Actually Live?

• If I asked to review your risk register right now, which statement would best describe it? Options: Single authoritative register, actively maintained, Multiple registers across teams, Spreadsheet(s) with limited ownership, Mostly tacit/knowledge-based, not written, I’m not sure
• Who is assigned as the owner for each high and extreme risk, and how often are owners required to update mitigation status?
• What percentage of register items have a verified mitigation plan with dates and owners? Options: 90–100%, 70–89%, 50–69%, Less than 50%, Unknown
• How do you currently validate that mitigations actually reduce operational exposure (metrics, sampling, audits)?
• Give an example of a risk that was either removed from the register or re-rated—what triggered the change and who signed it off?

Who Really Owns Safety When Shift Changes Happen?

• When operations transfer between bases, which handoff failures cause the most safety degradation? Options: Information not shared, Shift-level risk ownership unclear, Local mitigations not applied, IT/permissions mismatch, Other
• Describe how you route urgent safety issues across crews, local managers, and central safety—what works and what fails.
• Do you enforce multi-base role separation (local vs corporate) with technology today, and how effective is it? Options: Yes, very effective, Yes, but inconsistent, No, partially enforced manually, No enforcement
• How many people across the business need role-based access to safety data (approx number and teams)? Options: 1–10, 11–50, 51–200, 201–1000, 1000+
• What communication channels are relied on for urgent safety escalations (choose all that apply)? Options: Phone/voice, Email, SMS/Instant message, Safety platform notifications, Pager/dispatch, Other

If Your Front-Line Could Tell One Truth, What Would It Be?

• What do you hear from crew, technicians, or ramp staff about the reporting process—frustration, fear, indifference, or something else? Options: Fear of blame, Too much effort to report, Don't see result/value, Happy to report, Other
• How often do reports contain actionable detail versus vague observations? Options: Mostly actionable, Often actionable, Sometimes, Rarely actionable
• What mechanisms do you offer for confidential or anonymous reporting today, and how trusted are those mechanisms? Options: Confidential reporting available and trusted, Anonymous option available but mistrusted, No anonymity available, Unknown
• Share an example when a frontline report led to a meaningful operational change—what changed and who owned it?
• What would make your people say: 'When I raise something, it actually gets fixed'—list concrete signals. Options: Faster closure times, Clear feedback loop, Visible corrective actions, Recognition of reporters, Data-driven follow-up

What’s Blocking Data from Flowing Into Decisions?

• When data should inform safety decisions, what usually breaks the chain—collection, integration, quality, or analysis? Options: Collection issues, Integration/API gaps, Data quality problems, Lack of analytics, Decision-makers ignoring data
• Which systems do you need integrated with an SMS platform (choose all that apply)? Options: HR/roster, Maintenance MRO/EAM, Flight ops/FDM, LMS/training, ERP/finance, Regulatory reporting portals, Other
• Do you have internal data owners and an integration roadmap (documents, APIs, SLAs)? If yes, summarize timing and blockers.
• How real-time do safety feeds need to be to affect operations (immediate, hourly, daily, weekly)? Options: Immediate (minutes), Hourly, Daily, Weekly
• What data privacy or regulatory constraints must any integration respect (e.g., PII, vetted access for investigators)?

Imagine No Mystery Incidents — What Does That Look Like?

• If your SMS achieved everything you hoped in 12 months, what specific behaviors and metrics would show that success?
• Which of these would be the clearest sign the program works for you? Options: Sustained increase in voluntary reporting, Reduced time-to-closure for investigations, Up-to-date risk register with mitigations, Clean regulator audits, Operational decisions driven by trends
• What targets would you set for reporting rates, risk reduction, or investigation closure in the first 6–12 months?
• How would frontline workers and middle managers feel differently if those targets were met—what would they say?
• Who needs to be visibly cheering when those outcomes arrive (sponsors, teams, external stakeholders)? Options: Accountable Executive, Director of Safety, Operations leadership, Union/employee reps, Regulator, Other

What Would You Risk to Keep Doing Nothing?

• If investment in fixing SMS gaps didn't happen, what negative outcome is most likely within the next 18 months? Options: Regulatory finding, Operational disruption, Incident frequency increase, Reputational damage, Financial penalties, Other
• How do budget cycles and procurement windows constrain the speed at which you can act?
• What internal stakeholders would resist change, and why (cost, culture, perceived duplication)?
• What is an acceptable, bounded risk you’d be willing to tolerate during a phased deployment (e.g., limited to one base, manual backup processes)?
• If doing nothing carries risk, what minimal investment could materially reduce the greatest single exposure today?

Let's Prove It — Quick Wins, Pilot Scope & Success

• If you had to prove value in 90 days, where would you run a pilot—choose the site/team and why?
• Which pilot scope would most convince stakeholders: reporting culture uplift, risk register cleanup, investigation workflow improvement, or integration proof-of-concept? Options: Reporting culture uplift, Risk register cleanup, Investigation workflow improvement, Integration proof-of-concept, Combined small-scope pilot
• Who must be engaged and sign off on pilot success (roles and contact types)?
• What measurable acceptance criteria would you require to call the pilot successful (specific KPIs and thresholds)?
• Realistically, what internal support (IT access, data extracts, local champions) can you commit to for a pilot? Options: Full support available, Limited support during business hours, Minimal support — we need vendor-led work, Unknown
• How quickly could you start a pilot if resource and scope were agreed? Options: Immediately, Within 2 weeks, 1–2 months, 3+ months

The Human Side — Change, Training & Governance

• When a new safety process was introduced, what learning or adoption issue surprised you the most?
• Which training model has the best uptake in your organization: classroom, micro-learning, on-the-job coaching, or blended? Options: Classroom, Micro-learning, On-the-job coaching, Blended approach, Other
• What governance cadence do you currently have for safety metrics and remediation tracking (weekly, monthly, quarterly, ad-hoc)? Options: Weekly, Bi-weekly, Monthly, Quarterly, Ad-hoc
• Who are the change champions that would need dedicated time to support rollout (roles, not names)?
• What would make staff feel the change is fair and not punitive (communication tone, anonymity, visible fairness measures)?

Final Frame — Commitment, Risks & Next Steps

• What level of commercial commitment is realistic for your organization right now (pilot budget, multi-year, lease/subscription, not ready)? Options: Pilot budget only, Single-year contract, Multi-year commitment, Prefer Opex subscription, Not ready to commit
• Who must approve commercial and governance terms (roles and approval path)?
• What are the top three non-negotiable success signals that would trigger mutual commit to go live?
• What remaining questions or uncertainties would you need answered before agreeing to a pilot or scope of work?