FITDAT® v1.1 · Open standard · Governed by REALFIT®

The open library for
objective fitness testing

FITDAT® defines tests, protocols, metrics, and standards for physical fitness measurement. Every test is fully specified before publication — definition, protocol, normalization rules, fitness components, and population context. No exceptions.

Browse the test library → Try the scoring demo
Core principles
What FITDAT is — and isn't

Objective performance only

FITDAT covers measurable fitness performance — speed, strength, power, endurance, agility. Body composition, subjective assessments, and self-reported data are out of scope.

Fully specified or not published

Every test in the library has a complete TestDefinition, TestProtocol, and TestContext before it appears here. The library grows constantly — but never at the expense of specification quality.

Tests are facts, not judgments

FITDAT defines what was measured and how. Whether a result is "good" is the job of a Score Set — not the library. This separation is intentional and load-bearing.

Open infrastructure

FITDAT definitions are open for any developer to build Score Sets on. Scoring curves, component weights, and reference bands are proprietary to each Score Set — FITDAT defines only the foundation.

Ecosystem architecture

FITDAT is the foundation. Score Sets are built on top of it.

The REALFIT ecosystem has three layers. Understanding the separation between them is the key to understanding what FITDAT is for.

Governing authority
REALFIT®
Sets standards · Issues certification · Maintains FITDAT
↓
Layer 3
Apps
REALFITSCORE · ScoreMy40 · Developer apps · Certified or independent
↓
Layer 2
Score Sets
REALFIT Absolute Score · Army AFT · Marine PFT · Developer Score Sets
↓
Layer 1 — FITDAT®
Open test library
Growing test library · protocols · normalization rules · fitness components · replacement groups
FITDAT defines facts, not judgments. A 4.55-second 40-yard dash is a measurement. Whether that is "good" is the job of a Score Set — not the library. This separation is intentional and load-bearing.
REALFIT publishes Score Sets, not just tests. The REALFIT Absolute Score™ is REALFIT's proprietary flagship. REALFIT also publishes standardized implementations of military and professional standards — Army AFT, Marine PFT, NFL Combine — all built on FITDAT definitions.
Developers can build on the same foundation. Any developer can use FITDAT test definitions to build their own Score Set — their own scoring curves, their own weights, their own reference bands. REALFIT Certification is available for Score Sets that meet specification requirements.
Every layer is versioned and auditable. FITDAT test versions, Score Set versions, and protocol versions are all declared in every output. Results are reproducible across time, populations, and deployments.
Full architecture documentation →

What FITDAT covers

in.scope
  • Sprint and dash tests — 10 yard to 400m
  • Maximal strength — 1RM barbell lifts
  • Muscular endurance — max reps, timed holds
  • Power — jumps, throws, explosive movement
  • Cardiovascular endurance — runs, rows, timed events
  • Agility — shuttle runs, directional change tests
  • Any test that produces an objective, repeatable measurement

What FITDAT does not cover

out.of.scope
  • Body composition — BMI, body fat percentage, measurements
  • Subjective assessments — movement screens, pain scales, perceived exertion
  • Self-reported data — activity logs, sleep tracking, nutrition
  • Skill tests — sport-specific technique assessments
  • Medical or clinical evaluations of any kind
The boundary is simple: if it cannot be measured objectively and reproduced by a different administrator with the same result, it does not belong in FITDAT.
Data model

Six concepts. Every test uses all of them.

The FITDAT ontology defines exactly what each concept means and how it relates to the others. Click any row to see what fields it contains.

