I'm not privy to the set-up they're using but I can surmise. I'm curious why they upload the pairings into iCrew before the bidding solutions are even run. I'm sure it's to simplify things on their end. I would think they could upload the pairings into NavBlue without them being uploaded to iCrew. It's so easy to see the solutions as they run and see what trips I'm (or others) are getting. To keep it truly unknown until posting awards, would require something along the lines of:

1. A separate server, with either intranet access blocked, or no access at all, or:
2. Not loading the pairings into iCrew until after the awards are posted.

As each solution (run) is processed, it assigns names to rotations. If you're online, there is a way to see the process unfold. They'd have to do something like the above mentioned to keep it unknown until the publishing of awards. The pairings being uploaded to NavBlue and iCrew and the visibility of the names being assigned during the solution process tells me from a programmer view all I need to know.

Bottom line, I get what I get in the end, but the 0's and 1 side of me is curious!