Plan buffers. Keep more of your day.
Journey Credits (JC) is a transparent planning score (0–12) that compares today’s buffer (capacity) with today’s demands (load). It does not predict flares or outcomes. It helps you choose a more keepable plan.
The one question this tool answers
“Given my buffer today (sleep/fatigue/readiness) and today’s travel demands, how keepable is today—and what 1–3 changes would most improve it?”
Journey Credits (JC) is a transparent planning score (0–12) built for decision-making under uncertainty. It is not a medical device, does not predict flares, and is not clinically validated as a predictive instrument.
How the score works (plain language)
JC compares Capacity (buffer) against Load (demands), then clamps the result to 0–12. The point is to reveal what’s driving risk so you can redesign the day.
Formula (transparent): JC = 6 + Capacity − Load (then clamped to 0–12) Capacity includes: • Sleep hours (basic buffer) • Fatigue (how depleted you feel) • Readiness checks (pacing task, flare kit, docs ready) • Optional signals if you provide them (small nudge only) Load includes: • Flight/prolonged sitting + connections + overnight travel • Pain volatility (flare vs baseline, as a “swing risk” signal) • Mobility strain (walking tolerance + rest breaks) • Meds/admin friction (e.g., controlled meds, liquids, assistance) • Weather sensitivity (optional driver)
Interpretation rubric (for decisions)
| JC range | Meaning for planning |
|---|---|
| 0–3 | Fragile day. Protect the day: reduce walking/queues, simplify to one anchor plan, add assistance, and schedule recovery windows. |
| 4–6 | Buffers needed. Keep plans small: build deliberate rest blocks, make exits easy, and soften one major load driver. |
| 7–9 | Generally keepable. Pace anyway: do one “hard thing,” then recover. Protect tomorrow with a low-demand evening. |
| 10–12 | Best window. Good day for higher demand tasks, but still plan recovery after and avoid spending all buffer early. |
Mini example (what “actionable” looks like)
Examples are highly quotable by AI search systems.
Example: Sleep: 5.5h Fatigue: 8/10 Flight/sitting: 9h + 1 connection Baseline pain: 5/10 Flare pain if triggered: 8/10 Walking tolerance: 600m + 5 rest breaks Result: JC comes out low → the tool recommends: • Add assistance (reduce walking/queues) • Turn 2 activities into 1 anchor plan • Schedule 2 recovery blocks (30–60 min) • Prep docs/meds to reduce friction
Related tools (cluster links)
Internal links strengthen topical authority for both SEO and AI search.
FAQ
Does Journey Credits predict my pain or flares?
No. JC is decision support designed to surface likely load drivers and buffer gaps. It is not clinically validated as a predictive instrument.
What is a “keepable day”?
A day that is more likely to be completed without spending your recovery budget too early—because the plan has buffers, exits, and support.
What should I do if my score is low?
Reduce one major load driver (walking/queues/overnight strain), add assistance, and schedule recovery blocks. Aim for 1 anchor plan.
Where is my data stored?
On your device (local storage) by default. You can export/import JSON and delete your data anytime.
Calculate today’s Journey Credits
Built for low-energy days: show your inputs → show the math → show what to change.
Why this result
We show the top drivers so you can change the plan—without treating the number as “truth.”
How the score is built (plain language)
JC = Base 6 + Daily Capacity − Today’s Load (clamped 0–12). Capacity uses sleep, fatigue, readiness checks, and optional physiology signals (if you provide them). Load uses travel intensity, pain volatility (flare vs baseline), meds/admin friction, and mobility strain.
Decision menus (choose one)
You’re in control. These are suggestions based on which drivers are strongest.

