Dynamic Logic & Derived Gauges

Dynamic Logic & Derived Gauges

Compute coverage levels from answers, show/hide questions dynamically, and personalize offers in real time

Quick guide to how questionnaire answers become live coverage gauges and drive tailored offers.

Covered features

Derive coverage gauge levels from answers

Turn questionnaire answers into intuitive gauge levels and readable labels so users immediately understand their coverage needs.

Dynamic show/hide of derived questions

Certain follow-up questions appear or disappear automatically based on previous answers — keep the flow short and relevant.

Real-time gauge widgets

Gauge bars, step dots and labels update as soon as answers change so users see the impact of choices instantly.

Offers personalized from derived values

Offers adapt to the derived coverage profile, highlighting plans that fit the user’s selected levels and needs.

Safe defaults & overrides

System uses safe fallbacks when answers are incomplete, and supports manual overrides where needed.

Audit & test flows

Practical steps to test the dynamic logic and validate that rules behave as expected across edge cases.

Intro This page explains, in user-facing terms, how we compute coverage or needs gauge levels from questionnaire answers, when and why certain follow-up (derived) questions show or hide, how the gauge widgets respond immediately as users interact, and finally how those derived values are used to personalize offers. You’ll get concrete step-by-step workflows, tips, and common gotchas plus scenarios for real-world use.

Workflow: Compute gauge levels from answers (what the user does)

1

Step 1 — Start the questionnaire

Open the Needs / Budget questionnaire and read the short intro. Each section groups related coverages (e.g., hospital, ambulance, dental).

2

Step 2 — Answer the general questions first

Complete the top-level questions (personal situation, family, current coverage). These answers feed the first pass of derived values.

3

Step 3 — Watch the gauge(s) update

Every time you select an option, the corresponding coverage gauge updates: the orange fill moves, the selected dot lights up, and the short label under the gauge changes to reflect the computed level (for example: Basic, Standard, Premium).

4

Step 4 — Confirm derived labels

Read the human-friendly label shown next to the gauge (it’s derived from the most relevant answer for that coverage). If it doesn’t match your expectation, adjust answers until it does.

5

Step 5 — Save or override if needed

If you prefer a different level than the derived one, use the manual control on the gauge to set the level explicitly, then save to lock that preference.

Best practice: go top-to-bottom

Answer top-level, demographic, and household questions first. These have the largest effect on derived results and reduce the number of follow-ups you’ll see.

Workflow: Rules for showing/hiding derived questions (how to manage dynamic questionnaire flow)

1

Step 1 — Identify trigger questions

Notice which early questions control visibility (examples: ‘Do you have dependents?’, ‘Do you already have dental coverage?’). These are triggers for derived follow-ups.

2

Step 2 — Provide the trigger answer

When you answer a trigger (e.g., “Yes—I have kids”), the questionnaire checks for applicable derived questions and shows only the relevant ones (e.g., number of children, children ages).

3

Step 3 — Complete the derived questions

Fill the follow-ups that appear. Their answers further refine gauges and may cause additional derived questions to appear or disappear.

4

Step 4 — Backtrack to hide derived questions

If you change a trigger answer (for example, switch from “Yes” to “No”), any derived questions that depend on the previous answer will be removed. Make sure to review any values that were entered before they disappear.

5

Step 5 — Review the compacted flow

After hiding happens, read the summary at the end of the section to confirm the final set of answers and resulting gauge levels.

Tip: use the summary to catch hidden answers

If you’re unsure whether changing an earlier answer removed some follow-up inputs, consult the section summary — it lists the currently active derived answers so nothing is missed.

Gotcha: hidden answers are removed

When a derived question disappears due to a change in an earlier answer, any values you entered into that derived question are discarded. If those values are important, copy them somewhere before changing the trigger answer.

Workflow: Interacting with gauge widgets in real time (end-user interactions)

1

Step 1 — Use the dots or bar to set a level

Each gauge shows a horizontal bar and a set of step dots. Click a dot or a position on the bar to set the level you want.

2

Step 2 — Immediate visual feedback

