Register February 2013 No. 686
Chapter Game 4
DUTIES AND RESPONSIBILITIES OF ASSOCIATIONS
AND RACETRACK OPERATORS
Game 4.01   Purpose.
Game 4.02   Number of pari-mutuel races.
Game 4.03   Information/complaint window.
Game 4.04   Daily race programs.
Game 4.05   Approval of contracts.
Game 4.06   Security and first aid requirements.
Game 4.07   Race track requirements.
Game 4.08   Purse structure.
Game 4.09   Alternative use of facilities.
Game 4.10   Fees.
Game 4.11   Operator responsibility.
Game 4.12   Inclement weather.
Game 4.13   Financial audit.
Game 4.14   Restricted areas.
Ch. Game 4 Note Note: Chapter RACE 4 was renumbered chapter WGC 4 and corrections made under s. 13.93 (2m) (b) 1. and 6., Stats., Register, March, 1995, No. 471.
Ch. Game 4 Note Note: Chapter WGC 4 was renumbered chapter Game 4 under s. 13.93 (2m) (b) 1., Stats., and corrections made under s. 13.93 (2m) (b) 6. and 7., Stats., Register November 2003 No. 575.
Game 4.01 Game 4.01Purpose. The purpose of this chapter is to identify the duties and responsibilities of associations and racetrack operators regarding the operation of a race meeting. The duties and responsibilities here are in addition to those set forth elsewhere in the division's rules.
Game 4.01 History History: Cr. Register, March, 1990, No. 411, eff. 4-1-90.
Game 4.02 Game 4.02Number of pari-mutuel races. For the purpose of pari-mutuel wagering all races are considered separate and distinct:
Game 4.02(1) (1) Associations may request wagering on additional races. In acting on such requests, the division shall consider the effect of extra races on state revenue and on track and division employees, and the availability of greyhounds.
Game 4.02 History History: Cr. Register, March, 1990, No. 411, eff. 4-1-90; CR 03-070: r. (1), renum. (2) to be (1) Register November 2003 No. 575, eff. 12-1-03.
Game 4.03 Game 4.03Information/complaint window. Each association shall provide and clearly identify an information or complaint window where complaints may be made by members of the public. The association shall make available a current set of all division rules for public inspection during racing hours at every such window.
Game 4.03 History History: Cr. Register, March, 1990, No. 411, eff. 4-1-90.
Game 4.04 Game 4.04Daily race programs.
Game 4.04(1) (1)Required information for daily race programs. The association shall cause all daily race programs to contain the following information:
Game 4.04(1)(a) (a) This race meet is conducted under that authority of a license issued by the Wisconsin division of gaming and pursuant to the rules and regulations adopted by the division.
Game 4.04(1)(b) (b) The Honorable , Governor.
Game 4.04(1)(c) (c) Wisconsin Division of Gaming, 2005 West Beltline Highway, Suite 201, P.O. Box 8979, Madison, WI 53708-8979, (608) 270-2555.
Game 4.04(1)(d) (d) Wisconsin department of administration secretary.
Game 4.04(1)(e) (e) Wisconsin division administrator.
Game 4.04(1)(f) (f) Names and titles of:
Game 4.04(1)(f)1. 1. Track officers.
Game 4.04(1)(f)2. 2. Track officials.
Game 4.04(1)(f)3. 3. Wisconsin division of gaming officials.
Game 4.04(1)(g) (g) The address and telephone number of the track facility.
Game 4.04(1)(h) (h) A prominent notice that there is an information window where complaints may be made by the public and copies of the Division of Gaming's administrative rules viewed. Such notice shall specify the exact location of such windows.
Game 4.04(1)(i) (i) The location of facilities for handicapped patrons.
Game 4.04(1)(j) (j) The location of the division's office at the track facility.
Game 4.04(1)(k) (k) The location of photo finish pictures.
Game 4.04(1)(L) (L) The approximate payouts on different pari-mutuel odds.
Game 4.04(2) (2)Daily race program to supply pari-mutuel information for patrons. Each association shall include in the daily race program sufficient information to advise the public and new racetrack patrons about the pari-mutuel system. This information shall include but not be limited to the following:
Game 4.04(2)(a) (a) Wagers are to be made by daily race program number.
Game 4.04(2)(b) (b) Tickets shall be retained until the stewards have declared the race official.
Game 4.04(2)(c) (c) Payouts are not permitted until the stewards have notified the pari-mutuel department of the official order of finish.
Game 4.04(2)(d) (d) The division has adopted detailed rules for occurrences such as dead heats or the failure of patrons to select the winning animals or combinations of finishing animals. Such rules are available for public inspection at the information windows and the office of the division located at the track.
Game 4.04(2)(e) (e) The period of time and procedures for uncashed tickets to be redeemed.
Game 4.04(2)(f) (f) The daily race program shall provide a page for the advertisement and dissemination of information regarding the racetrack's adopt-a-greyhound program.
Game 4.04(2)(g) (g) The association shall make a good faith effort to ensure the accuracy of all information contained in the daily race program. All errors detected by the association after the printing of the daily race program has commenced shall be corrected by the association printing a corrected page for distribution with the daily race program, announcements of the error and correct information via a public address system, or both. The association shall obtain prior approval of the proposed daily race program from the division at least 15 days prior to the start of a new race meet or before formatting a new daily race program during the current race meet.
Game 4.04 History History: Cr. Register, March, 1990, No. 411, eff. 4-1-90; CR 03-070: am. Register November 2003 No. 575, eff. 12-1-03.
Game 4.05 Game 4.05Approval of contracts.
Game 4.05(1) (1)Scope. This section applies to any contract for goods and services or both entered into by any person licensed by the division pursuant to s. 562.05 (1) (a) or (b), Stats., and any other person.
Game 4.05(2) (2)Division approval.
Game 4.05(2)(a)(a) Any contract in excess of $10,000 per year for any goods or services or both shall be subject to approval by the division and submitted to the division for approval by the licensee. Such a contract shall not, as a matter of public policy, become effective and binding on the parties to the contract unless and until it has been approved by the division. Any contract not so approved shall be considered void as against public policy. Any person requesting division approval of a contract pursuant to this section shall provide the administrator a copy of the contract, which has been signed by all parties to the contract, within 15 days of execution.
Game 4.05(2)(b) (b) Any multiple contracts under $10,000 per year which the division finds are for same or substantially similar goods or services or both shall be deemed to be a contract requiring approval. Any multiple contracts deemed to be a contract requiring approval shall not be binding on the parties unless and until it has been approved by the division. Any contract or contracts not so approved shall be considered void as against public policy. If the division finds that the use of multiple contracts was to circumvent the requirements of this section, the parties thereto shall be subject to a forfeiture not to exceed $10,000 or suspension or revocation of licensure or both.
Game 4.05(2)(c) (c) Any amendment, alteration, addition or deletion of the terms of a contract previously approved by the division shall also be approved by the division. Such amendment, addition, alteration or deletion shall not, as a matter of public policy, become effective and binding on the parties until approved by the division. Any amendment, alteration, addition or deletion not so approved shall be considered void as against public policy. Any person requesting division approval of an amendment, alteration, addition or deletion shall provide the administrator a copy of the same, which has been signed by all parties, within 15 days of execution.
Loading...
Loading...
Published under s. 35.93, Stats. Updated on the first day of each month. Entire code is always current. The Register date on each page is the date the chapter was last published.