How Citizen Drafters Can Make a Bill Legally Credible Without a Lawyer

Legal credibility for a citizen-drafted bill has nothing to do with holding a law degree. It comes from following the same structural conventions, precision habits, and procedural logic that professional legislative drafters already use, and every one of those things can be learned.

Why citizens are structurally distant from the drafting stage

Every bill starts with a citizen's idea, but the actual writing happens somewhere citizens rarely reach. Oregon's legislative process guide lays out the standard path: a citizen brings an idea to a representative, the representative asks the Legislative Counsel's office to draft it into legal language, and the citizen's direct involvement ends right there, before a single clause gets written. That handoff feels like a rule. It's a habit, built up over decades, not a requirement written into any law that bars a citizen from doing the drafting work.

Sandra Strokoff, formerly of the House Office of the Legislative Counsel, put her finger on something telling about this arrangement. Elected members get called the "authors" of bills on the House floor, carefully crafting language they never actually wrote. The real drafting, Strokoff pointed out, is done by attorneys like her, functioning as ghost writers for legislation that carries someone else's name. If the people we call "authors" are mostly borrowing credit for language written by professional staff, authorship in the legislative process is already a more distributed, more negotiable thing than the ceremony around it suggests.

That matters for citizen drafters: the gap between "having an idea" and "producing a credible bill" is a convention, maintained by habit and reinforced by the fact that few citizens know what professional drafters actually do differently, not a wall built out of legal necessity. Non-lawyers draft legislation regularly. Policy advocates, agency staff, and organized citizen groups originate bills that later get refined by legal drafters, not replaced by them. The refinement stage exists to sharpen language, not to supply ideas the citizen couldn't have had. Understanding what that refinement actually consists of, the structural habits and precision rules behind it, is what closes the distance.

Why citizen bills fail before anyone reads their substance

Most citizen bills don't die because the policy idea is bad. They die because the document fails on form before a single legislator or staffer engages with what it's trying to accomplish. That's a learnable problem, not a sign that drafting requires some kind of legal instinct citizens lack.

A few failure patterns appear repeatedly in bills written outside professional drafting offices. One is the instinct to make language sound "legal," which usually produces jargon-heavy sentences that are harder to parse, not sharper in meaning. Clarity carries authority on its own. Dressing plain language up in borrowed legalese buries the point under jargon it doesn't need.

A second failure is inconsistent terminology. Define a term once, then describe the same concept with different words later in the bill, and the inconsistency becomes an opening. Courts read a shift in terminology as a signal that two different things were meant, even when the drafter intended one. A single term used two ways is often enough to create the kind of ambiguity a legal challenge can exploit.

A third failure comes from assuming subject-matter expertise is the same thing as drafting clarity. Knowing a policy problem in depth, sometimes better than anyone in the room, doesn't guarantee the bill communicates that problem unambiguously. The two skills are related but separate, and conflating them is one of the more common traps for a first-time citizen drafter.

A fourth failure is political rather than technical: softening language to hold a coalition together. Consensus language survives negotiation. It often doesn't survive a courtroom, because the vagueness that let five different stakeholders sign on is the same vagueness a lawyer can argue about later.

The stakes here aren't abstract. A 2026 guide on statutory language walks through a hypothetical built around the term "rural hospital," then anchors its real case study in a law built around "economically disadvantaged communities." The lesson from that case study: a vague definition can render an entire enacted law unenforceable after a court challenge, even after the bill passed both chambers and was signed. A program can clear every political hurdle in a legislature and still get enjoined because one definition was left too loose.

Anyone amending an existing statute rather than writing something new faces a more mechanical trap. Strike-and-insert language has to match the current statutory text exactly, word for word. One word off, and the amendment fails on a technicality that has nothing to do with the merits of the idea behind it.

The mandatory structure every credible bill contains

Every credible bill, regardless of subject matter, follows a structure that looks rigid from the outside but performs real legal work piece by piece. A citizen who includes each of these elements, in the right order, is sending a signal: this bill was built the way professional drafters build them.

