# Start with your athletes’ data.

MovePacket is being built for independent coaches and small coaching businesses that want reliable access to the data of the athletes they actually coach. The goal is athlete-authorised connections, supported history and dependable delivery of new activities.

**The private beta starts with original FIT uploads.** It does not yet connect provider accounts, invite athletes, import a coaching roster or synchronise activity history.

## Bring an activity today

1. Obtain an original FIT activity file through an export you are authorised to use. Available exports depend on the device or platform.
2. Upload it in your invited [workspace](/upload) or through the [API quickstart](/docs/quickstart).
3. Follow its processing status, then retrieve the decoded data and unchanged original.
4. Open the activity’s **Record** tab to inspect intake and decoder details, verify the original’s checksum, or export the current record metadata.

Only supported FIT activity files are accepted, up to 4 MiB each. A source brand being listed on the website does not mean its account is connected or that every export it produces is supported. See [activity limits](/docs/activities).

Upload only files you have permission to process. The current beta isolates workspaces but does not assign activities to verified athlete identities or enforce per-athlete access. Keep athlete mapping and end-user permissions in your own application until those capabilities are available.

## Existing coaching platforms

You can test MovePacket with an authorised original FIT export while retaining your existing coaching workflow. There is no TrainingPeaks account connection, coaching-roster import or historical sync in this release.

Do not share athlete passwords or use a coaching relationship as a substitute for permission to access another service. Any future platform adapter will require an authorised integration route. MovePacket is being designed to support multiple intake routes rather than depend on one coaching platform.

## The connection experience we are building toward

| Step | Required outcome | Current status |
| --- | --- | --- |
| Link an athlete | Verify the athlete identity and the coaching relationship | Planned |
| Authorise a source | Athlete sees and grants the access being requested | Planned |
| Bring history | Import what the source supports; report coverage and gaps | Planned |
| Receive new activities | Track delivery, retry failures and surface reconnect needs | Planned |
| Preserve the record | Keep originals, identifiers, provenance and processing details | Original FIT, checksum, receipt time, status and decoder metadata available; richer provenance planned |
| Control access | Scope app permissions, revoke access and support retention/deletion | Workspace authentication available; athlete/app grants and self-service controls planned |

Garmin, Wahoo, Karoo and COROS are initial candidate sources. Supported routes, historical coverage and launch order depend on authorised provider access and pilot needs. No launch date or universal compatibility is promised.

## What a healthy connection should show

A future connection should make the athlete and source clear, show when data last arrived, distinguish imported history from ongoing sync, and report missing periods or required action. A connected badge alone is not enough.

The beta’s activity status describes processing of an uploaded file. It is not a device-sync or source-freshness indicator.