Bring the proposed text
Use: Action preparation. Turn a concern into proposed legislative language and a specific request to the legislator or committee that can introduce and advance it.
A citizen can bring more than a request to fix a problem. Bring a clear proposal: the rule to change, the office responsible, the resources needed and the record that will show whether it worked.
This guide helps you prepare a legislative proposal for a sponsor and drafting review. It does not turn a citizen draft into an introduced bill or enacted law.
Choose an instrument that can do the job
Identify the government level that controls the issue. A federal statute, state statute, local ordinance, agency rule and internal policy have different adoption paths. Check the current law before choosing a title for your proposal.
In Congress, bills and joint resolutions can become law through the applicable process. Simple and concurrent resolutions can address internal matters or express a position, but do not themselves enact a public law. A joint resolution proposing a constitutional amendment follows a different path. House guide to bills and resolutions.
For state and local action, find the official legislature or council website, current code, charter and drafting instructions. Ask which body has authority, whether a higher law limits the change, and who may introduce it. Do not assume a local “resolution” has the same effect as a congressional resolution.
If the law already delegates the needed choice to an agency, consider a rulemaking petition. If the duty already exists and is not being carried out, an oversight or enforcement route may fit better than new legislation.
Build a packet a sponsor can use
- One-page decision brief. State the problem, affected people, strongest evidence, proposed remedy and requested next act. Say what current law fails to do.
- Current and proposed text. Identify the exact code section and source date. Show deletions and additions clearly, and supply a clean version. Explain any new terms. Label your document “Citizen proposal for drafting review.”
- Section-by-section explanation. Explain each clause in plain language. Name the person or office that must act, the trigger, deadline and expected result.
- Cost and operating note. Estimate staff time, systems, ongoing costs and who pays. State assumptions and unknowns. Do not call your estimate an official fiscal score. Ask the sponsor to obtain the appropriate budget review.
- Evidence and objections. Number sources and pinpoint pages. Include relevant contrary evidence, affected groups and alternative designs. Explain trade-offs rather than implying the change has no costs.
- Implementation and review. Specify how the duty starts, what funding or further rules it needs, who checks compliance, and what remedy follows a failure. Decide whether a review date or expiration is appropriate.
Ask drafting counsel to check cross-references, existing definitions, constitutional and statutory limits, conflicts with other law, enforcement, funding and transition. A model from another place is a starting point; its legal setting may differ.
A sponsor request to adapt
“The attached records show [problem]. We propose changing [provision] so [responsible office] must [defined action]. The packet includes proposed text, an explanation and cost assumptions. Will your office request drafting and fiscal review, identify the responsible committee, and tell us whether it will sponsor the proposal?”
Agree who may speak for a group before using its name. Keep factual support separate from an endorsement of the entire draft. Ask affected residents and the people expected to implement it to test the proposal.
Worked example: make a service delay visible
Hypothetical drafting exercise. This is not existing law or a finding about a named agency. A local benefit program publishes only an average processing time. Residents cannot tell how many applications remain overdue. Suppose local legal review confirms that the council can impose reporting duties on this office.
Citizen proposal for drafting review
Monthly service report. Beginning 90 days after this ordinance takes effect, the administering office shall publish a monthly report within 20 days after each month ends. Each report shall state: applications received; applications decided; applications pending at month-end; and pending applications beyond the program’s applicable decision deadline.
The report shall explain the counting method, identify missing records and describe material changes in the method. The office shall correct a material published error and keep a dated notice explaining the correction.
The report shall not disclose applicant identities or information protected by law. Before the first report, the office shall publish a method to protect people from identification through small groups of records.
The office shall present the report to the council committee responsible for the program each quarter and identify steps to address overdue cases. The council shall review the reporting requirement one year after the first report.
What must be settled before introduction
Replace “administering office” and the committee description with exact names. Verify the decision deadline and the council’s power. Ask staff to test whether the needed records exist and to estimate reporting costs. Specify the lawful funding source, effective-date clause and compliance process. Review privacy rules and whether the required publication could expose applicants.
The sample requires reporting and review. It does not create a new benefit, accelerate every case, or create a private right to sue. If the objective is timely decisions, examine whether a separate enforceable deadline, staffing change or appeal remedy is also needed.
How the citizen checks the result
Compare monthly publication dates and the overdue-case count under a stable definition. Inspect corrections and committee responses. A smaller backlog may be useful evidence; it does not by itself prove this reporting requirement caused the improvement. Check staffing, application volume and other changes.
Track the text, not just the promise
A House sponsor introduces a bill; the Clerk assigns a number and the Speaker refers it to the appropriate committee with the Parliamentarian’s assistance. Introduction is a recorded step, not a guarantee of a hearing or vote. House introduction and referral guide.
Keep a version log with these columns: date, official document and link, section changed, practical effect, your requested response, responsible office, and next check. Save the citizen draft separately from official versions. When text moves into another bill, record the new bill and provision.
- After a sponsor agrees: confirm the actual bill or ordinance number, introduced text and referral.
- Before committee action: check the agenda, proposed amendments and evidence submission rules. Ask for a specific correction tied to the current version.
- After each vote: save the adopted text and vote record. Check whether a deadline, funding term, safeguard or enforcement clause changed.
- After enactment: verify the final law, effective date, funding and implementing instructions. Follow the responsible office’s performance.
- If it stalls: record the procedural stage and unanswered request. Consider a narrower amendment, a different lawful instrument or another session; do not report silence as a defeat on the merits.
The CRS legislative-process report, dated November 24, 2020 in the retrieved copy, explains why bills do not all follow one predictable sequence. Use current chamber and committee rules for a live proposal; this historical overview does not certify today’s procedural details.
Your work product is a reviewable proposal and a record of what the institution does with it. A sponsor’s support is useful. The enacted duty, its funding and its delivery determine what changed for citizens.
Wider citizen routesIdentify who can actKeep the follow-through record