Help center › Using Vestoris

Workflow monitor and workflow rules

Everything in Vestoris that waits on a person moves through one workflow engine: orders (compliance, approval, trader assignment, working, allocation by Operations), soft-rule overrides, compliance rule drafts and sign-offs, violations, data batches and feed files held for review, access reviews, and the exception queue (stuck and duplicate orders). Workflow rules decide who must approve, which desk and person an item goes to, its priority and its SLA. The AI drafts, explains and predicts; it never moves an item. Paper trading only: the orders are simulated and nothing here is investment advice.

The workflow monitor (Workflow › Workflow monitor)

The board lists every item in flight: its stage, owner or queue, age, an SLA countdown (green, amber when a quarter of the time is left, red when breached), the reason it is blocked and the next action. It refreshes itself every few seconds; only what changed is sent.
Filter by type, desk, owner, account, SLA status and priority, and save the filters as a view (Admins can share views). Table is the dense list; Stages shows a column per stage.
Actions on an item: Claim, Release, Reassign (Operations, Compliance, Admins and the desk head), Escalate with a reason, Comment and Watch. Each is checked against your role and written to the event log. None of them approves: approving and rejecting still happen on the item's own screen (the order, the override, the rule).
Monitor brief: code finds what is stuck and predicts what will breach its SLA from how long each stage usually takes (the 90th percentile of the last 30 days); the AI writes the narrative. Suggested reassignments are applied only when you click Apply.
On an item, Why is this stuck? explains from facts: no owner, the owner is off desk, which approvals are missing, nobody eligible to approve is on desk, escalations so far.

Who sees what: Operations, Compliance and Admins see the whole firm. Traders and Portfolio Managers see their desks' items, their own and those they may approve. A Viewer sees the items on the accounts they can view and cannot act.

My work and bottlenecks

My work lists what waits on you (assigned to you, in your desk's queue, or where your approval counts), what you requested, what you watch, and your notifications. Escalations and rule notifications are also emailed (never for demo users).
Bottlenecks shows, for today, 7 or 30 days: items per stage now, average and 90th-percentile time per stage, SLA breaches, the busiest approvers, and rule ideas from patterns - for example "most small overrides are approved within a minute: consider auto-approval below $50,000". Ideas are proposals; a person drafts, tests and signs off any rule.

Workflow rules (Workflow › Workflow rules)

A rule has conditions and actions, and a priority (lower numbers are evaluated first).

Conditions: account, account group, rule package, asset class, sector, country, side, shares, notional, % of the account, % of average daily volume, the compliance result (pass, warning, override), origin (AI-proposed or manual), time of day and market session (New York), the requester's role; for violations the severity; for held data the data set. "All" conditions must hold and at least one "any" condition. A value can follow a firm setting, e.g. the firm's approval threshold.
Actions: require 1-3 approvals from roles or named people; auto-approve below a threshold; put the item in a desk's queue; assign it (round-robin or least loaded among the desk's members who are on desk, or a named person); set the priority; set an SLA with an escalation chain; notify people.
Several rules match? Approval requirements add up. For queue, owner, priority, SLA and auto-approval the first matching rule wins, and the item shows which rule was overridden.
Four eyes, always: the person who requested an item never approves it, and nobody approves twice. An "approver on the account" requirement needs "approve" on every account of the order; a role requirement needs that role and view access to the accounts.
Auto-approval applies only when its rule comes before every approval rule that matches, within its limit, never to anything compliance marked hard, never to an order after a soft warning or override, and never to an AI-originated item above the firm's AI limit (Desks and SLAs).
The default rules reproduce the firm's approval thresholds (orders above the order value or % of account need an approver; overrides above the override threshold need Compliance). With no other rules, Vestoris behaves exactly as before.

Writing a rule

Describe a rule in a sentence, e.g. "Orders over $1M in the Growth accounts need PM and Compliance approval, and must be released within 30 minutes." The AI proposes the structure; Vestoris checks every field, role, desk and account, and code writes the restatement you sign off. Without the AI a built-in parser understands common phrasings. Or use the form.
The test bench replays the last days of items of that kind under the current rules and with your change, and shows each item that would be routed differently, how many get stricter or weaker, and that the replay matches live routing.
Submit, then sign off. Every change needs an Admin. A change that weakens an approval (an auto-approval, fewer or looser approvals, retiring an approval rule) also needs Compliance, and so does any change where the Admin who signs is the person who asked for it. Compliance never signs a change it asked for. Choose when it takes effect: now or a date. The version it replaces stays in force until then, and every version keeps its dates so past routing can be replayed.
To change an active rule, make a new version; to stop it, ask to retire it (signed off the same way).

Desks and SLAs (Workflow › Desks and SLAs)

Admins create desks with a head and members and choose round-robin or least-loaded assignment. Anyone can go off desk (Operations and Admins can set others): their open items are re-routed to an available desk colleague, or back to the queue.
Each stage has a default SLA and escalation chain (after the SLA the desk head, after twice the SLA the Admins); Admins can change them per stage, and a workflow rule can set its own. Timers count business hours - 08:00 to 18:00 New York on the firm's business days (US holidays and the firm's own closed days skipped) - or run around the clock if the firm chooses.
The scheduler checks timers every minute and sends escalations by notification and email.

Try it in the demo All articles