-
Notifications
You must be signed in to change notification settings - Fork 19
Request issue eligibility requirements
Sally Maki edited this page Apr 22, 2020
·
2 revisions
Decisions being contested on appeals and higher level reviews have to have been decided within 372 days of the receipt date in order to be considered timely. Untimely issues are ineligible.
Timeliness exemptions can be requested by the veteran, which waives this requirement.
Issues that are connected to a legacy issue being opted in are not subject to the timeliness rules above (there are no checks that the decision date is within 372 days of the receipt date). However, they are impacted by a couple of other checks that the legacy issue is eligible to be opted-in. See Legacy issue opt-in eligibility requirements for more information on legacy issue eligibility rules.
- Home
- Acronyms and Glossary
- Caseflow products
- Caseflow Intake
- Caseflow Queue
- Appeals Consumer
- Caseflow Reader
- Caseflow eFolder
- Caseflow Hearings
- Caseflow Certification
- Caseflow APIs
- Appeal Status API
- Caseflow Dispatch
-
CSUM Roles
- System Admin
- VHA Team Management
- Active Record Queries Resource
- External Integrations
- Caseflow Demo
- Caseflow ProdTest
- Background
- Stuck Jobs
- VA Notify
- Caseflow-Team
- Frontend Best Practices
- Accessibility
- How-To
- Debugging Tips
- Adding a Feature Flag with FeatureToggle
- Editing AMA issues
- Editing a decision review
- Fixing task trees
- Investigating and diagnosing issues
- Data and Metric Request Workflow
- Exporting and Importing Appeals
- Explain page for Appeals
- Record associations and Foreign Keys
- Upgrading Ruby
- Stuck Appeals
- Testing Action Mailer Messages Locally
- Re-running Seed Files
- Rake Generator for Legacy Appeals
- Manually running Scheduled Jobs
- System Admin UI
- Caseflow Makefile
- Upgrading Postgresql from v11.7 to v14.8 Locally
- VACOLS VM Trigger Fix M1
- Using SlackService to Send a Job Alert
- Technical Talks