Source: https://www.acus.gov/recommendation/plain-language-regulatory-drafting
Timestamp: 2018-05-25 10:50:16
Document Index: 560875859

Matched Legal Cases: ['§ 301', '§ 2', '§ 301', '§ 301', '§ 1', '§ 301', '§ 301', '§ 301', '§ 301']

Plain Language in Regulatory Drafting | Administrative Conference of the United States
For decades, agencies have worked to make regulatory requirements more comprehensible to regulatory stakeholders and the public at large, including by using “plain language” or “plain writing.”[1] Clearly drafting and explaining regulations facilitates the core administrative law goals of public participation, efficient compliance, judicial review, and the protection of rights. Numerous statutory and executive requirements direct agencies to draft rules and guidance plainly.
The Plain Writing Act of 2010 (PWA)[2] and Executive Order 13,563[3] require agencies to use plain language in various public-facing documents.[4] Plain writing, as defined by the PWA, is “writing that is clear, concise, well-organized, and follows other best practices appropriate to the subject or field and intended audience.”[5] The Plain Language Action and Information Network (PLAIN)[6] further explains that “[w]ritten material is in plain language if your audience can find what they need, understand what they find, and use what they find to meet their needs.”[7] As such, writing in plain language does not mean abandoning complexity or nuance, nor does it mean omitting technical terms.[8] For the purposes of this recommendation, writing that is “plain” conveys the intended meaning in a way that the intended audience can easily understand.
The PWA requires agencies to use plain language in all “covered documents,” which are: documents necessary “for obtaining any Federal Government benefit or service or filing taxes;” documents that “provide information about any Federal Government benefit or service,” such as pamphlets; and documents that provide recommendations on “how to comply with a requirement the Federal Government administers or enforces,” such as guidance documents.[9] Although the PWA does not cover regulations, Executive Order 13,563 requires them to be “accessible, consistent, written in plain language, and easy to understand.”[10] The Office of Management and Budget (OMB) interprets the PWA to apply to “rulemaking preambles,”[11] because a “regulation,” as exempted by the PWA, is a “rule[] carrying the force of law,”[12] but a preamble explains a rule’s basis and purpose[13] and is not binding.
The PWA further directs agencies to: designate “senior officials to oversee . . . agency implementation”; communicate PWA requirements to employees and train them in plain writing; maintain a “plain writing section of the agency’s website”; and issue annual compliance reports.[14] Finally, the Act precludes judicial review of agencies’ compliance with its terms.[15]
The PWA formalized and expanded a decades-long internal administrative effort to promote plain language in rules and guidance documents.[16] For instance, many agencies have provided trainings and other resources on plain writing since the 1970s[17]—a practice codified by the Act.[18] Some agencies make their trainings and related resources publicly available. Trainings may cover the PWA’s requirements and plain writing techniques, including the use of organization and formatting to guide readers through a document; the use of bullet points, lists, and other visual aids; and the use of simple rather than complex vocabulary, if doing so will not alter the intended meaning. Additionally, trainings may focus on meeting the needs of the agency’s various audiences, such as regulated small businesses.
Agencies must also designate officials to oversee compliance with the Act’s requirements, such as by delivering trainings.[19] Agencies may designate plain language officials in a number of different kinds of offices, such as media, executive correspondence, or public outreach. These officials can provide a valuable coordination function when the agency is communicating with the public.[20] In some agencies, plain language officials may be well positioned to support agency staff during—not just after—the drafting process.
Rule and guidance drafting processes may directly incorporate other efforts to promote plain writing. Agencies’ internal drafting manuals, which provide style and formatting guidelines, often encompass plain writing techniques. Agencies also have guidelines specifying how offices within the agency should coordinate when drafting rules or guidance. These practices have important implications for how agencies implement plain writing, though divergent approaches may be equally successful. For example, one agency’s practice is to assign each office involved in drafting the responsibility for reviewing documents based on its expertise; this can include reviewing documents for plain language, in addition to reviewing them for technical sufficiency. In this agency, edits or comments on a document marked as within an office’s assigned responsibilities must be either accepted or resolved in consultation with that office. Thus, a regulatory attorney may flag text that could be interpreted in multiple ways as an issue of both plainness and legal ambiguity. Similarly, program staff, economists, and engineers may be responsible for ensuring that text involving their areas of expertise is not only accurate, but plain to relevant audiences. Other agencies may not assign such formal responsibilities to particular offices; rather, the program office originating a rule or guidance may be in charge of reviewing the whole of the document and working with other participating offices to ensure text is plainly written.
Each of the above practices structures how an agency drafts rules and guidance, both of which may inform an agency’s audiences of regulatory requirements or benefits.[21] For instance, a final rule may target an audience of legal professionals and industry experts who expect to see certain terms of art, whereas a guidance document may walk a small business through the process of filing financial forms. Though it is appropriate to tailor guidance to a specialist audience, sometimes tailoring documents to particular specialist audiences runs the risk of obscuring or glossing over important information for other audiences. In certain circumstances, some commentators have raised concerns that guidance may omit salient information, leaving non-specialist parties at a disadvantage compared to experts.[22] Crafting guidance carefully can ensure it is fully explanatory while remaining comprehensible—though this may come at the cost of brevity.[23]
Finally, though agencies have worked to implement plain writing for rules and guidance both prior to and since the PWA’s enactment, challenges remain. Inter- and intra-agency coordination in drafting is inherently difficult. Additionally, departing from language that external stakeholders expect to see, or that has required significant negotiation, may be costly. And, due to ever-present resource constraints, agencies must prioritize investing in plain writing when audiences will most benefit.
This Recommendation identifies tools and techniques agencies have successfully used to facilitate plain language drafting in rulemaking and guidance documents. Additionally, this recommendation proposes best practices for agencies’ internal drafting processes, makes suggestions to maximize the value of trainings and related resources, and notes special considerations for drafting rulemaking preambles and guidance documents.
3. To improve the accessibility of rules and guidance, agency drafting staff should consider soliciting guidance or input from senior officials responsible for overseeing an agency’s compliance with the Plain Writing Act (PWA).
Plain Drafting in Rulemaking Document
c. Examples of how the agency’s rules, guidance, or other documents have implemented these techniques.
i. The preambles to proposed rules should include a summary of the rule that non-specialists and the general public can understand. Such summaries may be those already required by the Administrative Committee of the Federal Register or applicable executive guidance. Other subparts of the preamble should include language that is plain for specialist audiences if it is not practicable to describe the rule’s purpose, reasoning, or requirements without legal or technical language, although these subparts may benefit from brief introductory summaries directed at non-specialists.
7. Agencies should consider including in each notice of proposed rulemaking a request for comments on whether the regulation’s purposes and requirements are clear and understandable. Agencies should also consider specifying topics or questions on which the agency would most benefit from feedback from non-specialist stakeholders and the general public.
[1] These terms carry the same meaning and are used interchangeably here.
[2] Pub. L. No. 111-274, 124 Stat. 2861 (2010) (codified at 5 U.S.C. § 301 note).
[3] Exec. Order No. 13,563, 76 Fed. Reg. 3821 (Jan. 18, 2011).
[4] Executive guidance issued prior to the PWA’s enactment also directs agencies to use plain language. Executive Order 12,866 provides that “[e]ach agency shall draft its regulations to be simple and easy to understand.” Exec. Order No. 12,866 § 2(b), 58 Fed. Reg. 51,735, 51,737 (Oct. 4, 1993). President Clinton’s 1998 Plain Language Memorandum further requires agencies to “use plain language in all new documents, other than regulations, that explain how to obtain a benefit or service, or how to comply with a requirement [the agency] administer[s] or enforce[s],” as well as “all proposed and final rulemaking documents published in the Federal Register.” Memorandum on Plain Language in Government Writing, 63 Fed. Reg. 31,885 (June 10, 1998).
[5] 5 U.S.C. § 301 note sec. 3(3).
[6] PLAIN grew out of early, informal agency efforts to share plain writing tools and techniques, and has served as a hub for such resources since its establishment during the Clinton Administration. About Us, Plain Language Action & Information Network, https://plainlanguage.gov/about/.
[7] What is Plain Language?, Plain Language Action & Information Network, https://plainlanguage.gov/about/definitions/.
[8] For guidance on writing plainly without compromising nuance or avoiding important technical terms, consult the Federal Plain Language Guidelines, a resource compiled by PLAIN, which both the PWA and executive guidance direct agencies to use. Plain Language Action & Information Network, Federal Plain Language Guidelines (Rev. ed. May 2011), http://www.plainlanguage.gov/guidelines/.
[9] 5 U.S.C. § 301 note sec. 3(2)(A).
[10] Exec. Order No. 13,563 § 1(a), 76 Fed. Reg. 3821, 3821 (Jan. 18, 2011).
[11] Office of Mgmt. & Budget, Exec. Office of the President, OMB Mem. M-11-15, Final Guidance on Implementing the Plain Writing Act of 2010 5 (2011).
[12] See United States v. Mead Corp., 533 U.S. 218, 226–27 (2001).
[14] Id. § 301 note sec. 4(a).
[15] Id. § 301 note sec. 6.
[16] See Cynthia Farina, Mary J. Newhart, & Cheryl Blake, The Problem with Words: Plain Language and Public Participation in Rulemaking, 83 Geo. Wash. L. Rev. 1358, 1367–79 (2015).
[17] Blake Emerson & Cheryl Blake, Plain Language in Regulatory Drafting 33 (Dec. 8, 2017) (report to the Admin. Conf. of the U.S.), https://www.acus.gov/report/plain-language-regulatory-drafting-final-report.
[18] 5 U.S.C § 301 note secs. 4(a)(1)(A), 4(a)(1)(C).
[19] Id. § 301 note sec. 4(a).
[20] Emerson & Blake, supra note 17, at 32–33.
[21] Some envision rulemaking and guidance documents as situated along a “continuum” ranging from more “complicated” documents like the rule itself to simpler documents that digest the material for non-specialist audiences. Complicated documents can be written plainly, but may require greater resource investment.
[22] Joshua D. Blank & Leigh Osofsky, Simplexity: Plain Language and the Tax Law, 66 Emory L. J. 189, 193 (2017).
[23] For a closer examination of guidance practices, see Nicholas R. Parrillo, Federal Agency Guidance: An Institutional Perspective (Dec. 1, 2017) (report to the Admin. Conf. of the U.S.), https://www.acus.gov/report/agency-guidance-final-report.