Exactly - please try to delay til xx:04, no make it xx:05. I will tell you why - xx;00 is catching up the xx:52 to Moreton - Marsh by Maidenhead. The xx:52 makes a Slough stop - as I experienced yesterday. Fortunately TVSC managed to route him into 8 at Reading and we were quickly routed into 9 landing in just over 23 mins despite slowing for signals. So really the XX;00 should leave by xx:01, and probably the xx;03 should be leaving at xx;05. Because they are all catching each other up! Lol!
I have ridden the xx;52 as well - and they don't hang about - completing the scheduled 13/14 minute run in close to 11.5 minutes. So even with that arriving 2 early - it still delays the xx;00. This is all a consequence of the schedule being timed for 24 mins plus 1 min recovery when we all know the 800's will do it easily in 22 to 23 minutes without even being driven flat out.
I wish the signallers would open up the platform starter at Reading to green which would allow most of the inbound services to come in on greens rather than crawling in on a single yellow. But that is an operational issue and prob for another thread.
Remember, the timetable is still for HST's, so the IET's performance isn't taken into consideration yet.
I agree about the platform starter idea, but if the train has an extended dwell, which is fairly common at Reading, or if the signal needs to be pulled for whatever reason, the signaller doesn't want to be the one to snarl up the interlocking for 2 minutes, or however long the time-out is at TVSC.
As well as that, GWR wouldn't appreciate their drivers entering the platform at a high speed, defensive driving techniques and all that
Reading uses TRTS plungers at every platform; if the staff are on their toes, they hit the plunger the moment the train stops in the platform, especially for the IET's.