ATCP 1.37 (3) (insert amended text using strike-throughs and underscores).
1.07 References to other provisions; citations.
Do not use general terms, such as "et. seq.," "this provision," "this rule," "of the code," or "of this chapter" when making references to another rule or part of a rule. Make the references specific.
It is not necessary to reproduce chapter, section, or subsection titles in a reference in the text of a rule; just use the numerical reference.
When existing rules are renumbered, repealed, or repealed and recreated, carefully review other rules that contain references to the revised rules and make any needed cross-reference changes by referring to the
Administrative Code Cross-Reference Manual that may be accessed at: http://legis.wisconsin.gov/rsb/code.htm. Search for the whole section number of the cite being affected, including the acronym (ex., ATCP 10.01). Revise all references located in your agency's code as necessary, including in chapters not otherwise affected by the rule. Inform LRB of any cross-references in codes promulgated by other agencies.
1.07(2)(2) Internal and external references
. Differing format is used for internal and external references. An internal reference is a reference to another portion of the Administrative Code that is within the same unit as the portion where the reference occurs, thus making a fully concise citation unnecessary. For example, "ATCP 1.01 (1) (b)" is an internal reference when referred to in other portions of ATCP 1.01. An external reference is a reference to portions of the code outside of the portion containing the reference, thus necessitating a full, precise citation in order to achieve accuracy. Examples of the recommended format for internal and external citations are as follows:
s. 15.01, Stats.
ch. ATCP 14
subch. IV [same chapter], subch. IV of ch. ATCP 14 [different chapter]
s. ATCP 14.24
s. ATCP 14.24 (2) [different section], sub. (2) [same section]
s. ATCP 14.24 (2) (a) [different section], sub. (2) (a) [different subsection], and par. (a) [same subsection]
s. ATCP 14.24 (2) (b) 3. [different section], sub. (2) (b) 3. [different subsection], par. (b) 3. [different paragraph], and subd. 3. [same paragraph]
Rules subdivision paragraph
this subd. 3. a.
s. ATCP 14.24 (2) (b) 3. a. [different section], sub. (2) (b) 3. a. [different subsection], par. (b) 3. a. [different paragraph], and subd. 3. a. [different subdivision or same subdivision]
this subsection or sub. (2) [reference is in sub. (1)]
sub. (1) or (2) [same section], s. ATCP 14.18 (1) or (2) [different section]
this subsection and sub. (2) [reference is in sub. (1)]
subs. (1) and (2) [same section], s. ATCP 14.18 (1) and (2) [different section]
subs. (1) to (5)
s. ATCP 14.18 (1) to (5)
NOTE: References to "Wis. Adm. Code" should not be used when making external references. For example, a reference to "s. ATCP 14.24 (1)" clearly refers to the Administrative Code and not the statutes, because the number "14.24 (1)" is preceded by "ATCP." Material relating to "ATCP" can only be found in the Wisconsin Administrative Code and not in the statutes.
1.07(3)(3) Federal statutes and regulations
When citing a federal law, use the U.S. Code reference; for example, 42 USC 1396a
(a) (13). If an agency wishes to include a reference to a Public Law or a named federal act, this may be done in a note. An exception to this citation requirement is permitted for citations to the Internal Revenue Code, which is a term that is defined in the statutes. When citing a provision in the Internal Revenue Code, cite either the U.S. Code provision or a section of the Internal Revenue Code, as defined in either s. 71.01 (6)
or 71.22 (4)
When citing a federal regulation that is currently in force, use the Code of Federal Regulations citation; for example, 22 CFR 13.2
NOTE: See s. 2.08, Manual, for the use in rules of the incorporation, by reference, of standards established by technical societies and organizations of recognized national standing.
1.081.08 Repetition of language. 1.08(1)(1) Statutory language
. Avoid unnecessary repetition of statutory language. Statutory language may be used if necessary to convey the intent of a particular rule.
1.08(2)(2) Federal regulations
. If an agency is required to adopt federal regulations in addition to its own administrative rules to implement a statute, the agency may include the verbatim federal regulations in its rules. The federal regulation language should be clearly indicated to distinguish it from the remainder of the rule.
1.09(1)(1) Explanatory material
. If it is necessary to clarify a rule by using examples, illustrations, or other explanatory material or if an agency wishes to disclose where or how particular information, including forms, may be obtained, the explanatory material follows the applicable rule provision and is labeled "Note:" or "Example:". Notes may not include substantive requirements and are not part of the substantive law created by rule.
1.09(2)(2) Creating, repealing, and amending notes.
If a note is created, repealed, or amended, that action should be included in the enumeration of provisions treated (in the introductory clause described in s. 1.02 (1) (a)
, Manual) and in the proper sequentially numbered rule Section
, as shown in the following examples:
To create a note, insert "…
to create NR 1.05 (Note)…
" in the enumeration of provisions treated. In the rule text, use the following treatment clause: "Section
____. NR 1.05 (Note) is created to read:". Insert the text of the new note, without underscoring, as it is entirely new language.
To repeal an existing note, insert "…
to repeal NR 1.05 (Note)" in the enumeration of provisions treated. In the rule text, use the following treatment clause: "Section
___. NR 1.05 (Note) is repealed." Do not show the text of the note, as the language is being repealed.
To amend an existing note, insert "…
to amend NR 1.05 (Note)" in the enumeration of provisions treated. In the rule text, use the following treatment clause: "Section
___. NR 1.05 (Note) is amended to read:". Insert the text of the current note and strike through material to be deleted and underscore material to be inserted.
1.09(3)(3) Reference to forms
. If a rule requires a new or revised form, include a reference to the form in a note to the rule. The note should indicate the address that a person may write to, or the telephone number that a person may call, in order to obtain the form. If the form is available on the Internet, the note should indicate the website from which the form may be obtained. A copy of the form should be attached to the rule or a statement should be included indicating where a copy of the form may be obtained at no charge. LRB will insert the note in the Administrative Code. [See ss. 227.01 (13) (q)
, Stats., for the treatment of forms in ch. 227
1.101.10 Time periods for action on permit applications.
Each rule that includes a requirement for a business to obtain a permit must include the number of business days, calculated beginning on the day a permit application is received, within which the agency will review and make a determination on the permit application. [s. 227.116 (1r)
NOTE: Under s. 227.116 (1g), Stats., "permit" means any approval of an agency required as a condition of operating a business in this state.
2.0012.001 Submission of materials to LRB. 2.001(1)(1)
All materials submitted to LRB for publication must be submitted electronically as Microsoft Word documents. In creating proposed rules and related documents, do not use any auto-formatting or auto-numbering.
Email documents to Admin-Code-Register@legis.wi.gov
. LRB will email an acknowledgement of receipt of each submitted item. If you do not receive the acknowledgement, contact Bruce Hoesly at LRB. Except for certified copies of rules required to be filed with LRB under s. 227.20
, Stats., LRB does not require submission of paper copies of any documents.
2.0032.003 Submission of materials to state administrative rules website.
Agencies are required to submit in electronic format to firstname.lastname@example.org
, for inclusion on the state's administrative rules website, all publicly available materials regarding rules that are submitted to DOA, the Rules Clearinghouse, the Chief Clerks, LRB, legislative standing committees, and JCRAR. This includes scope statements, submissions to the Rules Clearinghouse of proposed rules and accompanying materials (such as fiscal estimates and economic impact analyses), reports of the SBRRB, notices regarding hearings, final proposed rules and reports to the Legislature that are sent to the Chief Clerks for referral to standing committees, emergency rule-making orders, requests for extensions for emergency rules, modifications to proposed rules, withdrawals or recalling of proposed rules, and final rules that are submitted to LRB for publication.
2.0052.005 Statement of scope of proposed rules. 2.005(1)(a)(a)
For each administrative rule an agency plans to promulgate, a scope statement must be prepared, approved by the Governor, published in the Register, and approved by the person or body with policy-making powers for the agency. A scope statement is required for both proposed emergency rules and permanent rules. [s. 227.135
, Stats., and 2011 Executive Order #50
No state employee may perform any activity in connection with the drafting of a rule, except for the preparation of the scope statement, until the scope statement is approved by the Governor and the individual or body with policy-making powers for the agency. [See sub. (5), below, and s. 227.135 (2)
The scope statement must include all of the following elements, which should serve as the headings in the scope statement in the order stated below:
A description of the objective of the proposed rule.
A description of the existing policies and new policies included in the proposed rule and an analysis of policy alternatives.
The statutory authority for the proposed rule.
An estimate of the amount of time agency employees will spend developing the proposed rule and of other resources needed to develop the rule.
A description of all of the entities that will be affected by the proposed rule.
A summary and preliminary comparison of any existing or proposed federal regulation that addresses or is intended to address the activities to be regulated by the proposed rule.
The Governor must approve the scope statement in writing prior to submittal of the statement to LRB for publication in the Register. [s. 227.135 (2)
Upon approval by the Governor, the agency must send the scope statement to LRB for publication in the Register and, on the same day, send a copy to the Secretary of DOA. The agency should include the date of the Governor's approval in the electronic document submitted to LRB that contains the scope statement.
NOTE: 2011 Executive Order #50 states that an agency must file the scope statement for publication by LRB within 30 calendar days of the Governor's approval if it intends to proceed with rule-making or the Governor will deem the scope statement withdrawn.
Upon receipt by LRB of a scope statement for publication in the Register, LRB will assign a discrete identifying number to the scope statement in the following format: SS 001-11
, which will be published in the Register along with the scope statement and the date of the Governor's approval.
No sooner than 10 days after publication of the scope statement in the Register, the statement may be presented for approval to the individual or body with policy-making powers for the agency and published in the Register. [s. 227.135 (2)
NOTE: The Register is published on the 14th day and the last day of each month. See s. 2.06, Manual, for the Register deadline schedule for 2011 to 2014.
While the individual or body with policy-making powers may not approve a statement until at least 10 days after publication, the statutes contain no limit on when, following the Governor's approval, the scope statement must be published, no date by which a published scope statement must be approved by the individual or body with policy-making powers, and no time within which a proposed rule contemplated in the statement must be submitted to the Rules Clearinghouse. However, see the discussion of revised scope statements in sub. (6), below.
If an agency changes the scope of a proposed rule in any meaningful or measurable way at any time after a scope statement is approved by the Governor and the individual or body with policy-making powers, the agency must prepare and obtain approval of a revised scope statement in the same manner as the original statement was prepared and approved. The circumstances necessitating a revised scope statement include where the agency has changed the scope of the rule to include any activity, business, material, or product that is not specifically included in the original scope of the rule. [s. 227.135 (4)
, Stats.] It would appear that, if the change in scope of the proposed rule occurs after the Governor's approval of a scope statement and before approval by the individual or body with policy-making powers for the agency, a revised scope statement must be prepared and approved as provided in s. 227.135 (4)
A revised scope statement must contain all of the elements required for an original scope statement as set forth in sub. (2), above. The statement should be labeled a "Revised Statement of Scope" and contain a preface identifying the original statement that is being modified, as follows (as applicable):
This revised statement of scope modifies, SS ____, which was approved by the Governor on ______ (date), published in Register ____ (Register Number), on ______ (Register publication date), and approved by ________ (name of policy making body or individual for the agency as required by s. 227.135 (2)
, Stats.) on ______ (date), relating to __________________ (state the subject as it appears in the original statement.)
As with the original scope statement, the modified statement is submitted to the Governor for approval as provided in sub. (3), above, submitted to LRB for publication as provided in sub. (4), above, and submitted for approval by the individual or body with policy-making powers for the agency as provided in sub. (5), above. As with the original statement, no state employee may perform any activity in connection with the drafting of the rule, except for the preparation of the revised scope statement, until the scope statement is approved by the Governor and the individual or body with policy-making powers for the agency.
2.012.01 Submittal to Legislative Council staff. 2.01(1)(1)
Except for emergency rules, a copy of each proposed rule must be submitted to the Rules Clearinghouse as provided in s. 227.15
, Stats. [See s. 3.01
, Manual, for the requirements for submitting proposed rules to the Rules Clearinghouse for review.]
NOTE: On the same day that an agency submits to the Rules Clearinghouse a proposed rule that may have an economic impact on small businesses, the agency must submit the proposed rule and other materials to the SBRRB, as provided in s. 227.14 (2g), Stats. See 2011 Wisconsin Act 46 for changes to the rules promulgation process relating to the SBRRB.
The agency must submit to LRB for publication in the Register, and to the Secretary of DOA, a notice, approved by the person or body with policy-making authority over the subject matter of the proposed rule, that the agency has submitted a proposed rule to the Rules Clearinghouse. [See s. 227.14 (4m)
, Stats.] The notice must include all of the following:
The date the proposed rule was submitted to the Rules Clearinghouse.
The subject matter of the proposed rule.
Whether a public hearing is required. Include the date of the hearing if it is known. If a hearing is not required, note the applicable exemption under s. 227.16 (2)
, Stats., in the notice and proceed as provided in s. 2.05
The organizational unit that is responsible for preparing the rule.
The name and contact information for a contact person, if desired by the agency.
In addition to the above:
For rules submitted to Rules Clearinghouse for which the rule's scope statement was submitted for publication in the Register on or after June 8, 2011, and is subject to 2011 Wisconsin Act 21
, insert the following:
The scope statement for this rule, SS ____, was approved by the Governor on ______ (date), published in Register No. ___ (Register Number), on ______ (Register publication date), and approved by ________ (name of policy making body or individual for the agency as required by s. 227.135 (2)
, Stats.) on ______ (date).
EXAMPLE: The scope statement for this rule, SS 001-11, was approved by the Governor on July 20, 2011, published in Register No. 668, on August 14, 2011, and approved by the Natural Resources Board on August 28, 2011.
For rules submitted to the Rules Clearinghouse for which the rule's scope statement was submitted for publication in the Register before June 8, 2011, and is not subject to 2011 Wisconsin Act 21
, insert the following:
This rule is not subject to s. 227.135 (2)
, Stats., as affected by 2011 Wis. Act 21
. The scope statement for this rule,
published in Register No. ____ (Register Number), on ______ (Register publication date), was sent to LRB prior to June 8, 2011 (the effective date of 2011 Wisconsin Act 21
2.022.02 Notice and public hearings. 2.02(1)(1) General rule
. Except as provided in s. 227.16
, Stats., all rule-making by an agency must be preceded by notice and public hearing as required under ss. 227.17
, Stats., or any other specific statute.
. Unless another statute specifically requires the agency to hold a hearing prior to promulgating the proposed rule, s. 227.16
, Stats., provides that public hearing and notice for a proposed rule is not required if any of the following apply:
The proposed rule brings an existing rule into conformity with a statute that has been changed or enacted or with a controlling judicial decision. [s. 227.16 (2) (b)
The proposed rule is adopted as an emergency rule. Notice and public hearing are required after emergency rule adoption. [s. 227.16 (2) (c)
, Stats., and s. 2.12
The proposed rule consists of one or more forms that impose a requirement that meets the definition of a rule. [s. 227.23
NOTE: Except in the case of an emergency rule, if one of these exceptions is utilized, the agency should do all of the following:
1. Note in its notice of submittal to the Rules Clearinghouse [s. 2.01
, Manual] and its proposed rule-making order that the rules are being adopted under the procedure in s. 227.16 (2) (b)
, or (e)
2. Complete all other procedural requirements for rule-making as with any other rule.
2.032.03 Informal or informational hearings.
An agency may hold hearings to solicit public comment on a general subject area that may result in future rule-making. Hearings of this nature do not satisfy the requirement of s. 227.16 (1)
, Stats. Notices for informal or informational hearings may be published in the Register. [s. 227.16 (6)
NOTE: Agencies are encouraged to publish notices of this type in the Register. The Register is sent to subscribers of an agency's code as part of their upkeep subscription.