So, I successfully tested yesterday on a test instance using the following script (as there are over 250 transaction log files!)

RESTORE DATABASE [EproPat] FROM DISK = 'D:\tmp\EproPat_backup_2017_08_08_000106_1477461.bak' WITH NORECOVERY, REPLACE
RESTORE LOG [EproPat] FROM DISK = 'D:\tmp\EproPat_backup_2017_08_08_010007_1198079.trn' WITH NORECOVERY
RESTORE LOG [EproPat] FROM DISK = 'D:\tmp\EproPat_backup_2017_08_08_020006_9747574.trn' WITH NORECOVERY
RESTORE LOG [EproPat] FROM DISK = 'D:\tmp\EproPat_backup_2017_08_08_030005_2635503.trn' WITH NORECOVERY
(and so on for all the other transaction logs up until the latest one)
RESTORE DATABASE [EproPat] WITH RECOVERY

So, on the live system if I wait for the, for example, midnight (00:00) transaction log backup to complete then kick off the restore script at 00:01 there is no need for a 'tail log' backup to take place?  (I choose midnight as an example as nobody would be using the system at this time!) then once the database was up and running again it would be consistent as of the latest 00:00 transaction log?