Setup and administration
How should you evaluate Course when choosing course management software?
Choosing course management software means comparing the work your institution does with the records and actions the software actually supports. In Course, inquiries, students, education sales, payment collections, classes, lessons and exam results are managed as connected but separate records.
A feature appearing on a list does not mean every part of the work happens automatically. Look beyond the feature name: check which action creates a record, which decision needs approval and which information you must verify separately.
On this page
Compare Course's features with the work you do
This table summarizes the product's current workflows. Read the relevant page for any need that requires more detail; a feature name alone is not enough to make a purchasing decision.
| Need | Current feature | Limit to consider |
|---|---|---|
| Prospect tracking | Inquiries, advisors, interaction records and dated tasks. | Changing an inquiry status does not automatically reassign every task. |
| Education sales | Product line items, discounts, installment plans and management approval. | A new sale awaits approval; collecting payment is a separate action. |
| Payment collection | Full or partial payments against an installment, with a cash account transaction. | The down payment field alone does not record money received. |
| Lesson scheduling | Placement of classes, teachers, rooms and time slots. | Do not assume travel time or an entire week's schedule is automatically optimized. |
| Exam assessment | Net scores, points and ranking based on answers or subject totals. | These are not official exam scores or national percentiles. |
Match your institution's needs to the current workflows
List the work you need to do.
Use your institution's current processes to identify which records you need to keep, which users need to perform which actions and which results you need to report.
Examine connected records.
Review the transitions from inquiry to student, from student to education sale and from student to class placement. Do not expect these to happen in a single automatic record-creation step.
Check how exceptions are handled.
Read how to correct types of transactions your institution actually encounters, such as partial payments, rejected sales, class changes and incorrect exam results.
Write down unresolved points before deciding.
Clarify data migration, user permissions, required integrations and pricing terms using the product's current screens and the scope confirmed by the team.
What existing data can you import?
Course can import inquiries from Excel and CSV files. It reads the first worksheet and checks required fields, institution matches and duplicate phone numbers. This is not a general migration tool that imports historical sales, payment transactions and attendance from the same file.
List the types of data you need from your previous system separately. If a phone number or identity value has already been corrupted in the file, the import cannot repair it on its own. Assess not only the number of records imported, but also whether each field retained its correct meaning and why any records were skipped.
Clarify your expectations for permissions and automation
Course controls permissions for actions through roles. The data-scope options on the role screen, however, should not be treated as a general institution-wide or user-specific restriction applied to every query. Verify your sensitive-data visibility requirements against the permissions and query behavior that currently exist.
The AI assistant supports certain searches and record actions with previews; it is not general automation that can perform every task on every screen. Likewise, a report displayed in a table is not a substitute for a bank integration or an official accounting output. Check the relevant workflow to determine whether the result you need is actually supported.
Frequently asked questions
Are all records in Course created in one action?
Inquiries, students, sales, payment collections and class memberships are separate stages. Completing one stage does not mean the next has happened.
Does the Excel import migrate the entire previous system?
The current import is for inquiries. Do not assume it also imports sales, cash account transactions and attendance history.
Do the product's features guarantee better results?
No. The features support recordkeeping and carrying out actions. Improvements in enrollment conversion, payment collection or educational outcomes depend on how the institution uses them and on other factors.
Evaluate Course against your institution's workflow
Review the features described on this page in your account, or share your institution's needs with our team.