Montana Code 2-4-305. Requisites for validity — authority and statement of reasons
2-4-305. Requisites for validity — authority and statement of reasons. (1) (a) The agency shall fully consider written and oral submissions respecting the proposed rule, including comments submitted by the primary sponsor of the legislation prior to the drafting of the substantive content and wording of a proposed rule that initially implements legislation.
Terms Used In Montana Code 2-4-305
- Amendment: A proposal to alter the text of a pending bill or other measure by striking out some of it, by inserting new language, or both. Before an amendment becomes part of the measure, thelegislature must agree to it.
- Person: includes a corporation or other entity as well as a natural person. See Montana Code 1-1-201
- Presiding officer: A majority-party Senator who presides over the Senate and is charged with maintaining order and decorum, recognizing Members to speak, and interpreting the Senate's rules, practices and precedents.
- State: when applied to the different parts of the United States, includes the District of Columbia and the territories. See Montana Code 1-1-201
- Statute: A law passed by a legislature.
- Testimony: Evidence presented orally by witnesses during trials or before grand juries.
- Writing: includes printing. See Montana Code 1-1-203
(b)(i) Upon adoption of a rule, an agency shall issue a concise statement of the principal reasons for and against its adoption, incorporating in the statement the reasons for overruling the considerations urged against its adoption. If substantial differences exist between the rule as proposed and as adopted and the differences have not been described or set forth in the adopted rule as that rule is published in the register, the differences must be described in the statement of reasons for and against agency action. When written or oral submissions have not been received, an agency may omit the statement of reasons.
(ii)If an adopted rule that initially implements legislation does not reflect the comments submitted by the primary sponsor, the agency shall provide a statement explaining why the sponsor’s comments were not incorporated into the adopted rule.
(2)Rules may not unnecessarily repeat statutory language. Whenever it is necessary to refer to statutory language in order to convey the meaning of a rule interpreting the language, the reference must clearly indicate the portion of the language that is statutory and the portion that is an amplification of the language.
(3)Each proposed and adopted rule must include a citation to the specific grant of rulemaking authority pursuant to which the rule or any part of the rule is adopted. In addition, each proposed and adopted rule must include a citation to the specific section or sections in the Montana Code Annotated that the rule purports to implement. A substantive rule may not be proposed or adopted unless:
(a)a statute granting the agency authority to adopt rules clearly and specifically lists the subject matter of the rule as a subject upon which the agency shall or may adopt rules; or
(b)the rule implements and relates to a subject matter or an agency function that is clearly and specifically included in a statute to which the grant of rulemaking authority extends.
(4)Each rule that is proposed and adopted by an agency and that implements a policy of a governing board or commission must include a citation to and description of the policy implemented. Each agency rule implementing a policy and the policy itself must be based on legal authority and otherwise comply with the requisites for validity of rules established by this chapter.
(5)To be effective, each substantive rule adopted must be within the scope of authority conferred and in accordance with standards prescribed by other provisions of law.
(6)Whenever by the express or implied terms of any statute a state agency has authority to adopt rules to implement, interpret, make specific, or otherwise carry out the provisions of the statute, an adoption, amendment, or repeal of a rule is not valid or effective unless it is:
(a)consistent and not in conflict with the statute; and
(b)reasonably necessary to effectuate the purpose of the statute. A statute mandating that the agency adopt rules establishes the necessity for rules but does not, standing alone, constitute reasonable necessity for a rule. The agency shall also address the reasonableness component of the reasonable necessity requirement by, as indicated in 2-4-302(1) and subsection (1) of this section, stating the principal reasons and the rationale for its intended action and for the particular approach that it takes in complying with the mandate to adopt rules. Subject to the provisions of subsection (8), reasonable necessity must be clearly and thoroughly demonstrated for each adoption, amendment, or repeal of a rule in the agency’s notice of proposed rulemaking and in the written and oral data, views, comments, or testimony submitted by the public or the agency and considered by the agency. A statement that merely explains what the rule provides is not a statement of the reasonable necessity for the rule.
(7)A rule is not valid unless notice of it is given and it is adopted in substantial compliance with 2-4-302, 2-4-303, or 2-4-306 and this section, unless notice of adoption of the rule is published within 6 months of the publishing of notice of the proposed rule, and unless the adoption is in compliance with the prohibitions of subsection (11). The measure of whether an agency has adopted a rule in substantial compliance with 2-4-302, 2-4-303, or 2-4-306 and this section is not whether the agency has provided notice of the proposed rule, standing alone, but rather must be based on an analysis of the agency’s substantial compliance with 2-4-302, 2-4-303, or 2-4-306 and this section. If an amended or supplemental notice of either proposed or final rulemaking, or both, is published concerning the same rule, the 6-month limit must be determined with reference to the latest notice in all cases.
(8)(a) An agency may use an amended proposal notice or the adoption notice to correct deficiencies in citations of authority for rules and in citations of sections implemented by rules.
(b)An agency may use an amended proposal notice but, except for clerical corrections, may not use the adoption notice to correct deficiencies in a statement of reasonable necessity.
(c)If an agency uses an amended proposal notice to amend a statement of reasonable necessity for reasons other than for corrections in citations of authority, in citations of sections being implemented, or of a clerical nature, the agency shall allow additional time for oral or written comments from the same interested persons who were notified of the original proposal notice, including from a primary sponsor, if primary sponsor notification was required under 2-4-302, and from any other person who offered comments or appeared at a hearing already held on the proposed rule.
(9)Subject to 2-4-112, if a majority of the members of the appropriate administrative rule review committee notify the committee presiding officer that those members object to all or a portion of a notice of proposed rulemaking, the committee shall notify the agency in writing that the committee objects to all or a portion of the proposal notice and will address the objections at the next committee meeting. Following notice by the committee to the agency, all or a portion of the proposal notice that the committee objects to may not be adopted until publication of the last issue of the register that is published before expiration of the 6-month period during which the adoption notice must be published, unless prior to that time, the committee meets and does not make the same objection. A copy of the committee’s notification to the agency must be included in the committee’s records.
(10)This section applies to the department of labor and industry adopting a rule relating to a commercial drug formulary as provided in 39-71-704. This section does not apply to the automatic updating of department of labor and industry rules relating to commercial drug formularies as provided in 39-71-704.
(11)(a) In the year preceding the year in which the legislature meets in regular session, an agency may not adopt a rule between October 1 through the end of the year.
(b)This subsection (11) does not apply to:
(i)an emergency rule adopted under 2-4-303;
(ii)subject to subsection (11)(c)(i), a rule adopted for implementation of a program or policy if the unavailability of information, guidance, or notice precluded adoption of the rule before October 1; or
(iii)subject to subsection (11)(c)(ii), a rule adopted by providing the proposal notice and statement of reasoning with an opportunity to object to the appropriate administrative rule review committee.
(c)(i) A rule may only be exempted under subsection (11)(b)(ii) if the notice required under 2-4-302(1)(a) provides a statement explaining why the unavailability of information, guidance, or notice precluded adoption of the rule before October 1.
(ii)A rule may be exempted under subsection (11)(b)(iii) only if the agency provides a copy of the proposal notice and an explanation of the reason why the rule must be adopted before the end of the year by electronic mail to each member of the committee and the committee staff. If the committee does not object to the proposal within 10 business days after the electronic mail of the proposal and explanation has been sent to the committee, the agency may proceed with adoption of the proposed rule. If, during the 10-day review period, a majority of the members notify the committee presiding officer that those members object to the proposed rulemaking, the presiding officer shall notify the agency by electronic mail that the committee objects. Following notice of the objection, a rule may not be adopted before the end of the year.