[Eugenia Gabrielov]

There are a few different things that need to be taken into account with scouting sheets.

Prescouting
It's to your advantage to do some prescouting before your first competition. Look at websites, chief, other competition results, scouting databases (I am under the impression that Soap 108 runs a database), etc. These are resources that will give you a great idea of what sort of competition you're coming into. Keep an eye out for what's happening, and record it on a sheet for each team, or whatever you choose to do.

During the Competition: Results
How does this team perform quantitatively? Do they win their matches? Do they lose their matches? What is their ranking at the end of the day? These are basic things you should record, maybe on a simple table. I.e.,

Team > Wins > Losses > Scores (larger comment box) > Rank

During the Competition: Performance
How does this team perform qualitatively? What are their strengths and weaknesses? Michael Hill pointed out some great things to notice in the post above here somewhere. That is a great guideline. You should have a decent idea of what the team does during autonomous mode. Compatibility is crucial. Will their programming, actions, and strategy be compatible with your team? They may be awesome, but it doesn't make them compatible. Discuss carefully your priorities with your design team and drivers.

I would highly recommend a fairly simple system, although I just threw a lot of information at you. You need to be able to record these with your scouting team with much efficiency. If you are scouting alone, simplicity is exceptionally important.

Good luck!
- Genia