AB 2360 California Assembly · 2025-2026 Regular Session

State agencies: governmental linguistics.

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.

Bill status passed 3 of 5 stages cleared

Introduction

Feb 2026

Committee Review

Aug 2026

Assembly Passage

May 2026

Senate Passage

Governor

Introduced Feb 19, 2026 Last action Aug 13, 2026

Maddy AI version diff · 2 comparisons

What changed between versions

05/18/26 - Amended Assembly → AB2360 · 2 edits

MINOR

This diff represents a change in document format rather than substantive policy. The 'from' version is a formatted legislative document (Amended Assembly, May 18, 2026) and the 'to' version is a web page rendering of the same bill text. The underlying policy content of AB 2360 remains unchanged between the two versions.

TECHNICAL

The document was reformatted from a clean legislative text layout to a web page that includes navigation menus, metadata headers, and inline amendment markup showing old versus new language side by side.

Web page elements were added including navigation links (home, accessibility, FAQ, feedback, sitemap, login), search tools, bill tracking features, and version history display.

02/19/26 - Introduced → 05/18/26 - Amended Assembly · 5 edits · May 18, 2026

MODERATE

The amended version of AB 2360 adds a January 1, 2027 effective date for the plain language writing requirement, changes the plain language policy obligation from mandatory to permissive (agencies are now authorized rather than required to adopt one), and narrows the definition of covered documents to those that are 'publicly available.' A new optional provision allows agencies to use standards created by the Office of Data and Innovation.

Scope change

Scope narrowed in two ways: (1) only documents produced after January 1, 2027 are covered, giving agencies a transition period; (2) the definition of 'state agency document' now requires documents to be 'publicly available,' excluding internal or non-public communications from the plain language requirement.

TIMELINE

A specific effective date of January 1, 2027 was added. State agencies are now only required to write documents in plain language if produced after that date, rather than immediately upon enactment.

REQUIREMENT

The requirement for each state agency to create, adopt, and post a plain language policy on its website was changed from mandatory ('shall') to permissive ('may'). Agencies are now authorized but not required to adopt such a policy.

TECHNICAL

A new subsection allows state agencies to use standards created by the Office of Data and Innovation as a tool for implementing plain language principles. This is optional, not required.

The bill's internal structure was reorganized: definitions moved from subsection (d) at the end to subsection (a) at the beginning, and the plain language writing requirement shifted from subsection (a) to subsection (b). This is a drafting change with no substantive policy effect.

DEFINITION

The definition of 'state agency document' was narrowed. It now requires documents to be 'publicly available' (a new qualifier), replaced 'contract' with 'instruction,' and replaced 'announcement' with 'communication.' This reduces the scope of covered documents by excluding non-public materials.

Floor votes · Assembly May 27, 2026

How they voted

76–0

Passed · 3 other

Total votes 79

May 27, 2026

D Democratic59

57 Yea 2

96% Yea

R Republican20

19 Yea 1

95% Yea

Vote distribution

All Yea All Nay Mixed No data

Full legislative history

Actions timeline

Total actions

Key actions

Committee

Amendments

Aug 13, 2026

Upper · Passed

In committee: Held under submission.

upper

Aug 3, 2026

Committee

In committee: Referred to APPR. suspense file.

upper

Jun 23, 2026

Upper · Passed

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.

upper

Jun 10, 2026

Committee

Referred to Com. on G.O.

upper

May 27, 2026

Assembly · Passed

Assembly Vote: pass (76-0-3)

assembly

May 26, 2026

Lower · Passed

Read third time. Passed. Ordered to the Senate. (Ayes 77. Noes 0.)

lower

May 18, 2026

Lower · Passed

Read second time and amended. Ordered returned to second reading.

lower

May 14, 2026

Introduced

From committee: Amend, and do pass as amended. (Ayes 11. Noes 0.) (May 14).

lower

Apr 22, 2026

Committee

In committee: Set, first hearing. Referred to APPR. suspense file.

lower

Apr 9, 2026

Lower · Passed

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.

lower

Mar 9, 2026

Committee

Referred to Com. on G.O.

lower

Feb 20, 2026

Lower · Passed

From printer. May be heard in committee March 22.

lower

1 primary · 0 co-sponsors