Eligibility Criteria Checklist¶
Criteria checklist — instantiates Predicate Criterion Formalization
Turns a qualifying condition into an ordered list of evidence-backed criteria a reviewer applies to one candidate at a time.
An Eligibility Criteria Checklist turns a qualifying condition into an ordered list of individually checkable criteria that a reviewer applies to one candidate at a time, recording for each whether the required evidence has been supplied. Its defining nature is procedural application in a human workflow: it does not define what the criteria mean — it assumes those are fixed elsewhere — and it does not select a population; it walks a single candidate item by item and reaches a yes/no by confirming each criterion is satisfied on admissible evidence, under an explicit rule about who must supply that evidence and to what standard. What makes it THIS mechanism is the pairing of per-item evidence with a burden of proof: an item is not "true" because it feels true, but because the evidence the checklist demands is present.
Example¶
A caseworker assesses an application for disability benefits. The statute's definition of "qualifying disability" is fixed elsewhere; the checklist is how she applies it to Mr. Alvarez. It lists the criteria: a medically determinable impairment (evidence: signed clinician report), a condition expected to last twelve months or more (evidence: prognosis statement), and a functional limitation preventing substantial work (evidence: functional assessment plus work history). For each item the checklist names the document that counts and states who must provide it — the burden sits with the applicant, and the standard is preponderance, not certainty.
Walking the list, two items are satisfied on the submitted reports; the third lacks a functional assessment. Because the burden rule is explicit, the caseworker neither guesses nor denies outright — the item is not yet established, and the checklist's evidence rule tells her exactly what to request. Setup to outcome: an amorphous "does he qualify?" becomes a documented, reproducible determination that another caseworker could re-run and reach the same result on the same evidence.
How it works¶
- Order the criteria. List each necessary condition as its own line so the determination is decomposed and it is always visible which item, if any, failed.
- Bind evidence to each item. Every criterion names the admissible evidence that establishes it, so "satisfied" means "supported," not "assumed."
- Assign the burden and standard. State who must supply the evidence and how strong it must be (preponderance versus clear-and-convincing); a missing document is handled by the burden rule, not by defaulting to no.
- Conjoin to a determination. All necessary items satisfied ⇒ eligible; any item unmet ⇒ not-yet-eligible, with the specific gap named.
Tuning parameters¶
- Evidence stringency — how strong the required proof is per item. Stricter reduces false grants but raises applicant burden and denials on paperwork alone.
- Burden placement — applicant-supplies versus agency-verifies. Shifting the burden trades throughput against accuracy and fairness.
- Gating versus independent items — whether a failed gate item halts the rest (saving effort but hiding other gaps) or every item is always checked.
- Standard of proof — the confidence threshold each item must clear before it counts as satisfied.
- Compensation — strict all-must-pass versus allowing a strong item to offset a weak one (rubric-style), which adds flexibility and subjectivity.
When it helps, and when it misleads¶
Its strength is that it makes a determination reproducible, decomposed, and defensible — two reviewers reach the same answer on the same evidence, and a denial can point to the exact unmet item. The checklist form itself reduces omission errors in complex, high-stakes work.[n1]
Its failure mode is rigidity: a criterion tuned for the typical case mishandles the atypical one, and a reviewer treats a missing document as a disqualification when the burden rule should have triggered a request instead. The classic misuse is quieter — items accumulate over time until the checklist encodes a stricter standard than the underlying rule ever intended (criterion creep). The discipline that guards against this is to keep each item traceable to the defined criterion it enforces, and to keep the burden rule explicit so "not supplied" and "does not qualify" never silently merge.
How it implements the components¶
evidence_basis_rule— each criterion names the admissible evidence that establishes it, so the determination rests on documents rather than impressions.truth_evaluation_logic— the checklist conjoins its necessary items (all must be satisfied) into a single eligible/not-eligible verdict, and its decomposition shows precisely which item drove the result.confidence_and_burden_rule— it fixes who bears the burden of supplying evidence and the standard of proof each item must meet, so absence of a document has a defined consequence rather than a default one.
It does NOT define what the criteria mean or which candidates they range over — the property_definition and candidate_domain_statement are Policy Definition of Terms, which the checklist applies rather than authors; and the full separation and routing of indeterminate_case_policy states belongs to Unknown-State Routing Rule.
Related¶
- Instantiates: Predicate Criterion Formalization — the checklist is the human-workflow application instance, running one candidate through the criterion.
- Consumes: Policy Definition of Terms — the checklist applies the term meanings the definitions fix.
- Sibling mechanisms: Boolean Guard Clause · SQL WHERE Clause or Query Filter · Truth Table · Decision Table · Policy Definition of Terms · Predicate Version Registry · Test Case Matrix · Counterexample Register · Unknown-State Routing Rule
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: A reviewer evaluates one candidate's evidence against decomposed necessary criteria and produces a supported eligibility or not-yet-eligible finding with the specific gap named.
Nearest alternative: Decision, Gate & Allocation — Admission or routing may follow, but the checklist's defining output is the evidence-based qualification finding rather than the downstream allocation decision.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Public Administration & Policy
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Benefits and case administration established ordered, evidence-backed checks that apply program eligibility conditions consistently to each applicant.
Related originating lineages:
- Law & Governance — Legal elements tests supplied conjunctive criteria, evidence requirements, and reviewability.
Review resolution: Federal program rules explicitly require determining, verifying, and documenting eligibility; that administrative practice best explains the checklist, with law supplying its formal structure.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
[n1] Atul Gawande's The Checklist Manifesto argues that in complex, high-stakes work a simple checklist reliably prevents the errors of omission that expertise alone does not — the failure isn't ignorance but forgetting to apply what one already knows. An eligibility checklist borrows exactly this: it converts a criterion into a form that cannot skip a required step. ↩