How to use the Effort Intent tab and controls

Use this tab to review the effort-band values attached to the current calibration.

This tab answers one question:

Do the saved profile values and FIT-inferred values line up well enough to keep, or do they need a deliberate change?

What this tab is for

The Effort Intent tab helps you:

check whether the loaded calibration profile is complete
compare saved profile values against the values inferred from the FIT dataset
preview what each effort band means in more user-facing terms like typical effort, speed, and energy
decide whether you want to keep the current profile values or save a deliberate change

Working rule:

reviewing this tab does not change the planner by itself
changes matter only after you save or update a profile and make the trip use it

Step 1: Start with the status banner

Always start with the status card at the top.

It tells you whether the loaded profile has complete saved scalar values and whether those values match the FIT-inferred values.

If you see Missing saved scalar values, the loaded profile is not complete for this tab yet.

If you see the green complete state, the saved profile values and FIT-inferred values already match at UI precision.

Step 2: Compare the current profile against the inferred values

The main table is the core of this tab.

It compares:

the effort bands
the loaded profile values
the FIT-inferred values

Read this table in this order:

compare the loaded profile columns with kS0 inferred (FIT) and kE0 inferred (FIT)
identify which rows differ
leave editing off until you know which row you want to change

Do not adopt values just because they differ. The table is for comparison first.

Step 3: Treat the lower comparison table as confirmation, not the main story

The lower comparison table is a change-tracking view.

Use it to answer questions like:

did the workspace draft diverge from the loaded profile
which row changed
whether the current view is still showing saved values or a draft edit

Use it for confirmation, not as the first table to read.

Step 4: Read the summary table first

After the scalar table, read Effort Intent Summary (@ 0% grade).

This is the fastest way to answer:

What does each effort band mean in planner terms at 0% grade?

Start with these columns:

Effort Intent
Typical HRR
Typical HR
Modeled speed
Modeled energy

If these values already progress in the way you want, there may be nothing else to change here.

Step 5: Use the percentile detail view only when you need more depth

The percentile table is the deeper review view.

Use it when:

the summary table raises a question
you want to inspect a selected grade in more detail
you need to see whether an issue is broad or isolated

If the summary table already answers your question, you may not need this section.

When to use manual override

Use Manual override only when all of these are true:

the FIT-inferred values are not the values you want to save
you know which band you want to change and why
you plan to save or update a profile after editing

Do not turn on Manual override just to experiment without a target row or reason.

Recommended order

Use this sequence:

Read the status card.
Compare saved values against FIT-inferred values in the scalar table.
Leave Manual override off unless you know which row to change.
Read Effort Intent Summary (@ 0% grade).
Use Effort Intent Detail by Percentile only when the summary table is not enough.
Save or update a profile only after you know which values you want to keep.

When not to keep editing

Stop adjusting if:

the status card is already complete
the saved profile values already match the FIT-inferred values
the summary table already shows the progression you want
you are changing values only because they are unfamiliar

This tab is for choosing saved scalar values, not for editing every number until the table looks tidy.

What to do next

After reviewing Effort Intent, continue with: