
More than 10 violations in six months, all tied to the same regulation: Section 76140 record-keeping failures for graduate employment tracking. Graduation feels like the finish line. For compliance purposes, it is the start of a new set of obligations. Schools were not fined because their graduates had bad outcomes. They were fined because there were no records of what happened after students left. No employer names. No job titles. No evidence that anyone tried to find out.
What Section 76140 Actually Requires In practical terms, Section 76140 requires California schools to maintain individual records of each graduate's employment outcome. That means documenting: employment status (employed in the field, employed outside the field, not employed), employer name, job title, employment start date, and compensation. These are per-graduate records, not estimates or aggregate counts. Supporting documentation must exist as well. BPPE expects verifiable proof, not just a note in a file that says the graduate got a job. Acceptable documentation includes employer verification letters, signed employment verification forms, copies of pay stubs, or equivalent records that confirm the graduate's employment status and details. This data feeds directly into the School Performance Fact Sheet. The placement rates a school publishes under Section 74112 are derived from the individual records maintained under Section 76140. If the Section 76140 records do not exist, the SPFS placement rates are unsubstantiated. One gap creates two compliance problems.
Why This Is Hard to Do After the Fact Students disengage from their school quickly after graduation. Within 30 days, most have moved into their next chapter. Their phone numbers change. Their personal email addresses go dormant. They stop responding to calls and messages from the school because they no longer see a reason to stay in touch. Without a structured follow-up process that begins before the student graduates, the data collection window closes fast. By the time an inspector asks for placement records
from 12 or 18 months ago, there is nothing to produce. The school never captured the information, and the graduates are now unreachable. This is not a problem you can fix retroactively. You cannot call a graduate two years after completion and reconstruct their employment history from the months following graduation. The data either exists because you collected it in real time, or it does not exist at all. Some schools try to survey graduates by mail or email at the end of the reporting period. The response rates are low, typically well under 50%, because the school has no relationship with the graduate at that point. The time to build that data collection habit is while the student is still enrolled and still connected to the school.
A Practical Post-Graduation Outreach System Build a 30/60/90-day touchpoint schedule that starts on the student's graduation date. This is not a complex process. It is three check-ins over three months, each one designed to capture a specific piece of information. At 30 days, contact the graduate by phone, text, or email. Ask: Are you employed? Is the position in the field you studied? Who is the employer? What is your job title? When did you start? Document the answers, the date of contact, and the method. At 60 days, follow up with anyone who was still job-searching at the 30-day mark or who did not respond to the first contact. Update the record with any new information. At 90 days, make a final attempt for any non-responders. At this point, even if you do not get a response, document the attempt. Keep a log showing the date, the method of outreach, and the result. Inspectors recognize the difference between a school that tried to collect data and failed, and a school that never tried at all. For graduates who respond, request supporting documentation. An employer verification form (which the school can create as a simple one-page template) or a copy of a recent pay stub is sufficient. Make it easy for the graduate: send a short form they can fill out digitally and return. The most important upstream fix is to keep contact information current before graduation, not after. During the final weeks of the program, verify each graduating student's phone number, email address, and mailing address. Add a secondary contact if possible. This one step dramatically increases the chances of successful post-graduation outreach.
Connecting Placement Data Back to Your SPFS The individual records you collect under Section 76140 are the raw material for the aggregate placement rates you report under Section 74112. When the Section 76140 records are complete, the SPFS placement data assembles itself. The audit trail inspectors expect to see works like this: a named graduate record with employment details (employer, title, start date, compensation), linked to the aggregate placement figure published on the fact sheet. If your SPFS reports a 75% placement rate, an inspector should be able to see the full list of graduates, which ones were placed, which ones were not, and what documentation supports each placement determination. Schools that build a working Section 76140 tracking system eliminate the most common SPFS-related citation at the same time. The two requirements are not separate compliance burdens. They are two outputs from the same process. Doing the graduate tracking well means the SPFS data practically writes itself.
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.
Not at all. We’ll move your data and guide your team. You’ll be ready to go in days, not weeks.
Yes. Bella is built for vocational schools and stays updated with state and federal rules.
Bella is made to be simple. If you can check email, you can use it. And we’re here to help whenever you need.
It helps spot missing info, flags risks early, and reminds you of what’s due—without you having to dig.
Yes. Pricing scales with your size, and most schools save time and money within the first month.
Absolutely. Bella uses encrypted, secure hosting and is fully FERPA compliant.
Tips, checklists, and insights for school owners and admins, written in plain language, not tech speak.
