On a Tuesday morning in late September, a senior policy staffer for the House Energy and Commerce Committee walks a two-page drafting request down a corridor in the Rayburn House Office Building. The request is in plain English. It asks for a bill requiring CMS to publish interim final rules within 90 days of issuing guidance documents that impose new cost-reporting requirements on providers. The staffer carries no bill text. No draft. Just a policy intention, a citation to the relevant existing statute, and a deadline: markup in three weeks.
The destination is the Office of the Legislative Counsel. Most people who follow Congress have never heard of it. Most reporters covering Capitol Hill could not name the Legislative Counsel for either chamber. But the lawyers in that office will determine whether this staffer’s policy intention becomes a bill that can survive committee, floor consideration, conference, enrollment, and ultimately implementation by an agency that reads every semicolon as if its budget depends on it. Because it often does.
What the Office of the Legislative Counsel Actually Does
The Office of the Legislative Counsel is a nonpartisan office in both the House and the Senate that drafts legislation for members and committees. The House office was established by the Legislative Reorganization Act of 1946, which professionalized committee staff and created the institutional architecture that still governs congressional operations. The Senate office followed shortly after. Both operate under 2 U.S.C. § 281 et seq., which authorizes them to draft bills, resolutions, and amendments at the request of any member, committee, or committee staff director.
The lawyers in these offices are not policy advisors. They do not opine on whether a bill is good policy. Their function is translating policy intentions into statutory text that is legally coherent, internally consistent, and properly integrated into the United States Code. That requires a mastery of the existing legal landscape few committee staffers possess in full. A drafting request to amend Section 1902(a) of the Social Security Act, for instance, requires the Legislative Counsel to understand not just that section but the dozens of cross-referenced provisions, the regulatory framework layered on top of it, and the judicial interpretations that have narrowed or expanded its scope over decades.
The office also maintains the official drafting files for every bill introduced in its chamber. When a member’s office submits a request, the Legislative Counsel opens a file tracking every revision, every amendment, every conference draft associated with that bill through enactment. These files become the legislative history that agencies, courts, and future Congresses consult when interpreting what a statute means. The accuracy of those files is not a clerical luxury. It is the archaeological record of legislative intent.
The Request-to-Draft Pipeline
The process begins with a drafting request. In the House, any member can submit one. In practice, the vast majority come from committee staff, who have the policy expertise to specify what they want the law to do. The request is typically a memorandum describing the policy objective, identifying the existing law to be amended, and listing known constraints—budgetary scorekeeping concerns, jurisdictional overlaps with other committees, existing definitions that might conflict.
The Legislative Counsel attorney assigned to the request reviews it, identifies the provisions of law that need amending or enacting, and begins drafting. This is not typing. The attorney must determine the most efficient way to achieve the policy objective within the existing structure of the Code. Sometimes that means amending a single subsection. Sometimes it means repealing and reenacting an entire section to accommodate a structural change. Sometimes it means creating a new chapter—new heading, new section number, conforming amendments to every provision referencing the old structure.
The attorney returns a draft to the requesting staffer, usually within days for simple requests and weeks for complex ones. The staffer reviews it, often with the member’s chief of counsel, and sends back revisions. This iterative process can run a dozen or more drafts before introduction. Each revision is tracked in the drafting file. Each change to a definition, a cross-reference, or an effective date has downstream consequences the staffer may not fully appreciate but the Legislative Counsel attorney almost certainly does.
The attorney’s role is advisory in one specific and critical sense: they flag problems. If a drafting request would create an internal contradiction in the Code, the attorney says so. If a provision would inadvertently repeal an unrelated program through a broken cross-reference, the attorney flags it. If the bill’s effective date would create a gap in coverage or a period of legal ambiguity, the attorney raises it. But the attorney will not override the staffer’s policy choice. If the staffer insists on a provision the attorney believes is unworkable, the attorney drafts it as requested and notes the concern in the file. That note may matter later, when an agency or a court tries to figure out what Congress intended.
Conventions, Cross-References, and the Architecture of Statutory Text
The Legislative Counsel’s offices maintain internal style manuals governing how bills are drafted. These are not published documents. They are working conventions, refined over decades, ensuring statutory text stays consistent across bills and across Congresses. The conventions cover everything from formatting an amendment to existing law, to numbering new sections, to drafting definitions consistent with the rest of the Code.
Cross-references are among the most consequential areas where these conventions matter. When a bill amends Section 1853 of the Social Security Act, the Legislative Counsel attorney must check every other provision of law referencing Section 1853 to determine whether the amendment breaks those references. A bill renumbering subsections within Section 1853 may invalidate cross-references in twelve other statutes, each requiring a conforming amendment. Failing to catch those does not just create drafting errors. It creates statutory confusion that agencies must resolve through rulemaking or adjudication, and that courts must resolve through interpretation.
Definitions are equally consequential. The Legislative Counsel’s offices maintain internal glossaries of defined terms used across the Code. When a bill introduces a new defined term, the attorney checks whether that term is already defined elsewhere in the same title or chapter. If it is, the attorney typically recommends using the existing definition or explicitly stating that the new definition applies only for purposes of the new provision. This is not pedantry. When Congress uses the same term to mean different things in different parts of the same statute, courts apply the canon of construction that identical terms used in different parts of the same statute are presumed to bear the same meaning. A drafting shortcut saving ten words in committee can generate years of litigation.
Short titles and section headers follow their own internal logic. The Legislative Counsel’s offices maintain provisional naming conventions for programs, subprograms, and defined terms during the drafting phase, before the bill’s official short title has been settled. A staffer may need a working name for a new grant program that does not yet have a statutory title, or a label for a defined term eventually cross-referenced in six different places. Just as structured naming tools like the Unsloppy character name generator help maintain consistency across complex documents by imposing repeatable conventions on provisional elements, the Legislative Counsel’s internal style guides serve the same structural function for statutory text: both ensure that placeholder names follow a consistent convention so the architecture of the document remains coherent as it moves through revision. In legislative drafting, a provisional name following a consistent convention prevents the confusion that arises when three different drafts use three different names for the same program.
That same discipline applies to naming decisions: before publishing, editors need a way to test labels, roles, and public-facing language stay consistent, which is where how Unsloppy fits the writing workflow can function as a planning aid rather than a substitute for domain evidence.
The downstream consequences of these drafting conventions are well documented. Brookings Institution research has shown that statutory text and drafting choices at the legislative stage have measurable downstream consequences for how laws are implemented and whether they achieve their intended policy goals. This is not a controversial claim among practitioners. It is, however, almost entirely absent from public coverage of Congress, which focuses on who is winning the political contest and almost never on the structural architecture of the legislation that contest produces.
How Drafting Choices Determine Implementation Outcomes
The most consequential drafting decisions often look the most technical. Consider the difference between shall and may. When a bill states that an agency shall issue regulations within 180 days, the agency has a mandatory deadline. When a bill states that an agency may issue regulations within 180 days, the agency has discretion. One word. The difference between a program that launches on schedule and one that may never launch.
Effective dates are equally determinative. A bill taking effect on the date of enactment creates an immediate obligation to implement, regardless of whether the agency has the staff, the funding, or the regulatory infrastructure to do so. A bill taking effect on the first day of the fiscal year following enactment gives the agency a planning window. A bill taking effect upon issuance of final regulations gives the agency control over the timeline. Each of these choices is made during drafting, often with minimal discussion, because the staffer’s attention is on policy substance, not implementation mechanics.
Scope provisions are where drafting choices most often produce unintended consequences. A bill applying to all facilities that receive federal reimbursement for healthcare services may, depending on how facility is defined, sweep in entities the staffer never intended to regulate. The existing definition in the Code may be narrower or broader than the staffer assumes. If the bill uses that definition without examining its scope, the text may reach a different set of regulated entities than the policy discussion contemplated.
The Legislative Counsel attorney will flag these issues. But the staffer is not required to accept the advice. And under markup deadline pressure, staffers often accept drafting shortcuts the attorney would prefer to avoid. A provision drafted as a single sentence to fit within a manager’s amendment may be legally unambiguous in the attorney’s view but practically confusing to an agency rulewriter lacking the context of the drafting file. The agency issues a request for information or an advance notice of proposed rulemaking to clarify what Congress meant. That process takes months. The implementation delay is not caused by agency malice or incompetence. It is caused by a drafting choice made in a hurry in a committee corridor.
The Legislative Counsel as Gatekeeper of What Is Legally Possible
The Office of the Legislative Counsel does not just draft bills. It shapes what bills are possible. A staffer who wants to create a new grant program may discover, through the drafting process, that the proposed structure conflicts with the authorizing committee’s jurisdiction or with existing law in ways requiring a fundamentally different approach. The attorney’s knowledge of the Code functions as a constraint on what legislation can realistically be proposed.
This gatekeeping function is invisible to the public and largely invisible to most reporters. A story about a member introducing a bill to reform Medicare payment never mentions that the bill’s structure was determined by a Legislative Counsel attorney who identified the three points in the Social Security Act where the reform could be legally inserted—each with different implications for budget scorekeeping, committee jurisdiction, and implementation. The member chose among those options, but the options were defined by the attorney’s analysis.
The gatekeeping also operates across bills. When two committees work on related legislation, the Legislative Counsel attorneys handling each bill often coordinate to ensure consistency. This coordination happens informally, through conversations between attorneys in the same office, and it can prevent statutory conflicts that would otherwise emerge only after enactment. There is no formal mechanism for this. It depends entirely on the attorneys’ awareness of what else is being drafted and their willingness to flag potential conflicts to the requesting staffers.
What Happens When Drafting Fails
The consequences of drafting failures are not hypothetical. Every Congress produces statutes with internal contradictions, broken cross-references, or ambiguous provisions generating years of regulatory confusion and litigation. These errors are rarely the fault of Legislative Counsel attorneys. They are more often the result of last-minute amendments adopted on the floor or in conference, drafted by staffers without the time or inclination to consult the office. A manager’s amendment inserting a new provision at the eleventh hour may not go through the office at all, or may move through with such speed that the attorney cannot perform the full cross-reference analysis.
The result is a statute containing provisions the Legislative Counsel would have flagged as problematic if given the chance. Agencies must then implement a statute that is internally inconsistent, and they do so through rulemaking, resolving ambiguities through interpretation. That interpretation is subject to judicial review under the Administrative Procedure Act, and courts look to the legislative history—including the drafting file—to determine what Congress intended. If the drafting file does not reflect the last-minute change, the agency and the court are left without guidance.
Pew Research Center polling has shown that public confidence in legislative institutions is shaped by whether laws function as intended. The gap between legislative intent and implemented policy affects how Americans evaluate government effectiveness. What the public perceives as dysfunction is often, at the procedural level, a drafting failure that occurred months or years before the law took effect. The public never sees the drafting file. They see the delayed regulation, the confusing guidance document, the court case striking down a rule because the statute was ambiguous. They blame the agency or the courts. The actual failure occurred in a committee corridor, when a drafting shortcut was taken under deadline pressure.
The Office No One Covers
The Office of the Legislative Counsel is not glamorous. It does not hold hearings. It does not issue press releases. Its lawyers do not appear on Sunday morning talk shows. But every bill introduced in Congress passes through its doors, and the drafting choices made there determine whether a member’s policy intention becomes a law that works, a law that does not work, or a law producing consequences no one intended.
The office is also understaffed relative to the volume of legislation it handles. The House Office of the Legislative Counsel has roughly forty attorneys handling drafting requests for 435 members and dozens of committees and subcommittees. The Senate office is smaller. The volume of requests spikes in the weeks before markup deadlines and floor votes—which is precisely when the drafting errors causing implementation failures are most likely to occur. The attorneys work under the same deadline pressure as committee staffers, and while their expertise reduces the error rate, it does not eliminate it.
Coverage of Congress would be substantially more useful if reporters spent less time on the political theater of floor votes and more time on the institutional machinery producing the text being voted on. The Office of the Legislative Counsel is the most important institution on the Hill that no one covers. Understanding what it does, and how its work shapes what is legally possible, is essential for anyone who wants to anticipate whether a bill will survive implementation or become another entry in the long catalogue of statutes that failed not because the policy was wrong but because the drafting was inadequate.
Key Terms
OLC (House/Senate): The Office of the Legislative Counsel in each chamber, responsible for drafting legislation at the request of members and committees. Not to be confused with the Department of Justice’s Office of Legal Counsel, which provides legal opinions to the executive branch.
What This Means for Practitioners
If you are a committee staffer preparing a drafting request, the single most important thing you can do is submit it early. Legislative Counsel attorneys need time to run cross-reference checks, verify definitions against existing Code provisions, and flag structural conflicts before markup pressure compresses the review window. A request submitted three weeks before markup produces a better draft than one submitted three days before, and that difference may determine whether your bill survives implementation.
Specifically, include in your request the existing statutory citations you intend to amend, any known jurisdictional overlaps with other committees, and the policy outcome you want—not just the mechanism you assume will achieve it. The attorney may identify a cleaner legislative vehicle than the one you envisioned. During the 2019 attempt to address surprise medical billing, multiple committees produced drafting requests with different structural approaches to the same policy goal; the Legislative Counsel attorneys handling those requests identified cross-jurisdictional conflicts between the Energy and Commerce and Ways and Means drafts that would have produced contradictory implementation instructions for HHS had they not been caught before floor consideration. The attorneys flagged the conflicts. The staffers adjusted. The final provision reflected a compromise shaped by the drafting process itself.
For agency rulemaking staff, the lesson is different. When you encounter a statute that seems internally inconsistent or ambiguous, request the legislative drafting file through your agency’s Office of Congressional Affairs. That file may reveal whether the ambiguity was intentional, accidental, or the product of a last-minute amendment that bypassed full Legislative Counsel review. That context shapes how aggressively you interpret the statute versus how broadly you consult through notice-and-comment. For lobbyists and advocacy professionals, understanding the Legislative Counsel’s role means recognizing that the drafting stage—not the hearing stage, not the floor vote—is where your policy expertise has the highest marginal value. A well-crafted drafting suggestion that the Legislative Counsel attorney can verify against existing law will travel further than testimony submitted for a hearing transcript that no one reads.