The bill opens with a title and relating-to clause, typically beginning "AN ACT" followed by a description of the subject. That's not decoration. Many jurisdictions enforce single-subject rules, and a title that's vague or overly broad can invalidate the bill. A strong title names each major component of the bill specifically, so a court checking the text against the title has no room to find a mismatch.

Next comes the enacting clause, a jurisdiction-specific formula such as "BE IT ENACTED BY THE [Legislature] OF THE STATE OF [State]:" This has to appear exactly as prescribed. Paraphrasing it, modernizing the wording, or treating it as boilerplate to be tweaked counts as a technical defect, even if the substance of the bill is sound.

A purpose and findings section is optional in most jurisdictions but worth including. Its job is to give courts interpretive guidance later, when the operative language is ambiguous and a judge needs context for what the legislature intended. These statements should read as fact, not advocacy: "The Legislature finds that..." rather than "We believe..." A passage written as fact reads as something a court can rely on, while one written as advocacy reads as argument a court will set aside.

The definitions section comes early, often in Section 2 or Section 3 depending on the jurisdiction's drafting convention, so that every term is defined before it shows up in the operative text. Any term that isn't commonly understood, or that's being used in a specific technical sense, belongs here.

The operative provisions are the substance of the bill: what it creates, requires, authorizes, or prohibits. This is where the policy idea actually lives, and it needs to be organized logically enough that a reader can follow the bill's effect without cross-referencing five other sections to understand one sentence.

An effective date clause specifies when the law takes hold, whether that's upon passage, a set number of days afterward, a specific calendar date, or a phased rollout by section.

Finally, a severability clause protects the bill as a whole. If one section gets struck down as unconstitutional, severability language keeps the rest of the law standing rather than letting one bad section take down everything else. Any citizen drafter should include this as a matter of course.

A review stage deserves anticipation as well. In Maryland, it's long-standing practice, documented in Attorney General opinions and case law rather than spelled out in the Legislative Drafting Manual, that the Office of the Attorney General reviews every bill for constitutionality and legal sufficiency before the governor signs it. A citizen drafter who knows this kind of review is coming can write toward it from the start.

The language conventions that signal drafting competence to lawmakers and courts

Structure gets a bill taken seriously at a glance. Word choice determines what the bill requires once it's law. Statutory language carries specific conventions, and using the wrong word in the wrong place changes what the law requires, not just how it reads.

The sharpest distinction is between "shall," "may," and "must." "Shall" signals a mandatory obligation: it's the standard word for requirements in legislative drafting, and failure to comply with a "shall" provision can be challenged in court. "May" signals something permissive or discretionary. It grants authority without compelling its use, and courts generally won't force an agency to act on a "may" provision just because the authority exists. "Must" should be avoided in operative provisions. It feels natural in everyday English, but mixing it with "shall" in the same bill creates ambiguity about whether the two words were meant to carry different legal weight. "Will" belongs in findings or purpose sections, where it functions as a prediction, not in operative text, where it has no settled mandatory meaning.

The second distinction, smaller in appearance but just as consequential, is "and" versus "or." "And" requires every listed condition to be satisfied. "Or" requires only one of them. Mixing these up reverses the practical effect of a requirement: a provision meant to apply when three conditions are all present can end up applying when any single one is present, depending on which conjunction made it into the final text.

Consistency in terminology matters as much here as it did in the failure modes above. Every defined term should appear in exactly the same form everywhere it's used. A variation, even a small one, signals to a court that either a different meaning was intended or a mistake was made, and either reading creates the kind of ambiguity a bill is better off avoiding.

Operative provisions are written in present tense throughout. That's a drafting convention rather than a grammatical preference, and it holds across professionally drafted bills as a matter of course.

How citizen drafters who have successfully passed bills prepared

The work that makes a bill credible starts well before any text gets written. Understanding the current law a bill touches is the first real step in the process.

