Module · Statistics
Reliability and yellow cards
A yellow card (жовта картка) marks a specialist or client whose recent behaviour crosses one of the reliability thresholds: too many unanswered booking requests, late cancellations or reschedules, or complaints decided against them. It is a signal for the site team, not a penalty. A yellow card does nothing automatically. Moderation decides. The only automatic effect is that a specialist with an active card does not show the No disruptions fact on their profile.
The thresholds are set on Reliability → Thresholds; rule options are on Cabinet & rules.
The rules
A card is issued when at least one rule is reached. A rule whose threshold is 0 is off.
Specialists
Counted over the Specialist observation window (default 30 days), in the specialist's own time zone.
| Rule (as shown to the team and in emails) | What is counted | Default threshold |
|---|---|---|
| overdue requests without a reply: N or more | Booking requests that expired without the specialist's decision. | 3 |
| requests without a reply: N % or more (of M closed requests) | Expired requests as a share of all closed requests (confirmed, declined or expired). Applies only from the Minimum closed requests (default 5). | 20 % |
| your cancellations and rescheduling less than H h before the start: N or more | Sessions the specialist cancelled, or moved with the client's agreement, less than “Late” means less than hours (default 24) before the start. Changes staff made and attributed to the specialist count too. | 2 |
| justified client complaints: N or more | Client complaints filed in the window and decided with the specialist at fault. | 2 |
Options on Cabinet & rules can stop late moves from counting, skip seats cancelled together with a whole group meeting, and change which events count as "no reply".
Clients
Counted over the Client observation window (default 30 days), in the client's time zone.
| Rule | What is counted | Default threshold |
|---|---|---|
| client cancellations and rescheduling: N or more | Bookings the client cancelled and reschedules the client requested that were accepted, at any time before the session, plus changes staff made and attributed to the client. | 3 |
| justified specialist complaints about the client: N or more | Specialist complaints about the client filed in the window and decided with the client at fault. | 2 |
Client cards are visible only to administrators (Clients tab) and produce only the team email. Clients are not told about their card.
When figures are recalculated
- Right away for the people involved, after a booking request is confirmed, declined or expires, a booking is cancelled, a reschedule is accepted, and after a complaint is decided, its fault is changed or it is withdrawn.
- In the background for everyone, every Reliability sweep interval (default 5 minutes), a batch at a time. This catches cards that should clear simply because old events left the window.
- After a save of Thresholds or Badges.
Changing thresholds does not rewrite the history of past cards; it only changes what the next recalculation decides.
Background recalculation
The background pass runs through WordPress scheduled tasks. On a site with little traffic, WP-Cron may run late, so cards may clear later than expected. Each Reliability screen shows Last run: with the time of the last pass. If it has not run for longer than Sweep stale warning (default 15 minutes), you see "The background recalculation has not run for over N minutes. Ask a technical administrator to set up a server schedule (cron)." The fix is a real server cron job that calls wp-cron.php every few minutes.
What happens when a card is issued
- The card is recorded with a snapshot of the figures and the thresholds in force at that moment, and appears on Under watch with Under watch since and the triggered rules. The Reliability menu counter goes up.
- The team receives Yellow card — team (specialist) or Yellow card — team (client), if team letters are on.
- A specialist receives Yellow card — specialist once per card, if that letter is on.
- The specialist's cabinet overview and the Reliability block of their statistics page show Yellow card with an explanation like "A yellow card is in effect: … The platform team may take action. The card is removed automatically when the metrics for the last 30 days fall below the thresholds."
- The participant dossier shows Yellow reliability card issued in the activity feed and yellow card active in the summary.
- The No disruptions fact disappears from the specialist's public profile.
Nothing else changes: the specialist stays in search, keeps receiving requests and can work normally.
What the team can do
On Under watch or Specialists each specialist card offers:
- Open specialist bookings — review the actual bookings behind the figures.
- Remove from search (moderators, managers, administrators) with a reason the specialist receives by email; later Restore with a comment. See Removed from search.
- Remove yellow card (managers and administrators) — see below.
The hint on each card suggests a proportionate response: "Write to the specialist and remind them of the reply deadline. If it repeats — temporarily remove the profile from search." For clients: "Check whether the rescheduling had a valid reason. Repeated late cancellations can be discussed with the client by email."
Automatic clearing
When every rule is below its threshold again — usually because old events left the observation window — the card clears by itself at the next recalculation. If Yellow card minimum life (days) is set, the card stays at least that long. The dossier shows Yellow reliability card cleared automatically. No email is sent.
Removing a card manually
Use this when the figures are explained (for example, the cancellations were caused by an outage on your side) and you want to give the specialist a clean start.
- On Under watch or Specialists, type a Reason for removal (5–1000 characters).
- Click Remove yellow card and confirm "Remove the yellow card? Cases before removal will no longer bring the card back; a reason is required."
After a manual removal:
- Events before the removal no longer count: the specialist's window now starts at the moment of removal (but never earlier than the normal observation window). Complaints filed before the removal and late moves proposed before it are forgiven even if they are decided or accepted later. The specialist's statistics page shows the shorter window, for example since
, after the card was removed . - The card can come back only for new cases after the removal.
- The specialist receives Yellow card cleared — specialist, if that letter is on ("Yellow card removed; the email to the specialist is queued.").
- The removal, the operator and the reason are kept in the reliability history and appear in the dossier as Yellow reliability card cleared manually.
Other messages: "There is no card anymore; nothing was changed.", "A reason is required (5–1000 characters).", "Could not remove the card. Try again." Client cards cannot be removed manually; they clear automatically.
What specialists see
- Their own status in the Reliability block of the statistics page: All good ("You reply to clients on time and do not cancel meetings. Keep it up!") or Yellow card with the rules in plain words, plus the figures behind the rules and the window they are counted over.
- The yellow-card emails described above.
- The No disruptions fact is not shown on their profile while the card is active.
They do not see other people's cards, and they cannot remove a card themselves; it clears when their figures improve or when the team removes it.