< All Posts
News

Your Enrollment Agreement Might Be Getting You Fined: What BPPE Looks for in Every Student File

Written by
Bella Editorial Team
Published on
22 January 2021

An inspector reviews nine student files. Five have enrollment agreements that are unsigned, incomplete, or dated incorrectly. The fine starts at $2,500. The enrollment agreement is not a formality. It is not the form a student fills out to get started. Under CEC 94902 and 94912, it is a regulated legal document with specific requirements for who signs it, when they sign it, what disclosures are included, and where the student places their initials. BPPE inspects it as such.

What a Compliant Enrollment Agreement Looks Like CEC Section 94902(b) defines what an enrollment agreement must contain. In practical terms, the document needs to include the program name, the total institutional charges, the payment schedule, the refund policy, a description of the credential the student will earn, and the school's cancellation and withdrawal procedures. These are not optional fields. Each one is a regulatory requirement. An authorized employee must sign the agreement. "Authorized" is a specific designation. Not any staff member can sign it. The person signing needs to be formally authorized by the institution to execute enrollment agreements. That authorization should be documented, and the school should have a current list of who holds it. If an inspector asks who signed and whether that person was authorized, you need an answer. The student must sign the agreement before the enrollment start date. This is the timing requirement that tripped up multiple schools in the 2025 citation data. Students who started class and then signed their enrollment agreements a few days or weeks later were flagged. BPPE treats post-start signatures as a compliance failure, not a minor timing discrepancy. Backdating does not fix it, because the enrollment start date is documented independently. Under Section 94912, the student must place their initials on specific sections of the agreement, confirming that they received and reviewed certain disclosures. These include the School Performance Fact Sheet, cancellation rights, and refund policies.

Missing initials are cited as a separate compliance finding, distinct from missing signatures. The SPFS must be attached to or referenced within the enrollment agreement. If the student signed an agreement that did not include or point to the fact sheet, the agreement is deficient even if the student received the SPFS separately.

The Most Common Enrollment Agreement Failures The citation records from the second half of 2025 show a consistent set of enrollment agreement failures across the schools that were cited. Missing authorized employee signatures. In some cases, no staff member had signed the agreement at all. In others, the person who signed was not on the school's authorization list. In at least one case, the school could not produce documentation showing that any employee was formally authorized to sign enrollment agreements. Students who signed after their enrollment start date. This is almost always a sequencing problem, not an intentional violation. The enrollment conversation happens, the student is eager to begin, classes start, and the completed paperwork trails behind by days or weeks. BPPE does not accept that sequence regardless of the reason. Partially completed agreements. Required fields left blank, disclosure sections with no student signature, initials missing from the acknowledgment pages. In some cases, the agreement was only half filled out, as if someone started the form and never finished it. Outdated agreement templates. Schools using enrollment agreement forms that had not been updated to reflect current regulatory requirements. Every agreement signed on that outdated form carries the same compliance gap, which means one template issue can produce dozens of deficient files.

The Downstream Problem An incomplete enrollment agreement rarely exists in isolation. When a school does not enforce documentation standards at enrollment, it tends not to enforce them at any other stage either. The enrollment agreement is usually the first document in a student's file. If it is deficient, the rest of the file is almost always deficient too. Inspectors notice this pattern. A school that has unsigned enrollment agreements in five out of nine files is likely to also have missing high school verification, missing STRF

disclosures, and incomplete SPFS documentation. The enrollment agreement problem signals a broader process gap. Withdrawn student files carry the highest risk in this category. Students who exit before completing the program often have the least complete paperwork. The exit is rushed, administrative tasks are deprioritized, and the file goes into storage without anyone verifying that the enrollment agreement was ever properly completed. Inspectors review withdrawn files alongside current and graduate files, so the risk persists long after the student is gone.

Building a Process That Prevents This Treat the enrollment agreement as a gate between enrollment and instruction. No student moves into the classroom until the agreement is fully executed: authorized employee signature, student signature dated before the enrollment start date, all required initials, all disclosures attached or referenced. Document who is authorized to sign enrollment agreements and keep that list updated. If someone leaves the school, remove them from the authorization list. If you hire someone new in an enrollment-facing role, add them formally before they sign anything. An agreement signed by an unauthorized person is deficient, and the school has no defense if it cannot produce an authorization record. Run a monthly spot-check. Pull three student files at random and review the enrollment agreement for completeness. Check for signatures, dates, initials, and disclosures. This takes 15 minutes, costs nothing, and catches drift before an inspector discovers it. Review your agreement template at least once per year and whenever you become aware of a regulatory change. The California Education Code sections governing enrollment agreements have been amended multiple times. If your template is more than 12 months old, compare it against current requirements and update anything that has changed. One outdated template can create a compliance gap in every file that uses it. Keep a version log for your enrollment agreement form. Note when it was last reviewed, what changes were made, and when the updated version went into use. If an inspector reviews files from different time periods, you can show which template was current at the time each student enrolled.

Frequently Asked Questions
(FAQs)

Frequently asked questions ordered by popularity. Remember that if the visitor has not committed to the call to action, they may still have questions (doubts) that can be answered.

Is switching to Bella difficult?

Not at all. We’ll move your data and guide your team. You’ll be ready to go in days, not weeks.

Can Bella handle state board and NACCAS requirements?

Yes. Bella is built for vocational schools and stays updated with state and federal rules.

I’m not tech-savvy. Will this be too complicated?

Bella is made to be simple. If you can check email, you can use it. And we’re here to help whenever you need.

What does the AI actually do?

It helps spot missing info, flags risks early, and reminds you of what’s due—without you having to dig.

Is Bella affordable for small schools?

Yes. Pricing scales with your size, and most schools save time and money within the first month.

Is our data safe?

Absolutely. Bella uses encrypted, secure hosting and is fully FERPA compliant.

Resources to Help You Run a Smarter School

Tips, checklists, and insights for school owners and admins, written in plain language, not tech speak.