Originally Posted by TED74

I think you made similar comments last time the subject came up.

1. We're in negotiations; the PWA can be changed

2. LOAs can modify/ improve/ modernize language and we can all weigh in by memrat

3. Scheduling needn't wait 10 minutes if someone declines. If you watch a batch of 30 pilots responding to arcos while repeatedly refreshing, you can see declines and nominations happening at a rate of 5 or more per minute. The logic could look like this:
Scheduler Gets the report. Build the pool of 10 pilots. Hit "start", goes to get coffee. First pilot contacted at 1200 with phone call(s) and ARCOS. First pilot declines at 1203 after referencing details. Second pilot contacted instantly when pilot 1 hits decline, declines at 1205. Third pilot declines at 1208. Fourth pilot doesn't respond. 10 minutes after 4th pilot contacted at 1218, fifth pilot is contracted and accepts/acknowledges the rotation at 1221. Pilots 6 through 10 are never bothered about a GS they weren't going to get. Scheduler returns from the bathroom. ARCOS processed 5 pilots in 21 minutes - way faster than old school, 5 unanswered phone calls and an hour of labor. This scenario is also faster than current implementation of ARCOS, which uses the separate 15- and 10- minute response windows for a minimum completion of 25 minutes (and unnecessarily bothers 5 pilots).

In such a scenario, the software could also be programmed to give pilots an option to opt in if they have been placed in the bucket, prior to them getting their actual solicitation. Then those who want the extra lead time to consider, even knowing it isn't necessarily theirs, can have it. Those who don't want to deal with the head fake needn't do so, and they just don't opt-in for that feature.