How to define screening criteria before reviewing CVs

Define CV screening criteria before opening applications by separating essential requirements from preferences, documenting acceptable evidence for each criterion, and agreeing how missing or uncertain evidence will be handled.

Turn vague hiring-manager requests into explicit requirements and evidence expectations before candidate screening begins.

Practical guide · 9 min readAuthored by: Skilltage OÜPublished: Updated: Reviewed by: Janus JektvikFacts reviewed:

Why define screening criteria before opening CVs?

Define the criteria first so every reviewer applies the same job-related threshold. Recruiters are frequently asked to find someone “senior”, “commercial”, or able to “hit the ground running”. These phrases may communicate intent, but they do not tell a reviewer what evidence should count. If the criteria remain implicit, each reviewer creates a different threshold while reading applications.

Structured selection guidance consistently favors methods tied to the role and applied consistently. The practical implication is simple: define the job-related evidence before comparing people.

What should a screening criterion contain?

Skilltage guidance: use four fields that connect the role need to a repeatable review action:

CapabilityBusiness reasonAcceptable evidenceHandling missing evidence
The work the person must be able to doWhy that capability matters in this roleCV or application information that could reasonably demonstrate itWhether to reject, clarify later, or treat it as a preference

“Strong stakeholder management” becomes useful only when the team describes the stakeholders, the decisions involved, and evidence that would support the claim.

Worked example: recurring-revenue customer ownership

CapabilityBusiness reasonAcceptable evidenceHandling missing evidence
Own recurring-revenue customer relationships after contract signatureThe role must coordinate adoption, retention risks, and commercial handoversResponsibility for onboarding, renewals, expansion, implementation outcomes, or named customer-retention work; equivalent terminology countsDo not reject for a missing job title. Mark for clarification unless the application clearly shows the person has never owned post-sale customer work

Requirement review before intake

The define step keeps requirement text, priority, reviewer notes, and the final confirmation action together before candidates are processed.

Skilltage structured requirements dialog with requirement text, priority selector, note field, source hint, and confirm action
Skilltage app UI capture with fictional role data.

Which criteria are hard requirements, preferences, or trainable?

Reserve hard requirements for genuine entry conditions. These may include legal permission, an essential certification, a required language, or experience without which the person cannot perform the role. Preferences can help reviewers compare relevant strengths, but they should not quietly become rejection rules.

Treat trainable skills carefully. Calling every desired capability mandatory narrows the pool and makes screening less defensible.

Hard, standard, and preferred stay separate

Priority labels make entry conditions, normal screening criteria, and useful preferences visible as different reviewer concepts.

Skilltage structured requirements list showing hard, preferred, and nice-to-have priority examples
Skilltage app UI capture with fictional role data.

Requirements gate the intake workflow

The app blocks candidate intake until the team has reviewed and confirmed the screening basis for the opening.

Skilltage requirements confirmation notice blocking intake until requirements are confirmed
Skilltage app UI capture with fictional role data.

What counts as acceptable evidence?

Accept evidence that demonstrates the capability, even when the candidate uses a different title, sector, or vocabulary. Keywords are weak substitutes for meaning. Write evidence expectations broadly enough to recognize equivalent experience while remaining specific enough for reviewers to apply consistently.

Example:

  • Weak criterion: “SaaS experience”.
  • Better criterion: “Has owned recurring-revenue customer relationships and can show responsibility for retention, expansion, or implementation outcomes.”

How should two reviewers calibrate before screening?

Use one representative sample CV and compare the two reviews before opening the live candidate pool:

  1. Each reviewer independently marks evidence for every criterion.
  2. Each reviewer records missing or ambiguous information without turning it into failure.
  3. The reviewers compare their treatment of the same evidence and identify disagreements.
  4. The team rewrites any criterion that produced different thresholds, then repeats the exercise on that criterion.

If reviewers interpret a criterion differently, improve the criterion before processing a large candidate pool. Calibration is cheaper before screening than after a shortlist is challenged.

What are the limitations and decision boundaries?

A structured requirement does not prove that a candidate can perform the job, and a CV rarely contains complete evidence. The framework supports consistent initial review; it does not replace interviews, work samples, reference checks, accommodations, or professional judgement.

Skilltage guidance is to keep missing evidence distinct from negative evidence. A CV that does not mention a capability may justify clarification, not an automatic rejection.

Continue with a hiring intake template for a review-ready job brief, then use the human-review boundary for AI-assisted CV screening and the buyer checklist for evaluating recruitment tools.

Next step

Review one live role and rewrite its five most important requirements using capability, business reason, acceptable evidence, and consequence. If the team cannot agree on those four fields, the role is not ready for consistent screening.

References and provenance

Related resources

This is practical information, not legal advice. Skilltage supports human-reviewed decision support, not automated hiring decisions.

Want to see the workflow?

See how Skilltage turns role input into reviewable requirements before candidate evidence is assessed.

See structured screening in Skilltage