MCT207036 is marginally easier than the Lat/Lon.
True, but that is a measured position, rather than a published position. Is the 207 in degM - or defined using the published declination for MCT?
When the NATS system fist started, I created an easy, roughly square area brief for middle England by specifying a fictitious route from EGVN via VLN DCT SWB DCT CTM DCT MID DCT VLN back to EGVN. Route width of 40nm, so the information for legs on opposite sides of the rectangle overlapped, meaning that there was no 'hole in the middle'. I used this dozens of times, with top level of FL60 - or FL060 in NATS-speak...
It was saved as a route and was very simple to use. A circular 'point brief' would not have been as useful.
However, NATS later erased the route as I didn't use it for some weeks..... Thanks a bunch.
Now I have to specify DCT 5100N00238W DCT 5247N00239W DCT 5244N00039W DCT MID DCT 5100N00238W DCT which is far more error-prone and cumbersome.
If NATS
really wants to cut down on airspace infringements, then they need to produce a web-based 'red pin wall chart' and update it every time a new 'red pin' is created. I would also suggest a 'lower level' filter, so that people didn't have to wade through all the 'training of birds of prey' and unlit chimneys etc....