Skip to content
All capabilities Buyer guideReviewed catalogue guide

Student lifecycle guide

Student Management

Connect an authorised student record to class and section allocation, documents, identity, promotion and reviewable reporting across the school lifecycle.

Scope note: This page is an evaluation guide, not a separate entitlement. This guide connects existing student capabilities; it does not turn separate authorised steps into an automatic admission or promotion decision.

Guided product passage

See the workflow and what it produces.

Move manually between a visual product-story context, the reviewed workflow and a route-specific outcome. Where a current renderer or route capture exists, Outcome keeps it beside the clearly illustrative summary.

Connected school workbenchOne complete view · three linked focus windows
Complete conceptual workspaceMain screen
Illustrative responsive family portal for attendance, homework, fees and school updates.
Attendance at a glance
Homework status
Family notices

Family-side outcome of a connected student record. Homework statuses shown in the visual are school-recorded; it does not imply learner self-upload.

Illustrative product-story gallery · synthetic sample data · not a live customer screen The complete product-story frame is shown unfiltered, with three labelled crops from that same frame. It explains related context rather than claiming to be a live or exact product screen; theme selection changes only the surrounding website chrome.

The work, stage by stage

Follow the work, not a menu.

Where a reviewed catalogue route directly explains a stage, it is linked below. Some shipped capability stages do not have a separate public catalogue page.

  1. Stage 01Create or approve the student recordAn authorised admission or registration workflow creates the student record after the applicable review.Student Admission Enquiry Management
  2. Stage 02Allocate the learnerAssign the student to the intended class and section, then preserve that structure for connected academic work.Class Management Section Management
  3. Stage 03Maintain evidence and identityManage permitted documents and produce the applicable school identity artifact through their dedicated workflows.Document Management ID Card Management
  4. Stage 04Review progress and advance the yearUse scoped reports and the authorised promotion workflow rather than changing lifecycle state informally.Student Reports Student Performance Promotion Management

Product and rollout boundary

What the school gets — and what it must confirm.

Included

  • Governed student record lifecycleCreate, review, allocate and maintain the record through role-scoped product workflows.
  • Class, section and document contextKeep the structure and permitted evidence needed by academic and administrative teams.
  • Identity, progress and promotion linksEvaluate each linked capability on its own canonical page before rollout.

Not included, or set up separately

  • Not one automatic end-to-end decisionAdmission, document review, allocation and promotion retain their own authorised actions.
  • No arbitrary admission form promiseThe public registration and enquiry flows are reviewed separately from the general Custom Forms capability.
  • Access follows assigned roles and record scopeA guide relationship does not give every user access to every linked student record.
Who typically uses it
  • Admissions team
  • School office
  • Class teachers
  • Academic coordinators
  • Authorised administrators

Evaluation questions

Know the boundary before rollout.

Plan, provider, role and data dependencies are confirmed for your school during the review.

Does an application create a student immediately?

No. The reviewed registration or admission path creates the student only after the applicable authorised step.

Can the school import existing students?

A reviewed CSV/XLSX student migration path exists. Its supported columns, validation and rollback conditions are confirmed before rollout.

Are student documents verified automatically?

No. The document workflow supports authorised request, upload and review states; it does not make an admission decision.

Is every lifecycle step included in every plan?

No. Plan scope, release status, user permissions and migration requirements are confirmed against the canonical capability pages and written proposal.

Review it in your school context

Map student management to your current process.

Bring your current roles, records, providers and rollout questions. We will walk through the applicable product routes and the boundaries that matter.