From 1c0eaa06758863d555c0e66d10fa755afc3505c9 Mon Sep 17 00:00:00 2001 From: kate-shepherd Date: Mon, 28 Sep 2026 11:29:35 -0700 Subject: [PATCH 01/19] APS-1234-Kate - Add introduction for Eligibility Factor Verification (EFV) Introduced documentation for Eligibility Factor Verification (EFV) outlining its purpose, functionality, and future considerations. --- docs/introduction.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 docs/introduction.md diff --git a/docs/introduction.md b/docs/introduction.md new file mode 100644 index 0000000..02a7fbf --- /dev/null +++ b/docs/introduction.md @@ -0,0 +1,25 @@ +# Introduction + +Eligibility Factor Verification, or EFV, helps government programs check specific facts used in eligibility decisions. + +Many programs need to confirm similar things, such as income, residency, or other information an applicant provides. Today, this can involve manual document review, screenshots, forms, or staff follow-up. EFV is intended to reduce that effort by helping programs check certain facts against approved or trusted data sources, where available. + +EFV does not decide if someone is eligible for a program. EFV is not a program rule engine. It does not approve or deny applications. It helps check facts that a program may use in its own decision process. The program still owns its eligibility rules and makes the final decision. + +EFV can support a program by returning a verification result and related information, such as the source used, when the check happened, and any limits or caveats that apply. Program staff or systems can then use that result to support a decision, focus review on exceptions, or reduce the need for applicants to provide documents. EFV is in early development. The first focus is income verification. + +Future eligibility factors may be explored over time based on: +- program need +- source availability +- agreements +- policy authority +- privacy and security requirements +- technical feasibility + +## Example + +A program may need to confirm whether an applicant meets an income rule. + +Without EFV, the applicant may need to upload tax documents, and staff may need to review them manually. + +With EFV, the program may be able to request an income verification check through a trusted source. The program receives a result and supporting details. The program then applies its own rules and decides what happens next. From b39aefe4c8fbe9fa4f449c8ab6870dc70e516cc8 Mon Sep 17 00:00:00 2001 From: kate-shepherd Date: Mon, 28 Sep 2026 12:28:15 -0700 Subject: [PATCH 02/19] APS-1234-Kate - Create getting-started.md for EFV documentation Added a comprehensive guide on getting started with EFV, outlining its usefulness, data-use requirements, and candidate criteria. --- docs/getting-started.md | 62 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 62 insertions(+) create mode 100644 docs/getting-started.md diff --git a/docs/getting-started.md b/docs/getting-started.md new file mode 100644 index 0000000..36cf70f --- /dev/null +++ b/docs/getting-started.md @@ -0,0 +1,62 @@ +# Getting Started + +Use this page to decide whether EFV may be useful for your program or service. + +EFV is still developing. The best first step is to contact the EFV team with a clear use case. The team can help determine whether EFV is a good fit, whether an existing verification factor is available, and what other teams or approvals may be involved. + +## When EFV may be useful + +EFV may be useful when your program needs to check a specific fact used in an eligibility decision. +EFV may help when your program wants to: + +- Use a trusted source instead of applicant-submitted documents +- Reduce manual document review or staff follow-up +- Support more consistent decisions +- Keep a record of what was checked, when, and against what source +- Help staff focus on exceptions or higher-risk cases +- Reuse a verification pattern that may also help other programs + +## Understanding data-use requirements + +Using EFV may require more than a technical connection. Before information can be requested or used, the consuming program and data provider may need to confirm: + +- The applicable legal authority +- Privacy requirements +- Agreements +- Consent or notice requirements +- Security controls +- Business rules + +These requirements will depend on the program, the eligibility factor, the data source, and the intended use. The EFV team can help identify the requirements and teams that may need to be involved. The consuming program remains responsible for confirming that it has the authority and approvals needed to request and use the information. + +## What makes a good EFV candidate + +A good EFV candidate is usually a verification need that is specific, repeatable, and connected to a trusted source. + +EFV may be a stronger fit when: + +- The same fact is checked often +- The current process is manual +- The information is not already easy to access or reuse +- The verification pattern could help more than one program + +## When EFV may not be the right fit + +EFV may not be the right fit when: + +- The decision depends on case-by-case judgment +- The fact cannot be checked through a trusted source +- The program does not have authority to request or use the data +- The information is already available through an existing dataset, API, service, or public source +- The program needs broad data access instead of a specific verification need +- The program needs policy design support, rather than verification support + +## Before you contact the EFV team + +You do not need a full solution before contacting the EFV team. + +Start with the eligibility fact you need to check, how you check it today, and what problem you are trying to solve. + +If you already know the potential data source or provider, intended use, legal authority, consent or notice requirements, privacy and security considerations, or agreement needs, include those as well. You do not need to have every requirement resolved before contacting the EFV team. + +To discuss whether EFV may be a fit for your program or service, contact the EFV team. From b31a786ed5ad388252e2fdbccc031dbb7ca8da46 Mon Sep 17 00:00:00 2001 From: kate-shepherd Date: Mon, 28 Sep 2026 12:30:47 -0700 Subject: [PATCH 03/19] Rename getting-started.md to 01_getting-started.md --- docs/{getting-started.md => 01_getting-started.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename docs/{getting-started.md => 01_getting-started.md} (100%) diff --git a/docs/getting-started.md b/docs/01_getting-started.md similarity index 100% rename from docs/getting-started.md rename to docs/01_getting-started.md From cc41f8faaa30563b1ec92176fdc2010622dafd66 Mon Sep 17 00:00:00 2001 From: kate-shepherd Date: Mon, 28 Sep 2026 12:31:05 -0700 Subject: [PATCH 04/19] Rename index.md to 00_index.md --- docs/{index.md => 00_index.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename docs/{index.md => 00_index.md} (100%) diff --git a/docs/index.md b/docs/00_index.md similarity index 100% rename from docs/index.md rename to docs/00_index.md From 01df907dccb9dddd6694d58b9318370970a61888 Mon Sep 17 00:00:00 2001 From: kate-shepherd Date: Mon, 28 Sep 2026 12:31:24 -0700 Subject: [PATCH 05/19] Rename introduction.md to 01_introduction.md --- docs/{introduction.md => 01_introduction.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename docs/{introduction.md => 01_introduction.md} (100%) diff --git a/docs/introduction.md b/docs/01_introduction.md similarity index 100% rename from docs/introduction.md rename to docs/01_introduction.md From b51d0f84eceeea17d896ee568602395970cc070d Mon Sep 17 00:00:00 2001 From: kate-shepherd Date: Mon, 28 Sep 2026 12:31:54 -0700 Subject: [PATCH 06/19] Change name for getting-started --- docs/{01_getting-started.md => 02_getting-started.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename docs/{01_getting-started.md => 02_getting-started.md} (100%) diff --git a/docs/01_getting-started.md b/docs/02_getting-started.md similarity index 100% rename from docs/01_getting-started.md rename to docs/02_getting-started.md From 184d384bd4ab07c106817122908b205b8dd0c667 Mon Sep 17 00:00:00 2001 From: kate-shepherd Date: Mon, 28 Sep 2026 12:35:53 -0700 Subject: [PATCH 07/19] ASP-1234-Kate Add eligibility factors documentation for EFV This document outlines the eligibility factors for EFV, including income verification and the requirements for supporting various factors. --- docs/03_eligibility-factors.md | 50 ++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 docs/03_eligibility-factors.md diff --git a/docs/03_eligibility-factors.md b/docs/03_eligibility-factors.md new file mode 100644 index 0000000..7e54032 --- /dev/null +++ b/docs/03_eligibility-factors.md @@ -0,0 +1,50 @@ +# Eligibility Factors + +Use this page to understand how EFV looks at possible eligibility factors. + +An eligibility factor is a specific fact that a program may need to check before making a decision. This could include income or other information used in program rules. + +EFV is organized around these factors. Each factor may use a different source, need different approvals, or have different limits. Because of this, EFV does not treat every factor the same way. + +The first EFV factor is income verification. EFV is starting with income verification as the first reusable verification capability that programs may be able to consume. + +Future factors may be explored over time based on: +- program need +- source availability +- agreements +- policy authority +- privacy and security requirements +- technical feasibility + +Not every eligibility fact needs EFV. Some facts may already be supported through an existing dataset, API, service, or program process. EFV is intended for verification needs that are specific, repeatable, and not already easy for programs to access or reuse. + +Before a factor can be supported through EFV, the EFV team needs to understand: + +- What fact the program needs to check +- Which program rule or workflow the check supports +- Whether there is a trusted source for the information +- Whether the program has authority to request or use the information +- What legal authority, agreements, consent or notice requirements, privacy protections, security controls, audit requirements, or other provider conditions apply +- Whether the data is current enough for the program’s use case +- Whether the verification pattern could be reused by other programs +- Whether there is a practical technical path to access or verify the information + +Data providers need confidence that their information will only be requested and used for an approved purpose and under the required conditions. As part of developing an eligibility factor, the EFV team can help identify what requirements may need to be supported. This may include: + +- technical requirements +- legal requirements +- privacy requirements +- consent requirements +- agreement requirements +- business requirements + +This may also include determining whether a required authorization or consent check needs to occur before a verification request is sent. The specific approach will depend on the provider, program, data source, and approved use case. + +A factor should not be presented as available until the following are understood well enough to guide users: + +- the source +- permitted purpose +- authority +- agreement needs +- technical path +- support needs From f9128ae57186442fb5df38e15e9a237dcda2c01b Mon Sep 17 00:00:00 2001 From: kate-shepherd Date: Mon, 28 Sep 2026 12:44:42 -0700 Subject: [PATCH 08/19] ASP-1234-Kate Add income verification documentation This document outlines the income verification process as the first eligibility factor in development through EFV, detailing its status, support, response implications, program readiness, and limitations. --- .../income-verification.md | 61 +++++++++++++++++++ 1 file changed, 61 insertions(+) create mode 100644 docs/03_eligibility-factors/income-verification.md diff --git a/docs/03_eligibility-factors/income-verification.md b/docs/03_eligibility-factors/income-verification.md new file mode 100644 index 0000000..198a0e1 --- /dev/null +++ b/docs/03_eligibility-factors/income-verification.md @@ -0,0 +1,61 @@ +# Income Verification + +Income verification is the first eligibility factor **in development** through EFV. + +This page provides factor-specific information for programs that may need to check income as part of an eligibility process. + +## Status + +Income verification is in development as the first EFV use case. + +## What income verification may support + +Income verification may support programs that need to check income-related information as part of an eligibility decision or review process. + +The type of response EFV returns will depend on the approved use case and source requirements. + +For example, a program may need to confirm whether an applicant meets an income rule without asking the applicant to upload tax documents for manual review. + +## What the response does not mean + +An income verification response does not decide whether someone is eligible for a program. + +The program remains responsible for: + +- Defining eligibility rules +- Applying program policy +- Deciding how the response is used +- Managing exceptions +- Completing any required staff review +- Making the final eligibility decision + +## Program readiness + +Before using income verification, a program may need to confirm: + +- The income rule or program requirement being supported +- The purpose for using the income information +- The authority to request or use the information +- Consent requirements +- Privacy and security requirements +- Agreement or memorandum of understanding (MOU) requirements +- Audit and monitoring expectations +- How long records or consent evidence must be retained +- Who can access the result +- How exceptions, denied responses, or incomplete matches will be handled + +Depending on the approved use case and source requirements, additional conditions may be required to send a request for income verification. These might include required authorization, consent, or other conditions. The EFV team will work with the consuming program, data provider, and appropriate privacy, legal, security, and technical teams to identify the required approach. + +## Caveats and limitations + +Income verification has source-specific requirements and constraints. + +Programs should not assume that income verification can be used until all of the following are confirmed: + +- authority +- agreement path +- consent model +- technical approach +- operational support expectations + +**The EFV team can help determine whether income verification may be a fit for a program use case and what discovery is needed next.** From 083e50ccced3083c5e0e10727239b791fd208566 Mon Sep 17 00:00:00 2001 From: kate-shepherd Date: Mon, 28 Sep 2026 12:51:13 -0700 Subject: [PATCH 09/19] ASP-1234-Kate - Revise Income Verification documentation for clarity Updated the Income Verification documentation to enhance clarity and structure, including reformatting bullet points and adding emphasis on key responsibilities and requirements. --- docs/03.1_income-verification.md | 61 ++++++++++++++++++++++++++++++++ 1 file changed, 61 insertions(+) create mode 100644 docs/03.1_income-verification.md diff --git a/docs/03.1_income-verification.md b/docs/03.1_income-verification.md new file mode 100644 index 0000000..4a8f7e4 --- /dev/null +++ b/docs/03.1_income-verification.md @@ -0,0 +1,61 @@ +# Income Verification + +Income verification is the first eligibility factor **in development** through EFV. + +This page provides factor-specific information for programs that may need to check income as part of an eligibility process. + +## Status + +Income verification is in development as the first EFV use case. + +## What income verification may support + +Income verification may support programs that need to check income-related information as part of an eligibility decision or review process. +The type of response EFV returns will depend on the approved use case and source requirements. + +For example, a program may need to confirm whether an applicant meets an income rule without asking the applicant to upload tax documents for manual review. + +## What the response does not mean + +An income verification response does not decide whether someone is eligible for a program. + +The program remains responsible for: + +- Defining eligibility rules +- Applying program policy +- Deciding how the response is used +- Managing exceptions +- Completing any required staff review +- Making the final eligibility decision + +## Program readiness + +Before using income verification, a program may need to confirm: + +- The income rule or program requirement being supported +- The purpose for using the income information +- The authority to request or use the information +- Consent requirements +- Privacy and security requirements +- Agreement or memorandum of understanding (MOU) requirements +- Audit and monitoring expectations +- How long records or consent evidence must be retained +- Who can access the result +- How exceptions, denied responses, or incomplete matches will be handled + +Depending on the approved use case and source requirements, additional conditions may be required to send a request for income verification. These might include required authorization, consent, or other conditions. The EFV team will work with the consuming program, data provider, and appropriate privacy, legal, security, and technical teams to identify the required approach. + +## Caveats and limitations + +Income verification has source-specific requirements and constraints. + +Programs should not assume that income verification can be used until all of the following are confirmed: + +- authority +- agreement path +- consent model +- permitted data elements +- technical approach +- operational support expectations + +**The EFV team can help determine whether income verification may be a fit for a program use case and what discovery is needed next.** From 9971b9c038a6d2f949afdb2b998757b976b351b6 Mon Sep 17 00:00:00 2001 From: kate-shepherd Date: Mon, 28 Sep 2026 12:51:55 -0700 Subject: [PATCH 10/19] Delete docs/03_eligibility-factors directory --- .../income-verification.md | 61 ------------------- 1 file changed, 61 deletions(-) delete mode 100644 docs/03_eligibility-factors/income-verification.md diff --git a/docs/03_eligibility-factors/income-verification.md b/docs/03_eligibility-factors/income-verification.md deleted file mode 100644 index 198a0e1..0000000 --- a/docs/03_eligibility-factors/income-verification.md +++ /dev/null @@ -1,61 +0,0 @@ -# Income Verification - -Income verification is the first eligibility factor **in development** through EFV. - -This page provides factor-specific information for programs that may need to check income as part of an eligibility process. - -## Status - -Income verification is in development as the first EFV use case. - -## What income verification may support - -Income verification may support programs that need to check income-related information as part of an eligibility decision or review process. - -The type of response EFV returns will depend on the approved use case and source requirements. - -For example, a program may need to confirm whether an applicant meets an income rule without asking the applicant to upload tax documents for manual review. - -## What the response does not mean - -An income verification response does not decide whether someone is eligible for a program. - -The program remains responsible for: - -- Defining eligibility rules -- Applying program policy -- Deciding how the response is used -- Managing exceptions -- Completing any required staff review -- Making the final eligibility decision - -## Program readiness - -Before using income verification, a program may need to confirm: - -- The income rule or program requirement being supported -- The purpose for using the income information -- The authority to request or use the information -- Consent requirements -- Privacy and security requirements -- Agreement or memorandum of understanding (MOU) requirements -- Audit and monitoring expectations -- How long records or consent evidence must be retained -- Who can access the result -- How exceptions, denied responses, or incomplete matches will be handled - -Depending on the approved use case and source requirements, additional conditions may be required to send a request for income verification. These might include required authorization, consent, or other conditions. The EFV team will work with the consuming program, data provider, and appropriate privacy, legal, security, and technical teams to identify the required approach. - -## Caveats and limitations - -Income verification has source-specific requirements and constraints. - -Programs should not assume that income verification can be used until all of the following are confirmed: - -- authority -- agreement path -- consent model -- technical approach -- operational support expectations - -**The EFV team can help determine whether income verification may be a fit for a program use case and what discovery is needed next.** From 89ce1ef23a6e1e2b90094d139dd58c4b8cc09693 Mon Sep 17 00:00:00 2001 From: kate-shepherd Date: Mon, 28 Sep 2026 12:52:33 -0700 Subject: [PATCH 11/19] Rename 03.1_income-verification.md to 03_1_income-verification.md --- docs/{03.1_income-verification.md => 03_1_income-verification.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename docs/{03.1_income-verification.md => 03_1_income-verification.md} (100%) diff --git a/docs/03.1_income-verification.md b/docs/03_1_income-verification.md similarity index 100% rename from docs/03.1_income-verification.md rename to docs/03_1_income-verification.md From c9986673021731673af1f305b4f044cdc0efa388 Mon Sep 17 00:00:00 2001 From: kate-shepherd Date: Mon, 28 Sep 2026 12:53:26 -0700 Subject: [PATCH 12/19] Rename 03_eligibility-factors.md to 03_.eligibility-factors.md --- docs/{03_eligibility-factors.md => 03_.eligibility-factors.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename docs/{03_eligibility-factors.md => 03_.eligibility-factors.md} (100%) diff --git a/docs/03_eligibility-factors.md b/docs/03_.eligibility-factors.md similarity index 100% rename from docs/03_eligibility-factors.md rename to docs/03_.eligibility-factors.md From 8abab3c5f50b01e03b9e789406058a4e23db5e71 Mon Sep 17 00:00:00 2001 From: kate-shepherd Date: Mon, 28 Sep 2026 12:55:54 -0700 Subject: [PATCH 13/19] Add support and next steps documentation --- docs/04_next-steps.md | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 docs/04_next-steps.md diff --git a/docs/04_next-steps.md b/docs/04_next-steps.md new file mode 100644 index 0000000..463903a --- /dev/null +++ b/docs/04_next-steps.md @@ -0,0 +1,11 @@ +# Support and Next Steps + +EFV is still developing. Support channels and service expectations will be added as they are confirmed. + +To discuss whether EFV may be a fit for your program or service, contact the EFV team: [Justin.Hume@gov.bc.ca](mailto:justin.hume@gov.bc.ca). + +Include the program name, the eligibility factor you want to verify, the current process, and any timeline or pilot dependency. + +## Related resources + +Links will be added as they become available. From 73c282a910a03407b7f044d923d85c16afef95f2 Mon Sep 17 00:00:00 2001 From: kate-shepherd Date: Mon, 28 Sep 2026 12:57:32 -0700 Subject: [PATCH 14/19] ASP-1234-Kate - Add contact link for EFV team in getting started guide --- docs/02_getting-started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/02_getting-started.md b/docs/02_getting-started.md index 36cf70f..b172f96 100644 --- a/docs/02_getting-started.md +++ b/docs/02_getting-started.md @@ -2,7 +2,7 @@ Use this page to decide whether EFV may be useful for your program or service. -EFV is still developing. The best first step is to contact the EFV team with a clear use case. The team can help determine whether EFV is a good fit, whether an existing verification factor is available, and what other teams or approvals may be involved. +EFV is still developing. The best first step is to [contact the EFV team](mailto:justin.hume@gov.bc.ca) with a clear use case. The team can help determine whether EFV is a good fit, whether an existing verification factor is available, and what other teams or approvals may be involved. ## When EFV may be useful From 85fadf38c96de0354625415ae646eb5785bc6e66 Mon Sep 17 00:00:00 2001 From: kate-shepherd Date: Mon, 28 Sep 2026 12:58:43 -0700 Subject: [PATCH 15/19] ASP-1234-Kate - Add email link to contact EFV team --- docs/02_getting-started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/02_getting-started.md b/docs/02_getting-started.md index b172f96..c892ab6 100644 --- a/docs/02_getting-started.md +++ b/docs/02_getting-started.md @@ -59,4 +59,4 @@ Start with the eligibility fact you need to check, how you check it today, and w If you already know the potential data source or provider, intended use, legal authority, consent or notice requirements, privacy and security considerations, or agreement needs, include those as well. You do not need to have every requirement resolved before contacting the EFV team. -To discuss whether EFV may be a fit for your program or service, contact the EFV team. +To discuss whether EFV may be a fit for your program or service, [contact the EFV team](mailto:justin.hume@gov.bc.ca). From 1d2a1034fa27289149f621692f6851783a0807ae Mon Sep 17 00:00:00 2001 From: kate-shepherd Date: Mon, 28 Sep 2026 13:05:55 -0700 Subject: [PATCH 16/19] ASP-1234-Kate - Revise EFV documentation and add related links Updated the content to provide an overview of Eligibility Factor Verification and added links to related documentation. --- docs/00_index.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/00_index.md b/docs/00_index.md index 88ecb94..b70c977 100644 --- a/docs/00_index.md +++ b/docs/00_index.md @@ -1,5 +1,9 @@ # Eligibility Factor Verification (EFV) -Coming soon. +Eligibility Factor Verification, or EFV, helps government programs check specific facts used in eligibility decisions. -We are preparing the Eligibility Factor Verification documentation. Check back for updates. +1. [Introduction](01_introduction.md) +2. [Getting Started](02_getting-started.md) +3. [Eligibility Factors](03_.eligibility-factors.md) + - [Income Verification](03_1_income-verification.md) +4. [Next Steps](04_next-steps) From edc3ffeebf1e8f92e07f261992e34d602de517ea Mon Sep 17 00:00:00 2001 From: kate-shepherd Date: Mon, 28 Sep 2026 13:20:02 -0700 Subject: [PATCH 17/19] Revise EFV documentation to show upcoming updates Updated the EFV documentation to indicate it is coming soon. --- docs/00_index.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/docs/00_index.md b/docs/00_index.md index b70c977..88ecb94 100644 --- a/docs/00_index.md +++ b/docs/00_index.md @@ -1,9 +1,5 @@ # Eligibility Factor Verification (EFV) -Eligibility Factor Verification, or EFV, helps government programs check specific facts used in eligibility decisions. +Coming soon. -1. [Introduction](01_introduction.md) -2. [Getting Started](02_getting-started.md) -3. [Eligibility Factors](03_.eligibility-factors.md) - - [Income Verification](03_1_income-verification.md) -4. [Next Steps](04_next-steps) +We are preparing the Eligibility Factor Verification documentation. Check back for updates. From 3fff09a311ae161a5c7bcc64757be5eb694d6631 Mon Sep 17 00:00:00 2001 From: kate-shepherd Date: Tue, 29 Sep 2026 09:55:07 -0700 Subject: [PATCH 18/19] EFV-1234-Kate Enhance EFV documentation with detailed sections Expanded the Eligibility Factor Verification documentation with detailed explanations of its purpose, audience, use cases, and workflow. --- docs/00_index.md | 55 ++++++++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 53 insertions(+), 2 deletions(-) diff --git a/docs/00_index.md b/docs/00_index.md index 88ecb94..c116490 100644 --- a/docs/00_index.md +++ b/docs/00_index.md @@ -1,5 +1,56 @@ # Eligibility Factor Verification (EFV) -Coming soon. +## What it is -We are preparing the Eligibility Factor Verification documentation. Check back for updates. +Eligibility Factor Verification, or EFV, helps government programs check specific facts used in eligibility decisions. + +EFV is intended for situations where a program needs to verify information through an approved or trusted source, instead of relying only on applicant-submitted documents or manual review. + +EFV can help programs reduce repeated document checks, support more consistent decisions, and keep a record of what was checked, when, and against what source. + +EFV does not decide if someone is eligible for a program. It is not a program rule engine and does not approve or deny applications. Programs still own their eligibility rules and make the final decision. + +## Who this is for + +EFV supports both those building eligibility systems and those responsible for program outcomes. + +### Primary audience + +- Developers building eligibility tools and integrations +- Solution architects designing automated adjudication systems + +### Secondary audience + +- Product owners managing benefit programs +- Program and policy leads defining eligibility criteria +- Adjudicators and intake staff using decision-support tools + +## When to use Eligibility Factor Verification + +EFV may be useful when your program needs to check a specific fact used in an eligibility decision. + +EFV may help when your program wants to: + +- Use a trusted source instead of applicant-submitted documents +- Reduce manual document review or staff follow-up +- Support more consistent decisions +- Keep a record of what was checked, when, and against what source +- Help staff focus on exceptions or higher-risk cases +- Reuse a verification pattern that may also help other programs + +## How it works (high-level) + +- A program needs to confirm whether an applicant meets a specific eligibility requirement. +- With EFV, the program requests a verification check through a trusted Authoritative Data source. +- The program receives a result and supporting details. +- The program applies its own rules and decides what happens next. + +## Where to go next + +See the EFV documentation for more detailed information: + +1. [Introduction](01_introduction.md) +2. [Getting Started](02_getting-started.md) +3. [Eligibility Factors](03_.eligibility-factors.md) + - [Income Verification](03_1_income-verification.md) +4. [Next Steps](04_next-steps.md) From c9ae2bb6e5a3282c93766dd964a698aca9754166 Mon Sep 17 00:00:00 2001 From: kate-shepherd Date: Tue, 6 Oct 2026 09:56:01 -0700 Subject: [PATCH 19/19] Rename 00_index.md to index.md --- docs/{00_index.md => index.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename docs/{00_index.md => index.md} (100%) diff --git a/docs/00_index.md b/docs/index.md similarity index 100% rename from docs/00_index.md rename to docs/index.md