-
Notifications
You must be signed in to change notification settings - Fork 19
Advance on Docket (AOD)
Matt Roth edited this page Oct 31, 2022
·
16 revisions
Some appeals are marked AOD, or Advance on Docket.
AOD cases represent the highest-priority cases. Veterans can be "advanced on the docket" due to age, financial hardship, terminal illness, etc., and therefore skip ahead in the line.
AOD status is automatic when a Veteran reaches 75 years of age, while other reasons require that the Veteran file a motion.
The logic for whether an appeal is considered AOD is mostly encapsulated in Appeal#aod? (which also looks for AdvanceOnDocketMotions, and in LegacyAppeal#aod? (which ultimately comes from VACOLS through AppealRepository).
- https://www.va.gov/decision-reviews/legacy-appeals/priority-review/
- https://www.knowva.ebenefits.va.gov/system/templates/selfservice/va_ssnew/help/customer/locale/en-US/portal/554400000001018/content/554400000139892/M21-5-Chapter-7-Section-F-Docketing-Certification-and-Claims-Folder-Transfer-to-the-Board-of-Veterans-Appeals#6
- https://www.ecfr.gov/current/title-38/chapter-I/part-20#p-20.902(c)
- Log in as a user within the AodTeam Organization.
- Click the "Search" link in the top right corner of the page next to the username.
- Enter the docket number or Veteran ID , for the case that you want to mark as AOD, into the search field and click search
- Click on the docket number to bring up the case details screen
- Click the "Edit" link under the veteran id
- The Update Advanced on Docket Status modal will pop up
- For the AOD Motion Disposition field, choose grant from the drop down
- For the Reason field, choose a reason from the drop down
- Click the Submit
- After the modal closes there will be an a success banner on the top of the screen and an AOD label under the Appeal Stream Type to show that the case has been successfully placed in AOD status.
- 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
- Tier 4
- Bat Team
- Technical Documentation
- Backend Code Patterns
- Backend Working Group
- FACOLS, VACOLS DB Schema
- Asyncable Models
- External Data: where and why
- Data Fetching Scripts
- Caseflow Data Model and Dictionary
- User Access Permissions
- Controller Schemas
- Constants
- 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