// the platform

The software we could not buy,so we wrote it.

Everything below runs on every role we work. It is not a product we sell. It is the reason a small desk can read every applicant properly instead of skimming the first forty.

  1. 01

    Intake

  2. 02

    Parse

  3. 03

    Score

  4. 04

    Schedule

  5. 05

    Interview

  6. 06

    Decide

The first five run without anybody asking. The sixth is a person, every time, without exception.

// 01 intake and parsing

One structured record, whatever the source.

Applications reach us from the board, from email and from a direct approach. All of them become the same shape: roles held, dates, skills, notice period, salary history where it is given. A nine-page CV and a one-page one are then compared on identical terms.

  • A document that is not a CV never reaches the board, whatever else the reading of it said.
  • The same person applying twice to one role is matched on the identity we hold rather than on whatever the file happened to say, so two people who share a referee are not read as one.
  • A run that cannot be completed properly records no verdict at all and moves nobody, rather than guessing.

// 02 scoring

A score is only useful if you can argue with it.

Every application is scored against the job description you signed off, requirement by requirement: met, partly met, or not evidenced. Each score has to point at the thing in the CV it came from, a role, a date, a skill line or a gap, so when you disagree you are disagreeing with something visible.

    What it is forbidden to consider

    • Age
    • Gender
    • Nationality or national origin
    • Ethnicity or race
    • Religion
    • Marital or family status
    • Disability or health

    Where somebody lives is recorded as contact detail and may not count for or against them. The instruction is in the prompt itself, so it applies to every reading, not to the ones somebody remembered to check.

    // 03 governance

    The rules we holdourselves to.

    Automation in recruitment goes wrong quietly. These are the constraints we designed in, and they are the same ones we will put in a contract.

    No answer is sent by a machine

    Screening can move an application into a queue for review. It cannot answer anybody. Every rejection that reaches a candidate was approved and sent by a named person, and anything in that queue can be put back.

    Explainable by default

    Any candidate can ask for their score and the reasoning behind it, and we send it. Any client can audit the whole trail: who saw what, when, and on what basis they moved forward.

    Blind where it counts

    The characteristics listed above are forbidden inputs, and candidates stay anonymised to the client until they are accepted, unless the client asks us to turn that off.

    Your data stays yours

    CVs are held to put people forward for jobs. Ask us what we hold and we will tell you; ask us to delete it and we will.

    Give us the brief and we will show you what we will score against before we source a single person.

    Brief us on a role