A drafter needs a working understanding of existing law on the subject before starting to write, and if the bill amends a statute, the strike-and-insert language has to match the current text precisely. The Connecticut General Assembly's guidance on this is direct: the most important part of good drafting is thinking the bill through, understanding not just the change being sought but how that change interacts with the law already on the books.

Manya Chylinski's experience shows what that kind of preparation looks like when it works. On December 23, 2022, President Biden signed the Post-Disaster Mental Health Response Act into law, expanding eligibility for FEMA's crisis counseling assistance. Getting there required more than a general sense that FEMA's support should reach more people. Chylinski's preparation meant understanding the existing FEMA eligibility framework closely enough to identify precisely where it fell short and how an amendment could close that gap. That kind of precision, knowing the current rule well enough to name its exact limitation, is what separates a bill that moves from one that stalls in committee for lack of specificity.

What does this tell a first-time drafter about where to put their energy? Probably not into polishing prose before the underlying research is done. The research has to come first, because every structural and language choice described above only works if it's responding to the actual law as it currently stands.

Technology's changing role in what citizen drafters can do alone

Digital tools take over the mechanical and research-heavy tasks that used to require institutional access, leaving the legal judgment a credible bill requires to the drafter, which moves citizen drafters measurably closer to professional standards without needing a law degree to get there.

MAPLE, the Massachusetts Platform for Legislative Engagement, was built to help citizens get informed and submit testimony on pending legislation in a state that files thousands of bills in an average session. It now uses AI-powered tools to summarize bills and assign topic tags, and it's testing features that would let users compare similar legislation, get support drafting testimony, and analyze citizen input to help build consensus. The EU's LEOS platform offers a different piece of the puzzle: an open-source legal drafting environment where users co-edit legislative text, add comments, compare versions, and work within Akoma Ntoso, a structured standard that makes legal documents processable by government IT systems. LEOS is a working example of standards-compliant drafting made accessible outside a professional legislative office.

Government bodies are already using AI to manage the output side of this work, too. Italy's Senate has used AI to cluster similar legislative amendments and flag filibustering tactics, and the Italian Chamber of Deputies backed a tool called GENAI4LEX-B, which supports legislative research and drafting by summarizing committee amendments and checking bills against drafting standards. That last function, checking a bill against drafting standards automatically, is no longer a theoretical capability. It's running in a national legislature.

Scale is where these tools prove their worth most clearly. When British officials faced tens of thousands of public submissions on a water-sector overhaul, an in-house AI tool called Consult, part of the UK government's "Humphrey" suite, sorted the submissions into themes in around two hours. That kind of triage used to require teams of staffers working for weeks. AI-assisted sorting of citizen input is becoming routine practice inside government, not a novelty pilot.

The objections a well-drafted citizen bill still has to survive

A bill can hit every structural mark, use every word correctly, and still run into obstacles that have nothing to do with drafting technique. Honest preparation means reckoning with those obstacles directly rather than treating structural credibility as the whole fight.

One objection concerns the AI tools described above. Critics raise a real concern: these tools are genuinely useful for triage, summarization, and formatting, but they represent a structural shift in how citizens engage with the state, not just a convenience upgrade. Treating them as a technical fix risks missing what's actually changing. If governments or advocacy groups start treating AI-assisted tools as substitutes for genuine deliberative processes, rather than as supports that enable deeper human deliberation, the long-term legitimacy of public participation itself is what's at stake. The tools can sort submissions in two hours and summarize bills in seconds, but sorting and summarizing are not the same thing as a legislature actually weighing what citizens said.

That tension doesn't undercut the argument that citizens can draft credible, legally sound bills without a law degree. It sharpens it. The structural conventions, the language precision, the upfront research, these are learnable skills that put a citizen-drafted bill on equal footing with one that came out of a professional office. What they don't do is guarantee that the institutions receiving that bill will engage with it the way they would with a bill from inside the system. Closing the drafting gap is necessary. It was never going to be sufficient on its own, and treating it that way would be its own kind of imprecision.