Every batch is expected to have a responsible coach for:

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

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

This is the recommended best practice.

If the coach is removed before their batches are reassigned:

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

Even if a batch is unassigned:

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

This shared access model prevents operational downtime.

Admins can:

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

Lynk is designed so that:

This protects both operations and student experience.

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

This approach ensures organisational stability while allowing flexible team management.