Where teams use this builder
- Teachers share a single link so everyone opens the same preset.
- Docs/wiki teams embed tools with a responsive wrapper and consistent tracking.
- LMS portals use auto-height to reduce scrollbars.
How to use this tool effectively
This tool is designed to make scenario checks fast. Use a repeatable workflow: baseline first, one variable change at a time, then compare output direction and magnitude.
How it works
Run your first scenario with defaults. Then, change exactly one assumption and observe which result changes most. That is the fastest way to identify sensitivity and explain what drives the outcome.
When to use
Use this page when you need practical planning support, side-by-side alternatives, or a clean baseline for further discussion.
Common mistakes to avoid
- Changing multiple assumptions simultaneously.
- Confusing percent and decimal inputs.
- Mixing unit systems across scenarios.
- Relying only on rounded display output for final conclusions.
Worked example
Prepare a base case and one alternative case, then compare outputs and validate the direction, scale, and interpretation with the same assumptions across both cases.
See also
Frequently asked questions
What's the quickest way to create an embed?
Use the “Embed this…” button on a CalcBE page. This builder will open and auto-import the current URL, so you can copy a share link or an <iframe> right away.
When should I use cfg= (base64url)?
Use plain query parameters for short, simple presets. Use cfg= when the link gets long (many fields, long text, or LMS editors that break URLs). Toggle “Use base64url JSON (cfg=)” to pack parameters into cfg=.
How do I control iframe size (and avoid scrollbars)?
Keep Responsive enabled for a 16:9 layout, or turn it off and set a fixed Height (px). If you need dynamic resizing, copy the auto-height listener snippet and paste it into the host page.
What should I define first on this page?
Start with a clear baseline scenario and minimum required inputs. Keep optional controls at defaults for the first run, then change one assumption at a time.
Why do identical values differ across pages or tools?
Different pages often use different defaults, units, period definitions, and rounding rules. Align these before comparing outputs.
How to use Embed builder — share links & iframe code effectively
How this tool helps
Tools are designed for quick scenario comparisons. They work best when you keep one question per run, define success criteria first, and avoid switching objectives mid-stream. This reduces decision noise and produces results you can defend in follow-up review.
Input validation checklist
Before running, verify that required values are in the right format, that optional flags are intentionally set, and that baseline assumptions reflect current conditions. Invalid assumptions are often mistaken for tool bugs, so validation is part of interpretation quality.
Scenario planning pattern
Build three rows: conservative, expected, and aggressive cases. Keep data sources transparent for each case and compare output spacing. The pattern helps you spot non-linear jumps and decide whether a model is stable under plausible variation.
When to revisit inputs
Revisit inputs when input scale changes, time window shifts, or downstream decisions add new constraints. If constraints change, your previous output remains a useful reference but should not be treated as final guidance.
Operational checkpoint 1
Record the exact values and intent before you finalize any comparison. Confirm the unit system, date context, and business constraints. Compare outputs side by side and check whether differences are explained by one changed variable or by hidden assumptions. This checkpoint often reveals the single factor that changed everything.