What happens to batches when a coach is removed from organisation

Batches in Lynk are designed to remain operational even when a coach is removed. This ensures that sessions, attendance, and student progress are not disrupted due to team changes.

Written by Sumit Kapoor

Why Batch Reassignment Matters

Every batch is expected to have a responsible coach for:

  • Conducting sessions

  • Managing attendance

  • Tracking student progress

  • Maintaining continuity

However, Lynk is built to avoid operational breaks if a coach exits unexpectedly.

What Happens When a Coach Is Removed

When an organisation admin removes a coach, one of two scenarios applies:

Scenario 1: Coach Is Removed After Reassignment

  • All batches are already reassigned to another coach

  • Operations continue seamlessly

  • No disruption to sessions or students

This is the recommended best practice.

Scenario 2: Coach Is Removed Before Reassignment

If the coach is removed before their batches are reassigned:

  • The batches remain active in the organisation

  • The batches become unassigned

  • No batch data is lost

At this stage, the system expects the admin to reassign the batches.

Admin Access Ensures Continuity

Even if a batch is unassigned:

  • The admin retains full access

  • The admin can:

    • Run sessions

    • Mark attendance

    • Manage students

    • Maintain batch workflows

This design ensures that learning and operations do not stop due to staffing changes.

Coach vs Admin Access During Transition

  • Coach (removed):

    • Loses all access immediately

    • Cannot view or operate any batch

  • Admin:

    • Continues to see and manage the batch

    • Can temporarily run sessions

    • Can reassign the batch at any time

This shared access model prevents operational downtime.

Reassigning the Batch

Admins can:

  • Assign the batch to another existing coach

  • Restore standard coaching workflows

  • Ensure accountability and continuity

Until reassignment, the batch remains functional but flagged for action.

System Safeguards

Lynk is designed so that:

  • Batches never disappear when a coach is removed

  • Students are not impacted

  • Sessions can still be conducted by the admin

  • Reassignment restores normal ownership

This protects both operations and student experience.

Summary

When a coach is removed, batches are never broken or deleted.

  • Batches either get reassigned or become temporarily unassigned

  • Admins retain full control and can run sessions

  • Operations continue without interruption

  • Reassignment completes the transition cleanly

This approach ensures organisational stability while allowing flexible team management.

Related Articles