How to use the Effort Intent tab and controls

Use this tab to review whether the calibrated effort bands look believable for the current user.

This tab is less about curve fitting and more about one practical question:

Do the easier and harder effort levels tell a believable story for this calibrated user, or do I need to make 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

The practical operating rule is:

• reviewing this tab does not change your trip by itself
• changes matter only when you deliberately save or update a profile and use that profile

Step 1: Start with the status banner

Always start with the banner at the top.

It tells you whether the currently loaded profile is already in a clean, complete state for effort-band use.

If you see a warning about missing saved values, treat that as a sign that the current profile still needs attention before you trust it as a finished calibration profile.

If you see the clean green state, that usually means the saved profile and the inferred values are already aligned closely enough that no immediate action is required.

Step 2: Compare the current profile against the inferred values

The main table is the heart of this tab.

It lets you compare:

• the effort bands
• the values already saved in the profile
• the values inferred from the FIT dataset

The best first use of this table is simple:

• compare the saved profile values against the inferred values
• decide whether the current profile already looks believable
• avoid touching overrides until you understand the story the table is telling

If the inferred values look sensible across the effort bands, loading them into the workspace may be the right next step.

If one band looks clearly implausible, do not blindly adopt everything just because the button is available.

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

The lower comparison table is most useful when you need to confirm what changed and where.

Use it to answer questions like:

• am I still looking at default-like values?
• does the saved profile differ from the newly inferred values?
• did I make a draft edit that I have not saved yet?

That table is helpful for orientation, but it is not the main user-facing output of the tab.

Step 4: Read the summary table first

After the main comparison table, the most useful section is the summary view.

This is the fastest way to answer the user-facing question:

What does each effort band actually look like for this calibrated user?

Start by reading the broad story:

• do the easier bands look easier?
• do the harder bands look harder?
• do speed and energy rise in a believable pattern?
• does the overall progression match what you would expect from the user?

If the summary table already looks believable, there is often no reason to keep pushing deeper.

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

The percentile detail view is for deeper review.

Use it when:

• the summary view looks mostly right but you want a closer look
• you want to see how the interpretation changes at a selected grade
• you are trying to understand whether a strange result is a broad problem or just a tail-case issue

If the summary table already looks believable and you are not chasing a specific problem, you usually do not need to spend long here.

When to use manual override

Use Manual override only when all of these are true:

• the inferred values do not look believable enough to keep as-is
• you know which effort band you want to change and why
• you intend to save that change deliberately afterward

Do not use manual override just because the numbers are unfamiliar.

The real question is not whether the values are surprising.

It is whether they tell a believable story for this calibrated user.

A safe order of operations

For most users, the safest sequence is:

1. Read the status banner.
2. Compare saved profile values against inferred values.
3. Leave manual override off unless you have a deliberate reason to edit.
4. Use the summary table to sanity-check the effort bands.
5. Use the percentile detail view only if you need more depth.
6. Save or update the profile only after the overall story looks believable.

When not to keep editing

Stop adjusting if:

• the profile already looks complete
• the saved profile and inferred values already align well
• the summary table looks believable across the effort bands
• you are changing values only because they are unfamiliar, not because they are clearly wrong

This tab is about believable effort-band interpretation, not making every number look tidy.

What to do next

After the Effort Intent tab looks believable, continue with:

• Saved calibration profiles versus preview
• Apply calibration to a route
• Compare route outputs before and after calibration