Research & validation

We prove it before we show it.

BOUND validation approach · Updated October 2026

Summary

A wearable is only as useful as the trust staff can place in its numbers. BOUND keeps raw data, calibrates against reference equipment, labels every capability by status, and publishes its limits. V1 prototype boards are currently undergoing bench validation.

Validation roadmap

Each stage must pass before the next one means anything.

  1. In progressBenchElectronics and firmware behave as designed: every channel responds, data arrives complete and in order.
  2. NextLabInsole readings compared with reference force measurement under controlled movements.
  3. PlannedControlled fieldRepeatability on grass, in boots, through football-specific drills.
  4. PlannedPilotUsefulness and reliability in real squad training over weeks.

Current validation work

What we are testing now, and what comes next.

WorkWhat it involvesStatus
Prototype bench validationV1 prototype boards are currently undergoing bench validation: every sensor channel responds and data arrives complete and in order.In validation
Signal qualityTimestamps and sequence numbers on every raw sample, so gaps and dropouts are reported rather than hidden.In validation
CalibrationA framework for turning raw readings into force exists. No calibration model is validated yet.In validation
Real-world testingRepeatability in boots, on grass and in squad training, once bench and lab stages pass.Research / planned

Calibrated against a reference

An insole sensor outputs a raw reading, not force. Turning one into the other needs a model checked against established equipment.

Insole
raw readings
Reference equipment
e.g. force plate
Calibration model
fitted and tested
Validated measure
shown with its limits
No calibration model is validated yet, so BOUND shows no force values today.

Capability status

Everything BOUND does or plans to do, labelled.

BuiltIn validationResearch / planned
CapabilityDetailStatus
Pressure under the footSeven pressure-sensing zones per insole. Raw sensor values until calibration is validated.In validation
AccelerationA motion sensor per insole for movement context. V1 does not measure rotation.In validation
Raw data capture & archiveFirmware and software that record raw readings and keep them alongside processed results.Built
Phone recordingSessions stored on the phone first, uploaded later. Not yet run with real insoles.Built
Calibration to forceFramework exists; no model validated, so no force values are shown.In validation
Foot contact timingWhen each foot is on and off the ground, derived from pressure.Research / planned
Left/right comparisonHow loading differs between feet, against the player's own baseline.Research / planned
Session loadingAccumulated ground loading across a session, alongside existing load measures.Research / planned
Cutting, turning, kickingNeeds rotation sensing V1 lacks. A later hardware revision if field data justifies it.Research / planned
Injury relationshipsWhether any signal relates to availability or injury is an open research question. No claim is made.Research / planned

Research & analysis

Technical writing on player measurement, wearables and validation. Every piece cites its sources and separates evidence from our interpretation. How we check it.

Our rules

Keep the raw dataResults can be re-derived and checked when methods change.
Compare against a referenceNo value is presented until it has been validated against established equipment.
Label every numberUnvalidated measures are shown as such, or not shown.
Separate measurement from interpretationWhat a sensor recorded and what we think it means are presented separately.
Correlation is not causationA signal that moves with injury rates is not a cause or a prediction.
Publish limitationsMethods, sample sizes and what did not work are reported. Publications and datasets: none yet.

Design the studies with us

We are looking for university labs, sports-science groups and club research departments to run independent validation studies.