Rule < T25> states:
Be prepared for minor field variance. Field Element tolerances may vary from nominal by ±1.0”, unless otherwise specified in this Game Manual, official Q&A, or Appendix. Disc weights may vary from nominal to ±20 grams. High Goal heights may vary from nominal to ±1.0” (25.4mm). Teams are encouraged to design their Robots accordingly. Please make sure to check Appendix A for more specific nominal dimensions and tolerances.
The high goal has no secure attachment to the white pole, allowing it to slide side-to-side along the white pole up to several inches in each direction. This is largely because the black pole connecting the high goal to the center pole of the net has a lot of leeway. This often leads to the goal being out of the ±1" tolerance, especially when the high goal gets bumped during field reset. This leads to inconsistent autonomouses (due to the field being out of tolerance) and unequal scoring areas for each alliance.
The only way we see for teams to ensure the field is in tolerance before every match is to manually check it every time. However this is not an optimal solution, as it is impractical to have to inspect the high goals before every match.
Are there any other ways teams can ensure that the high goals are in tolerance at the beginning of each match?
Additionally, if the high goal is found to be out of tolerance after/during the match, would that warrant a match replay as per rule < T7 a. i.>?
If the answer to the previous question was yes, then how should event partners/head referees deal with more than just a few match replays (if the high goal was found to be out of tolerance in more than just a few matches)?
These images were taken from the exact same location to illustrate how far the goal can move with minimal effort (a little push, something that could easily happen during field reset)