Your reliability score

Five factors out of 100, what each is worth, why a new mentor has no score at all, and how to move it.

View as .md

Reliability is a score out of 100 measuring whether you do what you said you would. It is separate from your rating: a rating is how good the session was, reliability is whether it happened as promised.

The five factors#

FactorWorthWhat it measures
Turning up30Sessions you attended. The heaviest, because a missed session cannot be given back and it is entirely within your control.
Completion25Sessions that reached a completed state rather than being cancelled or abandoned.
Dispute outcomes20Disputes upheld against you - not disputes raised.
Cancellation discipline15Weighted by lateness. Two weeks out is an inconvenience; two hours out is a ruined afternoon.
Feedback delivery10Mock interview reports actually filed. Lowest because it applies to one service type.

The page lists your factors worst-first with a suggested fix on each, so the top item is always the one worth working on.

Before you have a score#

You need 5 completed sessions before any score is published. Below that you have no score - not a zero, and not a low one.

Until then the page says so plainly, and nothing counts against you.

When it updates#

Recalculated on a schedule, at most a few hours behind - it is not instant after a session. A change you make today shows up today, not within seconds.

Every past score is kept with its own breakdown, so a score can always be explained rather than asserted. If yours looks wrong, the breakdown is auditable.

Moving it#

In order of return:

  1. Stop missing sessions. 30 points, the largest single lever.
  2. Cancel early or not at all. Lateness is what is weighted, not the fact of cancelling.
  3. File your mock interview reports. 10 points, and entirely within your control.
  4. Resolve problems in the messaging thread before they become disputes - an upheld dispute is 20 points, and most disputes start as an unanswered message.

Was this page helpful?

Last checked against the product on . Behaviour changes are listed in the changelog.