The simplest addtions are direction indicators in column 8 of the CDs - Arrows for each compas direction - and control codes that allow for A-E, A-C, A etc, which already works, but only once per code. The next is to add small dots for the solutions sheet where the kites are placed including the zero (non existant kite).
Tom Dobra commented
Here is my take on what's most important in order, to help you prioritise, plus a few extras. I have written a PP add-on (TCTemplate) for TempO, but we're lacking a free program for PreO.
1. A, A-B, A-C, A-D, A-E in column B of the control descriptions - essential, but I appreciate will require a slight rewrite of the PP file format/how you id controls
2. Make the compass directional arrows in column C also available in column H - desirable, but can always be added in by hand if required - these arrows tell the competitor which direction to look to see the kites
3 (new). Option to show control descriptions with a navigate to finish for a score course. Sometimes the PreO map is too cluttered, so we omit the lines joining the controls, even though it is still a linear course.
4 (new). Option to manually specify the distance from the last control to the finish. In TrailO, it could be less than the calculated value.
5. What Iain says about producing solutions sheets I think needs considerably more development to be useful. We can currently achieve adequate results in OOM, so I consider it much less important for PP for now. Two distinct point symbols are required (jury is still out over what is best, but I use red and blue filled circles) to be added to the map and a legend also placed somewhere.