Skip to documentation
OneClickRooms Documentation OneClickRooms School ERP
Students and Parents

Student Separation and Readmission

School ERP is the school management product in OneClickRooms Education ERP Solutions. The other product is Higher Education ERP.

Submit and review School Leaving Certificates, manage clearances and Principal approval, configure signatures, record handover, verify certificates, and handle student separation and readmission in School ERP. Use Student Archive to search and read former student profiles within one campus.

School ERP keeps voluntary school leaving, administrative separation, and readmission linked to the student's enrollment history. The School Leaving Certificate remains the parent- and student-facing route for a voluntary departure; Student Lifecycle handles the recorded departure, clearance, administrative cases, and any later return.

Request and issue a School Leaving Certificate

A student or linked parent opens School Leaving Certificates from the hamburger menu, selects the student, and submits the leaving details. A parent with more than one linked student must work in the correct student's context. Dates on this page, including the requested leaving and handover dates, use the institution's configured date format. The financial eligibility check is per student: an outstanding balance blocks that student's self-service request, while a linked sibling whose account is clear can still submit. Resolve the affected student's balance in My Finances. Authorized staff can follow the staff-managed request route.

  1. Submit the request. Provide the requested leaving date, reason, and any other requested school details. The student and linked parent receive a queued email update when the request is submitted.
  2. Complete school clearances. The responsible offices record their clearance decisions for the student's academic record, finance account, library, transport, and accommodation. Each clearance can be saved on the request page; a success message confirms the save without a full-page refresh. The Principal reviews the recorded results. If an item remains outstanding, the approval note must explain how it will be handled.
  3. Review and approve. When a request is submitted or resubmitted after corrections, the assigned-campus Principal receives an unread badge at Hamburger menu > My Tasks > School Leaving Certificates. Open the request, review its details and clearances, enter the approval note, and select a required Character and conduct assessment: Excellent, Good, Satisfactory, Needs Improvement, Unsatisfactory, or Other. Selecting Other requires a written assessment. The selected wording is included naturally in the certificate. The student receives an unread badge when the request is returned for correction, declined, or approved and issued. The student and linked parent are emailed when the school accepts the request for review, returns it for correction, declines it, or approves and issues it.
  4. Issue the certificate. Before issuing for a campus, the Principal must save a signature for that campus. The issued PDF uses the institution's name and its configured logo and address as the letterhead; it includes the student and departure details, the Principal's saved signature, and a QR code opposite the signature.
  5. Verify the certificate. Scan the QR code to see whether the certificate is genuine and currently valid. The public verification page shows the student, school, campus when available, certificate number, issue date, and leaving date. It does not show clearance notes, balances, or other private workflow details. The student and linked parent receive a queued email update when the request is approved and issued.

Record certificate handover

After a certificate is issued, authorized school staff can record its handover on the request. Enter the recipient and delivery method, and record the handover date using the institution's configured date format. The student or linked parent can also confirm receipt in the authenticated portal. The handover is added to the request's activity history.

Set up a Principal signature

The Principal opens the profile menu, expands Settings, and selects My Signature. Select the campus whose certificates will use the signature, then upload a clear PNG or JPEG image under 2 MB. A transparent background is preferred; the system scales the image proportionally to fit the certificate. Signatures are saved per campus, so repeat the setup for each assigned campus that issues certificates. After saving, the modal closes and a success message appears.

Configure readmission

An Institution Admin opens System Settings > Student Separation & Readmission and enables or temporarily closes readmission requests. Set the one-time Readmission Processing Fee, payment due days, whether the processing fee is refundable, and the conditions for a refund. Use 0 for no processing fee. Configure the fee's tax treatment in System Settings > Tax Settings. Applicable admission charges configured for the requested grade or class, board, and academic term can also be included before review. A refundable setting records the institution's policy; Finance still reviews and processes an approved refund through the finance workflow.

Select whether the initial review goes to the target Campus Admin or Institution Admin. The Principal assigned to the target campus is the final authority for readmission and administrative separation. Review campus assignments and notification recipients before opening cases.

Record a voluntary departure through School Leaving

A student or linked parent starts a voluntary departure using the existing School Leaving Certificate request. The request follows its school leaving verification, approval, and clearance process. When departure is finalized, Student Lifecycle links the completed School Leaving Certificate and its recorded clearance outcomes to the student's separated enrollment episode. Use the School Leaving Certificate history to review that original process.

Academic completion or graduation follows the school's completion process; it is not treated as a departure for this readmission workflow.

Open an administrative separation case

  1. An authorized campus or institution administrator opens Hamburger menu > Administration > Student Lifecycle and selects New Separation Case.
  2. Select the campus and active student. Choose Administrative withdrawal or Disciplinary dismissal, enter the reason category and explanatory details, and set the effective date using DD-MM-YYYY.
  3. The case creates five clearance tasks: Academic Record, Finance Account, Library, Transport, and Accommodation. The responsible campus offices record Cleared, Not applicable, or Outstanding. An outstanding result must include an explanatory note.
  4. When all clearance tasks are cleared or marked not applicable, the case moves to the campus Principal for a final decision. The Principal can approve or decline with a recorded reason. The person who opened the case cannot approve it.
  5. If the approved effective date is in the future, the case remains scheduled until that date. When the separation takes effect, the current enrollment episode is closed, term enrollment history is retained as withdrawn, and the student profile becomes inactive.

