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
Corvus Education
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
Intake, evidence, review and offer.
Student identity, placement and permitted relationships.
The effective roster, leave, confirmation and corrections.
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
Give each team the right organisational context.
Make the calendar and curriculum explicit.
Track the decision from enquiry to accepted place.
Keep identity separate from changes in status.
Record who should be present and what changed.
Review later academic workflows as a defined package.
From accepted offer to everyday attendance
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
Confirm the intake, checklist, decision and accepted offer.
Create the linked student journey with an idempotent conversion record.
Use the placement, campus, effective dates and permitted relationships.
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
Teaching evidence, calculation, moderation and official publication require different responsibilities and a clear history.
Scope assignments, assessment versions, rubrics, rosters and authorised markers. Restricted questions and private feedback need their own access rules.
Keep calculation inputs, moderation and approval explicit. Contribution from another workflow does not automatically grant official publication authority.
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
Use fictional learners in demonstrations. Define guardian authority, restricted documents, campus access and what an applicant or family may see at each stage.
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.
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
No. The master inventory describes a broader product vision. The proposal must distinguish the selected operational package, later-phase features and roadmap extensions.
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.
No. Portal experiences depend on the selected workflow and explicit current authority. Applicant, delegate and guardian permissions must be reviewed separately.
Bring your admission stages, academic calendar and a fictional transfer or attendance example.
All Industry Apps · Implementation services · Corvus Cloud for Odoo