You realize that you can do some simple things with the pools and not diminish the chances of the bid passing, right? Here is what I mean. Suppose she takes a quick scan of the trips in that lone L-- pool you created. Suppose she says, ya know, there are a bunch of LGA layovers showing up. And I would rather not layover in LGA if there was another choice. Also, I really would prefer the trips that have 3 legs or less per day, if they are available. So do this:


1 AVOID Work Fri 0000 - Sun 2359 01Apr 00:00 - 30Apr 23:59
2 AVOID Trip Report Time < 0900 01Apr 00:00 - 30Apr 23:59
3 AVOID Trip Report Time >= 2100 01Apr 00:00 - 30Apr 23:59
4 AVOID Layover Any , Length <= 12:00 h 01Apr 00:00 - 30Apr 23:59
5 AWARD Work 01Apr 00:00 - 30Apr 23:59 [L--]
6 AVOID layovers city LGA
7 AVOID legs per day greater than 3
8 AWARD Work L-

Now LGA layovers and trips that have more than 3 legs in a day are frozen in the L-- bucket. Everything else moves up to the higher L- bucket. Does this guarantee no LGA layovers or no trips with more than 3 legs a day? No, but the system will try to honor that or at least minimize it. Doing this little maneuver does not change the odds of the bid group passing as the total number of trips available (yellow number) does not change. You are simply ordering choices rather than making it random.