Hello everyone.
This is team 1701 Robocubs’ filed scouting sheet. The idea is each team has one master sheet assigned to them. Each time they compete, you distribute their sheet to a scout. This way, data on each team is already sorted and easily accessible. let me know what you think.
Edwin Yazbec, team 1701 Director of Scouting
Field Scouting Spreadsheet.xlsx (12 KB)
Field Scouting Spreadsheet.xlsx (12 KB)
::rtm:: it looks grate but don’t you think it’s a little confusing for any person you pull out of the pit or just a random mentor. i made a seat my self and would love to get your opinion on it but i do not have it at this time. but it looks amazing. but it could use some comment sections in between the matches so you can get scouts opinions right away instead of at the night before alliance selection
One thing you may want to consider is to fill rows three to five with just white cells where you don’t have text. This way, the first cells that they can write in is in row 6, thus making it extremely unlikely for them to accidentally fill in the wrong cell.
Also, you could combine “Capture?” and “Scale?” into one column that just asks what they do with the tower, where the scouts could write in capture, scale, or neither.
Keeping track of all of the match data for a team on one sheet of paper (rather than 9 or 10) is certainly eco-friendly and cheaper. Would your scouts use tally marks on this master sheet to keep a running track of things like shots, or would they keep track elsewhere, and transfer the final numeric values into the spreadsheet at the end of the match?
I like the idea of keeping track of “assists” when crossing the drawbridge or sally port. I think that there are two types of assists, though: a) when the robot helps their alliance partners cross, and b) when an alliance partner helped the robot cross. Which are you tracking? If both types of assists are useful intelligence, might be worth adding a column and tracking both.
A bit of technical advice…using the “merge and center” option in Excel would allow you to get rid of the rose-colored cells and create a cleaner-looking header.
Our goal is simplicity. Scouts would use tally marks.
We are tracking “a) when the robots helps their alliance partners cross”
We created a relatively similar sheet for this year’s game. A few suggestions:
Keep in mind that these are all suggestions, so if you feel what you have works best for your system/team, then go for it. Overall, I can see this system working pretty well.
One thing I would keep in mind when creating a scouting sheet. Only collect data that you plan on using. The more different field a scouter has to collect the less accurate the data will be and the faster they will burn out. So really ask yourself, do we care about each of these fields. When ranking the teams will we actually use this data.
I would suggest adding a special row of a different color for recording what the team did in autonomous, as there currently isn’t anything about that on the sheet. (This row would be be best placed at the top, before the yellow rows.) You won’t want to lump autonomous and teleop together in your scouting system, because it will be important when considering who to select for your alliance, particularly when you get past district competition. It may even come into play before then.
Besides that, though, I like this sheet, and you’ve got the right idea.
As someone above says, I would recommend adding something to track autonomous.
Another thing, remember you only need 12 rows (max) for matches on a sheet. That could help clean this up and make it look a bit neater and more compact.
Additionally, have you considered a comments section? My head scouts always add one, just in case a robot does something noteworthy or unusual (This includes if they broke in a certain match, if they played really good defense, etc.). The kind of subjective data that is imperative when thinking about alliance partners.
Just a short story to illustrate my point (because I like stories): In 2014 at the Buckeye regional 910 was the number one seed, and when it came time to pick the third robot for our alliance we picked 639. They were actually ranked 11th or 12th on our pick list, as they were the only team at the entire regional that had been able to push our robot around, and we got them at number 24. We would not have known their defensive capabilities without a comments section, and their contribution to the alliance led to us winning the event.
So just numbers and tally marks will only get you so far.