The Questions Clubs Ask First

Be-Healthy analyses every day how a player’s injury-risk profile changes over time, considering factors such as match exposure, recovery time, fixture congestion, previous injuries and upcoming fixtures.

It compares those patterns with data from thousands of players across multiple seasons to produce a risk signal updated daily, so a club can see which players may need closer attention.

Many non-contact injuries develop over time rather than appearing without warning. Changes in match exposure, recovery time, fixture congestion, previous injuries and other factors give useful signals before an injury occurs.

Be-Healthy uses that consistently available information to identify changes in injury risk without needing access to a club’s own training-load systems. Club data makes the signal more precise where a club supplies it, but it is not required to get started.

Your medical team knows your players in far greater depth than we do. Be-Healthy sees something different: patterns across thousands of players, through multiple seasons and in different football environments.

We also look at a player’s whole career, whereas a club’s internal training data naturally begins when that player arrives at its own facilities.

The value is not that Be-Healthy knows more than your medical team. It is that we add a broader, independent view of injury risk that helps highlight the patterns worth their attention.

A player’s risk is not a fixed score.

As matches are played and fixtures approach, playing time, accumulated exposure, recovery time, fixture congestion, injury history and expected workload all change.

Be-Healthy reassesses the player as that context changes. A player can therefore move from Low to Medium-High risk even though there has been no injury or obvious change in his status.

We continuously compare our injury-risk signals with what actually happened to players.

As new, revised or additional data becomes available, we test whether it improves the signals, reveals new patterns or strengthens existing ones. A change is adopted only when the evidence shows it improves performance.

No. That would tell us very little about future injury risk.

We specifically test whether the model is identifying patterns that appear before an injury, rather than information that only becomes obvious once a player is already injured.

That distinction is fundamental to whether the signal is actually useful.

No. Different injuries can have different causes and warning patterns, so a single approach would not work equally well for everything.

Be-Healthy uses different models and data combinations depending on factors such as the type of injury, the player’s profile and career history, and the football environment. That lets us use whichever approach gives the most useful injury-risk signal for each situation.

It will sometimes be wrong. No injury-risk system can identify every future injury or avoid every false warning.

We track both missed injuries and false warnings, and use those outcomes to evaluate and improve the models. That is how we find new patterns and sharpen existing signals.

The important question is not whether every injury is predicted, but whether the signals consistently help clubs see where attention may be needed.

In the European Union. Everything you send us, and all the analysis we run during a Proof of Concept, is stored in Amazon Web Services’ Frankfurt region, and an enquiry from this site goes directly to that region rather than through anything in between.

We also notify the team by email so that someone can reply, and we use providers for business email, analytics and website infrastructure. The privacy notice sets out how those are handled, including the lawful basis where a provider processes personal data outside the European Economic Area.

These public pages are a separate matter: like most websites they are distributed through a content delivery network, which holds copies in Europe and North America so that pages load quickly. Those copies are the marketing pages themselves. They carry no enquiry submissions and no private product data.

Not in the sense that usually means. This site sets no cookies and stores nothing on your device, and it loads nothing from a third-party server: no tag managers, no advertising pixels, no embedded fonts or scripts reporting your visit elsewhere.

We do count things. When someone opens a solution page or starts the contact form, we record that it happened, so we can tell which pages are useful. Those counts are sent to our own domain rather than to an analytics company’s.

To count people rather than page loads, our analytics provider works out a temporary identifier from your network address and browser using a key it throws away at the end of each day. Nothing is stored on your device, the identifier cannot be traced back to you, and because the website’s own address forms part of it, it cannot be matched to you on any other site. It stops working the next day.

That is why you are not asked to accept anything: for the technologies currently in use there is nothing to consent to. If we introduce something that does require consent, we will ask for it before it is used.

It is used to respond to you and to understand which parts of the site prompt enquiries. It is not sold, and it is not shared for anyone else’s marketing.

It is deleted after 24 months. That is enforced by the database expiring each record on a stored date rather than by anyone remembering to run a clear-out, so the retention period holds whether or not we are paying attention to it.

The privacy notice sets out the detail, including how to ask for a copy of what we hold or have it deleted sooner.

In the standard Proof of Concept, publicly available football information about professional players: appearances, minutes, transfers, and injuries as publicly reported. Nothing in it comes from your systems: no medical records, no wellness or screening data, no training-ground monitoring, and no access to your databases.

That is how the Proof of Concept is designed rather than a limit on the product. Where a club chooses to supply its own data once we are working together, the product accepts it.

We share the findings with you in a written report. We do not publish player-level results from a club engagement, and anything we do publish is anonymised, with no name, and no combination of club, position and date that would identify an individual.

The terms covering our own handling of that data form part of the Proof of Concept agreement rather than being left to a page like this one.

No. Where a club supplies its own data, that data is used to sharpen the signal for that club and for nothing else. It does not enter the training set behind any other club’s models.

What the models read is publicly available information about professional players, collected from the point a player reaches senior football. That information exists independently of where the player is contracted. It was there before they joined you and remains after they leave, so it is not really your squad’s data in the sense the question implies, even while they are in your squad.

Anything you tell us during a Proof of Concept is feedback on our product, not training data. That includes how you judged the output, what was useful, and what was not.