How to use day-level diagnostics

Day-level diagnostics are where TRIPS becomes most actionable.

Route-level diagnostics tell you whether the whole trip looks demanding. Day-level diagnostics tell you which day is the problem and what kind of problem it is.

The main question this section answers is:

Which day stands out as unusually hard, and is that difficulty being driven by campsite placement, terrain, time, energy, or accumulated fatigue?

What day-level diagnostics are for

Use day-level diagnostics when you want to:

• turn one route into a realistic day-by-day itinerary
• see which day is the hardest
• understand why one day is much harder than the others
• decide whether to move campsites before touching deeper physiology inputs

A good operating rule:

• fix day structure before you start “fixing” the user

If one day is wildly harder than the others, campsite placement is usually the first thing to revisit.

Step 1: Start with Campsites

The day-level workflow begins with the Campsites panel.

Without campsites or split points, you do not really have day-level diagnostics yet. You only have a route.

Campsites define where each day ends. They are the structure underneath every day-level output, so they come first.

Use this panel to:

• add campsites on the route
• edit each campsite distance
• nudge split points with the -0.5, -0.1, +0.1, and +0.5 controls
• add nights for layovers or zero days
• remove campsites that are no longer useful
• jump to a campsite on the map with See on Map

What this panel is really asking:

Where should each travel day end so the itinerary is realistic and repeatable?

Practical rule:

• if one day looks broken, move campsites before assuming your physiology inputs are wrong

Step 2: Use Day-load distribution to find the outlier day

Once the route is split into days, move to Day-load distribution.

This is the best first screening tool for day-by-day imbalance.

Start here to find the day that clearly stands out from the rest. In this example, Day 2 is the peak day under the selected lens.

Use this panel to:

• compare days across a chosen lens
• see the peak day
• see the mean and range across calendar days
• select a day to focus on

The bars answer a simple question:

Which day is the worst by the lens I currently care about?

Step 3: Change the lens instead of trusting only one signal

The Lens menu is one of the most important controls in this section.

The lens menu changes what kind of “hard” you are looking at. This is how you tell the difference between a fatigue problem, a route-load problem, a time problem, an energy problem, or a steepness/exposure problem.

You can look at lenses such as:

• Max fatigue (cumFI)
• Risk area
• Max risk
• Total hiking time
• Total req kcal
• Pack start weight
• Distance
• Gain
• Deficit feasibility
• Load
• Exposure
• Time
• Energy
• Backload

How to use lenses well:

• start with Max fatigue (cumFI) or Load for a broad “which day is hardest?” view
• switch to Time if the day may simply be too long
• switch to Energy if the day may exceed energy capacity
• switch to Exposure or Backload when the terrain placement itself seems problematic
• switch to Distance or Gain when you want a simpler structural explanation

Do not trust only one lens.

The point is to compare several ways of being hard.

Step 4: Focus a specific day and read the day card

After you identify the standout day, focus it and read the day card.

The focused day card is the clearest single-day explanation in the planner. It tells you how big the day is, what the energy/weight context looks like, and what the day-level TRIPSignals say.

The day card gives you:

• Basics
• Energy & Weight
• TRIPSignals

Basics

Use the Basics block to ask:

• how long is this day?
• how much hiking time does it require?
• how much climb and descent is packed into it?
• how high does it go?

Energy & Weight

Use Energy & Weight to ask:

• what does the pack weigh at the start and end of this day?
• how much base and activity energy does this day require?
• is the planned intake clearly behind the required demand?

TRIPSignals

The day-level TRIPSignals help explain what kind of difficulty is showing up on this day.

Use the day-level signals to compare:

• terrain difficulty
• overall day strain
• whether the hard work is pushed late
• time and energy pressure
• where risk and accumulated burden are highest

Use the day card to answer:

Is this day hard because it is too big overall, too steep, too backloaded, too underfueled, or too burdened by accumulated fatigue?

Step 5: Use Daily charts to locate where the day gets hard

After the day card, move to Daily charts.

This is where you stop asking “is this day hard?” and start asking “where inside the day is it hard?”

The metric menu lets you inspect the same day through different charts. That is how you localize the problem instead of treating the day as one undifferentiated block.

The metric menu includes:

• Elevation
• Grade
• MDR
• Energy cost
• Speed
• cumFI
• Fatigue impact

How to use the chart menu:

• use Elevation to understand the broad shape of the day
• use Grade to find where the steep sections live
• use MDR to find where terrain demand peaks
• use Energy cost to see where each mile becomes expensive
• use Speed to see where pace naturally drops
• use cumFI to see accumulated burden through the day
• use Fatigue impact to find where the day is most likely to feel hardest in practice

This is the day-level version of the route-diagnostics chart logic, but applied to a single day instead of the entire route.

A safe reading order

For most users, the safest sequence is:

1. Use Campsites to define the day structure.
2. Use Day-load distribution to find the standout day.
3. Change the Lens to understand what kind of problem it is.
4. Focus that day and read the day card.
5. Use Daily charts to see where inside the day the problem lives.
6. Then move the campsite if the issue is structural.

That sequence goes from itinerary structure to comparison to diagnosis to action.

What day-level diagnostics are best at

Day-level diagnostics are strongest when you use them to:

• find the day that is clearly too hard
• see whether the problem is structural or physiological
• compare one itinerary split against another
• decide whether to move a campsite earlier or later

They are less useful when you ask them to prove whether one exact predicted number is perfect.

Common mistakes to avoid

Watch out for these:

• changing physiology inputs before checking whether campsite placement is the real problem
• trusting only one day-load lens
• staring at the selected day card without looking at the daily charts
• trying to equalize every day perfectly instead of just removing the biggest outliers

What to do next

After reading day-level diagnostics, continue with:

• Split a route into days
• Understand route and day outputs
• Compare plan versions instead of chasing precision