Start with the files the coach already has
Many teams have useful training history trapped in CSVs, wearable exports, dashboard downloads, and testing spreadsheets. AthDash treats those exports as the first path, not a temporary compromise.
The export audit checks whether the available data can support a coach-facing Driver Card. When it cannot, the output should say what is missing instead of making a loose claim.
What AthDash checks
- Whether drivers, outcomes, and lag windows are declared clearly enough to test.
- Whether the athlete has repeatable outcome events and adequate coverage.
- Whether confounders like recent load, travel, or soreness are available.
- Whether the result can be returned as ADVISE, BORROW, WITHHOLD, or DECLINE.
Why this is useful before integrations
An export audit shows whether the decision workflow is worth productizing for your coaching operation. It produces a sample artifact, identifies data gaps, and keeps the public claim honest before any live connection is promised.
Training rows
Sessions, load, notes, recovery markers, and benchmark outcomes.
Driver gate
Candidate signals are tested against declared outcomes and caveats.
Next data
The artifact says what to collect next when a claim is too thin.