[Bethie42]

The problem I foresee with Option B, at least at our regional [Oregon, few 'powerhouse' teams] is that in many matches there may well be no other minibots, so ANY minibot that scores is going to be ranked 1st. True, this might be balanced out by other matches, but with only ~8 matches, I'd rather not risk it. [Edit, I just noticed that the OP is from Team 360....an exception to the 'no powerhouses at AOR' rule *bows in respect* ]

Personally, I'd like to stopwatch-time each minibot, but I doubt we'll have the manpower for that. I'm leaning towards just a yes/no response: did a team's minibot score? but that has the huge disadvantage of being no help when you are trying to pick an alliance partner and 'Our data shows that this team's minibot reached the top of the pole 8 times, but then so did this team's....'

I'm in the early stages of planning our scouting system and I'm interested to know what others are thinking; are the strategy/scouting discussions mainly going on in the General Forum?

It might be interesting to have a scouting team assigned to just watch and time minibots [for teams with more than 9 members...heh]. I wonder if we will see teams picked solely on the basis of their minibot.

What is your opinion of recording a yes/no answer for match scouting, then relying on pit scouting for exact times? Self-reported times, however, will probably not take into account the time needed to maneuver up to the pole and deploy.