Many thanks for the feedback Morris! I've already made a few changes based on your comments.
As a general comment, we don't want LOP to be too much of a training manual. We expect controllers to "know the job" and not "learn the job" from reading the LOP. LOP simply contains local deviations or procedures that differ from General Operating Procedures (GOP). Currently our GOP documents are quite old however, and we are working on updating these as well. If we also had a comprehensive training manual explaining various techniques, terminology etc that would be even better, but it's beyond the scope of what we can do at this time (ideally this is something I would like to see centralised within SCA or even VATEUD - it makes little sense for each FIR to make this kind of documenation all on our own).
Morris Schussler (1384321) Regarding the layout, since the LOP does not have any images of the airport layout, I would suggest linking the appendix earlier in the document. Alternatively, adding diagrams of the taxi routes and apron entry taxiways in the LOP itself.
Adding such diagrams would basically be a copy/paste of the AIP, which we expect all controllers to be familiar with. Although I agree it would lighten up the document, it would be too much work to add this to all LOP (we have to consider commonality and not have a "special" LOP just for ESGG).
Morris Schussler (1384321) A wishlist item is that the LOP could mention the positions that cover ESGG top-down and the frequencies for these. It's not that important since you can figure it out based on who is online and simply asking, but it would give a better overview of the position structure.
The sector ownership is both complex and dynamic, and the best way to keep up with who is covering top down is to be effective in coordination, i.e. if a controller logs on he will verbally coordinate with any affected positions. You can also see adjacent frequencies in TopSky/ES - this is dynamic based on which positions are online so it should normally be accurate.