01
TestDefinition
What is being measured
The capability construct, input type, canonical unit, and scoring direction
+ expand
testId
Unique identifier — e.g. test_40yd_dash
testName
Display name — e.g. 40 Yard Dash
componentId
Primary fitness component measured
inputType
secondsOnly · minutesSeconds · repetitions · weight · distance
canonicalUnit
The unit scores are calculated in — seconds, kg, meters, reps
scoringDirection
Lower = higher score OR Higher = higher score
normalizationRuleId
Reference to unit conversion rule, if required
replacementGroupId
Which group this test belongs to for battery substitution
TestDefinition describes the construct — not the execution. Two tests with identical protocols but different constructs (e.g. Bench Press 1RM vs Back Squat 1RM) are separate TestDefinitions.
02
TestProtocol
How it is executed
Equipment, start conditions, measurement standard, and certification eligibility
+ expand
protocolId
Versioned protocol identifier
description
Full execution instructions in plain language
equipmentRequired
All required equipment listed explicitly
startCondition
Exact starting position and conditions
timingMethod
hand · electronic · n/a
measurementStandard
Precision and attempt rules — e.g. nearest 0.01s, best of two
certificationEligible
Whether a result can be REALFIT certified
version
Protocol version — protocols are immutable once published
A TestDefinition may have multiple Protocols if the construct remains identical. Protocol changes are versioned — old protocols are never deleted, ensuring historical results remain reproducible.
03
TestContext
Who and where it applies
Sport tags, setting tags, population tags, and ecosystem relevance scores
+ expand
sportTags
Sports and activities this test is relevant to
settingTags
gym · field · track · home · outdoor · water
equipmentProfile
none · minimal · standard · specialized
populationTags
pop_youth · pop_general_adult · pop_military · pop_elite · pop_masters_40+ etc.
ecosystemRelevance
Relevance score 0–1 per context type: member, team, organization, affiliate, official
coachingNotes
Implementation tips for administrators
TestContext makes the library searchable and filterable. Developers building Score Sets can query by sport, population, or setting to find relevant tests.
04
NormalizationRule
How inputs become canonical
Unit conversion — imperial to metric, mm:ss to seconds
+ expand
ruleId
e.g. norm_lbs_to_kg · norm_ftin_to_m · norm_mmss_to_seconds
inputUnit
The unit entered by the user
canonicalUnit
The unit used for scoring
conversionFormula
Explicit arithmetic formula — no ambiguity
precision
Rounding rule applied after conversion
appliesTo
List of testIds that use this rule
Three rules cover the entire current library: lbs→kg (strength tests), feet+inches→meters (jump and throw tests), mm:ss→seconds (timed tests). Scores are always calculated in canonical units.
05
FitnessComponent
What quality is expressed
The six measurable components of physical fitness
+ expand
muscular_strength
Maximal force production against external resistance
muscular_endurance
Sustained muscular output over repeated efforts or time
cardiovascular_endurance
Sustained aerobic output over long duration
power
Explosive force production — rate of work over distance
speed
Explosive movement and sprint capability
agility
Directional change speed and reactive movement
Each test has one primary FitnessComponent. Score Sets may assign weights across components — but FITDAT only defines which component a test predominantly expresses.
06
ReplacementGroup
Which tests are interchangeable
Structural equivalence groups for battery substitution
+ expand
replacementGroupId
e.g. rg_cardio_long · rg_upper_push_strength
componentId
The component all tests in this group measure
description
Plain language rationale for why these tests are equivalent
allowedTestIds
All test IDs eligible for this group
defaultTestId
The preferred test when no preference is specified
ReplacementGroups define structural equivalence — they do not authorize substitution in any specific battery. Whether one test can substitute for another within a Score Set is governed by that Score Set's specification.
Specification depth

What "fully specified" actually means

Every test in the FITDAT library passes through three layers of specification before it is published. This is the bar.

Layer 1

TestDefinition

What the test measures, how input is collected, what unit scoring uses, and which fitness component it expresses.

testId componentId inputType canonicalUnit scoringDirection normalizationRuleId replacementGroupId isActive version
Layer 2

TestProtocol

Exact execution instructions — equipment, start position, timing method, measurement precision, attempt rules, and certification eligibility.

protocolId description equipmentRequired startCondition timingMethod measurementStandard certificationEligible version
Layer 3

TestContext

Discoverability metadata — sports, settings, equipment profile, population tags, and ecosystem relevance scores across five deployment contexts.

sportTags settingTags equipmentProfile populationTags ecosystemRelevance.member ecosystemRelevance.team ecosystemRelevance.organization coachingNotes
Test library

Browse the test library

Full TestDefinition, TestProtocol, and TestContext for each test in the REALFIT Absolute Score™ battery. Filter by component, sport, or population.

Open the library →
Live demo

Try the scoring engine

Pick any test, enter a result, and see the REALFIT Absolute Score — plus the raw JSON payload and a copy-ready API snippet showing exactly what a Score Set returns.

Try the demo →