Operations guide
From admission request to student record: how should a school organise the journey?
A practical journey connecting the request, review, guardian, student record, enrolment and financial plan without repeated entry.
- Written by
- Raqeem content team
- Product review
- Raqeem product team
Direct answer
A controlled admission journey keeps the application separate while it is reviewed, completes or links the guardian, and only after acceptance creates the student record and enrolment for the selected year, level and class. The financial plan and first collection may then be added without leaving the request open or creating duplicate records.
Guide method and boundaries
This guide reflects capabilities reviewed in Raqeem at the stated revision date. It separates available functionality from planned work and does not claim external certification, integration or synchronisation without published evidence.
1. Receive the request without creating a student too early
The application remains a reviewable request containing the candidate’s details, contact information and available documents.
This separation avoids adding every applicant to the active student register before an admission decision.
2. Review and complete the guardian record
The school checks information, documents and possible duplicates, then links an existing guardian or creates a correct record when needed.
Family relationships should remain explicit without copying the same data into several places.
3. Accept and create the student record and enrolment
After approval, useful application data populates the student record instead of being typed again, and an enrolment is created for the selected academic year.
The level and class follow the actual decision, and the request is marked as converted so it no longer appears open.
4. Add the financial plan and first collection
Once enrolment exists, the school can attach the appropriate financial plan and record an initial collection when required, with the related receipt.
The plan, collection and receipt remain separate records linked to the correct student or family context.
Journey controls
- Check duplicates before student creation.
- Reuse application data instead of retyping it.
- Link the guardian and family relationships correctly.
- Create one valid enrolment for the selected year.
- Close the application state after conversion and verify the financial plan.
Related questions
Does accepting an application always create the student automatically?
Conversion should be a clear, controlled action. It may happen with acceptance or immediately afterwards, but it must prevent duplicates and record the correct state.
What happens when the guardian already exists?
The existing record should be linked after verification rather than creating a duplicate guardian.
Is the first collection part of the application?
It may be completed at the end of the journey, but it remains a separate financial operation linked to enrolment and the financial plan.
More guides on the student journey
From admission request to student record, including data preparation and files prepared for Massar upload.
How can a school connect admission, enrolment, finance and follow-up in one journey?
A connected journey from the admission request to academic, financial and administrative follow-up without unnecessary repeated entry.
How should a school move from Excel or a legacy system to Raqeem?
A practical plan to inventory, clean, test imports, reconcile results and launch gradually without disrupting school work.
Raqeem and Massar: what is the actual relationship?
A precise explanation of how Raqeem supports Massar-related work, including files prepared for upload without claiming direct synchronisation.