Risk intelligence
Early signals that feed playbooks — not only a manual “open a risk” button.
Who this is forShared service, managers (team scope), and board readers of trends.
Org adminHR reviewerCompliance officerManagerBoard sponsorScreenshot shown as: Priya Raman
moosh.app/risk/intelligence
Trends appear here before a formal risk is written — for example workload slipping while overtime rises. Data is always group-level and floor-safe.
In the orchestrated model, threshold patterns can **fire a playbook** that assembles a Decision Pack for the shared service, instead of relying on someone noticing a chart every morning.
It remains a heads-up, not a verdict. High-consequence formalisation still needs a human gate via pack or register.
For example
Three weeks of high Demands in Logistics triggers signal_threshold_pack; a Decision Pack lands by email rather than waiting for a manual review of the chart.
Worth knowing
- Signal
- An early hint that something might be wrong — not yet a confirmed, written-up risk.
What you can do here
- 1Watch trends and signal sources.
- 2Expect packs when thresholds fire — open Decision Packs to act.
- 3Open a full risk only when judgment requires it.