Skip to content
Qentak — The Education Operating System

Admissions & Student Lifecycle

Transfers & Withdrawals

Handle a change of school with care and clarity.

Coordinate academic records, clearance and enrollment changes when a student moves or leaves an institution.

Try the workflow
School adviser welcoming a relocating family in a library
THE PEOPLEA coordinated exit request

Capture the reason, destination where appropriate, effective date, and responsible registrar.

01 / 03

START WITH THE ACTUAL WORK

Why connect transfers & withdrawals?

A student leaving touches academic records, fees, learning access, and services. An informal email chain leaves the family and staff uncertain about what is complete.

WHAT THIS CAPABILITY BRINGS TOGETHER

Transfers & Withdrawals: records, decisions, and handovers.

01

A coordinated exit request

Capture the reason, destination where appropriate, effective date, and responsible registrar.

02

Departmental clearance

Bring finance, library, residential, and academic follow-ups into a visible checklist.

03

A considered record handover

Prepare the approved records and track what was released, when, and to whom.

FOLLOW THE WORK FROM START TO FINISH

Explore the transfers & withdrawals workflow.

This interactive illustration explains the operating model. It contains no live institutional records.

Student journey workspaceIllustrative preview
DEMONSTRATION RECORDTransfers & WithdrawalsAssigned to the responsible team
A coordinated exit requestTransfer and withdrawal categories
In focus
Departmental clearanceClearance responsibilities and exceptions
Next
A considered record handoverEffective-date and record-release requirements
Next
STEP 1 OF 4

Receive a transfer request

The registrar receives the request and confirms its effective date.

A WORKED EXAMPLE · ILLUSTRATIVE SCENARIO

A leaving date is an institutional handover

A family gives notice while the learner still has library items, a transport allocation and an academic report in preparation. These responsibilities end on different schedules.

The decision and its context

Record the approved last attendance date and assign clearance tasks to their owners. Resolve any record-release requirements with the registrar rather than treating every outstanding operational task as permission to withhold a record.

What a complete outcome looks like

Confirm which services end, which records remain, and what is released to the receiving institution. Keep the destination and release authority with the handover.

FOLLOW THE HANDOVERTranscripts & Academic RecordsThe registrar can prepare an authorized academic record for the next institution.

A CAPABILITY, NOT AN ISLAND

Connect transfers & withdrawals with the next workflow.

The same institutional context should support the next responsible team’s action. Explore the connected capabilities.

YOUR INSTITUTION’S RULES

Set the rules for transfers & withdrawals.

  • Transfer and withdrawal categories
  • Clearance responsibilities and exceptions
  • Effective-date and record-release requirements
Explore configuration and flexibility

WHEN THE DAY DOESN’T FOLLOW THE DEFAULT

A clearance item is disputed

Keep the dispute and decision visible to the authorized owner without silently changing the student’s exit date.

A clear exception keeps the reason, owner, and next decision visible.
Registry colleagues arranging pathway cards, a tablet and document folders on a deskTransfers & WithdrawalsA coordinated exit request → A considered record handover

SEE HOW THE WORK CONNECTS

Transfers & Withdrawals

Registrars · Finance · Student services. Capture the reason, destination where appropriate, effective date, and responsible registrar.

  1. 01

    A coordinated exit request

    Capture the reason, destination where appropriate, effective date, and responsible registrar.

  2. 02

    Departmental clearance

    Bring finance, library, residential, and academic follow-ups into a visible checklist.

  3. 03

    A considered record handover

    Prepare the approved records and track what was released, when, and to whom.

Illustrative workflow · Shape the details around your institution.

AUTOMATION WITH A PURPOSE

When the exit is approved.

Use an agreed trigger and response while keeping the responsible person in the decision.

WHEN

The exit is approved

THEN

Coordinate end dates for classes and services and flag the required financial review.

How connected workflows work

APPROPRIATE CONTROL

Who can act on transfers & withdrawals?

Record releases require authorized recipients and applicable consent. A financial balance and the right to receive an academic record must be considered under the institution’s governing rules.

Explore security and institutional control

KNOW WHETHER THE CHANGE IS HELPING

Handover completeness

Review unresolved clearance items and the time from an approved request to the completed record handover.

Agree the baseline, reporting period, and owner before comparing results.Connect evidence to decisions

SEE IT IN YOUR CONTEXT

Different institutions. Specific responsibilities.

A practical introduction

Bring a representative workflow, one recurring exception, and the people who own the handoffs.

Plan your implementation

BEFORE THE CONVERSATION

Useful questions about transfers & withdrawals.

Can an approved withdrawal be corrected?

Corrections need a recorded reason, authorized approval, and a review of the enrollment, billing, and service dates affected by the change.

How does this connect to the rest of the student journey?

The approved student identity, intake, and enrollment context carry into the next responsible team’s work. Review the exact handoff and its required fields during implementation.

PUT YOUR PROCESS IN THE PICTURE

Explore transfers & withdrawals in your institution.

Start with your current workflow, the decisions that take time, and the handoffs you want to improve.

This public page presents Qentak’s capability model and an illustrative workflow. Available modules, integrations, operating rules, and rollout scope are established in your implementation plan.

Explore all 69 capabilities