diff --git a/docs/01_introduction.md b/docs/01_introduction.md
new file mode 100644
index 0000000..02a7fbf
--- /dev/null
+++ b/docs/01_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.
diff --git a/docs/02_getting-started.md b/docs/02_getting-started.md
new file mode 100644
index 0000000..c892ab6
--- /dev/null
+++ b/docs/02_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](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
+
+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](mailto:justin.hume@gov.bc.ca). 
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
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.**
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.
diff --git a/docs/index.md b/docs/index.md
index 88ecb94..c116490 100644
--- a/docs/index.md
+++ b/docs/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)