As soon as you click, the fill animates, the dot’s color updates, and the short label changes. This happens without leaving the page: it’s immediate confirmation of the new derived level.

3

Step 3 — See related questions update

Setting a gauge can also show or hide follow-up questions (for example, selecting a high dental coverage level may reveal questions about orthodontics). Check the right-hand summary area for what changed.

4

Step 4 — Use manual override where provided

If the automatic derivation doesn’t match what you want, switch to manual mode (if available). Manual overrides keep the chosen level even if upstream answers change, unless you explicitly reset them.

5

Step 5 — Save and re-open to confirm

Save your settings and reopen the questionnaire later. The saved gauge levels and derived question visibility should persist and be reflected in personalized offers.

Tip: test changes incrementally

Change one thing at a time and observe the gauges and derived questions. This helps you learn which answers affect which coverages and avoids unintended deletions.

Workflow: How derived values drive offer personalization (from answers to recommended plans)

1

Step 1 — Complete gauges and derived questions

Finish the needs-level gauges and any active derived questions — these collectively form the user’s coverage profile.

2

Step 2 — System maps profile to offer filters

The resulting derived labels and explicit levels are used to filter and prioritize offers: plans that match the chosen levels are shown as recommendations first.

3

Step 3 — Review recommended offers

Look at the recommended plans. Each will highlight the aspects that match your derived needs (for example: “Best for Premium dental and Standard ambulatory”).

4

Step 4 — Adjust to explore alternatives

If you want different trade-offs, adjust one or more gauges and watch offers update in real time to show plans that better match the new profile.

5

Step 5 — Lock or personalize final selection

Once you find the plan that fits, either lock in that selection or use optional personalization (add-ons, co-pays) so the plan precisely matches the derived profile.

Warning: personalization depends on active derived data

If a derived question is hidden (because a trigger changed), any personalization driven by that question will no longer apply. Re-enable the derived question by reverting the trigger answer if you need that personalization back.

Steps:

  • Answer “No” to dependents.
  • You’ll see only adult-specific follow-ups (dental, vision, hospital).
  • Gauges reflect single-adult defaults and offers emphasize individual plans. Pros:
  • Short flow, fewer follow-ups. Cons:
  • Some family discounts won’t be shown.

Steps:

  • Answer “Yes” to dependents and provide number/ages.
  • Child-specific questions appear (pediatric dentistry, orthodontics).
  • Gauges for family coverages activate and offers display family plans. Pros:
  • Offers include family bundles and child benefits. Cons:
  • More questions — but only the relevant ones appear.

Steps:

  • Indicate existing coverage where asked.
  • Certain derived follow-ups (e.g., advanced dental add-ons) may be suppressed.
  • Offers prioritize plans that can act as complement (secondary coverage). Pros:
  • Avoids redundant suggestions. Cons:
  • Some comprehensive plans may be deprioritized even though they could still be useful; re-evaluate if your current coverage changes.

Before: Manual forms where all questions are shown regardless of relevance.

  • Long forms.
  • Higher abandonment risk.
  • Harder to find the right offer.

After: Dynamic flow driven by triggers and gauge derivation.

  • Shorter, context-aware questionnaire.
  • Real-time visual feedback.
  • Offers matched to your actual needs.

Advanced tip: use the preview/summary often

If available, use the questionnaire preview or summary to see the compacted, derived profile before moving to offers. It’s the fastest way to verify expected personalization without changing answers again.

Edge case: incomplete questionnaires

If a user leaves mandatory trigger answers blank, gauges may display conservative default levels. Encourage users to complete required triggers for the most accurate personalization.

Frequently Asked Questions

Final checklist before moving to offers

  • Complete all top-level trigger questions.
  • Verify gauge labels match what you intended.
  • Review the section summary to catch removed or hidden answers.
  • Use manual overrides only when confident you want to lock a different level.
  • Preview recommended offers and tweak gauges to compare alternatives.

Try it now

Open the questionnaire, experiment with a few answers and observe how gauges, follow-up questions and recommended offers update in real time.