Continuing Education and Contract Training Software: Why Does Your Credit SIS Refuse to Sell a Course?

Why continuing education divisions end up running a shadow system

A regional manufacturer calls the workforce dean in March. They want 40 supervisors through a leadership series, three cohorts, delivered on site, starting whenever the plant schedule allows, invoiced to accounts payable on a purchase order, with a completion roster back to HR (Human Resources). The dean says yes because that is the business. Then the operational reality begins.

The credit SIS cannot create a course that starts on a Tuesday in the middle of nothing. It wants a term. It cannot invoice a company, because every charge it knows how to make lands on a student account. It cannot allocate 40 seats to an employer and let the employer name the people later, because it has never heard of an employer. So a coordinator builds the cohort in a spreadsheet, takes the names by email, tracks attendance on paper, and asks the bursar to raise a manual invoice against a general ledger account that finance set up in 2019 and nobody remembers the rules for. The revenue is real. The system of record is a folder.

The stack in these divisions is typically Banner or Colleague for the credit side that the division is forced to touch, Modern Campus Destiny One or Augusoft Lumens if the institution has invested, CourseStorm for the simplest open enrolment listings, a Stripe or authorize.net account for card payments, Excel for contract cohorts, DocuSign for instructor agreements, and email for everything else. Destiny One in particular is a serious product built precisely for this problem, and for many divisions it is the right answer. The reason custom builds keep happening anyway is that a self supporting division behaves like a company, and companies outgrow the assumptions of packaged software in ways that show up as revenue you cannot recognise and margins you cannot see.

In continuing education projects we have delivered, the recurring cost is coordinator time reconciling registrations, payments and rosters across three places, plus a standing inability to answer the question every dean of a self supporting unit gets asked: which programs actually make money after instructor pay, room cost and the institution's overhead allocation. Neither of those is fixed by a better public course catalogue.

Problem 1: your courses do not have terms, and everything upstream assumes they do

A CDL prep course starts every second Monday. An online safety certification is self paced with a 90 day completion window. A contract cohort starts when the client's shift pattern allows. A conference happens once. A weekend Spanish class runs six Saturdays. None of that maps onto a fall term with a census date and an add drop calendar, and the credit SIS builds every rule it has on top of those concepts.

The workaround most institutions attempt is a permanent noncredit term, which then breaks refunds because refund windows are per section not per term, breaks reporting because everything falls into one bucket, and breaks scheduling because a term boundary that never closes confuses every downstream integration.

What a custom build does: make the section the unit, with its own start, end, enrolment window, refund schedule and capacity. Refund rules attach to the section as a schedule, meaning full refund until seven days before start, half until start, none after, with an override that requires a named approver and a reason. Self paced sections carry an entitlement window per registrant rather than a section end date. This sounds obvious and it is exactly what the credit SIS cannot express, which is why divisions leave it.

Problem 2: business to business is a different transaction and your systems only know students

Open enrolment is a person with a credit card. Contract training is a company with a purchase order, negotiated per seat pricing that differs by client and volume, seats allocated before names exist, a billing contact who is not the learner, net 30 terms, an invoice that must reference their PO number in the format their accounts payable system expects, and a completion roster returned to their HR system.

Lumens and Destiny One both handle contract training to a degree, and Destiny One handles it better than most. The friction we see is in the details that vary by client: substitution rules when a named employee cannot attend, partial billing when only 32 of 40 seats are used, multi year master agreements with drawdown balances, and consolidated invoicing across several cohorts. Divisions handle these in spreadsheets and then cannot reconcile against the general ledger at year end.

What a custom build does: model the client organisation as a first class entity with agreements, price schedules, seat pools and a drawdown balance. Seats are allocated to the agreement and named later, or substituted with a rule you define. Invoices generate against the agreement with the client's PO reference, post to the correct general ledger account, and reconcile automatically when payment lands. Give the employer a portal to name and swap their people and pull their own completion roster, because the alternative is your coordinator receiving those changes by email at 7pm. In our builds the employer portal is the feature clients notice, and the drawdown balance is the feature finance notices.

Problem 3: you are a business unit with a P and L and you cannot see it

A self supporting division has revenue targets and pays its own costs: instructor fees, materials, room charges, marketing, and an overhead allocation the institution takes off the top. The dean is accountable for the margin. The data needed to compute it lives in the registration spreadsheet, the DocuSign folder of instructor agreements, a room booking system owned by another office, and Banner Finance.

What a custom build does: attach cost to the section. Instructor pay as a contracted amount or a per registrant rate, materials cost, room charge, and the overhead rate finance actually applies. Then margin is a per section fact, and the report your dean has always wanted becomes obvious: which programs clear their costs, which are carried, and which contract clients are unprofitable once you count the custom curriculum development you did not bill for. In our experience this is where divisions find that a marquee program with strong enrolment loses money on instructor pay, and a dull compliance course nobody talks about funds the department. That report changes what the division sells next year, which is a bigger effect than any registration efficiency.

Instructor contracting belongs in the same build. Offer, acceptance, rate, cancellation terms if the section does not run, and payment trigger on completion, all generated from the section rather than typed into a document. It removes a genuine administrative burden and it makes cost data accurate as a side effect rather than as an extra chore.

