| README | All tasks | DR tasks | ES tasks | H tasks |

Docket types: Direct Review (DR), Evidence Submission (ES), and Hearing (H).

Appeals Process: mural

Tasks Overview #

The tasks presented on this page are organized into phases of the appeal process:

• Regional Office Phase
• Intake Phase
• Hearing Phase
• Decision Phase
• Quality Review Phase
• Dispatch Phase

How to interpret bullets and subbullets in “Associated tasks” sections:

• When a child task is always (or almost always) a child of a specific parent task, it is shown as a subbullet under the associated parent task.
• When a task is noted as only occurring for certain dockets, all child tasks also only occur for those specified dockets.
• The parent-child relationships were inferred by examining the Parent Tasks section of each task page for all dockets (e.g., Parent Tasks for JudgeDecisionReviewTask_User). The frequent parent-child relationships for each docket type ( DR:parent-child, ES:parent-child and H:parent-child) was also helpful.

At the bottom of the page are:

• MailTasks
• other tasks and
• deprecated tasks

Regional Office Phase #

Background:

• VSOs

Associated tasks:

• RootTask_Organization - not specific this phase
  • TrackVeteranTask_Organization - can happen at any phase

Intake Phase #

Background:

• Intake
• Caseflow Intake
  • Intake Data Model
• Issues presentation
• Intake Search training video

