Implementation
Start with one class. Prove every handoff.
Implementation begins with a representative workflow and ends with an explicit launch decision—so the effort is visible before registration opens.
Implementation phases
Choose the workflow
Name one program and one class that expose your hardest handoffs.
Leaves you withScope and success criteria
Configure the institution
Identity, roles, terms, programs, locations, policies, and public content.
Leaves you withA reviewable workspace
Rehearse the whole class
Registration, payment, attendance, completion, certificate, and reconciliation—with test data.
Leaves you withEvidence for every stage
Decide together
Owners review the learner experience, operations, finance, accessibility, and security.
Leaves you withA documented go or no-go
Who’s involved
The right people, before they’re blockers.
Every decision has an owner from the first week.
- CE leader
- Owns scope, operating decisions, and launch acceptance.
- CE operations
- Reviews registration, exceptions, policies, and learner service.
- Finance
- Reviews Stripe setup, refunds, reconciliation, and GL mapping.
- Instructor lead
- Rehearses the roster, attendance, grades, and closeout handoff.
- IT & accessibility
- Reviews identity, data boundaries, providers, and accessibility.
Scope
Know what’s included. And what isn’t.
Encore configures
- Institution identity and branded catalog
- Programs, courses, terms, and locations
- Roles, permissions, and policies
- One representative class, rehearsed end to end
Your college provides
- Public content and policy language
- A Stripe account and finance ownership
- Staff access and role assignments
- The launch decision and communications
Not in a first release
- Employer billing and grant draw-down
- Installment plans and SMS
- SSO and SIS integrations
- Data migration tooling
- AI features
Questions
Asked early, answered plainly.
Does Encore replace our student information system?
No. Encore runs the continuing education lifecycle—catalog through certificate. Where handoffs to a credit SIS are needed, they are scoped during implementation.
Who receives the money?
Your college does. Each institution connects its own Stripe account and is the merchant of record for learner payments.
Can the catalog carry our college’s identity?
Yes. Your name, logo, imagery, and page content appear throughout the learner experience, and staff publish their own pages and policies.
What isn’t in a first release?
Employer billing, grant draw-down, installment plans, SMS, SSO, SIS integrations, data migration tooling, and AI features are outside the current product.