You implemented exactly what I think the perfect scouting software this year should have. Make it more personal to your team’s strategic needs, and you’re probablly done.
Here are some of my tips, regarding to the state of the software you’ve showed us:
Build your team lists per regional. As it seems, for each team you’ll need to input the name of the regional again and again and again, though it is obvious you’re talking about the Israel regional (or Atlanta [Galileo, Newton, Archimedes, Curie], if it’s the second list ).
Make it more user friendly: Depending on who will be involved in your scouting team in the competition, you should probably present a simple UI for the scouters when they gather information, be it in the pits or from the matches. Later on, the info they give you, the strategy analyzers, the important info that you report to the driver team (what they should do in the next match, or what teams to chose for the eliminations).
I’d sugest taking note of some of the comments in the topic I posted above, regarding the amount of scouters you might need.
What programming language did you use? Looks like VB.
As far as recall it was programed in C#, although I wasn’t the one to write it (I prefer writing my scout programs in Excel). Good luck and hopefully we’ll meet up again in Atlanta and not just the regional