A free framework for runners
For anyone who has ever not crossed a finish line.
"Did Not Finish" is a race-system label. It is binary, externally imposed, and indifferent to your intent.
It does not tell you why. It does not tell you whether you failed. It does not tell you whether you belong in this sport.
What you do with the data determines what comes next.
The framework
Most runners either explain a DNF away or internalize it as a personal verdict. Neither response is useful. This framework replaces both reactions with honest analysis — usable after a DNF, a cutoff pull, a medical stop, or a finish that felt wrong.
DNFs should never be used to exile someone from running. Getting a DNF — or two, or three, or many — does not mean you shouldn't be here.
— Mark Vega, DNF: Data, Not FailureComplete within 48 hours while the data is fresh. Works after a finish, a DNF, or a DNS — at any distance, any age.
Start here
No stories until constraints are named. Complete this first.
Lens 1 of 5
The race you entered. This is where analysis must begin. Always. Cutoffs are not moral — they are operational.
Lens 2 of 5
Not "how fit did you feel?" — but "what could your body deliver, repeatedly, under load, on that terrain, that day?"
Lens 3 of 5
Where responsibility lives — and where learning is most actionable. Isolate variables: what was within your control?
Lens 4 of 5
Where the race changed. Separating forced outcomes from chosen outcomes — without moral judgment.
Lens 5 of 5
Now — and only now — do you earn the right to summarize the race. Use mechanical language, not emotional language.
Primary constraint
State it in one sentence. If you can't, the analysis is incomplete. Replace judgment with mechanics: not "I failed" but "my movement rate was incompatible with the cutoffs on that course that day."
Post-race after action review
DNF: Data, Not Failure
Created by Mark Vega · Run Long After 60 · datanotfailure.org
After action review
Outcome
Conditions
Cutoff interaction
Lens 1 — System constraints
Lens 2 — Physical capacity
Lens 3 — Execution
Lens 4 — Decision points
Primary constraint
Secondary contributor
One forward adjustment
What to keep
If the same constraint appears across multiple races, it is no longer incidental. It is structural.
This framework is evolving. If you used this tool after a race — finished or not — your feedback goes directly to Mark Vega and shapes what comes next. Your email is used only to reply to you. Nothing else.
Send feedback →DNF: Data, Not Failure was created by Mark Vega — practicing lawyer, stroke survivor, and endurance runner. It exists because DNFs are poorly understood, inconsistently reported, and wrapped in shame that prevents honest analysis.
A DNF can happen to anyone at any distance, at any age, at any point in their running life. A 15-year-old trying a 10K for the first time and a 65-year-old attempting a 100-miler both deserve the same thing after not finishing: not shame, but a framework for understanding what actually happened.
The full guide — including Cutoffs 101, the Age and Strength section, and the complete framework — is available at runlongafter60.com.