EvoFit Help Center

Bulk Operations on Clients

Select multiple clients and change status or apply tags in one click.

trainer guide/clients
What this is for: Move many clients through a status change without clicking each one.

What you can do in bulk

  • Change status for many clients (active / pending / offline / need_programming / archived).
  • Apply a tag to many clients (e.g. q1-launch, summer-shred).
  • Archive or reactivate many clients at once.
  1. Click Clients in the sidebar to see your roster.
  2. Tick the box beside a client to select them.
  3. Tick more clients. A bar appears with the number selected.
  4. Use Update Status or Assign Tag to change every selected client at once.

Step-by-step

  1. On /clients, you'll see a checkbox to the left of every row.
  2. Tick the checkbox on each client you want to act on. As soon as one row is checked, the BulkActionsToolbar appears at the top.
  3. The toolbar shows:
  • {N} selected — running count.
  • Update Status: opens a menu of statuses. Clicking a status applies it to every selected client straight away (there is no separate confirm step).
  • Assign Tag: opens a box ("Tag ID or name"); type the tag and click Apply.
  • Clear Selection: unchecks everything.
  1. After applying, a toast confirms success (e.g. "Updated 5 clients").

Status options

StatusWhat it means
activeCurrently training
pendingInvite accepted, hasn't logged in
offlineLogged in within last 30 days but not active
need_programmingYou owe them a program
archivedRemoved from main roster (soft delete)

Tags

Tags are free-text labels that survive on the client record. Use them to:

  • Group cohorts (e.g. q1-2026-cohort)
  • Mark intent (upgrade-prospect, case-study)
  • Track campaigns (black-friday-promo)

There is currently no central tag manager — tags surface as filter chips in the FilterBar after they exist on at least one client.

Common pitfalls

Where to find this

  • Page: /clients.
  • Component: BulkActionsToolbar.
  • API: POST /api/clients/bulk and PATCH /api/clients/[id]/status.
Was this article helpful?