Treasury Control Tower

Learning objectives

• Explain the main treasury decision that Treasury Control Tower is designed to support.
• Use Stress Scenario, Enable AI Insights to test how different assumptions change the scenario.
• Interpret ai Insight in plain language and connect them to an action or conclusion.
• State one limitation, risk, or governance consideration before using the result in a real decision.

Run modes

• Supported modes: Browser
• Demo type: Interactive browser demo
• Primary launch surface: demo.html

Before you start

Starts immediately in browser with no installs, no API keys, and classroom-safe defaults.

This helps set classroom expectations before students click into the live experience.

Core context

Look for cash position, forecast gap, stress scenario, and recommended action.

Observe how liquidity changes when inflows fall, outflows accelerate, or reserves are stressed.

Concepts covered

What students should note

Note that students should translate dashboard signals into a treasury decision and escalation path.

List of steps

• Choose the run mode that fits the class: Browser.
• Review the default assumptions before changing anything.
• Change one or two inputs, then use `Reset`.
• Read ai Insight first, then compare any supporting metrics, charts, or AI text.
• Capture one insight, one limitation, and one action recommendation.

Input variables explained

• `Stress Scenario` changes one part of the scenario; increase or decrease it deliberately and watch how the output shifts.
• `Enable AI Insights` changes one part of the scenario; increase or decrease it deliberately and watch how the output shifts.

Decision buttons explained

• `Reset` returns the demo to a known starting state so students can begin a fresh comparison.
• `Compare Scenarios` is the main action that computes, compares, or generates the next result from the current inputs.
• `Export Results` saves the current result so learners can document evidence or compare scenarios later.

Outputs explained

• `ai Insight` should be read as evidence for the decision, not just a display element. Ask what high, low, or changing values imply.

What to notice

• Look for cash position, forecast gap, stress scenario, and recommended action
• Observe how liquidity changes when inflows fall, outflows accelerate, or reserves are stressed
• Note that students should translate dashboard signals into a treasury decision and escalation path
• Compare the headline output with supporting views such as ai Insight before drawing a conclusion

Discussion and reflection

• What business or technical decision would you make differently after using Treasury Control Tower?
• If you changed one assumption and ran `Reset`, which output moved the most and why?
• What would you still want to validate with real data, policy, or expert review before acting on the result?