Questions, answered.

AccelPhase is a sprint-team management system with AI-assisted, athlete-by-athlete decision support. It keeps plan assignment, completion, coach review, feedback, and next-plan context connected.

It is designed for sprint coaches and the athletes they invite, especially teams that need one shared base plan plus athlete-by-athlete review.

Create a free coach account, finish onboarding, create a team, and invite athletes.

Yes. AccelPhase is free for coaches and athletes. No payment method or subscription is required.

Athletes join a team through a coach invitation and do not need to pay.

A coach creates an athlete invitation. The athlete opens the invitation, signs in or creates an athlete account, and joins that team.

Yes. A coach can reuse plan templates, import supported spreadsheet plans, or build a plan manually before reviewing individual adjustments.

No. AI prepares briefs and drafts; server rules validate them, and the coach reviews the result before a plan or adjustment is published.

Yes. The coach can keep the base plan, accept a recommendation, edit it, or require separate review. The coach owns the final action.

Missing values remain missing, conclusions are downgraded, and incompatible distances, timing methods, or training purposes are not silently compared.

A coach can currently see team-bound tasks, submitted task results and context, and reviewed feedback for that coach's team. Personal-mode records do not automatically enter the team view. Task communication is introduced in Stage 2.

AI may draft feedback privately for the coach. The athlete sees it only after coach review and send. Task-scoped plain-text follow-ups are introduced in Stage 2.

They are optional minutes supplied with the team task. Because their intensity is not collected, they are shown separately and are not added to session-RPE load or called total load.

AccelPhase stores a selected IANA time-zone identifier and uses it to interpret local training dates, deadlines, and daylight-saving changes. Existing event timestamps are not rewritten when the setting changes.

AccelPhase uses required session and short-lived authentication handoff storage plus on-device storage for drafts, language, navigation, idempotency, and recovery. It does not currently use advertising or third-party behavioral analytics.

A signed-in user can use the account or record deletion controls described in the privacy notice. AccelPhase verifies the request and applies the documented deletion and minimal-audit rules.

COROS and other wearable connections are not publicly available in AccelPhase. No waitlist or availability date is being promised.

They can verify implemented technical behavior or demonstrate a synthetic workflow. They do not by themselves prove real coach adoption, conversion, training improvement, medical safety, or legal compliance everywhere.