Skip to content
CogniYukti

Analytics

Some roles are not hard. They are dead, and nobody has said so.

A requisition with no movement for three weeks is consuming recruiter attention, client goodwill and your SLA — and it usually looks identical to a role that is merely slow.

Suite B

Nine cards, and a scored view over the roles that most need one.

Roles with no movement. Time in stage. Ageing against the SLA promised on the requisition. Submission-to-interview ratios that say whether the problem is sourcing or the client. And a scored view, so health is a defined measure rather than a colour somebody picked.

Senior Data EngineerClient A · 2 openingsNeeds a conversation
  • Days open63
  • Submitted4
  • Client responses1
  • Last movement17 days ago
  • Budget vs marketbelow band
  • Mandatory requirements6
Six mandatory requirements on a below-band budget, and a client who has answered once in nine weeks. None of those is a surprise on its own. Together they are the meeting you should have had a month ago.
Illustrative
  • Against the SLA on the role

    The days you actually promised, not a global default.

  • It names the side

    A role stuck because you have not submitted is a different problem from one stuck because the client has not responded, and the cards separate them.

Before you trust a roles list

What the scoring does and does not do.

Does it score every open role?

Not all of them at once — the scored view covers a limited set at a time, chosen by what most needs a look. Every role still carries its own signals: days open, movement, SLA position and where the delay sits.

Does it tell us whose fault a stalled role is?

It names the side the delay is on — yours or the client's — because that is a fact about timestamps rather than a judgement. What to do about it is yours.

Is a slow role always a problem?

No — a senior search is slow by nature; a volume role that goes quiet for three weeks is not. That is why the signals are shown beside the score rather than replaced by it.

Is there a single health score per role?

Yes, for the roles most at risk — a score with a short summary and a recommended next step. It covers a working set rather than every open role at once, and the underlying signals stay visible so you can disagree with it.

What makes a role look healthy when it is not?

A requisition with movement inside your own pipeline and nothing from the client. One status field hides that; two axes do not.

Can we see this for one client across all their roles?

Yes, and that is usually the more useful cut — one client answering slowly across five roles is a commercial conversation, not five recruitment ones.

Book a demo

Review a roles list together.

We will point at the ones that are dead and you can tell us if we are right.