Cont.Ed Continuing education, end to end
See it running Bring your rulebook
Author · Purchase · Grade · Track · Certify · Advertise

One system for the whole life of a school.

Instructors record. Learners buy and finish. The system grades, files every hour against the requirement it satisfies, and issues the certificate. Then it shows each learner the course that closes their next gap. Cont.Ed runs that loop for any program that has a set of requirements and a way to meet them.

Walk the lifecycle See the first school
Security and guard training Imaging and clinical technologists Trades and apprenticeships Bodywork and wellness practice Any board with a rulebook
The Cont.Ed lifecycle loop Six stages drawn as a loop: Author, Purchase, Grade, Track, Certify, Advertise. Advertising feeds back into Purchase because each learner's remaining gaps become recommendations. gaps becomerecommendations Author 01 Purchase 02 Grade 03 Track 04 Certify 05 Advertise 06
The loop closes on its own. A finished record shows what is still missing, and the catalog answers.
Who is in the room

Five kinds of people. One record.

learners

Learners

Own their account and their record. Buy courses, finish them, watch the requirements fill in, and decide who gets to look.

instructors

Instructors

Get a link, not a login. Record and assemble a course in the browser. Grade the work only a human should grade.

staff

School staff

Invite, review, price, publish. Run enrollments, refunds, support, and the mailing list from one console.

supervisors

Supervisors and mentors

See a learner's progress through a portal or a read-only link the learner can revoke. Verify what they supervised.

partners

Advertisers and providers

Apply, get reviewed, and place courses or openings where learners with a matching gap will actually see them.

01

Author

Record it once, in the browser, from a link.

  • The invite is the workspace. Staff send an instructor a link. It opens a studio scoped to that one course. No account to create, nothing to install.
  • Record camera, full screen, or a dragged region. Or upload the recording you already made in Zoom, Meet, or a slide export. Takes land in a library on the right.
  • Cut on a filmstrip timeline. Trim by dragging edges, split at the playhead, reorder by hand. Nothing is re-encoded until it ships, so edits are instant.
  • Start from a template. A 45-minute talk with a quiz and a reflection. Three 15-minute segments with checks between and a final exam. Or your own structure, with sections and tabs for each.
  • One shared block library. Slides, video, quiz, reflection, discussion, assignment, lab, embedded outside video, downloadable resources. New block kinds arrive as data, not as a redeploy.
  • Hours are tagged at the source. Each unit says which requirement categories it earns hours in and how many. The running total checks itself against the course credit.
  • Staff review unit by unit, nudge the stragglers with a recorded reminder, and publish into the catalog with the price attached.
02

Purchase

A public catalog. A free account. Pay per course.

  • Published courses show on your school's front page to anyone. No login to browse, no membership to buy.
  • Price per credit or per course. Make introductory courses free. Sell bundles and series as a set, and the system divides the revenue across the member courses by credit.
  • Checkout runs on your own Stripe account. Receipts, refunds, saved cards, and the customer portal come with it. Switch between test and live catalogs from the staff console.
  • Add-ons ride the same checkout. An optional membership for the hours tracker, or an elective second credit type on the certificate, each as a line item the learner chooses.
  • Presenters get paid from real numbers. Net of processing fees, split by the rule you set, rolled up by quarter, exportable.
  • Enrollment lands when the payment clears. The webhook is signed, idempotent, logged, and replayable, so a retry never enrolls twice and a hiccup never loses a sale.
03

Grade

The system grades what it can. Instructors grade what matters.

  • Quizzes are graded on the server. The answer key never reaches the learner's browser. Attempt limits are enforced where they are set, not in the page.
  • Video unlocks completion only after it has been watched. The player seals a unit when the recording actually ends, not when the tab was opened.
  • Reflections, discussions, and assignments leave a submission record. Instructors accept, grade, or return for revision. Self-grading is not expressible, by construction.
  • Participation gates completion. Lectures, quizzes, reflections, and the course evaluation, in order. A course is done when the rules say it is, not when a button is clicked.
  • Evaluations are collected before the certificate issues, so the school hears from every finisher.
  • Every attempt and every grade is retained for the review window your board expects, and staff can retrieve it on request.
