Where your team would feel the difference

• How many athletes are on your main-season roster that you plan to monitor? Options: <25, 25-45, 46-70, 71-100, >100
• What roles on your staff would be primary users of athlete workload and injury-risk data? Options: Head coach, Director of sports science, Head athletic trainer, Team physician, Position coaches, Strength and conditioning, Performance analysts, Other
• Describe the current cadence of player monitoring during a typical week in season
• Which existing data sources do you already use to track player workloads or injuries? Options: Wearable GPS/Inertial devices, Heart rate systems, Athlete management system, Video tagging, Medical records, Practice plans/schedules, Manual spreadsheets, Other
• How soon do you need to see measurable changes in injury incidents or workload management to consider a solution successful? Options: Within 1 month, 1-3 months, By mid-season, By season end, Multiple seasons, Unsure

Where current monitoring falls short

• What single monitoring failure over the past season would make you stop and demand change immediately?
• Walk me through a recent case where workload data did not trigger a preventable soft-tissue injury, what happened and who noticed it first?
• How often during the season do you see player workloads spike unexpectedly? Options: Multiple times per month, Monthly, A few times per season, Rarely, Never
• Who on your staff feels most pressure when a player is injured and how does that affect decision making? Options: Head coach, Head athletic trainer, Sports scientist, Team physician, Position coach, General manager, Other
• What downstream operational issues does an unexpected injury create for planning, roster management, or revenue?

The outcomes that would change decisions

• If your platform could reliably flag the top three players at immediate risk for soft-tissue injury, what decision would you make differently that you are not making today?
• What measurable KPIs would you use to judge success over the next season? Options: Injury rate reduction, Days lost to injury, Practice availability percentage, Player performance metrics, Workload compliance, Staff time saved, Other
• Who would need to sign off on changing practice intensity based on alerts, and how quickly could they act? Options: Head coach, Position coaches, Head athletic trainer, Director of sports science, Medical director, Other
• Within your budget cycle, what level of injury reduction or days-saved would justify a paid pilot? Options: 5% injury reduction / small days saved, 10-15% reduction, 20%+ reduction or major days saved, Unsure
• How would success look to players, not just staff, and what would make them accept being monitored?

What usually stops plans from becoming practice

• What single operational constraint has killed past performance initiatives here?
• Tell me about recent rollouts that ran into resistance from players or coaches, what was the turning point?
• Which budget or procurement timelines typically create the largest delays for new equipment or integrations? Options: Quarterly procurement, Annual budget cycle, Grant-based, Donor-funded, Short-term budgets, Unsure
• How many full-time technical or medical staff are available to support integration, configuration, and ongoing monitoring? Options: 0, 1-2, 3-5, 6-10, >10
• If we could prove impact in a pilot, what would still prevent you from scaling to the whole roster?

The other routes you're weighing

• Who else are you actively evaluating to solve workload and injury prediction, and why are they still in the running? Options: Other wearable vendors, In-house analytics build, Existing AMS vendor, Video analytics provider, No alternatives actively considered, Other
• Which current internal approach would have to demonstrably improve for you to keep relying on it instead of moving to a vendor?
• Has anyone on your staff proposed building an internal solution instead of buying, and what resource ask would that require? Options: Yes, significant resources and headcount, Yes, modest resources, No, Unsure
• What would a competitor need to show in a short pilot to beat your incumbent or internal option?
• How important is vendor support for device fitting, provisioning, and staff training compared with self-service tools? Options: Critical, Very important, Somewhat important, Not important

What must be true before we can deploy

• Which integration or data dependency would block the project if it were not available? Options: Video system API access, Medical records access, Athlete IDs roster feed, Live GPS gateway, None of the above, Other
• Which systems will need API-level access or data exports for analytics and thresholding? Options: Athlete management system, Video management system, Electronic medical records, Scheduling software, Identity directory, Other
• Who owns the API access and who would approve credentials in your organization?
• How clean and centralized is your roster and injury history data, would it require manual cleanup before onboarding? Options: Fully clean and centralized, Mostly clean with minor cleanup, Fragmented, significant cleanup needed, Not available digitally, Unsure
• Describe any regulatory, union, or compliance approvals that could delay device deployment to athletes
• Do you have a secure location and staff for charging, storing, and maintaining devices during season? Options: Yes, dedicated kit room, Yes, shared storage, No, need setup, Unsure

The specific signals that will convince you this works

