Definitely there is going to be an issue with TBA delay. For the data in general, we collect TBA and match data separately and store them in separate databases. Afterwards when we have the matches in a range we want for both data types, the system will prompt the scout leader to compare and check the data. A lot of the crucial data that comes from TBA we will require scouts to collect.
Our team does have a protocol for training tablet users. Even last year with our very basic app, we made sure to get all students (who wouldn’t be paper scouting, driving, or doing something else that’s crucial during comps) and teach them the basics of the app and what to look out for. Granted, this app did not include things like starting position as we did not rely so heavily on tablet data. Later on, we found out that the data collected could be more useful in match prediction and strategy, but that was a little bit too late as the pandemic situation started to develop after our first competition.
A lot of what I described for the TBA delay plan is currently in a demo or idea form. Preseason for strategy is going to be packed as it’s hard to discuss scouting app stuff other than what I’ve worked on in the past week during a weekly virtual Zoom meeting. Your post will make me think more about how much of a difference TBA delay might make.