Rival Systems has added multi-condition alerts, custom severity levels and targeted notifications to Rival Risk, connecting each warning to live account data and scenario analysis. The release turns the platform’s alerting layer into a workflow for identifying, assigning and investigating portfolio risk rather than sending isolated threshold messages.Users can combine account, position and risk conditions in one rule, direct the resulting notification to designated staff and review active issues from a central dashboard. From an alert, a risk manager can enter the affected account and model how market moves or portfolio changes could alter exposure. The functionality is aimed at broker-dealers, futures commission merchants, proprietary trading firms and hedge funds operating across futures, options, equities, fixed income, foreign exchange and digital assets. Its timing is relevant as more products trade beyond conventional sessions and risk teams have fewer quiet intervals in which to reconcile exposures. Single Thresholds Miss the Context That Makes Risk Material A basic warning may trigger when margin usage exceeds a percentage or an account loses a fixed amount. Those alerts are easy to understand but can be too blunt. A temporary breach in a diversified account may be less urgent than a smaller loss combined with concentration, illiquidity and an approaching settlement obligation. Multi-condition rules let a firm express that context. A risk team could assign higher severity when an account breaches a loss limit while also holding a concentrated position and having limited excess collateral. Another rule could focus on a sharp volatility move in an account with short options exposure. The benefit is prioritization. The danger is complexity. Rules with many conditions can become difficult to test and may fail to fire when one data input is delayed or a threshold is set too narrowly. Firms therefore need governance around who can create alerts, how changes are approved and whether historical events are replayed against new logic. Other providers are also embedding real-time warnings into broader dealer workflows. DXtrade integrated Tapaas analytics and alerts to help brokers monitor exposure, book risk and trading behaviour. Rival’s update focuses on linking alert design directly to investigation and scenario testing. The Dashboard Addresses the Operational Response Risk systems have long produced more information than teams can act on. A central alert dashboard helps only if it shows status, ownership, severity and the account context needed to decide what happens next. Rival says users can drill from a triggered warning into the current account view and perform custom scenarios without moving to another application. That reduces the time spent recreating a position in a separate analytical tool and lowers the chance that the second system uses stale data. Rob D’Arco, Chief Executive Officer of Rival Systems, said teams need the context to understand an event and determine a response, not merely a notification that something changed. He said the new workflow lets users define the condition, its importance, the recipients and the analysis that follows. The targeted-notification feature can also reduce indiscriminate escalation. Sending every warning to a broad distribution list creates alert fatigue and unclear responsibility. Routing an options-volatility event to the relevant desk and a collateral breach to credit staff can shorten response times, provided the organization has reliable coverage when named employees are unavailable. Continuous Markets Leave Less Time for Manual Review Rival Risk is already used in settings where trading continues around the clock. Wedbush selected Rival Systems for continuous Coinbase derivatives oversight, citing the need to monitor client accounts without interruption. In a traditional session, teams can use the market close to reconcile positions, investigate exceptions and prepare for the next day. Continuous derivatives and digital-asset markets reduce that buffer. A position can deteriorate while the primary risk team is offline, making severity, routing and predefined escalation more important. The same issue is emerging in prediction markets. Kalshi’s proposed margin model for event contracts would add calls and liquidation risk to markets that already respond to events at any hour. Continuous clearing projects are being built because batch processes do not match that operating schedule. Real-time monitoring is therefore becoming a staffing and governance question as much as a technology one. An alert sent at an inconvenient hour has value only if someone has authority to act and access to the necessary account controls. Scenario Analysis Can Turn an Alert Into a Decision A triggered rule describes the current state. Scenario analysis asks what happens next. A risk manager can test a further price decline, volatility increase or portfolio adjustment before deciding whether to request collateral, reduce a limit or liquidate positions. The quality of the answer depends on the model. Options portfolios require assumptions about volatility and correlations. Fixed-income positions respond to shifts in rates and spreads. Digital assets can gap across venues with different liquidity. A single scenario cannot capture every path, but a set of plausible shocks is more informative than a static breach number. Clearing houses are making similar investments in rapid simulation. Vermiculus delivered modular risk systems to OCC for margin and liquidity calculations within a broader infrastructure programme. Rival is bringing the monitoring, escalation and what-if sequence into an account-level enterprise tool. The update should help firms reduce the distance between detection and action. Its effectiveness will be measured by outcomes: fewer irrelevant alerts, faster ownership of material cases and decisions supported by current data. Adding more configurable rules is useful only if governance and staffing prevent the flexibility from becoming another source of operational risk. Firms should also measure alerts as a control population. Useful metrics include the proportion escalated, time to assignment, time to resolution, repeated triggers and losses avoided after intervention. A low escalation rate may indicate noise, while a very high rate can mean thresholds are detecting problems too late. The dashboard gives Rival a place to expose those patterns, although the release does not specify the reporting or model-validation tools available to supervisors.
