AB 887 creates the California Computer Science Demonstration Project Grant Program, a pilot that funds the introduction of computer science courses at public high schools that currently offer none. The pilot is funded by nonprofit and private entities (not the state), administered by those funding entities in coordination with a working group, and can cover expenses such as educator recruitment, professional development, certification costs, and incentives.
The bill requires both an interim and a final report to the Legislature with disaggregated enrollment and implementation data, and it directs the Department of Education to post school-level course enrollment data for grades 9–12. The pilot is explicitly temporary and sunsets January 1, 2029, leaving questions about scaling and long‑term funding if the approach is successful.
At a Glance
What It Does
Establishes a privately funded pilot that pays to start computer science courses at public high schools that do not currently offer them. Funding entities administer grants, pick participating schools with input from a working group, cover allowable expenses (recruitment, PD, certification, incentives, admin), and must submit an interim and final evaluation to the Legislature.
Who It Affects
Public high schools that offer no computer science courses, their districts, educators who would teach newly created classes, private nonprofits and industry groups that provide funding, and the California Department of Education which must publish course-level enrollment data.
Why It Matters
It uses private capital to expand access to CS instruction while building a public dataset on who takes those courses, including disaggregation by race, gender, special education, English learner, and socioeconomic status—creating both an experiment in delivery and an evidence base for future policy decisions.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill sets up a pilot grant program aimed specifically at public high schools in California that currently do not offer any computer science courses. Rather than drawing on the state treasury, the pilot is paid for by ‘‘funding entities’’—defined as nonprofits or private organizations—that contribute money, gifts, or in‑kind support.
Those funding entities, working with a designated working group, will run the pilot and decide which schools join, with an explicit priority on increasing access for pupils eligible for free or reduced-price meals and pupils underrepresented in computer science.
Eligibility for the pilot is voluntary and limited to public high schools that lack any computer science offerings. The bill lists allowable expenses—including educator recruitment, professional development, industry exam costs, incentives for districts and educators, and administrative costs—so the grants can be used for both start‑up and retention activities.
Funding entities get discretion over how their contributions are spent, but they must coordinate with one another and with the working group when selecting participants and preparing program evaluations.The bill builds in accountability through two required reports to the Legislature: an interim report due in mid‑2027 and a final report due in mid‑2028. Those reports must evaluate the pilot against its statutory purposes and include disaggregated pupil enrollment data (gender, race/ethnicity, special education, English learner, socioeconomically disadvantaged, and grade), equity and access metrics, educator support and curriculum data, implementation case studies, and recommendations for expansion and funding.
The reports must also name every working group member and disclose each funding entity and the nature of its contributions.Separately, the Department of Education must publicly post course-level data for grades 9–12 that are submitted and certified by local educational agencies as part of the Fall 2 CLPADS submission. That online dataset must include course names and codes and enrollment counts disaggregated by the same subgroups.
The pilot and its reporting requirements are temporary: the statute expressly repeals itself on January 1, 2029, which means the pilot is intended as a time-limited experiment rather than a permanent program.
The Five Things You Need to Know
Only public high schools that do not offer any computer science courses are eligible, and participation is voluntary.
The pilot is funded exclusively through contributions, gifts, grants, and in‑kind donations from nonprofit or private funding entities; the working group and pilot are not state-funded.
Funding entities administer the pilot, decide how their own contributions are spent within the program’s purposes, and must coordinate to submit one interim report (due August 1, 2027) and one final report (due July 1, 2028) to legislative education committees.
Both interim and final reports must include disaggregated enrollment data by gender, race/ethnicity, special education, English learner, socioeconomic status, and grade, plus lists of working group members and all funders with descriptions of their contributions.
The Department of Education must publicly post school‑ and district‑level course names, codes, and disaggregated enrollment counts for certified computer science courses beginning June 30, 2028, and the pilot statute sunsets January 1, 2029.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Purposes of the pilot
This subsection lists the pilot’s statutory goals: expand the number of high schools offering computer science, increase access for pupils eligible for free or reduced-price meals and those underrepresented in CS, and require disaggregated reporting on enrollment in courses created by the pilot. Framing the program by these three purposes guides allowable uses of funds and the metrics used in later evaluation and reporting.
Working group composition and coordinator engagement
The bill establishes a working group composed of nonprofit organizations and private industry stakeholders with CS education expertise. It permits the California Computer Science Coordinator to engage with the group so long as engagement matches the coordinator’s existing duties and does not create state costs. The provision leaves the working group’s internal governance, member selection process, and decisionmaking authority largely unspecified, which matters for transparency and stakeholder representation.
Administration, eligibility, and selection of participating schools
Administration rests with the funding entity or multiple funding entities; if there are multiple, each controls how its own funds are spent but must coordinate on implementation and reporting. Eligible participants are public high schools that currently do not offer any computer science courses, and participation is voluntary. The selecting entities must consider geographic diversity and prioritize schools serving pupils eligible for free or reduced-price meals and underrepresented populations, giving the program an explicit equity orientation in site selection.
Allowable expenses
The statute gives a specific, operational list of allowable expenses: educator recruitment, professional development, exam and industry certification costs, incentives to districts and educators, and administrative costs. That clarity narrows how funding entities may use contributions and signals an emphasis on both creating courses and supporting the workforce needed to teach them.
Evaluation and legislative reporting requirements
Funding entities, working with the working group, must evaluate the pilot against its statutory purposes and deliver an interim and final report to relevant legislative education committees. The reports must contain disaggregated enrollment data, equity and access metrics, educator support and curriculum data, implementation case studies, recommendations including funding considerations, and full disclosure of working group members and funders with detailed descriptions of contributions.
Funding rules and key definitions
The pilot’s funding model is defined: contributions may be monetary or in‑kind and must come from funding entities; the working group will not be state-funded. The bill also defines critical terms—'computer science,' 'computer science course,' and 'funding entity'—tying course eligibility to state academic content standards and requiring that courses go beyond passive technology use to creating computational artifacts.
Public data posting and sunset
The Department of Education must post course-level data for grades 9–12 (course names, codes, and disaggregated enrollment counts) that are submitted and certified via the Fall 2 CLPADS submission, starting by June 30, 2028 and annually thereafter. The entire section is set to repeal on January 1, 2029, making the pilot a time-limited experiment unless subsequent legislation extends or replaces it.
This bill is one of many.
Codify tracks hundreds of bills on Education across all five countries.
Explore Education in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- High school students eligible for free or reduced-price meals and students underrepresented in computer science — prioritization in site selection increases their chance of access to newly created CS courses and associated supports.
- School districts and high schools without existing CS offerings — receive targeted funding for startup costs (recruitment, PD, certification) and incentives to create sustainable classes.
- Educators who complete professional development — the bill authorizes incentives for teachers who finish PD and teach CS, improving supply and retention of qualified instructors.
- Nonprofit organizations and private industry funders — gain a role in shaping program design and can direct resources toward scalable models, plus visibility through required disclosure in legislative reports.
- Researchers and policymakers — obtain a new, public, disaggregated dataset on CS course enrollment that can inform policy, equity assessments, and decisions about broader investment.
Who Bears the Cost
- Funding entities (nonprofits and private organizations) — must provide all financial and in‑kind support for the pilot and bear administrative and reporting responsibilities tied to the interim and final evaluations.
- California Department of Education and local educational agencies — must manage course certification and post CLPADS-derived course enrollment data online, which will require staff time and technical effort that the bill does not explicitly fund.
- Participating school districts and schools — must comply with privacy laws, submit accurate Fall 2 CLPADS data, support implementation activities, and may shoulder match or operational costs beyond pilot grants.
- Working group members — nonprofits and industry stakeholders listed in reports may face reputational risk and time costs from governance, transparency, and disclosure obligations without state funding for their participation.
Key Issues
The Core Tension
The bill's central dilemma is between speed and scalability through private funding versus public accountability and long‑term sustainability: private donors can kickstart courses quickly and fund richer supports, but donor-driven programs risk uneven priorities, potential conflicts of interest, and a funding cliff when the pilot ends—while the state must weigh how much oversight and ongoing support it is willing to assume.
The bill relies on private and nonprofit funding to expand public school course offerings while demanding public transparency and legislative evaluation. That raises classic accountability questions: funding entities control how their contributions are spent within the program’s purposes, which accelerates deployment but also allows funders to shape priorities or favor models that align with their interests.
The working group is required to include nonprofit and industry stakeholders, but the statute does not mandate balanced representation (for example, from teachers, district administrators, or community advocates) or specify conflict-of-interest rules, leaving open the risk of undue influence.
The reporting and data requirements create both opportunity and administrative friction. Requiring disaggregated enrollment counts and public posting at the school and district levels improves oversight and research utility, but it also heightens privacy and compliance burdens for LEAs, especially small schools where subgroup counts can be statistically sensitive.
The bill ties public posting to the Fall 2 CLPADS certification, which is practical but depends on LEAs submitting accurate, timely data; the statute does not allocate state funds to support the additional validation and website publication tasks. Finally, the pilot sunsets on January 1, 2029—useful for forcing evaluation but problematic for sustainability: successful local programs will need a clear path to continued funding, teacher pipelines, and district ownership once private contributions end.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.