Execution Algorithms

Written execution objectives and benchmarks, hard limits on every parent order, a replay simulator, staged rollouts and regular reviews of TWAP, VWAP, shortfall and routing logic, for the researchers and engineers who build them.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Execution Algorithms, and click Install. It goes into your own files, and works offline from then on.

Before you start: this plan is general information to help your team organise its work. It is not financial, investment, tax, accounting or legal advice, and it does not recommend any product, investment or deal. Rules differ between countries, so check decisions that matter with qualified, licensed advisers in the countries concerned. Investing can lose money, and raising or managing other people's money is regulated in most countries.

What it installs.

1

Pillar

1

Area

50

Projects

203

Starter tasks

🧮 Quantitative Finance & Trading

Execution Algorithms

Designing and evaluating execution: TWAP, VWAP and implementation shortfall approaches, order scheduling, venue choice and testing changes safely.

  1. Written execution objectives by order type
  2. Choosing the benchmark each algo is judged on
  3. Inventory of algos, versions and parameters in use
  4. Historical intraday volume curve per instrument group
  5. Pre-trade estimate of duration and participation
  6. Hard limits and kill switch for every parent order
  7. Order book replay simulator for testing changes
  8. Order state and child order audit trail
  9. Execution change policy with staged rollout
  10. Daily exceptions check on yesterday's orders
  11. Weekly algo performance review against benchmarks
  12. Monthly volume curve refresh
  13. Monthly audit of limits and parameter overrides
  14. Quarterly venue and routing review
  15. Release calendar and change freeze windows
  16. Market calendar watch for auctions and half days
  17. Weekly child order fill quality sample
  18. Quarterly review of broker algos and their settings
  19. Execution incident log and post-mortem routine
  20. TWAP mechanics and randomised slicing
  21. VWAP tracking and its failure modes
  22. Implementation shortfall and the impact versus risk trade-off
  23. Percentage of volume algos and participation limits
  24. Limit order placement and price improvement tactics
  25. Smart order routing and venue types
  26. Opening and closing auction participation
  27. Information leakage and anti-gaming checks
  28. Urgency setting rule for portfolio managers' orders
  29. Build versus buy decision for execution algos
  30. Dark pool and conditional order policy
  31. Adaptive schedule that reacts to price and volume
  32. Short-term signal inside the order scheduler
  33. Randomised live test design for algo changes
  34. Retiring an unused algo variant
  35. Index rebalance day execution plan
  36. Go-live of a new algo version
  37. Annual algo self-assessment against regulatory rules
  38. Quarter-end and expiry day playbook
  39. Kill switch and runaway order drill
  40. Pilot of a new broker algo on limited flow
  41. First 90 days as an execution quant
  42. Execution setup for a small fund without a desk
  43. Order handling rules for a personal algo account
  44. Handover pack for an execution algo you built
  45. Execution algorithm write-up for a portfolio
  46. Explaining algo choices to portfolio managers
  47. Calibrating a market impact model for scheduling
  48. Basket and portfolio execution with risk constraints
  49. Futures roll and calendar spread execution
  50. FX and digital asset execution across fragmented venues

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Written execution objectives by order type

An algo cannot be judged good or bad until someone has written down what each kind of order is trying to achieve: minimise cost against the decision price, match the day's average, finish before the close or stay invisible. Writing one objective per order type, with the trade-off it accepts, stops arguments after the fact about whether a slow fill was patience or failure.

First tasks

  • List the order types sent in the last three months from the order log
  • Write one objective and its accepted trade-off for each order type
  • Agree each objective with the person whose orders it covers
  • Save the objectives beside the execution code

Choosing the benchmark each algo is judged on

Arrival price, interval VWAP, the closing price and the previous close each reward different behaviour, and a VWAP algo judged against arrival will look broken on every trending day. Matching one primary benchmark to each objective, and writing why, makes performance numbers comparable across months and people.

First tasks

  • Pair each order type with arrival, interval VWAP or closing price
  • Write the exact start and end time rule for each benchmark
  • Note one blind spot for each benchmark chosen
  • Get sign-off from each objective owner

Inventory of algos, versions and parameters in use

Execution stacks accumulate variants: a broker's VWAP with three custom settings, an in-house TWAP from two years ago, a close algo someone tuned once. A single inventory of every algo, its version, its default parameters and who may change them is the base for every review, limit and release that follows.

First tasks

  • Pull a list of distinct algo names and versions from last quarter's orders
  • Record default parameters and allowed overrides for each algo
  • Name an owner and a change approver for each entry
  • Flag variants with fewer than a handful of orders for review

Make it yours.

Install Execution Algorithms, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.