04

Track

Every hour filed against the requirement it satisfies.

  • Requirements are data, not code. Categories, minimums, per-area caps, live-versus-recorded ratios, supervised-practice hours, durations, prerequisites. If a board can write it down, the engine can load it.
  • Completed courses file themselves. The hours tagged at authoring land in the learner's record the moment the course completes. Outside training is logged by hand with evidence attached.
  • Coverage you can see. A ring for the whole credential, a treemap for the categories. What is done, what is left, what would overflow a cap.
  • Bring the past with you. Bulk upload prior training and attach the paperwork.
  • Supervisors and mentors see the record, through a portal or a read-only preview link that needs no account. The learner issues it and can revoke it.
  • One hour counts once. When a learner works toward more than one credential, the engine knows which requirements a course can satisfy and never double-counts.
  • Monthly progress email and a transcript export as PDF, ready for an application.
05

Certify

The certificate is the last gate, not a download button.

  • Issued only when the completion rules are met. Watched, answered, reflected, evaluated. Then, and only then, the PDF.
  • The syllabus rides along. Credit hours, category breakdown, and the course outline appended in the format a reviewing board expects to see.
  • Numbered, stored, re-downloadable. Certificates live with the learner's record and stay there through the retention window.
  • The record travels. A full transcript export, and preview links that let a reviewer walk the record with the evidence under each entry.
  • Templates belong to the school. Your name as issuer, your seal, your wording. The system fills in the rest.
One course, start to finish

What actually happens, in order.

  1. Staff invite an instructor
    2. →
  2. Instructor records and assembles
    3. →
  3. Staff review and price
    4. →
  4. Published to the public catalog
    5. →
  5. Learner creates a free account and buys
    6. →
  6. Enrolled on payment
    7. →
  7. Learner watches, answers, reflects
    8. →
  8. Quizzes graded, video sealed
    9. →
  9. Instructor grades the assignment
    10. →
  10. Evaluation collected
    11. →
  11. Hours filed against requirements
    12. →
  12. Certificate issued
    13. →
  13. Supervisor verifies the record
    14. →
  14. Remaining gaps surface the next course

Solid outline: a person does it. Dashed outline: the system does it, and writes it down.

What runs underneath

The parts nobody puts on a brochure.

Roles and access

Learner, instructor, staff, supervisor, advertiser. Every table is guarded row by row, so a lecturer sees their own roster and a student sees their own record, whatever the page asks for.

Staff console

Users, enrollments, refunds, support tickets, bug reports with screenshots, email templates, usage, analytics, and the payment-environment switch. One login.

Email that behaves

Transactional mail from your own sending domain. Queued, templated, tracked, with one-click unsubscribe and automatic suppression of addresses that bounce.

Payments you can audit

Signed webhooks, an event log, refund history, and purchase records that carry the fee and split for every sale. Test and live catalogs side by side.

Records that hold up

Attempts, grades, completions, certificates, and the audit retention a board asks about, kept past the point where a learner deletes their account.

Requirement schemas

A credential is a document: categories, minimums, caps, ratios, durations, conditions. Validated before it loads, versioned when the board changes its mind.

Run it as your school

Your name on the door. Your rules inside.

yourschool.conted.io

Your own address

Each school runs on its own subdomain with its own data. Nothing is shared with the school next door.

your Stripe

Your payment account

Sales settle to you. Refunds, payouts, and tax reporting are yours, not routed through a middleman.

your domain

Your sending address

Receipts, certificates, and reminders arrive from your school, verified on your domain.

your rulebook

Your requirement schema

Bring the board's requirements. We load them as data and the tracker, the certificates, and the recommendations follow.

The first school on Cont.Ed is open.

A clinical credentialing institute runs the full loop today: authoring, catalog, grading, tracking, certificates, placements.

See it running
Start here

Bring your rulebook.

If your program has a set of requirements and a process for meeting them, the loop already fits. Send the requirements document and we will load it as a schema and show you the tracker filling in.

Send us your requirements See the first school