How the TBL Travel Risk Score Works (PPRR)
This page explains what the Travel Risk & Readiness Tool measures, what it does not measure, and how to use the result to make safer, lower-decision-load travel plans.
This is decision support. It is not medical advice, not medical clearance, and not an emergency service.
What this tool is (and isn’t)
A fast pre-trip checker that blends (1) your baseline stability, (2) trip complexity, and (3) safety-net readiness into one score, then generates “Predict • Protect • Rescue • Restore (PPRR)” actions and a checklist.
- Not a medical device.
- Not diagnosis, treatment, prescribing, or clinical monitoring.
- Not “fit-to-fly” or “travel clearance.”
- Not real-time crisis support.
The scoring model (high level)
The tool produces:
- Total risk score (0–100)
- A risk level label (shown on the results page)
- Three sub-scores:
- Health baseline (50%)
- Trip complexity (30%)
- Safety-net readiness (20%)
Why these weights: baseline stability tends to dominate flare risk. Complexity can amplify triggers. Safety-net readiness is “damage control” when plans break.
How the math works (simple and transparent)
Each question is scored from 0 to 3:
0 = lowest risk / most stable, 3 = highest risk / least stable.
For each domain, the tool calculates an average (0–3), converts it to a percentage (0–100), then applies the domain weight:
- Domain % = (domain average ÷ 3) × 100
- Total score = (Health % × 0.50) + (Trip % × 0.30) + (Readiness % × 0.20)
Important: the score is deterministic (rule-based). If you change inputs, the score changes in a predictable way.
What inputs go into the score
Trip basics (complexity drivers)
- Travel mode
- Total travel duration
- Layovers/changes
- Time-zone shift
- Destination climate vs your triggers
Health & support (baseline and stability)
- Pain control
- Flare frequency
- Mobility
- Comorbidities
- Medication/treatment complexity
- Psychological strain
- Sleep stability
- Last trip outcome
- Self-management skills
Safety-net readiness (buffers + backup)
- Docs: scripts/letters/IDs
- Insurance & emergency plan
- Assistance booked (wheelchair/priority)
- Accommodation accessibility
- Contingency budget
- Support network & comms
How to interpret your result (what to do next)
Use the Level label shown on your result (low, mild, moderate, high, very high). Then apply this decision logic:
What it usually means: Generally travel-ready with routine buffers.
What to do next: Proceed, but harden the trip. Do Predict + Protect first, and build a simple Rescue plan.
What it usually means: Some friction expected, usually manageable with planning.
What to do next: Add 1–2 buffers (arrival time, rest blocks, fewer timed commitments), then recheck.
What it usually means: Meaningful flare risk unless you reduce load or strengthen buffers.
What to do next: Proceed only if you can make a “Red-to-Amber” change, then recheck.
What it usually means: High crash likelihood without changes.
What to do next: Do not lock in non-refundable costs until you reduce complexity and strengthen safety net. If unsure medically, discuss with a clinician before booking.
What it usually means: “Pause and redesign” signal for the current plan.
What to do next: Postpone or redesign to a minimum viable trip (shorter, fewer changes, safer environment, stronger supports). Discuss with a clinician before booking.
| Level | Score band | What it usually means | What to do next |
|---|---|---|---|
| LOW | 0–24 | Generally travel-ready with routine buffers. | Proceed, but harden the trip. Do Predict + Protect first, and build a simple Rescue plan. |
| MILD | 25–39 | Some friction expected, usually manageable with planning. | Add 1–2 buffers (arrival time, rest blocks, fewer timed commitments), then recheck. |
| MODERATE | 40–54 | Meaningful flare risk unless you reduce load or strengthen buffers. | Proceed only if you can make a “Red-to-Amber” change, then recheck. |
| HIGH | 55–74 | High crash likelihood without changes. | Do not lock in non-refundable costs until you reduce complexity and strengthen safety net. If unsure medically, discuss with a clinician before booking. |
| VERY HIGH | 75–100 | “Pause and redesign” signal for the current plan. | Postpone or redesign to a minimum viable trip (shorter, fewer changes, safer environment, stronger supports). Discuss with a clinician before booking. |
“Top drivers” (why your score is high)
The tool lists the factors that most pushed your score up. Typical patterns:
- Baseline instability (flares most days, poor sleep, recent bad trip outcome)
- High complexity (ultra duration, tight/overnight changes, major time-zone shift)
- Weak buffers (unclear insurance/emergency plan, accessibility unknown, limited support)
Your job is not to fix everything. Your job is to change the top 1–3 drivers that give the biggest risk reduction per unit effort.
What “PPRR” means (the action engine)
- Predict: identify what usually triggers you on this trip and where the first crack appears.
- Protect: add buffers, reduce complexity, and set ceilings (limits) before the trip borrows from tomorrow.
- Rescue: pre-decide what you do if symptoms spike (switch rules + minimal plan).
- Restore: a post-trip re-entry plan so recovery is protected.
This is why TBL focuses on pre-decisions and default pivots instead of willpower during a flare.
Data + privacy (default is on-device)
By default, tool inputs and outputs stay in your browser (localStorage). TBL does not automatically receive or sync what you enter. You can clear tool data anytime using in-tool reset/clear controls or by clearing site storage in your browser.
We use limited server-side processing only where needed to run the business (e.g., payments, support) and basic aggregated usage/error logs. We do not sell personal information, and we do not use your tool inputs to train general-purpose AI models.
AI-assisted features (accuracy + limits)
Some outputs may be generated with AI assistance. AI outputs are probabilistic and can be incorrect or incomplete. Use them as prompts, not directives—especially when decisions affect health, safety, or finances.
Core scoring is rule-based and does not “guess” your health status.
Evidence status + updates (honest + defensible)
Current status: a structured, rule-based scoring model designed for practical travel decisions under constraint.
How we improve it: we periodically refine question wording, action templates, and scoring rules to reduce false reassurance and reduce preventable “trip crashes.”
FAQ
Does a higher score mean I cannot travel?
Can this tool clear me to fly or travel?
Why do “safety-net” items affect the score?
Can I lower my score without changing my health?
Does TBL see my answers?
Next step
Use the tool to get your level, change the top 1–3 drivers, and rerun. That is the intended workflow.