• Name the single metric that would make you sign for full rollout after a pilot Options: Specific injury reduction percent, Days-saved threshold, Practice availability increase, Coach adoption rate, Other
• Which acceptance criteria must be met for device reliability and data latency during a pilot? Options: Battery life targets, Data completeness threshold, Maximum data latency, Device fit standards, Integration stability
• Who will sign acceptance at the end of the pilot and what checklist will they use?
• What minimum sample of athletes and duration do you expect a pilot to include to be convincing? Options: 10 athletes for 2 weeks, 25 athletes for 4 weeks, 50 athletes for 8 weeks, Full position group for 4+ weeks, Entire roster sample, Unsure
• If the pilot meets the metric, what procurement or legal hurdles remain before you could deploy at scale?

If we move forward, what happens next

• What would make your leadership sign within 30 days if the pilot proves the numbers?
• Which budget source would pay for a pilot and who controls release of those funds? Options: Operating budget, Capital expenditure, Performance grants, Research funds, Donor funds, Unsure
• What timeline constraints are non-negotiable for a pilot starting before key competition windows?
• Who else needs to be involved in next conversations to clear technical, medical, and coaching concerns? Options: Head coach, Medical director, IT lead, Athletic director, Player reps, Other
• Which single reason would stop procurement entirely even after a successful pilot? Options: Lack of player buy-in, Unresolvable data privacy concern, Procurement funding blocked, Integration impossible, Union or regulatory veto, Other

• Solution Experience — Workload to Protocol Walkthrough

• Confirm the current state
• You confirm the stated current state and its operational cost is accurate for your team.
• Provide two representative athlete profiles and one typical session file (sensor + session context) to be used in the pilot simulation.
• You confirm the demonstrated scenario produces the operational outcome you defined for reducing workload-related risk.
• Confirm the consequence to your team
• Run a pilot simulation on the provided roster data and deliver a session report with recommended athlete thresholds and a proposed protocol playbook within five business days.
• You agree on the remaining evidence needed and a pilot scope and success criteria to validate the future state.
• Walk through a realistic roster scenario
• Provide a list of stakeholders who must sign off on pilot acceptance criteria and confirm a two-week pilot window.
• Prove integrations and athlete-level thresholding
• Confirm the specific integrations to include in the pilot, such as your video system and medical records endpoint, and provide access details or API contact points.
• Confirm this matches what you need

• Solution Experience — Workload to Protocol Walkthrough
• Solution Experience Deck
• Solution Brief — Workload and Injury-Risk Protocols

• meeting
• slides
• document

• Provision and Ship Sensor Devices
• Onsite Device Fitting and Attachment
• Pair and Calibrate Sensors per Athlete
• Install and Configure Real-Time Gateway
• Activate Live Data Streaming
• Create Athlete Profiles and Individualized Thresholds
• Configure Dashboards and Team Reports
• Integrate Video Analysis Endpoint
• Integrate Medical Records Endpoint
• Deploy Charging Stations and Inventory Management
• Deliver Staff Training and Operational Playbook
• Provide Match-Day Live Monitoring Support
• Perform Firmware Updates and Device Management

Provision and Ship Sensor Devices

• How many sensor devices do you need provisioned for the initial rollout? Options: Less than roster, One per roster spot, Roster + 10% spares, Custom number
• Which device configuration do you require for the roster? Options: GPS+IMU, GPS+IMU+Heart rate, IMU-only, Custom
• Provide your preferred delivery window and any staging addresses for shipments.
• Assign the internal owner who will accept deliveries and manage device inventory.
• Specify any country import, customs, or logistics constraints we must plan for. Options: None, Customs paperwork required, Delayed clearance windows, Other

Onsite Device Fitting and Attachment

• Who on your staff will lead device fitting and attachment sessions? Options: Head athletic trainer, Director of sports science, Operations manager, Other
• Describe the typical training kit or vest you want sensors attached to (material, pockets).
• Select preferred attachment method for sensors during practices and matches. Options: Vest pocket, Elastic strap, Integrated bib, Adhesive mount
• When do you want onsite fitting scheduled relative to first live session? Options: 1 week before, 3-5 days before, Day before, Same day morning
• Indicate documentation you require after fitting (fit card per athlete, photos). Options: Fit card per athlete, Photos, Sizing inventory, None

Pair and Calibrate Sensors per Athlete

