Welcome to the Zone 8 Rules Proposals page. The purpose of this page is to provide an avenue for Zone 8 members to suggest new rules and changes to existing rules. You will also find all the permanent links to all zone competition & driving rules and regulations. All rules comments and concerns are catalogued and compiled to give a real reflection of member inputs for year-end rule modifications.
Suggestions for improving these rules are encouraged. The process is as follows:
What Happened to my Rule Change Proposal (PDF) (updated: August 17, 2018)
Rule Change Proposals (PDF) (updated: Jul 31, 2018)
Please comment! Please let us know if you agree or disagree with proposed changes. Do they increase fairness and fun? Do they make us safer? Or...? Please explain why you think what you think.
Submit comments on the proposed changes to the Rules Coordinator at: email@example.com
Submit proposals to the Rules Coordinator at: firstname.lastname@example.org
When submitting rule change proposals, please use the following format:
Current Rule and the Problem
Please tell us what the issue or problem is and what rule you believe should be changed to fix it. The most important concepts the Rules Committee needs are: What is going wrong. What is unfair, unsafe or otherwise broken. Who does it effect and how does it affect them. Providing data and analysis of results is always very helpful in supporting your suggestion.
If possible, please propose suggestions for changing the rule(s) in question.
Describe how the proposed rule changes would fix the problem and/or addresses the situation. In addition to clearly stating what you see is a problem, you must clearly demonstrate how and why your proposal resolves the situation.
Please use data and explain your reasoning in a clear and logical manner. Often rule proposals are rejected because the Rules Committee does not understand the author's description of the problem or what the proposal is trying to do or change. Another frequent cause of rejection is when the proposed change doesn't appear to address the issue presented.