CASE STUDY
From a hand-built certificate to a closed loop.
An education-certification program was producing thousands of certificates by hand, with student and teacher data scattered across systems that never talked to each other. This is what got built for teachers, state coordinators, and the staff who oversee it all, and what it proved.

At a glance
- 13,842
- ASSESSMENT RECORDS UNDER MANAGEMENT.
- 9,301
- STUDENTS CERTIFIED, 94.2% OF THOSE WITH ASSESSMENT HISTORY.
- 88.8%
- EXAM PASS RATE ACROSS 11,557 EXAM ATTEMPTS.
- 359
- SCHOOLS ACROSS 13 STATES, GEOCODED AND TRACKED.
- 252
- TEACHERS CURRENTLY CERTIFIED, 461 SYNCED INTO THE SYSTEM.
- 135/135
- AUTOMATED PRE-LAUNCH SECURITY AND ACCESS CHECKS PASSED.
Before: a full-time job that should not have existed.
Certificates were created by hand. Every time a student passed an exam, a staff member built the certificate themselves. At thousands of passes a year, that was a full-time drain with built-in delay and human error.
The data lived everywhere and nowhere. Assessment results sat in one system, coursework in another, contacts and outreach in a third, and tracking spreadsheets in between. Nobody could answer a question as simple as how many students were certified in one state last semester without manual reconciliation.
Coordinators and teachers had no visibility of their own. The people running the program in each state, and the teachers running the classrooms, had no way to see results, download certificates, or know when a certification was about to lapse.
Scale had outrun the process. The program spans hundreds of schools across more than a dozen states today. The manual process was not just slow, the organization had never had this data at real accuracy, at any scale.
A closed loop, not another dashboard.
Four existing systems plus one custom-built portal, each doing what it is best at, wired so a result in one place shows up everywhere it should by the next morning.
Teacher's personal link
Course platform
Exam engine
Automated certificate + records
System of record
A teacher is trained in person, then sits a certification exam. Passing it starts an automated chain: a certification record is created, the certificate is generated and delivered, renewal reminders are scheduled against the real expiry date, and the teacher is invited into the portal. No human touches any of it.
A student registers through their own teacher's personal link, so the teacher and school can never be mistyped. Their course account and enrollment are created automatically, and a contact record is waiting for them before they ever sit an exam.
A student passes an exam and the same automated chain fires for them: certificate generated, delivered, and written forward, visible to their teacher, their state coordinator, and program staff by the next morning.
The portal turns all of it into a product: a nightly sync rebuilds the full picture from scratch as the authority, with a two-minute delta check and a live push in between, so the data is never more than a couple of minutes stale.
The gap was not the automation. It was upstream of it.
The pipeline above starts the moment a student sits an exam. It said nothing about how the student got into the course in the first place, and that turned out to be where the data quality was actually being lost.
Students used to type their school and teacher into a free-text box, and free text produces exactly what free text always produces: the same school spelled three different ways, with nothing downstream able to tell them apart. Since the system of record stores a student's teacher as a real link rather than a typed name, a mistyped instructor could never be connected to the right record at all.
The fix was a personal signup link for every teacher, one link, reusable every year, with the teacher and school already filled in because the link identifies them. A student opening it sees only the courses that teacher is actually certified to deliver, nothing else.
A nightly safety sweep still checks for anyone who found a side door in anyway, and proposes a match against the real teacher roster rather than guessing. Every proposed match is reviewed and approved by a person before anything is written back. The sweep itself only ever reads. An automated system confidently reassigning a student between teachers on a fuzzy name match would do more damage than the problem it was built to solve.
Built FERPA-first, not FERPA-eventually.
Student assessment data is a legally protected education record, so the portal was designed around that from the first line of code, not patched in afterward. Role-based access is enforced at the query layer, not per page, so a person can only ever see what their role allows. A complete audit log records who viewed what, including during staff impersonation for support. Sessions expire in thirty minutes. The entire portal is excluded from search indexing.
A full independent audit ran before launch: 135 automated checks against production, through real authenticated sessions, covering registration, the full role and permission matrix, and access scoping verified against the database itself rather than the screen. Final result: 135 of 135 passing, after every defect the audit found was fixed.
That discipline did not stop at launch. Every access change since has been re-verified against the database, and attempts to reach another teacher's student, another state's school, or a certificate outside scope have consistently been refused.
What changed
- The manual certificate process is gone. Certificate creation went from a hand-built artifact to a webhook-triggered automation with zero staff touch time.
- First trustworthy numbers in the program's history. Real-time totals, sliceable by state, school, teacher, and semester, instead of a spreadsheet nobody fully trusted.
- The right view for every stakeholder. Program staff run the whole thing from one dashboard, state coordinators manage their own states without asking anyone for an export, and teachers serve themselves records and certificates that used to require staff time.
- Lapses are visible before they happen. An expiration tracker and automated reminders turned recertification from a surprise into a managed pipeline.
- The enrollment loop is closed. Students now arrive already correctly paired to the teacher responsible for them, and anyone who slips in through a side door is caught within a day and routed to a person, not silently mismatched.
On our own three questions: this one is almost entirely about time and speed. A full-time manual job removed, a semester of spreadsheet reconciliation replaced by a live dashboard, and a data problem the organization had lived with for years closed inside a single school year.
Find out what is actually broken before you spend another dollar on AI.
Two weeks, fixed fee, fixed start date. A map of what you run, a ranked list of where AI actually holds with a dollar figure on each, and a fixed price plan to build it. You own the document either way.
Read it. If you do not agree we found at least three things worth fixing, tell us and we refund the fee. You keep the document.
$5,000. TWO WEEKS. THE FEE COMES OFF THE BUILD IF YOU START WITHIN SIXTY DAYS.
WHO THIS IS FOR
A company of roughly ten to two hundred people, already running a CRM or operational system, with revenue coming through it and at least one process held together by hand. That includes agencies, whether the system is for your own operation or for a client's. Pre revenue, or want a chatbot on a marketing site? Wrong firm, and we will say so on the first reply.
- $5,000
- FIXED FEE. IT COMES OFF THE BUILD IF YOU START WITHIN SIXTY DAYS.
- 2
- WEEKS, ON A FIXED START DATE.