Architecture & tenancy
Review the multi-service platform model, role separation, tenant boundaries, and deployment architecture.
Government & Enterprise Procurement
Evaluate the platform beyond the sales page.
This center organizes the technical, security, accessibility, implementation, and evidence questions a public agency or enterprise buyer should review before purchase.
Procurement claims are evidence-bound
This page intentionally avoids claiming certifications, uptime levels, outcomes, or regulatory approvals unless those claims are separately supported and approved for public use. Contract commitments should be stated in the executed agreement, not inferred from marketing copy.
Identity & access
Review authentication, role-based authorization, administrative boundaries, and access revocation controls.
Auditability
Lifecycle actions such as enrollment, OJT verification, completion, and credentialing are designed to be recorded and reproducible.
Data ownership
Client data ownership, export expectations, processing responsibilities, and retention requirements belong in the procurement agreement.
Security review
Security questionnaires, encryption controls, incident-response expectations, and third-party dependencies can be reviewed during due diligence.
Accessibility
Accessibility is treated as a procurement requirement and is documented separately from general marketing claims.
Implementation
Implementation scope should define tenant setup, integrations, data migration, roles, training, launch criteria, and acceptance testing.
Support & service levels
Support channels, escalation, availability commitments, recovery objectives, and service levels are contract-specific and should be documented before purchase.
Buyer review checklist
What is public, what requires review, and what belongs in the contract
Review itemAccessWhat it covers
Privacy and data handlingPublic
Collection, use, sharing, retention, payment data, participant rights, and request handling.
Security control descriptionPublic
Identity, authorization, audit logging, encryption, incident handling, and control boundaries.
Accessibility statementPublic
WCAG 2.2 Level AA target, testing approach, accommodations, and barrier reporting.
Platform demonstrationPublic demo
Synthetic personas and example workflows; no production participant information is exposed.
Architecture, data flow, and subprocessorsAuthorized review
Shared during due diligence at the level appropriate to the proposed implementation.
Availability, recovery, and escalation commitmentsContract
Defined in the executed agreement for the purchased scope; not implied by public marketing.
Independent attestations and test reportsOn request
Provided only when a current report exists and the recipient is authorized to receive it.
A public description is not a substitute for a signed service level, completed security questionnaire, current accessibility evaluation, or independent assurance report.
Evidence package
Agency reviewers should be able to request the specific approval notice, registration record, policy, architecture description, security response, accessibility statement, implementation plan, or control evidence applicable to the purchase.
Review regulatory evidenceSecurity & data protection
Security controls and compliance-support capabilities are documented separately from formal third-party certifications. Buyers can review the public security surface and request a tailored questionnaire response.
Review security