• Pair how many athletes will receive individualized sensor pairing on day one? Options: Full roster, Core starters only, Subset for proof of concept, Custom count
• Calibrate which positional or static tests do you require for each athlete (for example standing reference, GPS baseline run)?
• Specify the acceptance criteria that define a successful per-athlete calibration (for example positional error < 1.5 m after 2 minutes stabilization).
• Identify who will supply the roster file with athlete IDs, jersey numbers, and medical identifiers.
• Name how you want athlete devices labeled in inventory (jersey/ID format) for pairing traceability. Options: Jersey number, Last name + number, Unique asset tag, Custom format

Install and Configure Real-Time Gateway

• Where will the real-time gateway hardware be located (stadium booth, control room, training center, cloud edge)? Options: Stadium booth, Control room, Training center, Cloud-hosted edge
• Connect what network types will be available at that location (Ethernet, Wi-Fi, cellular)? Options: Ethernet, Wi-Fi, Cellular, Combination
• Identify any firewall rules, ports, or proxy requirements needed to reach the platform integration endpoint.
• Schedule when installers can access rack space, power, and physical mounting for the gateway.
• Verify whether an uninterruptible power supply (UPS) or redundant power is required for the gateway. Options: Yes, UPS required, No UPS required, Will provide own redundancy, Undecided

Activate Live Data Streaming

• Which live data channels do you need streamed during sessions (position, inertial metrics, heart rate, event markers)? Options: Position, Inertial metrics, Heart rate, Event markers
• Define the acceptance criteria that will validate live streaming performance (acceptable latency, packet loss, minimum uptime percentage).
• Provide the consumer method for live data (API endpoint URL, secure RTMP, dashboard embed) and authentication mechanism.
• Connect to which internal systems should live feeds be routed (operations monitor, coaching tablets, third-party dashboards)?
• Report how you will verify match-day live data (who performs checks and what artifacts are recorded).

Create Athlete Profiles and Individualized Thresholds

• Who will provide baseline athlete metrics to seed individual profiles (medical staff, sports scientist, external testing lab)? Options: Medical staff, Sports scientist, External lab, Other
• Select individualized threshold types you require per athlete (acute:chronic workload ratio, speed zone limits, heart-rate zones). Options: Acute:chronic workload ratio, Speed zone limits, Heart-rate zones, Custom rules
• Confirm the acceptance criteria for individualized threshold configuration, including who must sign off and target alert precision.
• Attach or paste a sample roster file format you want us to ingest for athlete profile creation.
• State how often thresholds should be reviewed and updated during the season. Options: Weekly, Biweekly, Monthly, Event-driven

Configure Dashboards and Team Reports

• Choose the role-based dashboards required (coach view, sports scientist view, medical staff view). Options: Coach, Sports scientist, Medical staff, Operations
• List the default KPIs you want on the team home dashboard (player load, high-speed running distance, recovery score). Options: Player load, High-speed running, Recovery score, Custom KPIs
• Outline whether you need scheduled PDF or CSV reports delivered automatically after sessions and the recipients. Options: PDF, CSV, Both, No scheduled reports
• State any custom drill-down filters required (position group, session type, unit of distance).
• Estimate how many distinct saved reports or templates your team will use. Options: 1-5, 6-15, 16-30, More than 30

Integrate Video Analysis Endpoint

• Name the video integration method your system supports (RTSP stream, API clip export, file-drop). Options: RTSP, API clip export, File-drop, Other
• Attach the video endpoint URL patterns and authentication approach we should configure for the integration.
• Choose whether clip-sync should be timestamp-based or event-marker-based for your workflow. Options: Timestamp-based, Event-marker-based, Manual sync
• Map the field mapping rules between tracking timestamps and video frame time we must apply.
• Assign who will have admin access to the video system to approve integration credentials.

Integrate Medical Records Endpoint

• List which medical record document types you want integrated (injury logs, rehabilitation notes, clearance status). Options: Injury logs, Rehab notes, Clearance status, Imaging reports
• Upload the API endpoint or SFTP details and authentication method for medical data exchange.
• Confirm any consent forms, protected health information handling policies, or data-sharing agreements required by your medical team. Options: Yes, consent required, No additional consent, Under review
• Map which medical record fields must populate athlete profiles (diagnosis code, expected return-to-play date, treatment notes).
• Designate the medical staff member authorized to approve data access and role permissions.

Deploy Charging Stations and Inventory Management

• How many charging bays and spare devices do you plan to deploy across facilities? Options: 1 per 5 devices, 1 per 10 devices, Custom
• Indicate preferred locations for charging stations and whether they need lockable cabinets.
• Detail whether you require asset tagging (barcode, NFC) and which identifier format to use. Options: Barcode, NFC, QR code, Serial number
• Designate who will manage daily device check-in and charging rotation procedures.
• Estimate whether you need integrations between device inventory and your asset management system. Options: Yes, API integration, CSV exports only, No integration required

