Back to L&D HubOpen module BY: Tia Open module Open module BY: TiaBY: TiaBY: TiaBY: TiaBY: Tia Open module Open module BY: Tia Open module
BePACE Process Flow & Instructions
Canonical specification β 40 process flows across 6 L&D modules Β· Source: BePACE Process Flow & Instructions.xlsx
BeCOMPASS
BeCORE + BeLEAD competency framework Β· 10 flows
BeCORE
Competency Assessment
Self Assessment Superior Assessment
π Full Process Flow (34 steps)
- Setup β Notify β Self Assessment β Superior Assessment β Fully Completed β Auto ICDP Generation
- 1. System Setup
- Configure in system:
- Competency Ruler
- 5-point rating scale (Basic β Exceptional)
- Assign employees and reporting superiors
- Set assessment timeline
- 2. System Notification
- System sends automatic notification to:
- Employees (Self Assessment)
- Superiors (for upcoming review)
- Provide access to system and deadline
- 3. Self Assessment (Employee)
- Employee logs into system
- Completes assessment:
- Select rating (1β5) for each competency
- Add supporting comments/evidence
- Submit in system
- Status: Self Assessment Completed
- 4. Routing to Superior
- System automatically routes assessment to immediate superior
- Notification sent to superior for action
- 5. Superior Assessment (Key Responsibility)
- Superior logs into system
- Evaluates ALL assigned staff
- Performs:
- Final rating (1β5)
- Adds justification/comments
- Completion Status
- Once superior submits:
- Status: Fully Completed
- Assessment Weightage (Total: 100%)β
- Self-Assessment (SA) β 30% β
- Superior Assessment (SUP) β 70%
ICDP
ICDP
π Full Process Flow (60 steps)
- Assessment Completed β CCL Captured β ECL Assigned β Gap Analysis β Status Determined β ICDP Generated β Review & Agree β Development Execution β Monitoring
- 1. Trigger from Competency Assessment
- ICDP process automatically starts once:
- Competency Assessment = Fully Completed (Superior submitted)
- System pulls final results into ICDP module
- 2. Capture Current Competency Level (CCL)
- System records:
- Final rating (1β5)
- Converted % score
- Overall competency score
- This becomes the Current Competency Level (CCL)
- 3. Assign Expected Competency Level (ECL)
- System assigns Expected Competency Level (ECL) based on Job Grade:
- Job Grade Expected Level (ECL)
- NE I, NE II, NE III Foundational
- NE IV Applied
- E I, E II, SE I, SE II Proficient
- M I, M II, SM I, SM II Expert
- 4. Convert Score to Competency Level
- System maps % score into level:
- Level % Range
- Foundational 0β49%
- Applied 50β69%
- Proficient 70β84%
- Expert 85β100%
- This determines employeeβs actual level (CCL level category)
- 5. Gap Analysis (CCL vs ECL)
- System compares:
- Current Level (CCL) vs Expected Level (ECL)
- Identify:
- Competency gaps
- Strength areas
- 6. Competency Result Status Determination
- System assigns status automatically:
- Status Definition
- On Track Meets expected competency level
- Off Track Below expected level, requires improvement
- Above Expectations Exceeds expected level
- Logic:
- CCL = ECL β On Track
- CCL < ECL β Off Track
- CCL > ECL β Above Expectations
- 7. ICDP Auto-Generation (System + AI)
- Based on gap analysis, system generates:
- Off Track
- Mandatory training
- Structured development plan
- On Track
- Continuous improvement actions
- Above Expectations
- Advanced development
- Leadership / talent pool programs
- 8. Development Plan Structuring
- ICDP includes:
- Target competencies to improve
- Recommended:
- Training programs
- On-the-job learning
- Coaching / mentoring
- Timeline & priority level
Training Bond
Training Bond Notification to User
π Full Process Flow (25 steps)
- 1. Training Completion / Enrollment Trigger
- Start Point: Training is registered
- System captures:
- Total Training Cost (fees + flights + accommodation + transport + others)
- Training Type (Certification / Non-Certification)
- 2. Eligibility Check (Auto Decision Engine)
- System evaluates:
- Condition A: Cost-Based Trigger
- If total training cost > RM 10,000
- Condition B: Certification Override
- If Certification Training β Automatically qualifies (override cost rule)
- If YES (either A or B) β proceed to Training Bond
- If NO β End process (No bond required)
- 3. Training Bond Notification (To User)
- System automatically:
- Notifies user that they are subject to Training Bond
- Displays:
- Bond duration
- Bond terms
- 4. Bond Duration Calculation (Auto Logic)
- System assigns bond duration:
- RM 10,000 β RM 20,000 β 5 Years
- RM 20,001 β RM 40,000 β 6 Years
- RM 40,001 and above β 7 Years
- Certification Training β 5 Years (override all)
Training Bond Letter Template
π Full Process Flow (10 steps)
- Admin:
- Uses predefined template in system
- System:
- Auto-populates:
- User details
- Training details
- Bond duration
- Letter is:
- Issued upon training completion / certification pass
- Sent to user (email + system record)
Training Bond Balance
π Full Process Flow (10 steps)
- System continuously tracks:
- Bond start date
- Bond duration
- Remaining balance (time-based or monetary equivalent)
- Notifications:
- Periodic updates to:
- Admin
- User
- Automatic alert when:
- Bond is fully completed
Training Bond termination
π Full Process Flow (10 steps)
- Trigger:
- User resigns OR employment is terminated
- System Actions:
- Notify Admin to review bond status
- Calculate:
- Remaining bond duration
- Equivalent payable amount (if applicable)
- Notify User:
- Remaining bond obligation
- Payment required to company
Training Bond Closure
π Full Process Flow (7 steps)
- If:
- Bond duration completed β System marks Completed
- OR payment settled β System marks Closed (Paid)
- To notify user remaining time prior to bond completed (90/60/30/ on the bond complete day)
- Final notifications sent to:
- Admin- Capability Department PIC
- User
Line Training
Line Training
π Full Process Flow (12 steps)
- 1. Record Auto-Created in Training Record
- - System generates record upon confirmed attendance
- 2. Tagged to line training
- - Record is linked to individual participant profile
- - Includes training history & competency category
- 3. Budget Updated (line trainer allowance is under B&R Department)
- - Budget utilisation is auto-updated
- 4. Dashboard & Reports Generated
- Real-time visibility:
- - Individual training records
- - Department training summary
- - Budget utilisation tracking
BeLEAD
All Pre & Post Assessment
1. 270' Assessment (Self, Superior, Peer, & Subordinate) 3. Psychometric Test
β‘ Simplified Flow
- 1. Assessment Initiated β Status: Pending Completion
- 2. Notification Sent β Staff to Complete Assessments (Self, Peer, 3. Superior, Subordinate, Psychometric)
- 4. Assessment In Progress β Status: In Progress
- 5. All Assessments Submitted β Status: Completed
- 6. Notification to Capability Team (Focal: Fazlin) β Ready for reporting
π Full Process Flow (13 steps)
- 1. Assessment cycle has been initiated. Notifications have been sent to participants. (Assessment Launch)
- Status: Assessment Initiated
- Trigger:Capability team activates assessment cycle
- 2. Staff are required to complete assigned assessments (Self, Peer, Superior, Subordinate, Psychometric. (Notification to Participants)
- Status: Pending Completion
- Trigger:System sends email + in-app notification
- 3.Assessment is currently in progress. Pending inputs from assigned evaluators. (Assessment In Progress)
- Status: In Progress
- Trigger: At least 1 assessment started but not all completed
- 4. All assigned assessments have been successfully completed.
- Status: Completed
- Trigger: All required inputs submitted
- 5. Assessment completion recorded. Notification sent to Capability Team (Focal: Fazlin). Results are ready for reporting and development planning.β
Training Evaluation
Training Evaluation
β‘ Simplified Flow
- 1. Training Completed β Status: Completed
- 2. T+1 Evaluation Notification β Status: Pending Evaluation
- 3. Reminder Every 3 Days β Status: Pending Evaluation
- 4. Evaluation Submitted β Status: Evaluation Completed
- 5. Certificate Enabled Once Evaluation Completed
π Full Process Flow (20 steps)
- 1. Training has been completed. Evaluation will be available starting tomorrow.
- Trigger: Training session status marked as Completed
- System Action: Schedule evaluation notification (T+1 day)
- 2. Notify all registered participants to complete:
- Training Evaluation
- Training Provider Evaluation
- Status: Pending Evaluation
- *Evaluation Notification Sent (T+1 Day)
- 3. Evaluation Incomplete
- Status: Pending Evaluation (Reminder Cycle)
- System Action:
- Send reminder every 3 days
- Continue until submission is completed
- 4. Evaluation Submitted
- Status: Evaluation Completed
- System Action:
- Mark participant as completed
- Stop reminders
- 5. Certificate Available for Generation
- Enable certificate generation/download
BEES
E-learning platform tracking & completion Β· 3 flows
BEES
N/A
N/A
β‘ Simplified Flow
- Tia
π Full Process Flow (18 steps)
- User View (Learner Journey)
- 1. User logs into BEES e-Learning platform
- 2. Receives training:
- - Self-enrol OR auto-assigned based on role/requirement
- 3. Views course details
- 4. Confirms enrolment (if required)
- 5. Completes training:
- - Attend session / complete modules
- 6. Submit assessments (if any)
- 8. System auto-updates:
- - Completion status
- - Learning progress
- 9. Receives:
- Completion notification
- Certificate (generated by system)
- 10. Dashboard insights:
- -Self performance(number of complete, on going, not yet started course/ modules) with specified category.
- - Hours spent in completing course/module
N/A
N/A
π Full Process Flow (17 steps)
- Admin View (Learning / Capability Team)
- 1. Create/upload training programme
- 2. Configure system settings:
- 3. Automation Layer:
- - Auto-send reminders (before training, staff that behind schedule/timeline,)
- - Auto-update attendance/completion (based on criteria)
- - Auto-trigger notifications (active, inactive course/modules)
- 4. Post-training reporting & analytics:
- - Results / assessments (system-integrated)
- - Completion rate
- - Attendance rate
- - No-show / drop-off trend
- 5. Dashboard insights:
- -Training utilisation
- -Department performance (number of complete, on going, not yet started course/ modules) with specified category. Example, leaderboard by division
- - Hours spent in completing course/module
- -Export data for audit / management reporting
N/A
N/A
π Full Process Flow (13 steps)
- Manager/HOD view
- 1. Notification Stage (Revised)
- Manager receives automated notifications when:
- - staff enrols in a course (self-enrol or assigned)
- - Staff completes a course/module
- Notification includes:
- -Training title
- -Date / duration
- -Completion status
- 2. Dashboard insights:
- -Department performance
- -Export data for management reporting/ KPI evaluation
- π No approval required β purely for awareness and transparency
Training
Training management, HRDC, budget & payment Β· 7 flows
Learning Funding
HRDC Contribution
Grant Registration
β‘ Simplified Flow
- 1. Register Grant β Trigger: Submit Form β Status: Pending Approval
- 2. Grant Created β Trigger: System Validation β Status: Pending Approval
- 3. Reminder to Focal β Trigger: Schedule β Status: Pending Approval (Reminder Sent)
- 4. Approve Grant β Trigger: Focal Action β Status: Approved (Pending Documents)
- 5. Upload JD14 & T3 β Trigger: User Upload β Status: Documents Submitted
- 6. Upload HRDC Invoice β Trigger: Focal Upload β Status: Claim Completed
π Full Process Flow (18 steps)
- 1. User submits HRDC grant registration with required details, including trainer profile, quotation, and course outline.
- Trigger: User clicks Submit after completing form and uploading documents
- Status: Pending Approval
- 2. Grant registration is successfully created and is currently pending approval.
- Trigger: System validates submission and saves record
- Status: Pending Approval
- 3. System sends reminder notification to HRDC focal to update grant approval status once training session has concluded.
- Trigger: Scheduled trigger (e.g., every 3 days)
- Status: Pending Approval (Reminder Sent)
- 4. HRDC focal updates grant status to βApprovedβ (pending JD14 and T3 form submission).
- Trigger: HRDC focal updates status to Approved
- Status: Approved
- 5. User uploads JD14 and T3 forms to complete grant documentation.
- Trigger: User uploads JD14 and T3 forms
- Status: Documents Submitted
- 6. HRDC focal uploads the HRDC invoice. Grant claim process is now completed.
- Trigger: HRDC focal uploads official HRDC invoice
- Status: Claim Completed
Company Contribution
Training Payment
β‘ Simplified Flow
- 1. Training Completed β Status: Completed (Pending Payment Initiation)
- 2. Notify Capability Team β Status: Pending Payment
- 3. Upload Invoice & Payment Advice β Status: Documents Submitted
- 4. Submit to Finance β Status: Pending Finance Processing
- 5. Payment Processing β Status: Payment In Progress
- 6. Receipt Uploaded β Status: Payment Completed
- 7. Notify Capability β Status: Payment Completed (Final)
π Full Process Flow (19 steps)
- 1. Training session has been successfully completed.
- Status: Completed (Pending Payment Initiation)
- Trigger: System auto-detects training end date OR provider marks training as completed
- 2. System notifies Capability Team to initiate payment processing for the completed training.
- Status: Pending Payment (Capability Review)
- Trigger: Auto-notification sent to Capability Team (email/system alert)
- 3. Capability Team uploads payment documents: Capability Team uploads required documents, including trainer invoice and payment advice, and verifies training details.
- Status: Payment Documents Submitted
- Trigger: Document upload (Invoice + Payment Advice)
- 4. Submit for finance processing: Capability Team reviews and submits the verified payment request to Finance.
- Status: Pending Finance Processing
- Trigger: Capability Team clicks βSubmit for Paymentβ
- 5. Finance team processes payment based on submitted documents.
- Status: Payment in Progress
- Trigger: Finance acknowledges and starts processing
- 6. Finance uploads payment receipt & completes payment: Finance uploads proof of payment (receipt) and updates the payment status.
- Status: Payment Completed
- Trigger: Receipt upload by Finance
- 7. System notifies Capability Team that payment has been completed with receipt attached.
Training Needs Analysis
N/A
N/A
β‘ Simplified Flow
- Budget + Competency rule/CDF + Port Business = TNA
π Full Process Flow (69 steps)
- User View (Input Trigger):
- 1. Identify Training Needs (Data-Driven)
- - Staff completes competency assessment in the system
- System Logic (Core Engine):
- 1. Gap Identification
- System determines:
- - Current competency level
- - Required competency level (by role)
- - Competency gap is auto-generated β becomes the basis for TNA
- 2. Competency Ruler Mapping
- System maps gap against competency framework:
- - Required vs current level
- System outputs:
- - Types of training required to close gap
- Skill gap areas:
- Priority level: critical, important, nice to have
- 3. Port Business Alignment
- System auto-classifies training under:
- - BPHB organisational & operational capability categories
- Assigns:
- Business impact level: High, Medium, Low
- 4. Budget Alignment
- System checks:
- Department training budget (annual allocation)
- - Flags: Within budget β , Exceeds budget β οΈ
- If exceeds:
- System assigns priority for decision-making: High (retain), Medium (review), Low (defer)
- Admin View (Review & Consolidation Layer)
- 1. Retrieve TNA from System
- Admin extracts system-generated TNA output:
- - Competency gaps
- - Suggested training types
- - Priority level
- - Budget status
- 2. Review & Validate
- Admin performs quality check:
- - Relevance of training vs competency gap
- - Alignment with business priorities (port operations)
- - Budget feasibility
- Admin may:
- - Consolidate similar training across departments
- - Refine training scope (merge / split programmes)
- 3. Prepare TNA Proposal
- Admin compiles refined TNA list:
- - Prioritised training programmes
- - Proposed participants
- - Budget allocation
- Manager / HOD View (Endorsement Layer)
- 4. Notification & Review
- Manager/HOD receives notification:
- - Team competency gaps
- - Proposed training plan
- Reviews:
- - Relevance to team needs
- - Operational feasibility
- 5. Decision Point
- Manager/HOD provides action:
- - Agree / Endorse β proceed to training plan
- - Request Revision β send back to Admin
- Admin Action (If Revision Required)
- 6. TNA Adjustment
- Admin revises based on feedback:
- - Adjust participant numbers
- - Reprioritise training
- - Refine scope
- - Updated TNA is resubmitted for endorsement
- Final Output
- β Endorsed TNA β feeds into Annual Training Plan (ATP) - calendar
- π Non-endorsed β loop back for refinement
Attendance
N/A
N/A
β‘ Simplified Flow
- Setup β Attend β Check-in β Validate β Record β Detect No-show β Notify β Deduct Budget β Report
π Full Process Flow (31 steps)
- 1. Training Setup (Admin)
- - Capability Team creates training in system
- - Registers participants (no self-registration required)
- - System sends training notification to staff
- 2. Training Day (User Action + System Capture)
- Staff attends training session
- Performs check-in via:
- β’ Face Recognition OR
- β’ QR Code
- System validates:
- Check-in within 08:00 β 17:00
- 3. Attendance Recording (System Logic)
- - If valid check-in:
- β Status = Present
- - If no check-in by end of window:
- β Status = No-show
- 4. No-Show Detection (Auto Trigger)
- At end of session (after 17:00):
- - System identifies participants with no attendance record
- 5. Enforcement Action (System Auto-Process)
- System executes for No-show:
- π§ Email notification sent to Manager / Supervisor
- π° Training cost charged to department budget
- 6. Reporting & Monitoring (Admin + Manager)
- System generates:
- - Attendance report
- - No-show list
- - Budget deduction summary
- Manager / HOD can view:
- - Team attendance
- - Budget impact
Registration
N/A
N/A
β‘ Simplified Flow
- N/A
π Full Process Flow (1 step)
- N/A
BeSTEP
N/A
N/A
β‘ Simplified Flow
- Record Auto-Created in training recordβ Tagged to beSTEP Profile β Budget Updated β Dashboard & Reports Generated
π Full Process Flow (13 steps)
- 1. Record Auto-Created in Training Record
- - System generates record upon confirmed attendance
- 2. Tagged to beSTEP Profile
- - Record is linked to individual participant profile
- - Includes training history & competency category
- 3. Budget Updated
- - Training cost is allocated to department
- - Budget utilisation is auto-updated
- 4. Dashboard & Reports Generated
- Real-time visibility:
- - Individual training records
- - Department training summary
- - Budget utilisation tracking
Evaluation
N/A
N/A
β‘ Simplified Flow
- N/A
π Full Process Flow (1 step)
- N/A
Internship
Intern management, attendance & allowance Β· 6 flows
Internship
Internship Application
Summary of Application
π Full Process Flow (15 steps)
- Start Point: Applicant submits internship application
- System captures raw data:
- Place of study
- Duration
- Programme of study
- Gender
- Age
- 2. Application Summary Dashboard (Admin View)
- System processes raw application data into:
- Summary dashboard
- Filterable views (by programme, gender, duration, etc.)
- Output:
- Admin can:
- View consolidated applicant data
- Generate Allowance Report based on duration / intake
Department Vacancies
π Full Process Flow (6 steps)
- Admin sets internship capacity per department:
- Minimum: 1 student
- Maximum: 3 students
- System maintains:
- Real-time vacancy status per department
- Availability tracking (filled vs remaining slots)
Internship Offer to Deparments
π Full Process Flow (14 steps)
- Trigger:
- New application OR shortlisted candidates
- System Actions:
- Automatically notify Head of Department (HOD)
- Share applicant details for review
- HOD Decision:
- Approve
- Reject
- Decision is sent back to system
- If APPROVED:
- Proceed to Offer Stage
- If REJECTED:
- Mark application as unsuccessful
- Proceed to Rejection Notification
Internship offer to applicants
π Full Process Flow (9 steps)
- System:
- Uses Offer Letter Template
- Auto-populates:
- Applicant details
- Internship duration
- Department
- Sends:
- Offer notification to applicant
- Status update in system
Allowance Reporting
π Full Process Flow (6 steps)
- Based on:
- Approved interns
- Duration of internship
- System generates:
- Allowance summary report
- Breakdown per department / intake
Internship Attendance
π Full Process Flow (57 steps)
- 1. Attendance Submission by Intern (Trigger)
- Start Point: Intern records and submits monthly attendance
- System captures:
- Intern details
- Department
- Attendance records (daily / total days)
- Month of submission
- Rule:
- Submission deadline: 25th of each month
- 2. Deadline Monitoring & Reminder
- System actions:
- Sends auto-reminders to interns:
- Before deadline (e.g. 20thβ24th)
- Tracks submission status:
- Submitted
- Pending
- If NOT submitted by 25th:
- System flags as Late Submission
- Notify:
- Intern
- Admin- Capability Department PIC
- 3. Admin Review & Consolidation (Capability Department PIC as Admins)
- After submission:
- Admin reviews:
- Attendance completeness
- Accuracy
- System supports:
- Dashboard view of:
- All intern submissions
- Missing / late submissions
- Admin actions:
- Approve attendance
- Request correction (if needed)
- 4. Attendance Consolidation Report
- System generates:
- Monthly Attendance Report
- Summary by:
- Intern
- Department
- Total days attended
- 5. Submission to Benefits & Rewards Department
- Trigger:
- All attendance approved OR submission deadline reached
- System/Admin action:
- Submit consolidated report to:
- Benefits & Rewards Department
- 6. Allowance Processing
- Benefits & Rewards uses:
- Attendance data
- Internship duration
- To process:
- Monthly allowance payout
- 7. Notifications & Tracking
- System notifies:
- Admin β submission completed
- Benefits team β report received
- Intern β attendance approved / issues (if any)
Training Room
Room booking & availability management Β· 2 flows
Book a room
N/A
N/A
π Full Process Flow (14 steps)
- User View (Front-End Flow)
- 1. User accesses the βBook a Roomβ application
- 2. Inputs required details
- 3. Clicks Submit
- 4. System displays confirmation:
- - βRequest submitted successfullyβ
- - email notification for record
- Admin View (Back-End Flow)
- 1. Admin receives booking request notification (email/system dashboard)
- 2. Reviews request details:
- 3. Check room availability
- 4. Decision point:
- - Approve β system sends confirmation to user
- - Reject β system notifies user with reason
Calendar view
N/A
N/A
π Full Process Flow (1 step)
- System updates room schedule/calendar in real-time
Study Loan
Loan allocation, invoice & claim tracking Β· 12 flows
Study Loan
Study Loan Application
Submission from User
π Full Process Flow (9 steps)
- Start Point: Employee submits application
- (for self / spouse / children)
- System captures:
- Applicant details (employee / dependent)
- Course details (level, institution, mode)
- Supporting documents:
- Acceptance letter
- IC (if applicable)
- Certificates
Application Validation
π Full Process Flow (7 steps)
- System auto-check:
- Completeness of documents
- Minimum service: β₯ 2 years & confirmed employee
- One active study loan at a time
- Course is recognized / approved
- If Incomplete / Invalid β Reject & notify applicant
- If Valid β Proceed to eligibility review
Eligibility & Background Screening
π Full Process Flow (7 steps)
- System + Admin checks:
- Performance record
- Disciplinary status
- Bankruptcy status
- Study mode does not interfere with work
- If Fail criteria β Reject
- If Pass β Proceed to approval
Approval workflow
π Full Process Flow (6 steps)
- Routed to:
- President / GCEO (or authorized approver)
- Decision:
- Approve
- Reject
- System records decision
Offer & Agreement Generation
π Full Process Flow (12 steps)
- If APPROVED:
- System generates:
- Study Loan Offer Letter
- Loan Agreement
- Includes:
- Loan amount (max RM25,000)
- Covered items:
- Fees, accommodation, transport, etc.
- Requirement:
- 2 guarantors validation
- β₯ 2 years service
- No bankruptcy / criminal record
Loan Disbursement Process
π Full Process Flow (10 steps)
- Trigger:
- Agreement signed + registered
- System actions:
- Disbursement:
- Direct to institution OR applicant
- Based on:
- Course schedule / invoices
- Control:
- Next disbursement only if:
- Exam results submitted
Study Monitoring
π Full Process Flow (8 steps)
- System tracks:
- Academic progress
- Exam results
- Completion status
- Requirement:
- Submission of:
- Exam results
- Completion certificate
Repayment Schedule Generation
π Full Process Flow (12 steps)
- System auto-calculates repayment:
- Loan Amount Repayment Period
- < RM3,000 2 Years
- RM3,001β5,000 3 Years
- RM5,001β8,000 4 Years
- RM8,001β12,000 5 Years
- RM12,001β18,000 6 Years
- RM18,001β25,000 7 Years
- Repayment Start Logic:
- With salary β immediate (next month)
- No salary β 6 months after completion
- Children β employee pays
Repayment Tracking & Notification
π Full Process Flow (10 steps)
- Monthly installment tracking
- System notifies:
- Employee- User
- Admin- Capability Department PIC
- Benefits & Reward Department PIC
- Features:
- Early settlement option
- Alerts for:
- Missed payments
- Breach of agreement
Study Discontinuation
π Full Process Flow (6 steps)
- If:
- Fail exam / discontinue study
- Breach agreement
- System triggers:
- Full repayment required
- Eligibility revoked
Bond management (If resign)
π Full Process Flow (7 steps)
- System applies:
- Bond duration (post-study)
- If early resignation:
- System calculates:
- Remaining bond value
- Notifies:
- Employee β repayment required
Loan Closure
π Full Process Flow (5 steps)
- Status updated when:
- Fully repaid
- OR
- Converted & bond completed
- Final notification sent
