Admission Decision and Joining
Epic summary
The Admission Decision and Joining epic is the controlled point where the institution accepts or rejects the candidate and then records whether an approved candidate actually joined.
Approval and joining are separate:
- Admission approval confirms that the candidate may be admitted against the actionable allotment.
- Joining confirms that the approved candidate completed the required formalities and took the seat.
Actors and access
| Actor | Access |
|---|---|
| Admission Nodal Officer | Prepares the decision and confirms workflow completeness |
| Authorised Dean/Principal | Approves, rejects, or returns the case |
| Admission Clerk | May record physical joining after approval where assigned |
| Counselling Coordinator | Receives decision and joining status for authority reporting |
| Candidate | Receives published letters and acknowledgements |
| Internal Auditor | Read-only decision evidence and audit trail |
Screen structure and data captured
The workspace contains a read-only Decision Summary, an authorised Admission Decision panel, and a separate Joining Event panel.
Decision summary fields
| Field group | Information shown |
|---|---|
| Candidate and case | Case number, candidate identity, institution, cycle, and programme offering |
| Actionable allotment | Authority, process, round, allotment number, seat pool, quota, category, rank, and source version |
| Time controls | Reporting deadline, joining deadline, statutory cutoff, decision time, and blocking expiry |
| Verification | Document completion, unresolved deficiencies, eligibility recommendation, and senior decisions |
| Clearances | Finance, medical, programme, and bond/legal outcome with responsible officer and timestamp |
| Seat validation | Applicable matrix version, availability, and conflict status |
| Preparation | Proposed outcome, preparer’s note, unresolved warnings, and readiness result |
Admission-decision fields
| Field | Entry type | Required | Meaning and validation |
|---|---|---|---|
| Decision | Selected | Yes | Approve, reject, or return for correction |
| Decision reason | Selected/entered | Conditional | Mandatory for rejection, return, exception, or conditional approval |
| Effective date/time | System captured | Yes | Must not breach the statutory cutoff |
| Approval authority | Selected/inherited | Yes | Delegation/order under which the approver acts |
| Exception used | Selected | No | References an approved senior decision; cannot bypass a hard prohibition |
| Conditions before joining | Entered | No | Explicit actions still permitted after approval but before joining |
| Decision letter template | Selected | Yes | Versioned template appropriate to outcome and programme |
| Digital signature/approval | Captured | Yes | Approver identity and signing event |
Joining-event fields
| Field | Entry type | Required | Meaning and validation |
|---|---|---|---|
| Joining date/time | Captured/entered | Yes | Actual joining event; authorised back-entry requires a reason |
| Joining location | Selected | Yes | Institution/counter where joining completed |
| Candidate acceptance | Captured/uploaded | Yes | Signed or digital declaration accepting the seat and conditions |
| Fee/bond completion confirmation | System shown | Yes | Must meet configured joining gates |
| Original-document custody | System shown/confirmed | Conditional | Custody receipt and responsible office |
| Joining status | Selected | Yes | Joined, joining incomplete, declined, or no-show |
| Joining order/letter | Generated | Conditional | Versioned output with reference number |
| Recorded by and witness | System/selected | Yes | Responsible officer and witness where required |
Use case 1: Prepare a case for decision
As an Admission Nodal Officer
I want to prepare a complete decision summary
So that the approver can decide without reconstructing the case manually.
Acceptance criteria
- The summary identifies the current actionable allotment and seat.
- Reporting, documents, eligibility, finance, medical, programme, bond, and cutoff states are shown separately.
- All unresolved mandatory blockers are listed.
- The Admission Nodal Officer records a recommendation and any relevant authority order.
- Preparing the decision does not itself approve admission.
- The summary is frozen to a version when submitted to the approver.
Negative cases and alternate flows
- Mandatory clearance missing: Prevent submission unless the case follows an authorised exception path.
- Allotment superseded: Return the case to allotment review.
- Cutoff expired: Block an approval recommendation and record the expired status.
Use case 2: Approve admission
As an Authorised Dean/Principal
I want to approve an eligible and complete case
So that the candidate may formally take the allotted seat.
Acceptance criteria
- The approver reviews the versioned decision summary and supporting findings.
- The system rechecks the actionable allotment, seat availability, mandatory clearances, and cutoff at the moment of approval.
- Approval records the approver, time, decision version, and applicable authority.
- The approved seat is reserved for joining according to the configured process.
- The system generates the provisional or final admission letter required by the institution.
- The approver cannot edit specialist evidence from the decision screen.
Negative cases and alternate flows
- Case changed after submission: Require the approver to review a refreshed summary.
- Seat no longer available: Stop approval and escalate reconciliation.
- Attempt after cutoff: Refuse the action; do not provide a warning-only bypass.
- Approver lacks entity scope: Deny the action even if the user can see a consolidated summary.
Use case 3: Reject or return the case
As an Authorised Dean/Principal
I want to reject or return an incomplete or ineligible case
So that the institutional outcome is clear and defensible.
Acceptance criteria
- Rejection requires a reason code, written explanation, and supporting findings.
- The approver can return a correctable case to a named role without rejecting it.
- The candidate receives only the approved external explanation.
- Rejection triggers the configured seat and authority follow-up.
- The case retains any review or appeal route configured by the institution.
Negative cases and alternate flows
- Correctable deficiency within time: Permit Return for Correction instead of final rejection.
- Candidate disputes decision: Record the review request without changing the original decision.
- Source allotment cancelled: Use the appropriate cancellation or movement reason rather than labelling the candidate academically ineligible.
Use case 4: Record joining
As an Admission Nodal Officer
I want to record that an approved candidate joined
So that the seat becomes occupied and can be reported to the authority.
Acceptance criteria
- Joining is available only for an approved, actionable admission.
- The actual joining date and time are recorded.
- Required joining acknowledgements and signatures are captured.
- Joining creates the authority-reporting event and updates the seat position.
- The candidate receives a joining acknowledgement.
- The case becomes eligible for student-enrolment handoff.
Negative cases and alternate flows
- Candidate does not appear: Record Not Joined after the applicable deadline and begin vacancy processing.
- Candidate declines at joining: Record withdrawal or non-joining according to the governing rule.
- Joining after deadline: Block unless an authorised extension is recorded and still falls within the statutory cutoff.
- Duplicate joining: Prevent a second active joining for the same admission.
Success outcome
The institution has a versioned, authorised admission decision and a separate, time-stamped record of whether the candidate actually occupied the seat.