Institution and academic structure
Prepare campus names, academic years and terms, classes or programmes, sections, courses, and teaching responsibilities. These records give admissions and everyday operations a consistent context.
IMPLEMENTATION GUIDE
A considered start. A more confident first term.
Move from separate records to connected working practices with a rollout your institution can understand, own, and check.
Institution-aware workflows Role-based access
Built around your people.
A CLOSER LOOK
Start with a working agreement.
Successful implementation begins with decisions: who owns each record, who can approve changes, which academic period is active, and what a complete transaction looks like. Use a bounded first rollout to check those decisions with the people doing the work.
People and permissions
Identify the institution owner, administrators, teaching staff, finance users, and approvers. Match their responsibilities to the appropriate scope, rather than giving everyone administrative access.
Data quality before import
Check identifiers, duplicate learners, active enrollments, guardian relationships, and required fields before importing records. Use available student validation results to correct rows before a governed import.
A launch you can verify
Walk through real operating examples with authorized staff: an admission, a class session, a fee record, or an exam cycle. Check the relevant documents and the next person’s view before widening access.
HOW IT WORKS
Four stages, with clear ownership.
The sequence is a planning guide; agree dates and responsibilities for your institution.
- 01
Discover
Define your current processes, initial modules, decision owners, and success criteria.
- 02
Configure
Set up institution identity, academic masters, roles, plan scope, and provider settings that are actually needed.
- 03
Rehearse
Validate prepared data, review sample records, and practice each approval and exception path with the responsible staff.
- 04
Launch and review
Activate the agreed workflows, communicate support routes, and review outstanding exceptions with named owners.
BEFORE YOUR FIRST WALKTHROUGH
Bring the details that shape the rollout.
A focused preparation pack makes the discussion more useful without sharing sensitive student records.
A structural overview
Institution type, campuses, approximate learner and staff numbers, academic calendar, and the programmes or classes in scope.
A workflow priority list
The first three processes to improve, current handoffs, approval responsibilities, and the exceptions that consume time.
A data and service inventory
The formats your records are in, who maintains them, and which existing payment or communication providers need evaluation.
COMMON QUESTIONS
A few details
worth getting right.
Questions about your institution’s exact setup? Prepare a focused request.
Find the right contact routeDo we need to move every module at once?
A staged rollout can start with a defined set of capabilities. Agree the dependencies between them so that admissions, student placement, attendance, and finance do not rely on missing master records.
Can we upload our existing spreadsheets?
Student bulk operations include validation and governed import for supported fields. Review your files against those fields first; not every legacy format or record type has an automatic importer.
What should our staff verify before launch?
Check their sign-in and institution context, assigned classes or records, approval responsibilities, sample document downloads, and the support path for a blocked task. Use authorized sample data for rehearsal.
BUILD A CLEARER OPERATING DAY