Enterprise review

Compliance Controls & Evidence

Inspect implemented controls, evidence sources, and acceptance boundaries instead of relying on unsupported compliance badges.

Implemented control areas

Each area below describes a system capability that can be inspected. Legal or certification conclusions depend on the governing requirements and evidence for the specific deployment.

Workforce Reporting Infrastructure

Participant, service, employment-outcome, performance, PIRL mapping/export, and report-run data structures support workforce reporting workflows when source data is recorded.

Review reporting controls

Education Data Access Controls

Authentication, role-based access, tenant scoping, row-level security, consent records, and audit events are used to protect supported learner and program workflows. These controls support FERPA-aligned administration; they are not a blanket legal certification.

Review privacy practices

Accessibility Program

The platform includes accessibility-focused components and release checks. Conformance must be demonstrated by automated and manual testing against the production experience; this page does not assert an unverified WCAG certification.

Review accessibility statement

Audit & Evidence Records

Applications, enrollments, attendance, apprenticeship hours, learner risk events, interventions, credentials, regulatory evidence, and selected administrative actions can retain auditable records in the canonical database.

Open enterprise review

Acceptance boundaries

These boundaries prevent a buyer, learner, agency, or administrator from mistaking an implemented control for a certification or guaranteed legal outcome.

No SOC 2, PCI DSS, HIPAA, GDPR, Section 508, COPPA, or similar certification is represented unless a current attestation or authoritative evidence is available for the exact scope claimed.
Funding and WIOA statements are program-specific; participant eligibility and authorization remain decisions of the responsible agency.
Accessibility is treated as a tested release requirement, not as a marketing badge that substitutes for production testing.
Reporting tools do not make incomplete or inaccurate source data compliant by themselves.
Security controls must be verified against the deployed application, Supabase policies, and role boundaries before enterprise acceptance.

Review the actual evidence package

Enterprise acceptance should inspect architecture, access control, data flows, audit records, regulatory evidence, credential integrity, accessibility tests, and production health together.

Enterprise Review Request Evidence Review

Acceptance boundaries

These boundaries prevent a buyer, learner, agency, or administrator from mistaking an implemented control for a certification or guaranteed legal outcome.

No SOC 2, PCI DSS, HIPAA, GDPR, Section 508, COPPA, or similar certification is represented unless a current attestation or authoritative evidence is available for the exact scope claimed.

Funding and WIOA statements are program-specific; participant eligibility and authorization remain decisions of the responsible agency.

Accessibility is treated as a tested release requirement, not as a marketing badge that substitutes for production testing.

Reporting tools do not make incomplete or inaccurate source data compliant by themselves.

Security controls must be verified against the deployed application, Supabase policies, and role boundaries before enterprise acceptance.