Koro Research · BPPE operations
BPPE readiness depends on year-round evidence.
What Koro’s analysis of 1,149 BPPE citation lifecycles reveals about the records, handoffs, and source evidence California private postsecondary schools need for inspections and annual reporting.
Koro Solutions
Published July 29, 2026
12-minute read
The operating reality
The annual-report deadline is only the final step.
An annual report is assembled once a year. Its evidence is created every day.
Where required, a student must receive the current catalog and applicable School Performance Fact Sheet before signing the enrollment agreement. Payments, cancellations, withdrawals, and refunds must produce the required records. Applicable completion, licensure, employment, and contact evidence must remain connected to the correct student, program, location, and reporting year.
That is why a calendar alone cannot carry BPPE readiness. The institution needs an operating system for ownership, document versions, evidence, exceptions, review, retrieval, and corrective action.
Why this matters now
BPPE is conducting materially more inspections than it did four years ago.
BPPE’s official statewide data show more inspections, more citations, and more assessed fines between FY2021/22 and FY2024/25. Those trends establish an environment with broader inspection coverage; they do not prove that schools have become less compliant.
- Compliance inspections
- 289429
- Citations issued
- 146327
- Fines assessed
- $537K$2.69M
Through March 31, 2026, BPPE reported 347 inspections in FY2025/26, including 231 unannounced inspections. It reported 234 citations year to date, slightly fewer than the 243 reported for the comparable prior period. Inspection coverage remains expanded. Review the May 2026 year-to-date report (opens in a new tab) and the May 2025 comparable report (opens in a new tab).
Assessed amounts are not the same as final amounts or money collected. The official totals reflect Bureau enforcement activity, including approved and unapproved activity. BPPE also attributes citation growth partly to improved inspection and investigation efficiency and backlog reduction. See the 2026 BPPE Sunset Review (opens in a new tab).
Koro citation analysis
The most frequent categories involved everyday operating controls.
We reviewed public BPPE records across a curated cohort of 839 schools listed as current in Koro’s July 28, 2026 extraction. The citation issue dates span April 26, 2012 through July 20, 2026. Each original citation and its later appeal, modification, settlement, compliance, or closure records count as one lifecycle. In Koro’s operational recoding, the leading categories involved records, source evidence, filing workflows, and enrollment execution.
- schools listed as current in Koro’s dated cohort
- 839
- distinct citation lifecycles reviewed
- 1,149
- individual violation records classified
- 2,071
- of citations required corrective action through abatement
- 97.8%
Individual violation records in Koro’s operational recoding
Records and access
337225 citation lifecycles across 213 schools
STRF collection and submission
296294 citation lifecycles across 212 schools
SPFS evidence and substantiation
231231 citation lifecycles across 207 schools
Annual-report submission
217201 citation lifecycles across 162 schools
Enrollment execution and sequencing
181138 citation lifecycles across 133 schools
What “missing evidence” meant
Collection, substantiation, and retrieval are different controls.
A polished fact sheet cannot repair source data that was never collected, evidence that cannot substantiate the number, or a record that exists but cannot be produced.
- SPFS-substantiation violation records involving missing or unavailable evidence
- 216of 231
- SPFS-substantiation violation records stating that required data had not been collected
- 118overlapping subset
- citations involving an inability to retrieve requested records
- 10354 also cited unavailable personnel
These are Koro findings from a dated, curated cohort. They are not BPPE statewide statistics. The method and limitations are published below.
The evidence lifecycle
Reporting evidence begins at enrollment.
Annual reporting is the final assembly of a chain that begins with disclosure and enrollment, continues through student records and outcomes, and ends with a complete, reviewable submission.
Publish the current version
Keep the catalog, program-level School Performance Fact Sheets, required website disclosures, and related student materials current and aligned.
Deliver disclosures before enrollment
Provide the current catalog and applicable SPFS before the student signs the enrollment agreement. Obtain the signatures, dates, and initials required for the SPFS disclosures and enrollment record.
Execute the enrollment record
Use the correct agreement version and an authorized institutional signature, then preserve the complete executed record.
Maintain the student evidence
Keep payment, refund, attendance, progress, leave, withdrawal, completion, warning, complaint, and related records as applicable.
Follow outcomes to their source
Capture licensure, employment, contact-attempt, verification, and supporting details required for each applicable program and reporting period.
Review before reporting
Resolve missing evidence, confirm program and location scope, test calculations, and document who reviewed each submission component.
Submit and preserve the receipt
Complete every required portal field, manage any separate financial-statement track, retain the receipt, and keep the source package retrievable.
New operating load in 2026
Payment and refund rules now require more frequent recordkeeping.
Current payment, cancellation, withdrawal, and refund rules took effect January 1, 2026. Among other requirements, 5 CCR sections 71746(b), 71750(d), and 71751(d) address receipts or updated ledgers within five business days of payment, cancellation and withdrawal documentation, and logs kept current monthly.
The details depend on the transaction and student status. The operating lesson is broader: waiting for the annual-report season is too late to reconstruct this evidence reliably. Review the current regulations (opens in a new tab).
Beyond a reminder calendar
A deadline tells you when. A system shows whether the work is ready.
BPPE does not require a particular CRM or compliance platform. It does require institutions to maintain adequate procedures under 5 CCR section 71760 and produce required records under, among other provisions, 5 CCR section 71930(c) and (e). The useful question is not “Do we have another tool?” It is “Can our team see and verify the work?”
| Control | Reminder calendar | Evidence operating system |
|---|---|---|
| Due dates | Tells the team when a filing is due. | Connects the due date to the work that must happen throughout the year. |
| Completion | Marks a task complete. | Shows whether every required field, signature, source, and review is complete. |
| Evidence | Links to a folder or spreadsheet. | Identifies the authorized record, correct version, evidence location, and accountable owner. |
| Exceptions | Depends on someone noticing the problem. | Surfaces missing records, stale versions, failed handoffs, and overdue follow-up before submission. |
| Retrieval | Assumes the person who knows the files is available. | Tests whether an authorized backup can retrieve the requested evidence during business hours. |
| Recurrence | Resets after the deadline. | Connects corrective action to the process change, owner, and verification that keep the issue from returning. |
- Due dates
- Reminder calendar
Tells the team when a filing is due.
- Evidence operating system
Connects the due date to the work that must happen throughout the year.
- Completion
- Reminder calendar
Marks a task complete.
- Evidence operating system
Shows whether every required field, signature, source, and review is complete.
- Evidence
- Reminder calendar
Links to a folder or spreadsheet.
- Evidence operating system
Identifies the authorized record, correct version, evidence location, and accountable owner.
- Exceptions
- Reminder calendar
Depends on someone noticing the problem.
- Evidence operating system
Surfaces missing records, stale versions, failed handoffs, and overdue follow-up before submission.
- Retrieval
- Reminder calendar
Assumes the person who knows the files is available.
- Evidence operating system
Tests whether an authorized backup can retrieve the requested evidence during business hours.
- Recurrence
- Reminder calendar
Resets after the deadline.
- Evidence operating system
Connects corrective action to the process change, owner, and verification that keep the issue from returning.
Original Koro operating model
Connect each requirement to the work, evidence, review, and remediation behind it.
- 01
Obligation
What the current requirement asks the institution to do.
- 02
Operating event
Where that requirement becomes real in the student or reporting lifecycle.
- 03
Evidence
Which authorized record proves the work was completed correctly.
- 04
Review
Who checks completeness, version, timing, and exceptions before submission.
- 05
Remediation
How a missing item becomes a corrected process instead of a recurring scramble.
A practical readiness test
Six questions to ask before the annual-report build.
Use a random student or program sample. The goal is not to produce a polished answer after a meeting. It is to test whether the operating path works without reconstruction.
Can an authorized backup retrieve the current catalog, the applicable signed and initialed SPFS disclosures, and the executed enrollment agreement for a randomly selected student?
Can the team identify which program, location, reporting year, and document version apply without reconstructing the answer from email?
Can every reported outcome be traced to its underlying source evidence, contact history, verification, and reviewer?
Are payment, cancellation, withdrawal, and refund records and logs updated within the required operating cadence?
Can the team see missing evidence, an accountable owner, and the next action before the annual-report build begins?
After a deficiency is corrected, can the institution show which process changed and how recurrence will be checked?
If an answer depends on one person, an inbox search, or a spreadsheet rebuilt for the deadline, the gap is operational. Map the owner, event, evidence source, review, exception path, and backup before adding automation.
Where Koro fits
Map the operating work before configuring the tool.
We can help postsecondary teams define owners, handoffs, document versions, evidence locations, exception queues, reviews, dashboards, and training around BPPE-related operations. Where HubSpot is appropriate, it can coordinate status and work without replacing the institution’s student information system or authorized records repository.
We do not provide legal advice, certify compliance, guarantee a filing outcome, or promise that a system will prevent a citation.
Methodology & sources
The method and limitations belong beside the findings.
We separate official statewide measures from Koro’s cohort analysis, and we preserve the limitations of public regulatory records.
Koro created a curated cohort of 839 schools listed as current in its July 28, 2026 extraction from BPPE’s approved-school records. The cohort was frozen for this analysis. It is not presented as a census of every institution that has ever appeared in Bureau records.
The analysis covers 1,149 distinct citation numbers found for the cohort, with issue dates from April 26, 2012 through July 20, 2026. Public-record matches and dispositions were verified against BPPE’s disciplinary archive on July 28–29, 2026. Appeals, modifications, settlements, and closure letters were treated as one citation lifecycle rather than separate citations.
The 2,071 violation records were recoded from the cited provisions and factual-cause summaries into an operational taxonomy created by Koro. The taxonomy is not a BPPE classification.
BPPE inspections are risk-selected, public records may be delayed or incomplete, and dispositions can change. No public citation match does not mean an institution was never cited.
Counts describe documented records, not causation. They do not show that a particular system would have prevented a citation or that every institution faces the same risk.
Primary sources
- BPPE Annual Reports (opens in a new tab)
Current portal dates, reporting instructions, and program-level SPFS scope.
- California Code of Regulations, Title 5 (opens in a new tab)
Current regulations effective July 1, 2026, including enrollment, records, refunds, SPFS, annual-report, and compliance-procedure requirements.
- California Private Postsecondary Education Act (opens in a new tab)
Current statutory compilation as of January 1, 2026, including enrollment, disclosure, website, record, and inspection provisions.
- BPPE 2026 Sunset Review Report (opens in a new tab)
Official inspection, citation, assessed-fine, processing-time, and program-capacity trends.
- May 6, 2026 Advisory Committee materials (opens in a new tab)
FY2025/26 activity through March 31, 2026 and annual-report portal workflow data.
- May 28, 2025 Advisory Committee materials (opens in a new tab)
Comparable FY2024/25 activity through March 31, 2025 used to qualify the current year-to-date citation trend.
- BPPE Disciplinary Actions (opens in a new tab)
Public citation index used for Koro’s citation-lifecycle analysis, with BPPE’s stated limitations.
- BPPE Approved Schools (opens in a new tab)
Official approved-institution search used as the starting point for Koro’s dated school cohort. BPPE notes that status information is effective as of each search result date.
Citation issue dates: April 26, 2012–July 20, 2026. Public records and current requirements verified July 28–29, 2026.
This article is general operational information, not legal advice. Requirements vary by institution and program. Review current BPPE statutes, regulations, guidance, and any applicable accreditor or licensing-agency requirements, and consult qualified counsel when needed.