Honest arithmetic about your own days.

This page is the whole calculation. Nothing in Endure is a black box: every number on your screen can be traced from the questions you answered to the result you see, and the rules below are the exact ones the app runs on your phone.

Part one

Reserve, the daily score

Reserve is one number from 0 to 100 that summarizes what you have to work with today. It comes from the eight questions in the check-in, each a slider from 1 to 10.

  1. Eight questions. Sleep quality last night. Energy. Emotional reserve. Physical state. Sense of calm. Presence with family and friends. Fulfillment in work. Recovery time today.

  2. Each answer becomes a 0 to 100 contribution: value × 10. A slider you leave untouched counts as 5, so 50.

  3. The eight questions roll into six domains. A domain's score is the average of its questions.

  4. Reserve is the equal-weighted average of the six domain scores, rounded to a whole number.

Recovery

Sleep quality, recovery time today

Emotional Resilience

Emotional reserve, presence with family and friends

Cognitive Load

Sense of calm

Physical Strain

Physical state

Performance Readiness

Energy

Meaning and Purpose

Fulfillment in work

Why every domain counts the same

No data yet justifies weighting one domain above another, and a secret weighting formula is exactly the part of consumer wearable scores that does not hold up. Equal weights are transparent and checkable. The weights change only when real data earns a change, and that is a decision made in the open, not a tuning knob.

What Reserve is, and is not

Reserve is a daily composite readiness index, modeled on how elite athletic daily-wellness monitoring works: short self-report items, aggregated into one readiness number, computed entirely on your phone. It is labeled in the app as a directional indicator, because that is what it is today. It is not yet a validated clinical scale. The validation plan is at the bottom of this page.

Reserve means the most within one person over time. Your Tuesday against your Thursday is signal. Your 62 against a colleague's 68 is not the point, and it is not how the product uses the number. Every serious claim Endure makes is a within-person claim.

Part two

Levers, what moves your Reserve

A Lever answers one question from your own data: which conditions in my work measurably raise or lower my Reserve? Each condition you tag in a check-in (the chips) becomes a candidate Lever.

  1. Split your logged days into the days you tagged the condition and the days you did not.

  2. Average your Reserve on each side. The difference is the Lever: mean(with) − mean(without).

  3. Wait for enough days. A Lever needs at least 3 days with the condition and 3 without it. Below that it reads "building data" and is never shown as a result. The earliest a first Lever can appear is your sixth check-in.

Worked example. Twelve logged days, five of them tagged "Inbox overload." Average Reserve on those five: 54. Average on the other seven: 68.

54 − 68 = −14, so the app reports: inbox days cost you 14 points. Reverse the sign for a protective condition, and the app reports what it gives back.

The rules that keep a Lever honest

RuleValueWhat it does
Minimum days3 with, 3 withoutA real minimum from single-case research design, not an arbitrary gate.
Noise floor1 pointA difference of one point or less is reported as no clear effect. Trivial differences are not dressed up as findings.
Daily constant10+ days, under 3 withoutA condition present on nearly all your days has no comparison group, so it is reported by presence instead of as a difference. For many clinicians, EHR friction lives here.
Thin comparisonone side ≤ 10% of daysThe Lever is shown, with a visible caveat that one side is thin.

Why within-person is the whole trick

Each clinician is their own control. Comparing your days with a condition to your days without it cancels out everything that differs between people: personality, baseline mood, specialty, how you use a scale. That is the cleanest cause-and-effect signal available without running an experiment on someone, and it is a recognized approach, called single-subject or n-of-1 method. The minimums and the constant rule are grounded in published standards, listed in the bibliography.

Part three

The aggregate, when an organization runs Endure

When clinicians in an organization choose to share, the Conditions Report does not pool everyone's raw days, because one heavy logger would then dominate the numbers. Instead:

  1. Each person's own within-person difference is computed first, on their phone's terms, exactly as above.
  2. Those personal differences are averaged across people, one vote per clinician.
  3. Nothing is shown for fewer than five clinicians. A small group rolls up into its parent group or is left out.

So an organization reads "on average, across clinicians with enough data, inbox days cost about 12 points of Reserve." Never an individual, never a group under five.

Part four

What the numbers can and cannot say

Part five

Validation, and where a statistician comes in

For the daily product, the analysis is transparent within-person arithmetic, and it does not need a statistician to be valid, because it claims only what it computes. Proving that Reserve tracks something real is a different job, and that job is under way.

Milestones, so "enough data" is concrete. Two to three weeks of your own logging unlocks your first Levers. Five or more sharing clinicians per condition unlocks that line of a Conditions Report. A few months of paired daily and monthly data unlocks the first real answer to whether Reserve measures something real.

Questions about the math are welcome: the contact form on the About page reaches the people who wrote it.