Educator Systems · Licensure & credential records · Early access · 2026

The credential and staffing records a district actually needs to stay compliant

A district carries real liability when a teacher’s license expires unnoticed, when a substitute’s clearance is not current, or when a state agency asks for staffing data that lives in three different spreadsheets. Educator Systems is the records side of the platform: licensure tracking with expiration alerts before gaps appear, a credential file per staff member, an assignment model with HR-gated access, and a credential gate that keeps unverified staff out of student-contact roles. Built on the same single-school privacy wall as the rest of the platform — staff HR data is never visible to a photography studio rep or any non-HR session.

Reserve early access See the capabilities

We are honest about status. The core records capabilities are built and production-ready. The substitute-pool workflow surface is in early access. State reporting and the district rollup console are in development and planned respectively. We say so on every card.

License trackingexpiration dates, endorsement codes, and alert logic built into the credential store

Credential filesa structured, access-controlled file per staff member — documents stored at the platform, never in a shared folder

HR-gated accessserver-resolved, not a client flag — an HR record is invisible to any session without explicit HR-level access

Single-school walleach school’s staff data isolated at the database layer — the same wall as every other part of the platform

The records problem

Most districts track credential expiration in spreadsheets or not at all

The risk is not abstract. A teacher whose background clearance expires mid-year, a substitute placed in a student-contact role without a current license, a state audit that asks for assignment records that have not been centrally maintained — these are the situations that create liability and interrupt school operations. They are also situations that arise routinely when credential tracking is split across a spreadsheet in HR, a file cabinet in the front office, and a system that does not talk to the scheduling engine.

The records Educator Systems tracks are the ones that close those gaps: the teaching license and its endorsements; the background clearance and its renewal date; any supplemental certification the district requires; the school-to-role assignment that tells the scheduling engine whether this staff member can be placed in a student-contact slot. All of it is in one place, with an access model that restricts who can see it, and a tracking layer that surfaces gaps before they become liability.

The core capabilities — the credential file store, the licensure tracking engine, the endorsement mapping, the HR-gated staff roster — are built and production-ready. We are plain about what is not: the district-wide rollup console is planned; state agency reporting is in active development; the combined substitute-pool workflow surface is in early access. A conversation is the honest way to see the current state directly.

Get in touch See all capabilities

Capabilities

What is built, what is in early access, and what is coming

Every capability is labelled at its actual status. Built means the engine is production-ready. Early access means the engine is built but the end-to-end workflow surface is not yet complete. In development means in active build, not available today. Planned means designed, not yet in build. We do not claim otherwise.

Built and production-ready

Staff roster with HR-gated roles and assignments

The staff roster is the single source of truth for who is employed, what their role is, and which school or subject they are assigned to. Role identity is resolved from the server side — an HR administrator’s access is established at the server, never from a client-supplied claim. A staff record is tied to one or more school tenants through the assignment model; a user whose record is not in the assignment table for a school cannot read that school’s HR data, regardless of what their request carries. Changes to a staff member’s role or assignment propagate to every surface that reads the roster — the scheduling engine, the capability gate, the credential file — without a second update pass. The staff roster and assignment model are built and production-ready.

Built · production-ready

Credential file store per staff member

Each staff member has a credential file: a structured, access-controlled store for the documents HR and compliance staff need to retain. Teaching licenses, background clearances, endorsement certificates, transcripts, emergency contact authorisations, and any district-defined document type attach to the staff record and are retrievable by authorised HR staff without a file-cabinet hunt. Documents are stored at the platform level — not in a shared folder where access cannot be controlled — and are never visible outside the HR-gated surface. The credential file store is built and production-ready. Electronic signature on documents is planned; no live e-sign is available today.

Built · production-ready (e-sign planned)

Licensure tracking with expiration alerts

