Tag Management
A real home for library tags — create, rename, merge, and organize them across your whole training library, personal or shared.
Overview
Tags used to be something you typed into a program or exercise and hoped for the best — there was no way to rename one, see everything it was applied to, or clean up a duplicate once it existed. We've built a proper Tags section into your library that fixes that, and extended tagging to reach Workouts, Blocks, and Progressions for the first time — previously only Programs and Exercises could be tagged at all.
What's New
A dedicated Tags page
- Every tag now lives in a real management page under your library, listing its name, content type, and scope (Personal or Institution), with usage counts so you can see exactly what a tag is applied to before you touch it.
Tag any of your five library content types
- Programs, Exercises, Workouts, Blocks, and Progressions can all be tagged now — the last three are newly taggable with this release.
- Adding a tag happens right on the item's own form, in the same tag field you're already used to — search existing tags or create a new one on the spot.
Rename, delete, and clean up safely
- Renaming a tag updates it everywhere it's used. Deleting one asks for confirmation and tells you exactly how many items it'll be removed from first.
- Select multiple tags at once to bulk-delete them.
Personal tags vs. shared tags
- Tags follow the same personal-vs-institution split as your library content (see Personal Library, from our May update): a tag you create in your personal library stays private to you.
- When you're ready to share one, use Move to transfer a tag — and everything it's applied to — into your institution's shared set, or the other way around.
Why It Matters
- A tag vocabulary that actually stays useful. Typos and duplicate tags can be fixed once instead of haunting your library forever.
- Nothing gets tagged by accident into the wrong audience. Personal tags stay personal until you explicitly choose to share them.
- More of your library is organizable. Workouts, blocks, and progressions join programs and exercises as taggable content.
Healthy Roster Integration
Injury status from your athletic trainers' own system, synced into FYTT automatically — no re-keying required.
Overview
We've added a Healthy Roster integration, syncing injury data straight from the athletic-training EMR many of our customers' ATs already use every day into FYTT. Once connected, injuries for matched athletes import automatically every night, so the information a coach sees in FYTT reflects what the training room already knows — without anyone entering it twice.
What's New
Connect with your Healthy Roster credentials
- Ask your athletic training staff (or Healthy Roster support) to issue API credentials for your organization's Healthy Roster account — an Application ID, an Application Secret, and your Healthcare Provider ID — and enter them in FYTT to authorize the connection.
Automatic athlete matching
- FYTT imports your Healthy Roster organizations and athletes and matches them to your FYTT roster automatically. Review the matches afterward to make sure everyone is covered, and correct any that didn't match on their own.
Nightly injury sync
- Once athletes are matched, their injuries import from Healthy Roster every night, keeping FYTT current with what's logged in the training room.
Shows up right where you already look
- Synced injuries appear automatically on the athlete's Injuries tab and in team injury reports — the same places an injury logged directly in FYTT would show up.
Why It Matters
- No more double entry. Athletic trainers already record injury status in Healthy Roster; coaches don't need to ask for it separately or re-type it into FYTT.
- Fewer surprises at practice. Coaches can see who's dealing with what, sourced straight from the AT's own records, without a manual handoff.
- Careful with sensitive data. FYTT imports only participation-relevant injury details — no clinical notes or diagnosis information — consistent with how FYTT already handles PHI everywhere else.
Individualized Athlete Reports
Give one athlete their own version of the team report, without touching what everyone else sees.
Overview
Every athlete's default report used to be identical to the team's shared template — if you wanted something different for one athlete, your only option was changing it for the whole roster. Now a coach can individualize a single athlete's report: create a private copy just for them, customize it freely, and leave the team default untouched for everyone else.
What's New
Individualize with one click
- From an athlete's profile, select Individualize to create a copy of the team report just for them. In FYTT's own words: "You can customize it without changing the team default, and it will replace the team report on this page and on their mobile profile."
A clear indicator when a report's been customized
- Once individualized, the athlete's profile shows an Individualized badge, so it's obvious at a glance that this athlete's report has diverged from the team standard.
Revert anytime
- Select Use Team Default to delete the individualized report and switch the athlete back to the shared template — FYTT tells you up front that this deletes any customization you made.
Why It Matters
- Handle exceptions without disrupting everyone else. A rehabbing athlete, a specialist position, or a unique testing protocol no longer forces a change to the whole team's report.
- No risk of losing the team standard. Individualizing one athlete never touches the default template everyone else still sees.
- Easy to undo. If an individualized report isn't working out, reverting is one click away.
Hawkin Dynamics Force-Plate Integration
Force-plate results sync straight from Hawkin Dynamics into FYTT — no more retyping test days by hand.
Overview
We've added a Hawkin Dynamics integration, syncing jump and isometric test results from Hawkin Cloud — the platform force plates already upload to — straight into FYTT. Once connected, results for matched athletes import on a daily schedule and behave like any other FYTT metric, showing up in reports, calendars, and triggering the same automation rules as coach-entered data.
What's New
Connect with an API token
- Institution managers create an API token from Hawkin Cloud (Settings → Integrations) and paste it into FYTT's Hawkin + FYTT setup screen to authorize the connection.
Automatic athlete matching
- FYTT matches Hawkin athletes to your FYTT roster automatically — by email first, falling back to name — and gives you a review screen to confirm or hand-correct any that didn't match.
Coach-controlled metric selection
- Hawkin reports dozens of metrics per test type. Pick exactly which ones sync into FYTT from a searchable list organized by test type, so only what you care about becomes a FYTT metric.
Unit handling for common measurements
- Height, distance, speed, weight, and time metrics sync in whatever unit you've set FYTT to display. Force, power, and energy metrics — like RSI, peak force, or power output — sync using Hawkin's native units, since there's no meaningful FYTT conversion for those.
Sync status at a glance
- The integration screen shows how many athletes are matched and how many metrics are syncing, and flags the connection if a token stops working so you can reauthorize before data falls behind.
Why It Matters
- Force plates are the dominant testing system in collegiate and pro strength & conditioning, and coaches previously exported Hawkin numbers and retyped them into FYTT by hand — this removes that chore entirely.
- Getting athlete identities matched between two systems is usually the most tedious part of setup; automatic matching means a coach can connect and see data flowing in minutes.
- Keeps each institution's metric library focused — hundreds of possible force-plate outputs don't flood your library unless you choose to bring them in.
Also New: Group-Based Automation Conditions
Automations can now branch on group membership, not just metric values — so a rule can check whether an athlete belongs to a specific group as one of its conditions, alongside the metric-based logic you could already build.