Demographic eligibility
A requirement about who the funded work must serve, or in some programs who must own or lead the applicant. It is a rule about people rather than about organisations, and the two are often confused.
Part of the GrantTrove grant funding glossary — one entry for every field the catalogue stores.
Also called Priority populations · Target population · Who must benefit
In detail
Most demographic clauses are about beneficiaries: the project must serve veterans, rural residents, a defined income band, a specific age group. A smaller and legally distinct set is about the applicant itself — ownership, leadership, or membership requirements.
These clauses also shift with policy. A priority population named in one cycle may be absent in the next, which makes the date a record was last confirmed unusually load-bearing on this field.
Where a program expresses a preference rather than a requirement — extra points rather than a screen — that difference is the whole meaning of the clause, and it is kept in the source’s wording rather than compressed into a flag.
Against a scoring preference
A requirement excludes; a preference adjusts a score. An application that misses a requirement is not read, while one that misses a preference simply starts behind. Recording a preference as a requirement would hide programs an applicant could still win, and recording a requirement as a preference would send them into a screen they cannot pass. The record keeps whichever the source stated.
How GrantTrove stores it
- Demographic clauses are stored as their own dimension, separate from geography and entity type, so a preference for one is not read as a restriction on another.
- Because these clauses change between cycles, every record carries the date its fields were last confirmed against the source page.
Common questions
Is this about who applies or who benefits?
Usually who benefits. Requirements about the applicant’s own ownership or leadership exist but are a distinct and smaller category, and the record keeps the source’s framing rather than merging the two.
Do preferences make a program worth applying to?
Often, yes — a preference is not a barrier. That is exactly why it is not stored as an eligibility screen.
How current are these clauses?
They change with policy cycles more than most fields. Each record shows when it was last confirmed, so you can see how much weight the answer carries.