Eligibility gates and decision rights
6 min read
Lesson objectives
- Apply eligibility gates and decision rights to a development case, explaining inputs and decision limits.
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
An initiative can appear promising on paper while remaining ethically or operationally unready. An eligibility gate asks what must be resolved before scoring benefits: may the proposed data be used for this precise purpose under the rules applicable to the organization? Is there a safe way to handle a beneficiary challenge? Can the partner actually provide the described service? Do not borrow a legal rule from another country to answer; ask the responsible specialist to document permission, scope, and retention. At design stage, mark each gate ‘met with evidence,’ ‘not met,’ or ‘unknown pending verification,’ then attach an appropriate interim decision. Unknown is not implicit authorization to start. If the service needs sensitive data and access has no established basis, a smaller pilot using the same data does not cure the restriction. A demand hypothesis might instead be tested with aggregated or less sensitive voluntarily supplied data, if permitted.
Separate three decision rights in the record. The outcome owner defines the change sought and who may be affected. The resource owner approves a spending cap and conditions. The relevant control specialist examines permitted data use, safety, and fairness in the organization's context. In a small institution one person may hold more than one role, but the responsibility must remain visible in the minutes. Do not let a technical specialist alone declare risk acceptable merely because a solution can be built, and do not let a funder interpret beneficiary silence as consent. State who can pause a trial after a material complaint, who remediates it, who authorizes restart, and when the matter returns for review. Record the reason, evidence, date, and scope of each decision so that permission for a limited trial does not silently become approval for general scaling.
A gate is not a permanent punishment. If partner capacity is unproved, name the evidence that would change the judgment: a staffing plan, service dates, and a tested referral process. If outcome data are incomplete, a limited learning phase may be allowed without collecting unnecessary data or claiming impact. If no defensible comparison can be established, operating results can still be reported under their proper names rather than marketing the program as having measured economic impact. A restart condition differs from a performance target. The former says what must exist for an alternative to be considered; the latter says what is expected after launch. Making ‘40% employment’ a prelaunch gate confuses expectation with evidence, whereas a named follow-up owner and a permission record can be verified now. Nor should an overall risk score compensate for an individual blocker. Many risks can be mitigated, but lacking a right to essential data may stop the design itself.
Give each gate a verifiable output rather than a broad verb such as ‘review privacy.’ For example, require a written record of permission to use contact details for six-month follow-up, access roles, and the date the operational copy will be deleted, reviewed by the organization's specialist under its actual rules. For the partner gate, require a dated schedule for 60 practical tasks with a contact owner, not merely a letter of intent. For equity, require a specified invitation process for eligible groups and a way to monitor reach gaps, not a promise that the program will be fair. A reviewer can then say yes, no, or unknown and request particular evidence. Do not copy gates mechanically across initiatives. A water service may need safety and operating checks unlike an employment service. The common question is which minimum condition, if absent, makes delivery or interpretation irresponsible.
A committee needs a usable challenge route, not an unread mailbox. In an employment referral service, a beneficiary may report incorrect data or wrongful exclusion. Name who receives the complaint, how identity is checked without collecting excess documents, who reviews exclusion, and how the outcome reaches the person. Measure complaint volume, resolution time, and recurring error types without displaying personal details on a public dashboard. If complaints reveal a systematic eligibility error, pausing new referrals and fixing records may be more appropriate than resolving one case. Few complaints do not prove absence of harm; people may not understand the route or may fear losing service. Check that instructions are clear in the service languages and that intended groups can actually use the channel.
Lesson summary
Eligibility gates and decision rights