Problem 4: CEUs, certificates and licensure boards have rules you cannot improvise

The continuing education unit has a defined standard, where one CEU represents ten contact hours of participation in an organised programme under responsible sponsorship. If you are an accredited provider you have record retention obligations and audit expectations attached. Beyond that, licensure driven audiences bring their own requirements: real estate, nursing, engineering, insurance and trades each have state boards with their own reporting formats, provider numbers and submission deadlines, and learners will hold you responsible when their credit does not appear.

Generic registration tools issue a certificate PDF. They do not track contact hours against attendance, they do not carry a provider number per board per course, and they do not submit rosters to a board on a schedule.

What a custom build does: record attendance at the session level, compute contact hours from what actually happened rather than from what was scheduled, and derive CEUs from that. Certificates render from the record with a verification identifier so an employer can check one without calling you. Board reporting becomes a scheduled export per board with the fields they require, and the failures come back into a queue rather than into a learner complaint. Retention rules are enforced by the system, which is what makes an accreditation review a short conversation.

Problem 5: rooms, instructors and the credit side are fighting over the same resources

Your noncredit welding course needs the same lab as a credit section. The credit schedule is built in 25Live or EMS by an office with different priorities and a build cycle that closes months before your client calls. So your coordinator books rooms by emailing someone, and occasionally two classes arrive at the same door.

What a custom build does: integrate with the campus scheduling system rather than replacing it, requesting and holding space through its API where one exists, and modelling instructor availability and qualification so that the same person is not offered to two sections. Where the campus system cannot be integrated, the build maintains its own resource calendar for the spaces the division controls and flags shared spaces as requiring confirmation. That is an honest compromise and it is better than the current state, where the source of truth is a person's memory of an email thread.

What this costs and how long it takes

Across the 2,000-plus projects Digital Heroes has delivered, this is the honest shape. A focused first release, meaning section based course setup with real refund schedules, open enrolment checkout with payment, contract cohorts with agreements, seat pools and invoicing, attendance and CEU tracking, and certificate issuance, runs $70,000 to $150,000 and ships in 12 to 16 weeks. That is a system your coordinators run a live cohort on. A full platform adding an employer portal, instructor contracting with electronic signature, section level cost and margin reporting, general ledger integration, state workforce reporting, licensure board submissions, and campus scheduling integration runs $180,000 to $400,000 phased over 6 to 12 months.

What drives price up specifically here: general ledger integration, because Banner Finance, Workday Financials and PeopleSoft each have their own posting rules and your controller will have opinions that are not negotiable. The number of licensure boards you report to, since each is a separate format and a separate deadline. Grant funded programmes, which carry per participant reporting obligations and eligibility checks that are effectively a second system. State workforce reporting where your programmes sit on an eligible training provider list, because outcome reporting on wages and completion has its own data demands. And whether you need a shared identity with the credit side so a noncredit learner who later enrols for credit is recognised as the same person, which is the right thing to do and is real integration work.

What keeps price down: starting with open enrolment plus one contract client, and leaving board reporting and grant programmes to phase two. Most divisions get their operational relief from those two flows alone.

Build versus buy, and when buying is the right call

Buy if your division is under roughly $800,000 a year, almost entirely open enrolment, with card payments and simple certificates. CourseStorm is inexpensive, competent, and will have you selling next week. Augusoft Lumens is a fair fit for community education divisions with conventional operations, and Modern Campus Destiny One is a genuinely capable product for institutions whose continuing education operation looks like the model it was designed around.

Build when two or more of these are true. Contract and corporate training is more than a quarter of your revenue and you are managing it in spreadsheets. You cannot produce a per section margin and your dean is being asked for one. You report to multiple licensure boards or a state workforce system and the exports are manual. You have a shadow database that a coordinator maintains beside your official system, which is the clearest signal in this category. Or your division is expected to grow into a genuine revenue line for the institution, in which case the constraint is not registration mechanics, it is that packaged tools cannot express the commercial arrangements you will need to sign.

Our position: this is the part of a college that behaves like a company, and it should be run on software that understands companies. Buying is right until the day you sign an agreement your system cannot represent. After that, every month you wait is another spreadsheet that becomes load bearing.

How to choose a developer for continuing education software

Ask them to model a contract cohort on a whiteboard. The right answer has a client organisation, an agreement with a price schedule and a drawdown balance, a seat pool, registrants who may be named later or substituted, an invoice referencing the client purchase order, and a completion roster going back. A developer who draws students and courses has built an ecommerce checkout and is about to learn business to business billing on your budget.

Ask how refunds work when a section is cancelled three days before start with 22 registrants, eight of whom paid by card, ten on an employer invoice, and four with a grant voucher. If they have not thought about refund paths differing by payment source, your coordinators will be doing manual reversals forever.

Ask what general ledger they have posted to and how. Banner Finance and Workday Financials are different problems, and the answer needs to include your controller's chart of accounts and approval expectations, not a claim that integration is straightforward.

Ask who owns the code and the learner records, in writing, before kickoff. You should own the repository, the cloud accounts and the right to hire anyone else to continue. At Digital Heroes the client owns the code from the first commit. Your division's completion records are evidence for licensure boards and employers, and they should not sit in a vendor account you cannot reach.