Skip to main content

AB 2360 — California

State agencies: governmental linguistics.

Passed one chamber 20252026 session Assembly

This page lists STATE bills only. Open States, our source for this data, tracks state legislatures -- it has no visibility into city councils, county commissions or school boards. We don't yet have a free, storable source for local measures; see the About page for why.

Summary

Existing law requires each department, commission, office, or other administrative agency of state government to write each document, as defined, that it produces in plain, straightforward language, avoiding technical terms as much as possible, and using a coherent and easily readable style.

This bill would instead require each state agency, as described above, to write each document it produces after January 1, 2027, either digitally or in print, in plain language, as specified, and would define "plain language" for purposes of that provision. The bill would authorize a state agency, as described above, to use standards created by the Office of Data and Innovation that identify how a state agency incorporates plain language principles and practices. The bill would require the head of each state agency to, among other things, designate one or more senior officials within the state agency to oversee state agency implementation of these provisions.

Official abstract, as published by the legislature.

  • AB 2360 is a bill in the California Assembly, 20252026 session, introduced February 19, 2026.
  • Current status: passed one chamber.
  • Most recent action (August 13, 2026): In committee: Held under submission.
  • 5 recorded votes; the most recent, on August 3, 2026, passed 7-0.
  • Subjects: Stateagencies, governmentallinguistics.

Contact your legislator about this bill

Bill text & documents

Sponsors

Cosponsors (1): Arambula

History

  1. Introduced, completed
  2. Passed Assembly, completed
  3. Passed Senate, in progress
  4. Sent to Governor, not reached yet
  5. Signed into law, not reached yet
  1. Assembly Read first time. To print.
  2. Assembly From printer. May be heard in committee March 22.
  3. Assembly Referred to Com. on G.O.
  4. Assembly Do pass and be re-referred to the Committee on [Appropriations] with recommendation: To Consent Calendar

    22 yes 0 no Passed, 100% yes

  5. Assembly From committee: Do pass and re-refer to Com. on APPR. with recommendation: To Consent Calendar. (Ayes 22. Noes 0.) (April 8). Re-referred to Com. on APPR.
  6. Assembly In committee: Set, first hearing. Referred to APPR. suspense file.
  7. Assembly From committee: Amend, and do pass as amended. (Ayes 11. Noes 0.) (May 14).

    Do pass as amended.: 11 yes 0 no, 4 other Passed, 100% yes

  8. Assembly Read second time and amended. Ordered returned to second reading.
  9. Assembly Read second time. Ordered to third reading.
  10. Assembly Read third time. Passed. Ordered to the Senate. (Ayes 77. Noes 0. Page 5381.) Milestone
  11. Senate In Senate. Read first time. To Com. on RLS. for assignment.
  12. Assembly AB 2360 Arambula Assembly Third Reading

    77 yes 0 no, 3 other Passed, 100% yes

  13. Senate Referred to Com. on G.O.
  14. Senate From committee: Do pass and re-refer to Com. on APPR. with recommendation: To Consent Calendar. (Ayes 14. Noes 0.) (June 23). Re-referred to Com. on APPR.

    Do pass, but first be re-referred to the Committee on [Appropriations] with the recommendation: To Consent Calendar: 14 yes 0 no, 1 other Passed, 100% yes

  15. Senate In committee: Referred to APPR. suspense file.

    Placed on suspense file: 7 yes 0 no Passed, 100% yes

  16. Senate In committee: Held under submission. Latest

Source: Open States. Last checked November 6, 2026. How we keep this accurate ›