Skip to Content

Corvus Education

Connect the student journey.
Keep the history intact.

Bring admissions, enrolment and attendance together around an accountable student record.

For education groups, campuses and institutions aligning their academic structure with the people, decisions and records that keep it running.

Admissions and student operations · Teaching and results scope reviewed separately

THE STUDENT JOURNEY

  1. 1
    Application

    Intake, evidence, review and offer.

  2. 2
    Enrolment

    Student identity, placement and permitted relationships.

  3. 3
    Attendance

    The effective roster, leave, confirmation and corrections.

  4. 4
    Academic record

    Defined teaching and results scope, with its own qualification.

Illustrative workflow. Roles, configuration and acceptance are agreed for your deployment.

An institution is more than a student list

Start with a dependable operational foundation.

01

Institutions & campuses

Give each team the right organisational context.

  • Groups, institutions, campuses, facilities and rooms
  • Assigned-campus and enabled-company access
  • Governed configuration, terminology and document scope
02

Academic structure

Make the calendar and curriculum explicit.

  • Years, terms, programmes, grades and subjects
  • Sections, staffing, calendars and timetable context
  • Versioned curriculum and published course offerings
03

Admissions

Track the decision from enquiry to accepted place.

  • Intakes, applications and supporting checklist review
  • Evaluations, offers and controlled seat reservations
  • Invitation-based applicant/delegate experience
04

Student & enrolment

Keep identity separate from changes in status.

  • Canonical student, guardians and relationship history
  • Placement, transfers, suspension and withdrawal
  • Accepted-application conversion and onboarding
05

Attendance & continuity

Record who should be present and what changed.

  • Date-effective rosters, leave and session context
  • Confirmation, locking and controlled corrections
  • Intervention triggers and role-appropriate journey reporting
06

Teaching & results scope

Review later academic workflows as a defined package.

  • Classroom work, assessment banks and grading schemes
  • Moderation, approval and official publication boundaries
  • Examinations, progression and term-close records

From accepted offer to everyday attendance

The next system should not create a second student.

An accepted application already contains reviewed identity and relationship information. Carry that decision into the canonical student, enrolment and placement records, with clear conversion history.

Then use the effective placement and authorised relationships to govern attendance and access. A later transfer or guardian change should preserve the earlier history instead of rewriting it.

OFFER → ENROLMENT → ATTENDANCE

  1. 1
    Review the application

    Confirm the intake, checklist, decision and accepted offer.

  2. 2
    Convert the accepted place

    Create the linked student journey with an idempotent conversion record.

  3. 3
    Activate the right context

    Use the placement, campus, effective dates and permitted relationships.

  4. 4
    Record and correct

    Confirm attendance, preserve locked history and record authorised corrections.

Illustrative workflow. Roles, configuration and acceptance are agreed for your deployment.

Academic evidence and official records

A mark is not yet a published result.

Teaching evidence, calculation, moderation and official publication require different responsibilities and a clear history.

Prepare the evidence

Scope assignments, assessment versions, rubrics, rosters and authorised markers. Restricted questions and private feedback need their own access rules.

Review the decision

Keep calculation inputs, moderation and approval explicit. Contribution from another workflow does not automatically grant official publication authority.

Qualify the package

Teaching and results workflows are available within a defined scope. Full upgrade reconciliation for later phases is not yet complete; we will confirm the supported package and required acceptance checks before deployment.

Expand with a deliberate scope

Do not turn the roadmap into a launch promise.

Student privacy

Use fictional learners in demonstrations. Define guardian authority, restricted documents, campus access and what an applicant or family may see at each stage.

Institutional extensions

Fees, transport, hostels, health, libraries, LMS, mobile/offline and specialist institution packs appear in the wider product roadmap. They require separate scope and readiness confirmation.

Your academic rules

Calendars, assessment, grading, progression, retention and external reporting differ between institutions and jurisdictions. Confirm the rules and responsible reviewers before configuration.

Make the next step specific

Demonstrate the journey your institution needs.

Does this page promise every feature in the master inventory?

No. The master inventory describes a broader product vision. The proposal must distinguish the selected operational package, later-phase features and roadmap extensions.

Can we migrate existing student history?

Start with a redacted data map covering identity, campus, enrolment, guardians, documents and attendance. Agree duplicate resolution, reconciliation and historical acceptance checks before a live migration.

Are public self-service and all guardian access automatic?

No. Portal experiences depend on the selected workflow and explicit current authority. Applicant, delegate and guardian permissions must be reviewed separately.

Bring a workflow.
Leave with a clear scope.

Bring your admission stages, academic calendar and a fictional transfer or attendance example.

Discuss Education ↗

All Industry Apps · Implementation services · Corvus Cloud for Odoo