I like the idea of lowercase driver names, I've used the driver-name - P to know that driver named Joe - P is a portal version of Joe in the past, for example.
The Schedule Library from Driver Rule plus it's companion Copy Commands From..., found in the driver commands, is the best combination ever and simple to use too.
In the edit session screen, enable the Schedule Library.
Go into the driver commands and add Copy Commands From...
Go back to the Session editor where you added the Schedule Library and open that up.
You'll be present with a blank area. Create a schedule. You'll have to give it a name. Enter in your commands as if you are adding them to a driver. The only command that doesn't work properly here is the repeat command because it confuses things.
You can create multiple "schedules" of driver commands, group them together and even rename them if you want.
Once all your driver "schedules" are created, you then edit your drivers and insert the Copy Commands From... in the driver command queue.
Place a Wait 20 seconds add in Copy Copy Commands From. That command will open up and you then choose Insert schedule. This will present you with the list of the schedules that you created previously. There are other options, but only use Insert Schedule. They have never worked properly, meaning they get a bit squirrelly and weird things happen due to their inconsistent nature. Once your copy commands from command is setup, you can have the driver do whatever. If you want to repeat, place at the end as usual. The wait command is important because it gives the command a change to load. You can string multiple Copy Commands from together one after another. Insert a Wait 20 between them. This is great for setting up complex schedules. I use it this way, for example, to create a lengthy trip, I divided up the very large route into what I called divisions. The Schedule Library schedules were grouped by divisions and this made finding them a bit easier when setting up the driver (They're not displayed in the same fashion and are alphabetically organized). I also named the schedules descriptively.
How it works.
In Driver, your AI driver will wait its 20 seconds as requested. Then the Copy Commands From... driver command will pop up as if water was added and everything spilled out. The driver commands as presented can be changed on the fly if needed, but this doesn't affect the original in the Schedule Library. This is great for troubleshooting and for other on the fly changes. The good thing is, however, if you do discover a bug, you can go back to the Schedule editor and edit the schedule for many drivers at once by editing the one schedule in the Schedule Library.
Where this command and rule combo shines is with repeatable commands used by many consists such as a transit route, or other schedules that have multiple drivers doing the same thing, and especially with portals where inserting a consist from the pre-made consists followed by a driver and wait and Copy Commands From makes the portal setup so easy.