Introduction
Coach reassignment is designed to ensure smooth operational continuity when responsibility for a batch changes. When a batch is reassigned to a new coach, Lynk cleanly transfers future execution ownership without altering past records or disrupting enrolled students.
This allows organisations to adapt to staffing changes while preserving historical accuracy.
What Reassignment Changes
When a coach is reassigned, the system updates ownership and access for that batch.
Access Changes
The new coach gains access to the batch
The previous coach loses access to batch operations
Organisation admins retain full access throughout
This ensures only the currently responsible coach can run sessions going forward.
Impact on Sessions
Upcoming Sessions
All future sessions are now assigned to the new coach
The new coach can:
Conduct sessions
Mark attendance
Add coach notes
Use the session planner
View batch insights
Generate progress reports
Ownership of execution moves forward from the reassignment point.
Completed Sessions
All past sessions remain unchanged
Attendance, notes, and session records stay linked to the original coach
Historical data is preserved for reporting and audits
Reassignment never rewrites history.
Impact on Students
Students continue in the same batch without interruption
No re-enrolment or re-grouping is required
Communication and session schedules remain unchanged
From a student perspective, the transition is seamless.
Visibility for the New Coach
Once reassigned, the new coach can immediately:
See the batch in their dashboard
View upcoming session schedules
Access batch-level insights
Review past session summaries (read-only)
This enables a smooth handover with full operational context.
Visibility for the Previous Coach
After reassignment:
The batch no longer appears in the previous coach’s active list
They cannot run sessions or edit batch details
Past contributions remain recorded under their name
This ensures clean accountability boundaries.
Admin Control During Reassignment
Organisation admins:
Can run sessions if required
Can reassign the batch again if needed
Maintain oversight across all coaches and batches
Admins act as a fallback layer to prevent operational gaps.
What Does Not Change
Reassignment does not affect:
Batch schedule (days and timings)
Batch type (online/offline, group/one-on-one)
Enrolled students
Pricing or payment status
Completed session history
Only future ownership changes.
Why Clean Reassignment Matters
Clean reassignment ensures:
No loss of data
Clear accountability
Uninterrupted sessions
Smooth coach transitions
Accurate reporting and insights
It allows organisations to scale and adapt without operational risk.
Summary
When a coach is reassigned, Lynk transfers future session ownership to the new coach while fully retaining past session history. The new coach gains immediate access to upcoming sessions and batch workflows, while admins maintain oversight. This design ensures continuity, accountability, and zero disruption for students.