---
name: hiring-intake-scorecard
description: Hiring Intake Scorecard converts role mission, first-year outcomes, competency IDs, must-have gates into success profile, weighted scorecard, interview evidence plan, constraint register, and unresolved intake decisions, with cited evidence, explicit rules, and unresolved exceptions. Use for hiring intake scorecard, recurring review, and decision preparation.
license: Apache-2.0
metadata:
  adlass.categories: "hr-people/recruiting"
  adlass.industries: ""
  adlass.tags: "process-review,evidence,exceptions,decision-support,source-traceability"
  adlass.adaptation: "mapping"
  adlass.source: "original"
  adlass.version: "1"
---

# Hiring Intake Scorecard

## Purpose

Hiring Intake Scorecard turns the supplied records into success profile, weighted scorecard, interview evidence plan, constraint register, and unresolved intake decisions. It keeps source facts, derived values, recommendations, and limitations separate so each conclusion can be checked.

## Scope

Cover role mission, first-year outcomes, competency IDs, must-have gates, preferences, weights, rating anchors, interview questions, location, budget. Preserve source identifiers, dates, units, and wording needed to trace every result.

**Excluded for role definition and hiring-panel alignment:** changing source records, taking external actions, making a human approval or employment decision, and asserting facts absent from the corpus.

## Data basis

- Process documents and tables containing role mission, first-year outcomes, competency IDs, must-have gates, preferences, weights, rating anchors, interview questions, location, budget.
- Company policy, rubric, schema, templates, and reference tables in scope.
- Run input for period, audience, entity, or threshold when it changes this run.

## Result

Produce success profile, weighted scorecard, interview evidence plan, constraint register, and unresolved intake decisions. Each material row and conclusion cites a document, section, page, row, field, or run input.

## Quality criteria

- Every competency weights and evidence coverage record is included or has an exclusion reason.
- Calculations state fields, units, denominator, and rule.
- Missing, contradictory, stale, and ambiguous values stay labelled rather than guessed.
- Facts, interpretations, and proposed next actions use separate fields.
- Supplied terminology, thresholds, and status values are used consistently.
- The final limitations section states what the corpus could not establish.

## Instructions

Separate outcomes, requirements, preferences, and constraints. Use the competency framework; treat gates as gates only with explicit support. Do not score protected traits or invent a pass threshold. Preserve original values beside normalized values, cite every material finding, and use “not assessed” when required evidence or a rule is absent. When sources disagree, show both citations and explain the conflict. Keep row-level evidence in the supporting sheet and summarize only supported conclusions in the document.

## Adapt before use

- Map the requisition and competency mapping fields and row citation convention.
- Add the governing policy, rubric, schema, or reference tables to the scope.
- Define thresholds, status values, units, and exception severity.