Deliver Staff Training and Operational Playbook

• Register the attendee groups for initial training and their expected headcount.
• Outline your preferred training format (on-site workshop, virtual live, train-the-trainer) and session length. Options: On-site full day, On-site half day, Virtual, Train-the-trainer
• Detail whether you require written standard operating procedures and quick-reference match-day playbooks. Options: SOPs and quick cards, SOPs only, Quick cards only, None
• Schedule when initial and follow-up training sessions should take place relative to go-live.
• Upload how you want training materials delivered (digital, printed, learning management system upload). Options: Digital (PDF), Printed, LMS upload

Provide Match-Day Live Monitoring Support

• Do you require on-site technical support coverage for match-day live monitoring? Options: Yes, full match, Yes, kickoff to halftime, No on-site required, Remote support only
• Define your escalation path and maximum response times for operational incidents during events. Options: 15 minutes, 30 minutes, 1 hour, Custom
• Appoint the on-site operations contact and backup contact for match operations coordination.
• Highlight which monitoring dashboards and alert thresholds should be visible in the operations room.
• Capture your desired data retention period and clip capture policy for match-day sessions. Options: 24 hours, 7 days, 30 days, Custom

• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Order Form / Subscription Agreement
• Hardware Purchase Order
• Service Level Agreement (SLA)
• Acceptance Criteria & Test Plan
• Data Processing Agreement (DPA)
• HIPAA Business Associate Addendum (BAA)
• Data Access & Integration Authorization
• Mutual Non-Disclosure Agreement (NDA)
• Change Order Agreement

• Go-live Health Check (Week 1-4 post go-live)
• First Measurement Review (Week 4-10)
• Acceptance Gate — Outcome Validation (around day 90)
• Ongoing Quarterly Success Review

• Schedule the next quarterly success review and circulate the required data extracts ahead of the meeting.
• Implement a device adherence improvement plan addressing causes of missed sessions.
• Produce a short data-quality report highlighting any measurement gaps and proposed fixes.
• Restate acceptance criteria and numeric targets
• Produce a documented acceptance decision with pass/fail recorded per Mutual Commit acceptance criterion and a named buyer signatory if applicable.
• For any unmet criteria, record a remediation plan with concrete tasks and resolution dates to close the acceptance loop.
• Publish the acceptance record documenting pass/fail outcomes and the buyer signatory or conditional acceptance terms.
• Create a remediation tracker listing each failed criterion, the remediation tasks, and firm resolution dates.
• If incumbent systems exist, implement the agreed archival or decommission plan and verify access changes.
• Trend review vs Mutual Commit targets
• Confirm that outcome trends remain within acceptance thresholds or record corrective plans for any regressions.
• Prioritize the enhancement backlog and agree a schedule for the highest priority items to be delivered before the next review.
• Update the enhancement backlog with prioritized items and estimated delivery windows.
• Open remediation tasks for any regression in outcome metrics and record checkpoints to validate fixes.
• Reconfirm committed success criteria and owners
• Confirm the deployment components match the Scope and are functionally available for baseline data collection.
• Record all high-priority blockers and an agreed immediate remediation plan to enable meaningful data collection for the first measurement review.
• Publish a short deployment health summary showing device counts, gateway status, and session capture coverage.
• Resolve outstanding provisioning and connectivity errors and update the provisioning status for affected athlete profiles.
• Confirm training completion for staff who will ingest and act on device alerts.
• Present first measurement data
• Determine whether early outcome metrics are moving toward the Mutual Commit targets and document any shortfalls.
• Agree a prioritized set of corrective actions, including threshold adjustments and adherence remediation, with clear due dates to support the acceptance decision.
• Tune athlete-level threshold rules and publish the updated threshold table used for alerts.
• Present outcome data against each criterion
• Persistent issues and blocker burn-down
• Deployment and provisioning validation
• Data quality and signal integrity review
• Document acceptance decision and signatory acknowledgement
• Early adoption and usage signals
• Enhancement requests and shared channel review
• Root-cause diagnosis for gaps
• Operational adjustments and next-quarter focus
• Agree remediation plan for failed or conditional criteria
• Open issues and blockers
• Corrective actions and timeline to acceptance gate
• Immediate remediation and short plan
• Incumbent system wind-down checklist, if applicable