Every license and certification on a staff record carries its expiration date, the issuing state, and any endorsement codes the license carries. The tracking layer reads those dates against the school calendar and raises an alert when a credential is approaching its expiration window — configurable at the district level for how far in advance the alert fires. An expired credential on a staff member who is assigned to a student-contact role surfaces as a compliance flag, not a silent gap. The tracking engine and expiration alert logic are built and production-ready. Automated submission of licensure data to a state agency is in development; it is per-state work and is not claimed as available today.

Built · production-ready (state reporting in development)

Endorsement and certification code mapping

A teaching license carries endorsements — the specific subjects or grade bands the license holder is certified to teach. The endorsement model maps each endorsement code to a subject, a grade range, and an authorisation level. When a staff member is being considered for an assignment, the assignment gate checks the endorsement map against the role: a staff member cannot be placed in a subject they are not endorsed for, and the reason is returned as a machine-readable check code, not a silent failure. The endorsement and certification code mapping is built and production-ready.

Built · production-ready

Early access, in development, and planned

Substitute pool with credential-gated student-contact assignments

The substitute management surface builds on the scheduling engine’s credential gate: a substitute is assignable to a student-contact shift only when their background clearance is current, their license covers the subject, and their district match holds. The gate throws before any write lands; it re-runs on an open-shift claim with an atomic single-winner check. An unverified substitute cannot be placed in a student-contact role: the check is fail-closed. The credential gate is built and runs in production on the scheduling engine. The combined staffing-plus-substitute workflow surface — the HR console that coordinates the credential check with the sub-pool calendar — is in early access and in active development. We describe it honestly.

Credential gate built · substitute workflow surface in early access

District-wide credential status rollup

A district HR administrator needs a view across buildings: which schools have approaching licensure expirations, where there are open staffing slots, and which credential files are incomplete. The data model supports a cross-school rollup for a district tenant; each school’s records are isolated at the database level, and the district rollup is a query that aggregates across the schools the district tenant is authorised over. The rollup surface — the console view a district HR director would use for the across-buildings compliance picture — is planned. The underlying data is there; the aggregation UI is not yet built.

Planned · data model supports it; rollup surface in design

State agency staffing and credential reporting

State education agencies require annual or event-triggered reports on staff licensure, assignment counts, and credential completeness. The credential data the platform holds — license numbers, endorsement codes, expiration dates, assignment records — is the source material for those reports. Generating a per-state report format from that data is in active development. This is genuine per-state work: each state has its own submission format, its own field mapping, and its own submission channel. We are building it for the states where our districts operate first. State agency reporting is in development; it is not available today and we do not claim otherwise.

In development · per-state scope; not available today

How it works

The credential compliance workflow in four stages

From initial roster import through mid-year renewal coordination, the platform is designed to surface compliance gaps before they require emergency action. Each stage is described as it runs today.

1 Import the staff roster and build credential files A district HR administrator imports the staff list: names, roles, school assignments, and any existing credential identifiers the district already tracks. Each staff member gets a credential file on import. HR staff upload the existing license documents, clearance certificates, and endorsement records into each file — the platform takes whatever the district has and indexes it against the staff record. Assignment data is set at this stage: which staff member covers which school, subject, and grade band. The roster import, credential file creation, and assignment setup are built and production-ready.
2 Track expiration dates and receive alerts before gaps appear Once licensure data is in, the tracking engine reads every expiration date against the current date and the school calendar. A credential expiring within the configured alert window surfaces as a flag on the staff record and in the HR dashboard. An HR administrator does not need to run a manual report to find approaching gaps; the system raises them. An expired credential on a staff member in a student-contact role is a compliance flag, not a silent record. Alert configuration (how many days in advance, which document types trigger an alert) is district-level. The expiration tracking and alert system are built and production-ready.
3 Gate scheduling assignments against current credentials When a staff member or substitute is being scheduled for a student-contact assignment, the scheduling engine runs the credential gate: background clearance current, license covers the subject and grade, district assignment matches. A staff member who does not clear the gate cannot be placed in that slot — the check throws before any write, and the reason is a machine-readable check code. An unverified substitute is fail-closed for student-contact roles. The credential gate is built and runs in production. The combined substitute-pool workflow surface that integrates the gate with the sub-pool calendar is in early access.
4 Produce compliance records and coordinate renewals When a license needs renewal, the HR administrator opens the credential file, reviews the existing certificate, notes the renewal deadline, and coordinates the renewal process through the file record. Once the renewed certificate arrives, it is uploaded to the credential file and the expiration date is updated — the compliance flag clears, and the assignment gate is immediately current. No manual cross-reference is required: the same credential file that flagged the expiration receives the renewed document and closes the loop. State agency reporting from this data is in development for the states where our districts operate; it is not available today.

