[jweston]

Your strategists and scouters are really the ones to make or break this argument. Their jobs are directly affected by it, for better or worse.

A lot depends on what kind of data they find important. Stats (points scored, misses, fouls, etc.) for each robot works well. Qualitative assessments (stability, execution speed, durability, etc.) or showing illustrations (routes, critical point on the robot, etc.) can be harder to incorporate into a good UI. This is especially true if your UI did not anticipate a game metric your strategists would want.

Does your team currently have the tools to use electronic records in a way that would make a difference to your strategists during an event? If not, you may be putting the cart before the horse.

Regardless of how your team chooses to implement, I recommend ensuring your scouting system serves the people who use it and not the other way around.