Starting an Intake
When processing a form using Caseflow Intake, it is expected that the user has access to both the form they are going to intake, the receipt date of that form, and either the VBA file number or the SSN for that Veteran. For Compensation and Pension lines of business, the Mail Portal is used to queue and display incoming mail. Business lines with smaller volumes sometimes have more manual processes for managing incoming mail.
NOTE: The Mail Portal is also responsible for uploading the document to the Veteran's VBMS eFolder. For this reason, intake does not handle uploading the document to the eFolder or any other document store.
In order to start an intake, the user can visit https://appeals.cf.ds.va.gov/intake where they can select the form they will be intaking. Then, they will type in the user's SSN or VBA file number to begin the intake.
Before the intake is started, Caseflow Intake performs a handful of automated checks:
- It validates that there is a Veteran that matches the SSN or file number entered
- It validates that the user performing the intake has the appropriate access level for the Veteran, based on the Veteran's sensitivity.
- It validates that no other user is currently performing an intake for the same type of form. In these cases, there is high risk of duplicate work being performed.
NOTE: If an intake stays open for longer than 24 hours, it is considered to be expired, and other users will be allowed to perform an intake for that Veteran again.
If the search succeeds, Caseflow will record the user who started it, and when the intake was started. This data can be used to form a paper trail of actions performed related to a Veteran's decision review forms, or collect data on how long it takes employees to process a form intake. It will also prevent that user from concurrently intaking any other form - they must either successfully complete this intake, or cancel it (see: "Canceling an intake").
- Home
- Acronyms and Glossary
- Caseflow products
- Caseflow Intake
- Caseflow Queue
- 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
- Technical Talks