Student and parent access while separated

The student continues using the same credentials. Before the effective date, normal access remains available. Once separation takes effect, server-side authorization restricts ordinary student pages and APIs. The student can still open Student Lifecycle and My Finances to request readmission, follow the case, review the fee notice, and submit payment evidence.

A parent's account is not disabled because one child is separated. The parent can keep using the Family Dashboard for other linked children and can select the separated child to request or follow that child's readmission. This case does not give a parent access to unrelated students.

Submit a readmission request

After a departure is recorded and the institution has enabled requests, the student signs in with the existing account or a linked parent selects the correct child. In Student Lifecycle, choose the target campus, an active academic term at that campus, and the requested grade or class. Explain the reason for returning. The available campus, term, and class must belong to the same institution and destination campus. Only one open readmission request is allowed for a student at a time.

Readmission invoice and payment

When the processing fee or applicable admission fees are due, OneClickRooms creates the corresponding student finance charges and tax lines and sets the request to Awaiting payment. The student or parent working in the selected student's context opens My Finances and submits evidence against the fee notice. The request is not sent for review merely because evidence was submitted: Finance must verify and post every required charge first.

If no charges are due, the request can go directly to the intake review. If evidence is rejected or an amount remains outstanding, resolve it through My Finances. Any refund is handled by Finance under the saved refund conditions and normal finance controls; the portal does not automatically pay out a refund.

Initial review, Principal decision, and placement

  1. After all required payment is verified, OneClickRooms sends the request to the intake role selected in System Settings: the target Campus Admin or Institution Admin. That reviewer starts the initial review and checks the requested campus, term, class, and reason.
  2. The target-campus Principal makes the final decision. Approval moves the case to placement pending; a decline records the reason and keeps the prior enrollment history unchanged.
  3. After approval, Campus Administration completes placement into the requested campus, term, and grade or class. Approval by itself does not restore the student's access.
  4. When placement is saved, OneClickRooms creates a new active enrollment episode linked to the previous departure, updates the student's academic context, and restores normal student portal access.

Emails and auditable actions

Lifecycle emails are queued for the student, linked parent contacts, and relevant staff as the request or invoice is created, payment is verified, clearance tasks are updated, the Principal decides, and placement is completed. Standard mail delivery still needs to process each queued message.

Student Lifecycle keeps the case timeline, status changes, and the name of each person who acted. Authorized staff can open a linked person's information card from an actor name. Campus staff see cases only in their assigned campus scope; Institution Admin access remains within its institution.

Find former students in Student Archive

Academic > Manage Students now separates the everyday roster into Current Students, Suspended, and Student Archive. Current Students contains active students. Suspended students remain in their own view. The archive is a campus-scoped way to search and read former student records; it keeps the existing student profile and history rather than creating a duplicate record.

  1. Open Student Archive and choose one Former Campus that is within your role's access. The archive search requires a campus and shows former students for that campus only. Institution Admins remain within their institution; campus roles cannot search another campus by changing a filter or request.
  2. Use the quick search to find a person by name, student record ID, roll number, registration number, email, or mobile. For academic narrowing, expand Advanced Search and select the relevant Board or Class. Choose the former campus in the archive panel; it remains the boundary for the archive search. Narrow the result by Exit Outcome or Departure Date, then select Apply. Use Reset to clear the archive filters. Results show the former campus, outcome, departure date, and last academic term. Dates use the format configured in System Settings. A record without a saved departure date displays Not recorded.
  3. Interpret the archive outcome carefully: Graduated identifies a completed student record with graduated status; Confirmed Separation identifies an inactive student linked to a completed separation case; Needs Review identifies an older inactive record with no completed separation case linked to it. Needs Review does not determine why the student left.
  4. Open View Profile to review the historical record. Profiles opened from Student Archive are read-only. If a legacy inactive record needs a verified reason or effective date, review the supporting school record and record the outcome through the appropriate Student Lifecycle process; do not guess or classify it as a confirmed separation.

Student Archive is for finding and reviewing former students. Suspended, inactive, and graduated students are excluded when a new event audience or class schedule recipient list is resolved. The archive preserves historical academic details for authorized staff.

Example: A student leaves the Islamabad campus after an approved separation case takes effect. A campus administrator selects Islamabad in Student Archive, searches by the student's roll number, and sees Confirmed Separation with the recorded departure date in the school's configured date format. The administrator can open the read-only profile to review the last academic term. The student will not be included in a new event audience or class schedule recipient list. If the record is only marked Inactive and has no completed separation case, it appears as Needs Review until staff verify the institution's records.

For quick answers, visit School ERP Support.