Privacy & access

Staff credential data is HR-gated and single-school isolated at the database level

The access model for staff credential data is the same architecture as every other sensitive record on the platform: enforced at the query layer, not at a display filter a client request could bypass. An HR administrator sees the credential files for the schools their assignment covers. A teacher can see their own record. A photography studio sales representative gets zero rows from the HR surface, regardless of what their session claims — the gate runs at the database, before any data is returned, not in a feature flag on the front end.

The single-school wall means a district running ten schools on the platform has ten isolated HR domains. A credential file for a teacher at School A is not visible to an HR administrator scoped to School B, even if both are in the same district. The district-wide rollup console that aggregates across schools for a district HR director is planned; until it is built, each school’s credential surface is managed separately. We say so directly.

Staff data and student data are separate domains with separate access controls. An HR record and a student academic record sit on the same platform but behind different capability gates. A user whose assignment covers a class roster does not gain access to a colleague’s credential file by that fact alone. Separation is enforced at the query layer on every surface.

How the privacy wall works Security & trust

The educator network

Educator Systems is one property in a network built for the same professionals

The platform has several educator-facing properties. Each is its own product with its own angle; none is a rebranded version of another.

educator.technology

Education technology chosen by teachers, not sold to them. Classroom tools honestly labeled: live surfaces marked live, early access marked early. No demo dressed as a shipped product.

educator.technology →

schedule.software

The scheduling platform the credential gate runs on: picture-day booking, parent-teacher conferences, admissions, staff and substitute scheduling, facilities booking, and photo-crew dispatch. The credential gate for substitute assignments is built here.

schedule.software →

homeroom.software

The school publishing platform: the student record, yearbook, picture day, and communications layer the credential and staffing records sit alongside. The same single-school privacy wall protects every arm.

homeroom.software →

homeroom.software/records

The student records side of the platform: online registration with permission at sign-up, the roster, terms and periods, enrollment and withdrawal, guardians, and class assignments. The staff roster and the student roster share the same privacy architecture.

homeroom.software/records →

Frequently asked

Common questions, answered honestly

What does “HR-gated” mean in practice?

It means the staffing and credential data is only accessible to users whose role gives them HR-level access, and that determination is made at the server, not in a front-end permission flag. A teacher cannot see another teacher’s credential file. A photography studio sales representative gets zero rows from the HR surface, regardless of what their session claims — the gate runs at the query layer before any data is returned. An HR administrator is scoped to the schools their assignment covers; a district-level HR role is not yet a live surface (it is planned). HR-gated means the access model is at the data layer, not at a UI checkbox.

What credential documents can we store?

Any document the district tracks as part of a staff credential file: teaching licenses, background clearance certificates, endorsement certificates, transcripts, subject-area certifications, emergency authorisations, and any district-defined document type. The document type model is extensible; a district is not limited to a fixed list of categories we defined. Documents are stored at the platform level and are access-controlled; they are never stored in a shared folder. Electronic signature on documents is planned; no live e-sign is available today — if e-sign is a requirement, we say so up front and discuss what that timeline looks like.

How does the expiration alert work? Who receives it?

The tracking engine reads every expiration date in the credential store against the current date and flags records that are within the configured alert window. The alert window is configurable at the district level: a district can set a 60-day, 90-day, or 120-day advance window depending on how much lead time their renewal process requires. The flag surfaces in the HR dashboard and on the individual staff record. Delivery to an HR administrator through a notification channel is a feature we are building; today the flags are visible in the credential management surface.

