Returning to running after pain, injury, or time away
About
Rungevity
Rungevity helps runners make clearer next-run decisions using body response, not generic progression rules.
Running progress is rarely as simple as adding more each week. Pain, stiffness, fatigue, missed sessions, and life stress all affect whether the next step should be progress, progress with caution, repeat, reduce, rest, or seek review.
Rungevity exists to make that decision clearer.
Why it exists
More data is not always the answer.
Many runners do not need more data. They need help interpreting what their body is telling them.
A watch can tell you pace, distance, and load. It cannot always tell you whether next-morning stiffness matters, whether a sore run should be repeated, or when a small flare-up deserves more caution.
Rungevity was built around that decision gap: helping runners connect what they did with how their body responded.
What it helps with
Built for the uncertain next step.
Building from run-walk to consistent running
Understanding pain and stiffness after running
Deciding whether to progress, progress with caution, repeat, reduce, rest, or seek review
Tracking response over time instead of relying on one-off guesses
Using your own plan while still monitoring how your body responds
Decision framework
The Rungevity decision framework
Rungevity is built around a simple but useful idea: your next run should be guided by how your body responded to the last one.
Start a decision checkProgress
When your response is settled and the next step can be modest.
Progress + caution
When progression may be reasonable, but one signal deserves closer monitoring.
Repeat + monitor
When the current level is useful, but adding more may be too soon.
Reduce + monitor
When the next run should be easier, shorter, slower, or more controlled.
Rest
When symptoms or recovery suggest running may need a short break.
Seek review
When symptoms are worsening, unusual, changing how you move, or affecting daily life.
Founder
Built by a physiotherapist
Hi, I'm Christiaan. I'm a runner based in Melbourne, Australia, a practising physiotherapist, and am completing a PhD in digital health.
I've been running for nearly two decades and, like most runners who stick around long enough, I've had my share of injuries, setbacks, false starts, and frustrating returns to training!
Rungevity grew out of a simple frustration: runners are surrounded by information, but not always by guidance that they can act on when a decision actually matters. Should I progress? Repeat the same run? Should I be getting help?
My work is focused on helping runners understand how their body is responding to training and giving them clearer tools to make better next-run decisions.
Rungevity combines practical running education, response-based check-ins, decision support, and optional physiotherapy-guided review. It is built around my simple belief: technology can help organise the signal, but people still need human-centred guidance to make sense of it.
Scope
What Rungevity is not
Rungevity is not an emergency service, diagnosis tool, or replacement for physiotherapy or personalised medical care.
It provides general running education, decision support, check-ins, and optional physiotherapy-guided support. If symptoms are worsening, unusual, changing how you walk or run, or affecting daily life, consider professional advice.
Rungevity provides general running education and decision support based on self-reported symptoms and training response. It does not diagnose injuries, replace physiotherapy or medical care, or provide urgent medical advice.
Next steps
Make your next running decision clearer
Start a decision check
Use the free checker to think through pain, stiffness, fatigue, and recent training context.
Read the blog
Read practical articles on pain, stiffness, progression, and return-to-running decisions.
View Decision Guides
See the guide library we are building for sore, uncertain, beginner, and returning runners.
Request physio-guided support
Request a physiotherapist review when your situation needs closer support.
