Case study · Care-sector training (LMS)

An admin console that lets a training company run its LMS without SQL

This company runs a training platform for care-provider organizations, each with its own brands, divisions, regions and locations. Support, content, compliance and finance staff all needed to change things on the platform, and too much of that work needed an engineer. We built a 28-screen Retool console so they can do it themselves.

The challenge

What wasn’t working

The platform is multi-tenant. Every customer organization has its own settings, feature flags and a hierarchy of brands, divisions, regions and locations underneath it.

Staff needed to add users in bulk, enroll them in learning paths, load courses and quizzes in three languages and keep CEU and state approvals current.

Questions like “who never logged in?” or “what did we bill last month?” meant someone writing SQL.

The solution

What we built

Tenants and hierarchy

Create and edit organizations, their settings and feature flags, and the levels underneath them, with cascading dropdowns.

Users and enrollment

Single and bulk user creation from CSV, admin roles, magic login links, and learning path enrollment and completion.

Bulk content loading

CSV templates for courses, quizzes and learning checks in English, Spanish and Haitian Creole. Files are validated and sent in small batches, with a report of what failed.

Compliance

CEU accrediting bodies, approval windows, state approvals by level of care and a job-title-to-role map with a preview of the training plans it produces.

Reports and NPS

Learner progress reports, a course stats dashboard and NPS analysis by person, course, learning path and admin, all exportable.

Billing view

Daily active learner snapshots with monthly peaks and invoice figures finance can copy straight out.

How it works

How reads and writes are split

  1. 1

    Reads go to the database

    Around 107 SQL queries power the reports, hierarchy lookups and dropdowns.

  2. 2

    Writes go through the API

    Around 32 REST calls to the platform’s admin API create and update records, so business rules stay in the back end.

  3. 3

    Bulk jobs are throttled

    CSV rows are checked in JavaScript, then sent in small batches with a result table.

  4. 4

    Reports export

    Tables export to CSV, and a Retool Workflow handles larger downloads.

Screens

Inside the build

The result

What changed

  • Support, content, compliance and finance staff work without engineering help
  • Reports that once needed SQL are filterable and exportable
  • Onboarding, enrollment and course loading run in bulk from CSV
  • Every write goes through the API, so the platform’s rules still apply

Have a project like this?

Tell us what you need to build. In 30 minutes we’ll map what to build first and follow up with a fixed-scope estimate.

Official Retool Agency Partner5.0 on Clutch, 9 reviewsBuilding software since 2015Reply within one business day