Tasks created upon Intake Phase success (see Appeal#create_tasks_on_intake_success!):

• TrackVeteranTask_Organization
• DistributionTask_Organization
  • EvidenceSubmissionWindowTask_Organization if in ES docket
  • ScheduleHearingTask_Organization if in H docket
  • InformalHearingPresentationTask_Organization if the representing VSO should_write_ihp?(appeal); occurs only in DR and ES dockets
    • InformalHearingPresentationTask_User
• TranslationTask_Organization
  • TranslationTask_User
• VeteranRecordRequest_Organization

The following fake task tree merges several appeals to exemplify parent-child task relationships associated with the Intake and prior phases (Click on task links above to browse for task trees of actual appeals):

flowchart TD style 0.RootTask fill:#eeeeee 0.RootTask(["0.RootTask\n(organization)"]) style 1.TrackVeteranTask fill:#cccccc 1.TrackVeteranTask(["1.TrackVeteranTask\n(organization)"]) style 2.DistributionTask fill:#dddddd 2.DistributionTask>"2.DistributionTask\n(organization)"] style 3.InformalHearingPresentationTask fill:#fdb462 3.InformalHearingPresentationTask["3.InformalHearingPresentationTask\n(organization)"] style 4.TranslationTask fill:#bebada 4.TranslationTask["4.TranslationTask\n(organization)"] style 5.TranslationTask fill:#bebada 5.TranslationTask["5.TranslationTask\n(user)"] style 6.InformalHearingPresentationTask fill:#fdb462 6.InformalHearingPresentationTask["6.InformalHearingPresentationTask\n(user)"] style 7.VeteranRecordRequest fill:#ffed6f 7.VeteranRecordRequest["7.VeteranRecordRequest\n(organization)"] 0.RootTask --> 1.TrackVeteranTask 0.RootTask --> 2.DistributionTask 2.DistributionTask --> 3.InformalHearingPresentationTask 2.DistributionTask --> 4.TranslationTask 4.TranslationTask --> 5.TranslationTask 3.InformalHearingPresentationTask --> 6.InformalHearingPresentationTask 0.RootTask --> 7.VeteranRecordRequest

Hearing Phase #

Background:

• Caseflow Hearings

Associated tasks:

• RootTask_Organization - not specific this phase
  • DistributionTask_Organization
    • HearingTask_Organization only in Hearing docket; almost always a child task of DistributionTask_Organization
      • ScheduleHearingTask_Organization
        • HearingAdminActionTask - blocks scheduling a Veteran for a hearing. A few scenarios (e.g., missing data or Veteran situations) automatically create HearingAdminTasks. A hearing coordinator must resolve these before scheduling a Veteran. Subclasses of various hearing admin actions are listed below.
        • HearingAdminActionVerifyAddressTask_Organization
          • HearingAdminActionVerifyAddressTask_User
        • HearingAdminActionOtherTask_Organization
          • HearingAdminActionOtherTask_User
        • HearingAdminActionForeignVeteranCaseTask_Organization
        • HearingAdminActionFoiaPrivacyRequestTask_Organization
          • HearingAdminActionFoiaPrivacyRequestTask_User
        • HearingAdminActionContestedClaimantTask - 0 occurrences
      • AssignHearingDispositionTask_Organization or ChangeHearingDispositionTask_Organization
        • NoShowHearingTask_Organization
          • NoShowHearingTask_User
          • TimedHoldTask_Organization
        • TranscriptionTask_Organization only in Hearing docket (1 occurrence in ES docket); can also be a child of MissingHearingTranscriptsColocatedTask_Organization
• EvidenceSubmissionWindowTask_Organization only in ES and H dockets

The following fake task tree merges several appeals to exemplify parent-child task relationships associated with the Hearing and prior phases (Click on task links above to browse for task trees of actual appeals):

flowchart TD style 0.RootTask fill:#eeeeee 0.RootTask(["0.RootTask\n(organization)"]) style 1.TrackVeteranTask fill:#cccccc 1.TrackVeteranTask(["1.TrackVeteranTask\n(organization)"]) style 2.DistributionTask fill:#dddddd 2.DistributionTask>"2.DistributionTask\n(organization)"] style 3.HearingTask fill:#fb8072 3.HearingTask["3.HearingTask\n(organization)"] style 4.ScheduleHearingTask fill:#80b1d3 4.ScheduleHearingTask["4.ScheduleHearingTask\n(organization)"] style 7.HearingAdminActionVerifyAddressTask fill:#ffed6f 7.HearingAdminActionVerifyAddressTask["7.HearingAdminActionVerifyAddressTask\n(organization)"] style 8.HearingAdminActionVerifyAddressTask fill:#ffed6f 8.HearingAdminActionVerifyAddressTask["8.HearingAdminActionVerifyAddressTask\n(user)"] 4.ScheduleHearingTask --> 7.HearingAdminActionVerifyAddressTask 7.HearingAdminActionVerifyAddressTask --> 8.HearingAdminActionVerifyAddressTask style 9.HearingAdminActionFoiaPrivacyRequestTask fill:#ffed6f 9.HearingAdminActionFoiaPrivacyRequestTask["9.HearingAdminActionFoiaPrivacyRequestTask\n(organization)"] style 10.HearingAdminActionFoiaPrivacyRequestTask fill:#ffed6f 10.HearingAdminActionFoiaPrivacyRequestTask["10.HearingAdminActionFoiaPrivacyRequestTask\n(user)"] 4.ScheduleHearingTask --> 9.HearingAdminActionFoiaPrivacyRequestTask 9.HearingAdminActionFoiaPrivacyRequestTask --> 10.HearingAdminActionFoiaPrivacyRequestTask style 5.TranslationTask fill:#bebada 5.TranslationTask["5.TranslationTask\n(organization)"] style 6.TranslationTask fill:#bebada 6.TranslationTask["6.TranslationTask\n(user)"] 3.HearingTask --> 5.TranslationTask 5.TranslationTask --> 6.TranslationTask style 11.AssignHearingDispositionTask fill:#8dd3c7 11.AssignHearingDispositionTask["11.AssignHearingDispositionTask\n(organization)"] style 12.NoShowHearingTask fill:#b3de69 12.NoShowHearingTask["12.NoShowHearingTask\n(organization)"] style 13.TimedHoldTask fill:#fccde5 13.TimedHoldTask["13.TimedHoldTask\n(organization)"] style 14.NoShowHearingTask fill:#b3de69 14.NoShowHearingTask["14.NoShowHearingTask\n(user)"] 11.AssignHearingDispositionTask --> 12.NoShowHearingTask 12.NoShowHearingTask --> 13.TimedHoldTask 12.NoShowHearingTask --> 14.NoShowHearingTask style 15.ChangeHearingDispositionTask fill:#d9d9d9 15.ChangeHearingDispositionTask["15.ChangeHearingDispositionTask\n(organization)"] style 16.TranscriptionTask fill:#fb8072 16.TranscriptionTask["16.TranscriptionTask\n(organization)"] style 17.EvidenceSubmissionWindowTask fill:#fccde5 17.EvidenceSubmissionWindowTask["17.EvidenceSubmissionWindowTask\n(organization)"] 3.HearingTask --> 15.ChangeHearingDispositionTask 15.ChangeHearingDispositionTask --> 16.TranscriptionTask 15.ChangeHearingDispositionTask --> 17.EvidenceSubmissionWindowTask 0.RootTask --> 1.TrackVeteranTask 0.RootTask --> 2.DistributionTask 3.HearingTask --> 4.ScheduleHearingTask 2.DistributionTask --> 3.HearingTask 3.HearingTask --> 11.AssignHearingDispositionTask

Decision Phase #

Background:

• Caseflow Queue
  • VLJ Support, interactions with other teams (FOIA/Privacy Act, IHP, …)
  • Organizations
  • Fixing task trees
  • structure_render and task tree render
• Caseflow Reader
• Routing of admin actions changed (deprecating some Colocated tasks)

Associated tasks:

• RootTask_Organization - not specific this phase
  • JudgeAssignTask_User
    • AttorneyTask_User
  • JudgeDecisionReviewTask_User
    • AttorneyTask_User
    • AttorneyRewriteTask_User

Colocated tasks are usually children of AttorneyTasks:

The following fake task tree merges several appeals to exemplify parent-child task relationships associated with the Decision phase (Click on task links above to browse for task trees of actual appeals):

flowchart TD style 0.RootTask fill:#eeeeee 0.RootTask(["0.RootTask\n(organization)"]) style 5.JudgeAssignTask fill:#ccebc5 5.JudgeAssignTask[\"5.JudgeAssignTask\n(user)"/] style 6.AttorneyTask fill:#bc80bd 6.AttorneyTask["6.AttorneyTask\n(user)"] style 7.OtherColocatedTask fill:#80b1d3 7.OtherColocatedTask["7.OtherColocatedTask\n(organization)"] style 8.OtherColocatedTask fill:#80b1d3 8.OtherColocatedTask["8.OtherColocatedTask\n(user)"] 0.RootTask --> 5.JudgeAssignTask 5.JudgeAssignTask --> 6.AttorneyTask 6.AttorneyTask --> 7.OtherColocatedTask 7.OtherColocatedTask --> 8.OtherColocatedTask style 9.JudgeDecisionReviewTask fill:#d9d9d9 9.JudgeDecisionReviewTask[["9.JudgeDecisionReviewTask\n(user)"]] style 10.AttorneyTask fill:#bc80bd 10.AttorneyTask["10.AttorneyTask\n(user)"] style 19.AttorneyRewriteTask fill:#b3de69 19.AttorneyRewriteTask["19.AttorneyRewriteTask\n(user)"] 0.RootTask --> 9.JudgeDecisionReviewTask 9.JudgeDecisionReviewTask --> 10.AttorneyTask 9.JudgeDecisionReviewTask --> 19.AttorneyRewriteTask style 11.IhpColocatedTask fill:#bcffff 11.IhpColocatedTask["11.IhpColocatedTask\n(organization)"] style 12.IhpColocatedTask fill:#bcffff 12.IhpColocatedTask["12.IhpColocatedTask\n(user)"] style 13.MissingRecordsColocatedTask fill:#bebada 13.MissingRecordsColocatedTask["13.MissingRecordsColocatedTask\n(organization)"] style 14.MissingRecordsColocatedTask fill:#bebada 14.MissingRecordsColocatedTask["14.MissingRecordsColocatedTask\n(user)"] 10.AttorneyTask --> 11.IhpColocatedTask 11.IhpColocatedTask --> 12.IhpColocatedTask 10.AttorneyTask --> 13.MissingRecordsColocatedTask 13.MissingRecordsColocatedTask --> 14.MissingRecordsColocatedTask style 15.TranslationColocatedTask fill:#ccebc5 15.TranslationColocatedTask["15.TranslationColocatedTask\n(organization)"] style 16.TranslationTask fill:#bcbd22 16.TranslationTask["16.TranslationTask\n(organization)"] 10.AttorneyTask --> 15.TranslationColocatedTask 15.TranslationColocatedTask --> 16.TranslationTask style 17.MissingHearingTranscriptsColocatedTask fill:#eba5ea 17.MissingHearingTranscriptsColocatedTask["17.MissingHearingTranscriptsColocatedTask\n(organization)"] style 18.TranscriptionTask fill:#fb8072 18.TranscriptionTask["18.TranscriptionTask\n(organization)"] 10.AttorneyTask --> 17.MissingHearingTranscriptsColocatedTask 17.MissingHearingTranscriptsColocatedTask --> 18.TranscriptionTask

Quality Review Phase #

Background:

• Quality Review

Associated tasks:

• QualityReviewTask_Organization
  • QualityReviewTask_User
    • JudgeQualityReviewTask_User
      • AttorneyQualityReviewTask_User

The following fake task tree merges several appeals to exemplify parent-child task relationships associated with the Quality Review phase (Click on task links above to browse for task trees of actual appeals):

flowchart TD style 0.RootTask fill:#eeeeee 0.RootTask(["0.RootTask\n(organization)"]) style 3.QualityReviewTask fill:#fdb462 3.QualityReviewTask[\"3.QualityReviewTask\n(organization)"\] style 4.QualityReviewTask fill:#fdb462 4.QualityReviewTask[\"4.QualityReviewTask\n(user)"\] style 5.JudgeQualityReviewTask fill:#bc80bd 5.JudgeQualityReviewTask["5.JudgeQualityReviewTask\n(user)"] style 6.AttorneyQualityReviewTask fill:#bc80bd 6.AttorneyQualityReviewTask["6.AttorneyQualityReviewTask\n(user)"] 0.RootTask --> 3.QualityReviewTask 3.QualityReviewTask --> 4.QualityReviewTask 4.QualityReviewTask --> 5.JudgeQualityReviewTask 5.JudgeQualityReviewTask --> 6.AttorneyQualityReviewTask

Dispatch Phase #

Background:

• BVA Dispatch

Associated tasks:

• BvaDispatchTask_Organization
  • BvaDispatchTask_User
    • JudgeDispatchReturnTask_User almost only in DR and ES dockets
      • AttorneyDispatchReturnTask_User only in DR and ES dockets

The following fake task tree merges several appeals to exemplify parent-child task relationships associated with the Quality Review phase (Click on task links above to browse for task trees of actual appeals):

flowchart TD style 0.RootTask fill:#eeeeee 0.RootTask(["0.RootTask\n(organization)"]) style 6.BvaDispatchTask fill:#b3de69 6.BvaDispatchTask{{"6.BvaDispatchTask\n(organization)"}} style 7.BvaDispatchTask fill:#b3de69 7.BvaDispatchTask{{"7.BvaDispatchTask\n(user)"}} style 8.JudgeDispatchReturnTask fill:#ffffb3 8.JudgeDispatchReturnTask["8.JudgeDispatchReturnTask\n(user)"] style 9.AttorneyDispatchReturnTask fill:#fccde5 9.AttorneyDispatchReturnTask["9.AttorneyDispatchReturnTask\n(user)"] style 10.OtherColocatedTask fill:#80b1d3 10.OtherColocatedTask["10.OtherColocatedTask\n(organization)"] style 11.OtherColocatedTask fill:#80b1d3 11.OtherColocatedTask["11.OtherColocatedTask\n(user)"] style 12.OtherColocatedTask fill:#80b1d3 12.OtherColocatedTask["12.OtherColocatedTask\n(user)"] 0.RootTask --> 6.BvaDispatchTask 6.BvaDispatchTask --> 7.BvaDispatchTask 7.BvaDispatchTask --> 8.JudgeDispatchReturnTask 8.JudgeDispatchReturnTask --> 9.AttorneyDispatchReturnTask 9.AttorneyDispatchReturnTask --> 10.OtherColocatedTask 10.OtherColocatedTask --> 11.OtherColocatedTask 10.OtherColocatedTask --> 12.OtherColocatedTask

MailTasks #

A mail task is used to track when the mail team receives any appeal-related mail from an appellant.

• Mail is processed by a mail team member, and then a corresponding task is then assigned to an organization.
• Such tasks are assigned to organizations, including VLJ Support, AOD team, Privacy team, and Lit Support, and include:
  • add Evidence or Argument ( EvidenceOrArgumentMailTask_Organization)
  • changing Power of Attorney (POA, PowerOfAttorneyRelatedMailTask_Organization)
  • advance a case on docket (AOD = advance on docket, AodMotionMailTask_Organization)
  • withdrawing an appeal ( AppealWithdrawalMailTask_Organization)
  • switching dockets ( DocketSwitchMailTask_Organization)

Based on existing appeals, the following tasks can happen at any time after the DistributionTask and before the BvaDispatchTask:

• EvidenceOrArgumentMailTask_Organization
  • EvidenceOrArgumentMailTask_User only in DR and ES dockets

Other Tasks #

Background:

• Litigation Support handles congressional inquiries, motions (pre- and post-decisional), CAVC remands, and responds to status inquiries on BVA cases. They are one of the last known teams who received a Queue and will work in Caseflow.

Other tasks:

• TimedHoldTask_User
• Task_Organization
  • Task_User
• SpecialCaseMovementTask_User - always has parent DistributionTask_Organization
• BoardGrantEffectuationTask_Organization
• PulacCerulloTask_Organization
  • PulacCerulloTask_User

Deprecated tasks #

• InformalHearingPresentationTask_Vso - IHP tasks assigned to VSO
• GenericTask_Organization
  • GenericTask_User