Provident

Introduction

Provident Platform is a suite of web and mobile products, designed to close learning gaps for every child through tools that are joyful, simple to use, and that integrate seamlessly into schools, virtual learning centres, and homes.

Provident is on a mission to unlock brighter futures for children by delivering engaging, accessible learning tools—thoughtfully designed and rigorously backed by research and evidence.

We’re building AI-native learning tools grounded in Dr. Palko’s interdisciplinary research—drawing on Philosophy, Cognitive Science, Education, Nonlinear Systems Theory, and Theory of Language—and supported by expert literacy, early childhood, and pedagogy specialists across the US, the UK, and Ireland.

Platform at a glance

Provident is made up of a few core parts. You don’t need to understand everything upfront—this is just the mental model.

Provident Web Portal

The web portal is where administrators and educators typically:

Set up an organisation (workspace), schools/sites, and cohorts/classes
Manage users and roles (e.g., Admin, Educator/Coach)
Assign learning experiences and review progress
Configure policies and (where available) integrations

Provident Learner Apps

Learner-facing mobile/tablet apps are where children do the learning. They’re built to be:

Engaging and accessible (clear flows, low friction)
Consistent across contexts (school, centre, home)
Supportive of adults (educators/guardians can understand what’s happening)

Learning Content and Evidence Layer

Provident learning experiences are structured so they can be:

Sequenced into pathways (what a learner should do next)
Measured (what we observed, not just what was “completed”)
Improved over time via research and iteration

Personalisation and AI Systems

Personalisation in Provident is designed to be:

Grounded in evidence (observable performance and learning signals)
Pedagogically aligned (supports, not replaces, sound instruction)
Transparent (adults can understand recommendations and progress)

Tip: If you’re evaluating or integrating Provident, start with the learner journey first, then map the admin and data needs around it.

Quick start checklist

1) Create your workspace

Create an organisation/workspace in the web portal
Add your first site (school/centre) and set basic settings (age ranges, cohorts, etc.)

2) Add your team

Invite Admins (deployment + configuration)
Invite Educators/Coaches (day-to-day learner support)
Confirm permissions and access boundaries

3) Add learners and structure

Create cohorts/classes/groups
Import learners (manual entry or bulk import, depending on your setup)
Assign learners to the right groups

Install the Provident learner app(s) on the intended devices
Sign in with the learner method used in your deployment (codes, credentials, SSO—depending on configuration)
Run a short “first session” to confirm audio, accessibility, and basic navigation

5) Assign learning and start a pilot

Assign an initial learning pathway (or starter programme)
Run a small pilot group first (recommended) to validate:
- login flow
- device readiness
- classroom/centre routines
- reporting expectations

6) Monitor progress and iterate

Review engagement and progress in the web portal
Capture educator feedback (what worked, where friction appeared)
Adjust groupings, assignments, and routines as needed

Terminology

A few terms you’ll see throughout the docs:

Workspace: Your organisation’s environment in Provident (settings, users, sites).
Site: A school, centre, or deployment location inside a workspace.
Cohort/Class/Group: A set of learners managed together (for assignment and reporting).
Pathway: A sequenced learning experience (what a learner does over time).
Session: A learner’s active use period (a “sitting” of learning).
Signals/Evidence: The observable learning data used for reporting and personalisation.

Next steps

Once you’ve completed the checklist above, continue with:

Platform overview and roles (how Admins/Educators/Learners fit together)
Deployment guide (devices, onboarding routines, accessibility considerations)
Content and pathways (how learning experiences are structured and assigned)
Reporting and progress (what to expect from dashboards and learner views)
Integrations (if applicable to your rollout)
API reference (if you’re integrating programmatically)

Support and feedback

If you find anything confusing, please share feedback via GitHub Discussions:
https://github.com/providenthq

Quick Start