Control Tables templates

[PJW]

Remember though, you can use whatever format you wish. Even your own creation.

Jerry

I've seen some examples of Route Control Tables that list points available to be called N / R under the Route level; and also list these sets of points again under the aspect level, although here they list them as point ends set, locked and detected...

As these point numbers are essentially the same, I'm keen to save precious minutes by listing them only once; I'm unsure which is more likely to demonstrate understanding, though - or if there's a way to demonstrate this understanding quickly with a brief note?!

any guidance would be helpful - or even a slating if I've totally missed the plot?!
----------------------------------------------------------------------------------------------------------------------
If using the one route to a page type Control Table then the route level is above the aspect level; I suppose that you could put "see below" (on your blank) in the point entries at the route level. Wouldn't quite work for swinging overlaps though, but perhaps not worth worrying too much by that

For the column type CT, then some varieties only ever had one points column so I suppose you could just do that. As you say, there are also disadvantages in such a presentation as checking for availability before permitting the route to set is actually separate (although related) functionality.
I suppose you could just head the column "points" and cross reference a note on the lines of:
Route level: Point are checked to be correct or free to go Aspect level: Points are proved set, locked and all ends detected

Doubt that it'll save you much time, but they say "every little helps"