⚪

What are Execution Algorithms?

Overview of Execution Algorithms

Trading execution algorithms are one of many ways advisors can leverage trading technology for their clients. Algorithmic trading relies on predictive analytics to recognize and take advantage of patterns that may be indiscernible to human traders.
Over the past twenty years, algo trading has taken over the market as the single most common trading strategy. More than 80% of US stock trades are algorithmic while the global market is predicted to grow to $18 billion by 2025.
Although the specific implementations of order execution algorithms used in the industry tend to be proprietary and closed-source, they tend to derive from one of the following algorithms.

Time-Weighted Average Price (TWAP)

The TWAP algorithm aims to execute orders in a uniform manner in a previously determined period. In other words, TWAP algorithms have the objective of trading at a rate proportional to time.
Consider a case where a trader wants to buy 100 shares of a given stock in the following hour. If we split the hour into 10 intervals, the algorithm should buy 10% of the total order in the first 6 minutes, 20% at 12 minutes, and so on. By the one-hour mark, the algorithm should have acquired 100 shares.
Following these rules can be trivially done by sending a market order for 10 shares every 6 minutes. Of course, this would not be very convenient. Although we are reducing market impact by dividing a big order into smaller ones, we are not optimizing the average fill price. This simple algorithm can be strictly improved by also introducing Limit Orders.
On t=0, we create a limit order for 10 shares. After 6 minutes, the TWAP checks how many shares we were able to acquire at the given limit price and creates a market order for the remaining quantity. For example, if only 5 of the 10 shares were bought during the first 6 minutes, the execution algorithm creates a market order for the 5 remaining shares required.
Having done so, the algorithm creates the next limit order for 10 shares that should be bought during the next 6 minutes. The unfilled quantity will again get filled by a market order at the 12-minute mark.
This process will continue until we acquire the entire 100 share lot, which will happen with certainty sometime between 54 and 60 minutes after starting the TWAP.
When implementing a TWAP algorithm, the developer has to consider the following parameters:
  • The total time horizon for executing the algorithm: If the time horizon is too short, the overall impact on price will increase. Conversely, if it is too large, risk exposure to changes in price increases.
  • The number of intervals: the fewer intervals, the bigger each order will be, leading to increased market impact. On the other hand, too many intervals decrease the duration of each one and thus decrease the probability of the limit order of getting filled.
  • Limit Price: the further away the limit price from the market price, the higher the probability of having to fill the quantity with a market order at the end of the interval.
The execution profile of the algorithm looks as follows:
​
​
​
​

Volume-Weighted Average Price (VWAP)

It is a known fact that there are times of the day that tend to have more transactions than others. For example, the first and last minutes of each trading day feature a larger number of transactions than any other time of the day. Given that an order’s market impact is smaller when large volumes are traded, it stands to reason that it is convenient to place larger orders at such intervals. This is exactly what VWAP does.
Instead of splitting orders into fixed intervals as the TWAP algorithm does, the VWAP algorithm splits a large order into smaller ones based on the volume traded. It also follows a schedule, but instead of being proportional to time, the VWAP schedule is proportional to the historical intraday volume profile of the asset.
Regardless of the shape of the profile, the algorithm will split the order into segments of equal volume and form a schedule. If the VWAP is instructed to buy 100 shares over the next hour, it will do so based on the estimated interval volume. If 10% of the total volume occurs over the first 3 minutes (double the average volume), it will fill 10% of the total order size over that interval.
In contrast to the TWAP, the VWAP requires forecasting the volume profile based on historical patterns. These have to be as accurate as possible and require taking into consideration lots of features that have large impacts on traded volume, such as:
  • The time of the day
  • The day of the week
  • The existence of “special” days. Dates where futures or options expire feature much larger trading volumes than “regular” days.
Having stated the main distinction between the TWAP and the VWAP, the remaining considerations are exactly the same and choosing the time horizon, the number of intervals, and the limit price has the same implications.
The trading profile of the VWAP looks as follows:

Implementation Shortfall (IS)

Also known as Arrival Price algorithms, Implementation Shortfall execution algorithms are among the most widely used algorithms in the industry. In contrast to TWAP and VWAP, the basic implementation of the IS algorithm cannot be characterized with precision. Instead, we will outline the general idea behind these types of execution algorithms.
Implementation Shortfall is commonly known as a performance metric that measures the difference between a realized live trading implementation and the respective paper trading or backtesting counterpart. If we define the arrival price as the price where a given signal is issued, Implementation Shortfall is the difference between the realized buy and sell price and the arrival price.
​One of the earliest and most popular implementations describes an algorithm whose objective function is to minimize the execution cost, a risk penalty, and the expected alpha cost.
  • Execution Cost: speeding up the trade will increase execution costs.
  • Risk: speeding up the trade will decrease risk, as measured by the potential change in price.
  • Alpha Loss: if the alpha of a given signal decreases rapidly (like for news events), slowing down execution will increase the alpha loss.
Execution and Risk can be thought of in the usual risk-return terms commonly used in investment. Also, all else being equal, a greater positive alpha will lead to more aggressive trading. The alpha loss is also not required to be linear but can have a trajectory that depends on time.
Having considered all three aspects of an Implementation Shortfall algorithm, we could characterize the objective function as follows:
E[TotalCost] = E[ExecutionCost] + E[AlphaLoss] + RiskPenalty
Whereas execution costs and the risk exposure are the same for all market participants (at least in principle), the risk penalty is subjective and unique for each trader and depends on the traders’ individual risk aversion.
As said previously, the specific implementation and execution of an Implementation Shortfall algorithm cannot be precisely characterized, but we can still analyze how the parameters affect the objective function.
We could, for example, execute an order with a TWAP algorithm, and the Implementation Shortfall objective function would determine its time horizon.
  • In absence of a risk penalty and alpha, the TWAP would have a long time horizon that would minimize the execution cost.
  • The higher the volatility of the stock and the higher the risk aversion of the trader, the shorter the time horizon would be.
  • A bigger alpha signal with a steep alpha loss profile would lead to a shorter time horizon for the TWAP.
As can be seen, some variables are minimized with longer time horizons, whereas others are minimized with shorter ones. This leads to a trade-off, and the optimal is found by minimizing the total expected cost.
In-House vs. Broker Implementation Shortfall algorithms
Last but not least, there is an important distinction to be made between proprietary IS algorithms developed and operated in-house and the ones used by brokers.
Proprietary firms do have information regarding their risk aversion and their expected alpha, meaning that they can incorporate these parameters in order to optimize the IS objective function and create an optimal trading schedule.
Brokers, on the other hand, are unable to know the individual risk aversion of each client. Also, for obvious reasons, traders are also reluctant to share the alpha profiles. The workaround that brokers have created is to aggregate both the risk aversion and the alpha of the client into a single parameter: “urgency”. This will determine how aggressively an order should be executed. It is up to the clients to determine how “urgent” a given order should be, and this is done by testing a few trades with different “urgency” values and creating an “urgency” profile that they can plug into their Implementation Shortfall function and run the optimization in-house.

Conclusion

As can be seen, order execution algorithms play a non-trivial part in the performance of proprietary firms and hedge funds alike, and the degree of sophistication of their implementations can require entire teams devoted to their research and optimization.
In the present article, I only covered the most important and popular ones. Although these straightforward implementations might not be used by the most rigorous shops, we can safely assume that their in-house implementations derive from at least one of the algorithms covered.