Execution algorithms explained: TWAP, VWAP and beyond
- Severity
- Informational
- Status
- Published
- Affected area
- Execution
- Published
- Last reviewed

If you want to buy a million shares, you cannot simply send a market order for a million shares — you would sweep the book, move the price against yourself, and pay dearly for the privilege. Execution algorithms exist to solve this: they slice a large parent order into many small child orders and work them into the market over time, balancing the cost of impact against the risk of the price drifting away while you wait.
§01TWAP: spread it evenly over time
Time-Weighted Average Price is the simplest scheduler. It divides the order into roughly equal slices and releases them evenly across a chosen window. TWAP does not care about volume — it just paces the order over time. Its virtue is predictability and simplicity; its weakness is that it trades the same amount into thin periods as into busy ones, which can be conspicuous.
§02VWAP: trade where the volume is
Volume-Weighted Average Price schedules child orders to match the market’s historical volume profile — trading more when the market is naturally busy and less when it is quiet. The goal is to blend in: by participating in proportion to everyone else, you minimise your footprint and aim to achieve close to the volume-weighted average price, a common institutional benchmark.
§03POV: track a share of the flow
Percentage-of-Volume takes VWAP’s intuition and makes it reactive. Rather than following a historical profile, POV targets a fixed share of whatever volume actually trades in real time — say, ten percent. When the market speeds up, you trade more; when it slows, you ease off. It adapts to the day the market is actually having, at the cost of a less predictable completion time.
§04Implementation shortfall: mind the whole cost
The most sophisticated family, implementation-shortfall algos, optimise against the arrival price — the price when the decision was made. They trade off market impact against timing risk explicitly, front-loading or back-loading the schedule based on urgency, volatility, and the trader’s risk appetite. The aim is not to match a benchmark but to minimise total cost versus the moment you decided to trade.
§05Choosing the right tool
No algorithm is best in all cases. A patient, cost-sensitive order in a liquid name may suit VWAP; an urgent order ahead of news may call for implementation shortfall or aggressive taking. The skill is matching the algo to the objective, the liquidity, and the urgency. Everything here is a simplified, educational explanation and not investment advice.