SB 726 amends Public Resources Code section 5090.77 to impose an explicit, recurring reporting obligation on the Department of Parks and Recreation for the Outdoor Equity Grants Program. The department must gather information from applicants after each award year and produce an annual summary for the Legislature.
The change centralizes and standardizes the program’s data flows: the bill ties the department to a statutory list of program metrics and a required submission format. That increases transparency for budget and policy reviewers but also creates new operational and data-collection requirements for the department and grant applicants.
At a Glance
What It Does
The bill requires the Department of Parks and Recreation to collect information from program applicants following each award year and to summarize and report that information to the Legislature’s budget and fiscal committees on an annual basis. It also prescribes the report’s submission method under the Government Code.
Who It Affects
The department itself and organizations that apply for Outdoor Equity Grants — including local governments, local educational agencies, joint powers authorities, open-space authorities, and nonprofit providers — will need to supply standardized data. Legislative budget and fiscal staff gain a recurring, statutory data feed for oversight and budget decisions.
Why It Matters
By creating a standing, statutory reporting duty and specifying metrics, the bill formalizes program evaluation and makes grant outcomes visible to budget reviewers. That can influence future funding and program design, while introducing recurring compliance and data-management costs for program administrators and applicants.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The Outdoor Equity Grants Program exists to expand access to outdoor environmental education for underserved and at-risk populations at state parks and other public lands. SB 726 focuses not on eligibility or funding, but on the program’s measurement and reporting architecture: it directs the department to gather specified information from applicants after each award year and to assemble that information into an annual summary for legislative budget and fiscal committees.
Practically, the bill turns informal or ad hoc evaluation into a statutory requirement. The department must collect standardized data elements from applicants and grantees, including counts of children served, the types and number of entities receiving awards, partnerships formed, whether educational objectives were met, the volume of applications, and a hypothetical count of children who would have been served if all applicants had been funded.
The statute also requires the department to include recommendations to improve the grant program.SB 726 overrides an existing Government Code provision to ensure annual reporting rather than letting the department skip or fold this report into other periodic filings. The bill also mandates that the final report be submitted in the specific manner required by another Government Code section, which standardizes how the Legislature receives and archives the information.
That creates predictable timing and format for reviewers but also means the department must align internal processes and IT systems to the Legislature’s reporting platform.Although the amendment is described as nonsubstantive in the digest, the text embeds concrete operational obligations. Departments and applicants will need clear data definitions, submission deadlines, and secure handling for any personally identifiable information about children.
The statute does not itself create new program eligibility rules or change funding formulas — its effect is to make measurement and oversight routine and statutory rather than optional.
The Five Things You Need to Know
SB 726 amends Public Resources Code §5090.77 to require the Department of Parks and Recreation to collect information from applicants following each award year for the Outdoor Equity Grants Program.
The bill requires an annual summary of that information to be delivered to the Legislature’s appropriate budget and fiscal committees, explicitly overriding Government Code §10231.5 to ensure yearly reporting.
The statute lists required report elements: total number of children served, total number and types of entities awarded grants, partnerships formed, educational objectives achieved, total number of applications, and the total number of children who would have been served if all applicants had been funded, plus recommendations to improve the program.
SB 726 requires the department to submit the report in compliance with Government Code §9795, tying the summary to the Legislature’s prescribed submission format and routing.
Although the Legislature's digest calls the change nonsubstantive, the bill’s text contains a duplicated phrase for 'educational objectives achieved,' indicating a drafting error even as it creates binding, recurring reporting duties.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Data collection and annual summary for program evaluation
Subdivision (a) directs the department to gather information from applicants following each award year for the purpose of evaluating how well outdoor environmental education programs meet the grant program’s objectives. The provision imposes a recurring, operational duty: the department must collect a defined set of metrics from applicants and assemble them into a program-level summary. For administrators, this means establishing data collection templates, timelines tied to the award year, and processes to verify submissions.
Statutory list of required report elements
The amendment enumerates specific items the annual report must include, such as counts of children served, the number and types of grantees, partnerships formed, educational objectives achieved, the number of applications received, a counterfactual estimate of children who would have been served if all applicants were funded, and recommendations to improve the grant program. That level of specificity reduces agency discretion over what gets measured but also raises methodological questions about definitions and how the counterfactual estimate should be calculated.
Submission format and statutory routing
Subdivision (b) requires the department to submit the annual report in compliance with Government Code §9795, which standardizes how reports are delivered to the Legislature (format, portal, or other procedural requirements). The amendment also includes a 'notwithstanding' clause overriding Government Code §10231.5 to require annual reporting even where other reporting schedules might differ, effectively prioritizing this report’s frequency and routing in the state’s statutory reporting framework.
This bill is one of many.
Codify tracks hundreds of bills on Environment across all five countries.
Explore Environment 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
- Underserved children and communities — standardized reporting makes it more likely the program’s reach, gaps, and outcomes are visible to budget and policy decision‑makers, which can lead to targeted improvements or reallocation of resources.
- Legislative budget and fiscal committees — they gain a regular, statute-backed dataset to evaluate program performance and to inform funding decisions.
- Program advocates and researchers — access to consistent metrics and annual summaries supports evidence-based advocacy, evaluation, and independent research on program effectiveness.
- Successful grantee organizations — clearer outcome expectations and documented partnerships can strengthen future funding applications and partnerships by demonstrating impact.
Who Bears the Cost
- Department of Parks and Recreation — it must build or adapt data collection processes, validate submissions, prepare the annual summary, and integrate with the Legislature’s reporting system, all of which require staff time and likely system changes.
- Applicant organizations and small nonprofits — they must collect and submit standardized data to the department, increasing administrative workload for groups that may have limited reporting capacity.
- State IT and records units — aligning submission to Government Code §9795 and handling potentially sensitive data (children’s participation counts) creates extra work for secure transmission, storage, and compliance.
- Legislative staff — committees receiving more frequent, structured reports will need to allocate time to review, analyze, and act on the new data stream.
Key Issues
The Core Tension
The central dilemma is accountability versus administrative feasibility: the bill strengthens oversight by making program metrics and annual summaries mandatory, but it does so without supplying definitions, resources, or privacy safeguards—so the pursuit of better oversight can create burdens and inconsistent data unless balanced by clear implementing guidance and support.
The bill advances transparency and program evaluation by converting informal monitoring into a statutory annual report, but it leaves several important implementation questions open. The statute prescribes what must be reported without defining how the department should calculate key items (for example, what counts as 'children served,' how to categorize 'educational objectives achieved,' or the method for estimating the counterfactual number of children who would have been served).
Those definitional gaps can produce inconsistent data across applicants and award years unless the department issues implementing guidance or regulations.
The statute also raises data‑privacy and administrative-burden issues. Requiring counts tied to children’s participation may implicate privacy protections and require de-identification standards or parental-consent processes that the bill does not address.
Operationally, smaller nonprofit applicants are the likeliest to struggle with new reporting requirements, and the law does not provide funding, transitional timelines, or technical assistance to offset compliance costs. Finally, the text carries a duplicated phrase and is labeled nonsubstantive in the digest; that combination suggests the amendment may be intended as a technical clean-up but has the practical effect of imposing binding, recurring duties without resolving implementation mechanics.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.