How does the credential gate interact with the substitute pool?

The scheduling engine’s credential gate checks a substitute against their background clearance, their license-to-subject match, and their district assignment before placing them in any student-contact shift. An unverified substitute cannot be assigned to a student-contact role: the check is fail-closed, not a warning that can be overridden without an explicit authorisation step. The gate runs before any write lands; a conflict returns a check code, not a silent over-placement. The gate itself is built and runs in production on the scheduling engine. The substitute-pool workflow surface that brings the credential check together with the sub calendar in a single HR console is in early access and in active development.

Does the platform handle state licensure submission?

Not yet. The credential data — license numbers, endorsement codes, expiration dates, assignment records — is the source material for state agency reports, and that data is in the platform. Generating the per-state submission format from that data is in active development, starting with the states where our current districts operate. Each state has its own format, field mapping, and submission channel; this is genuine per-state engineering work. We do not claim state reporting is available today. If a specific state’s reporting format is a requirement for your district, a conversation is the honest next step so we can tell you where that state sits in the build sequence.

Is the district-wide rollup view available?

Not yet as a live surface. The data model supports a cross-school rollup for a district HR administrator — each school’s records are isolated at the database level, and a district-level query can aggregate across the schools the district is authorised over. The rollup console view is planned; the underlying data model is in place. A district with multiple buildings can work with school-level credential surfaces today while the district rollup is being built.

How is staff data separated from student data?

Completely. The staff HR surface and the student records surface share the same single-school privacy wall at the database level, but they are separate data domains with separate access controls. An HR administrator can see staff credential files; they cannot browse student academic records beyond what their teaching assignment covers. A teacher can access their own class roster; they cannot see another staff member’s credential file. A photography studio representative, whose session is scoped to picture-day operations, gets zero rows from either the HR surface or the student records surface. Separation is at the query layer, enforced before data is returned, not at a display layer that a client request could bypass.

What can we use right now, and what is still coming?

Built and production-ready today: the staff roster with HR-gated roles and school assignments; the credential file store for document upload and retrieval per staff member; the licensure tracking engine with expiration date alerts; the endorsement and certification code mapping; and the credential gate on the scheduling engine for student-contact assignment checks. In early access: the combined substitute-pool workflow surface that integrates the credential gate with the sub-pool calendar in a single HR console. In development: state agency staffing and credential reporting (per-state scope). Planned: the district-wide cross-school credential rollup console; electronic signature on staff documents. A conversation is the honest way to see exactly where each piece sits and what access looks like for your district.

Reserve early access

If the credential and staffing record problem is one your district is dealing with, a conversation is the honest next step

We do not have a signup form or a self-serve trial. The platform is in early access for districts and HR teams that want to work through the current state of the credential and licensure tracking capabilities directly. A conversation means: we walk through the built surfaces with you, we are plain about what is in early access and what is in development, and we find out whether the platform is a fit for what your district actually needs. No pricing commitment, no contract pressure, no demo dressed up as a finished product.

If the credential file store, the licensure expiration tracking, the endorsement gate on substitute assignments, or the state-reporting build sequence is relevant to your district’s current situation — reach out. We respond to every inquiry and we are direct about where the product stands today.

[email protected]

Status transparency

What is built, what is in early access, and what is not available today

Built and production-ready: the staff roster with HR-gated roles and school assignments; the credential file store for document upload, storage, and retrieval per staff member; the licensure tracking engine with expiration dates and alert logic; the endorsement and certification code mapping; and the credential gate on the scheduling engine for student-contact assignment checks. These are running in production today.

In early access: the combined substitute-pool workflow surface that brings the credential gate together with the sub-pool calendar in a single HR console. The credential gate itself is built; the end-to-end workflow surface is in active development.

In development: state agency staffing and credential reporting. This is per-state engineering work starting with the states where our current districts operate. It is not available today.

Planned: the district-wide cross-school credential rollup console for a district HR director; electronic signature on staff documents. The data model supports the rollup; the surface is not yet in build.