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