Applicant tracking
Screening through an ATS
Day-to-day screening once Greenhouse is connected: import the roles you are hiring for, lock a scorecard against each one, and work the candidate stack as applicants arrive. If you have not connected yet, start with Connecting an ATS.
1. Import a role
Reckn lists the jobs in your ATS. Import the ones you are actively hiring for — importing everything creates scorecards you will never use and noise in the candidate stack.
An imported role carries its job post across as the source document. That post is what criteria get extracted from, so a thin posting makes a thin scorecard.
The ATS job list, with a role being imported into Reckn.
2. Review the scorecard
Open the role. Reckn extracts the criteria it finds in the job post — each one a named requirement with a description of what is being assessed.
This is the step that decides the quality of everything downstream:
- Cut criteria that are boilerplate rather than requirements. Most postings carry a few.
- Add what the posting assumes but never says. If the team will not hire without it, it belongs on the scorecard.
- Tighten vague wording. "Strong communication skills" assesses worse than a criterion that says what communication the role actually demands.
Reviewing extracted criteria on a role, editing wording and removing boilerplate.
If auto-generate is on, the scorecard is already drafted by the time you open the role. It is still a draft until locked — the automation saves you the generation step, not the review.
3. Weight and lock
Weight the criteria — how much each one moves a candidate's result — and lock the scorecard. Locking is what makes every candidate on this role comparable: same criteria, same weights, same version, every time.
Candidates cannot be evaluated against an unlocked scorecard. If candidates are arriving and nothing is happening, this is the first thing to check.
Weights on a role's scorecard, immediately before locking.
The locked scorecard is the defensible part of the record. When someone asks why a candidate was assessed the way they were, the answer is these criteria, these weights, locked on this date, applied identically to every applicant for the role.
4. Set the trigger stage
The trigger stage is the ATS stage that means "evaluate this candidate." Set it once in ATS settings and it applies across roles. Candidates moving into that stage are what Reckn acts on.
Pick the stage where you actually want screening to happen. Set it too early and you evaluate applicants nobody has looked at; too late and the evaluation arrives after the decision.
5. Candidates arrive
When a candidate reaches the trigger stage, Reckn:
- Receives the stage change from your ATS
- Matches the candidate to the role's locked scorecard
- Pulls their resume
- Evaluates it criterion by criterion
- Writes the result back against the candidate in your ATS
With auto-evaluate off, the candidate arrives in Reckn and waits for you to start the evaluation. With it on, the evaluation is already running by the time you look.
A candidate moving into the trigger stage in Greenhouse, then appearing evaluated in Reckn.
6. Work the candidate stack
The candidate stack is every candidate evaluated against one role, ordered by result. It is a queue, not a verdict — the ordering tells you where to start reading, not who to hire.
The candidate stack for a role, ordered by evaluation result.
Read the low-confidence candidates before the low-scoring ones. A confident low assessment is usually right. A low-confidence one is where the resume was ambiguous — and that is where a human reading it changes the outcome.
7. Open a breakdown
A candidate's breakdown is the whole record, not a score with a sentence attached. Per criterion you get the assessment, the weight it carried, the reasoning in full, the confidence, and what in the resume the assessment rests on.
The raw evaluation data behind the breakdown is available too, for when you need to see exactly what the evaluation produced rather than how it is presented.
Drilling into a candidate breakdown, criterion by criterion, through to the raw evaluation data.
8. Compare candidates
Put candidates side by side against the same locked scorecard. Because the criteria and weights are identical, the comparison is between the candidates rather than between two differently-framed assessments.
Two candidates compared criterion by criterion on one role.
9. Interview kit
For a candidate you are taking forward, Reckn produces an interview kit built from their own evaluation — questions aimed at the criteria where the assessment was thin, uncertain, or worth probing.
It turns the screening record into the interview plan, so the interview covers what screening could not settle instead of re-covering what it already did.
An interview kit generated from a candidate's evaluation.
What recruiters see in Greenhouse
People working the pipeline in your ATS do not need a Reckn login to see that screening happened. Against each evaluated candidate Reckn writes:
- A note on the application with the evaluation result, at the visibility configured on the connection
- An evaluated tag on the candidate, so screened and unscreened applicants are distinguishable at a glance
The Reckn note and evaluated tag on a candidate inside Greenhouse.
Activity feed
The activity feed is the running record of what the system did — roles imported, criteria generated, scorecards locked, candidates evaluated, results delivered — with the actor and the timestamp on each. It is the first place to look when you want to know what happened, and the record you produce when someone else asks.
The ATS activity feed across roles and candidates.
When something does not arrive
| Symptom | Usual cause |
|---|---|
| Candidates reach the stage but nothing evaluates | The role's scorecard is not locked, or auto-evaluate is off and the evaluations are waiting for you to start them. |
| Candidates appear under "unassigned" | They applied to a job that was never imported into Reckn. Import the role, or dismiss the events. |
| Evaluation completed but no note in Greenhouse | Result delivery failed. Retry delivery for that run — the evaluation does not need to be re-run. |
| Nothing arrives from the ATS at all | The connection was authorized by a non-admin or by an account that has since been deactivated. Reconnect with a Site Admin service account. |
Login
Request a demo