WVOIC-1258 · Design Walkthrough

Tracking Appeals on OIC Claims

A working draft to review with the Board of Review team at SCRUM — how we could capture appeals after a decision is released, two ways to surface it, and the questions we need answered to build it.

Status: Open Reporter: Teresa L. Camp Priority: Low Type: Enhancement
The request

What Teresa asked for

On an OIC claim, once a Hearing Examiner decision is released, there’s currently no place to record whether that decision was appealed and how the appeal turned out. Teresa marked up the Decision tab with two ideas: add an “Appealed” indicator on the decision line, or stand up a dedicated “Appeals” tab.

How we read your example

Your sample rows aren’t a simple yes/no — they trace an appeal up the chain: a decision released by the Board of Review (BOR), then carried to the Intermediate Court of Appeals (ICA), then the Supreme Court of Appeals (SC) — each level with its own disposition (Affirmed / Reversed / Remanded), board or panel member, and release date. That “one decision → several appeal actions” shape is what drives the design below. Please correct us if we misread it.

Where things stand

What the system does today

Appeals aren’t modeled anywhere in WVOIC yet — there’s no appeal object or field. The Decision record already holds Status, Disposition, Written Decision, Board Member, and Release Date, and links to a Protest. So we’re adding a new concept, not reshaping an existing one — which is good news: it means we can design it cleanly around how appeals actually flow, rather than bending the decision record.

Two ways to build it

Option A vs. Option B

Option A · Lightweight

“Appealed” indicator on the Decision line

Add an Appealed (Y/N) column and an Appeal Date to the existing Decision Listing. Fast, minimal setup.

Good for

  • At-a-glance “was this appealed?”
  • Small config, quick to ship
  • Nothing new to learn

Limits

  • Can’t hold the BOR→ICA→SC chain
  • One row can’t track multiple levels
  • Likely needs rework later
Option B · Recommended

A dedicated “Appeals” tab

A new Appeal record tied to a decision, shown on its own tab — one entry per appellate action, so the full chain is visible.

Good for

  • Full BOR / ICA / SC lifecycle
  • Multiple appeals per decision
  • Searchable & reportable

Cost

  • New data object + tab
  • More admin-UI setup
  • Roles/permissions to define

We lean toward Option B because your own example is multi-level — but the two aren’t exclusive. AC5 below puts a derived “Appealed” indicator back on the Decision line, so you get Option A’s at-a-glance view and Option B’s detail.

Wireframe · Option A

Decision tab with an “Appealed” column

Tracking Inbox / Claim / Decision Listing
Claimant: Philip Whitlatch
Employer: Marshall County Coal
Claim: 202006006492 — OI Occupational Injury
Status: Closed
PartiesProtestsClaim EvidenceHearingCase NoteDecisionDocumentsTasksWorkflow LogOIC
+ NewPrintCSVColumn Filters ▾
Related Protest IdSubmit DateStatusIssued by (HE)DispositionBoard MemberRelease Date Appealed NEWAppeal Date
PR-104/14/2026Released — BORHunter, LisaReversedCrouse, Bradley08/13/2026Yes08/13/2026
PR-204/14/2026Released — BORHunter, LisaRemandedCrouse, Bradley08/13/2026No—

Option A: two columns added to the existing listing (shaded). Cheap, but the “Appealed = Yes” row has nowhere to record what happened next at the ICA or SC.

Wireframe · Option B

A new “Appeals” tab

Tracking Inbox / Claim / Appeals
Claimant: Philip Whitlatch
Employer: Marshall County Coal
Claim: 202006006492 — OI Occupational Injury
Status: Closed
Case NoteDecisionAppealsNEWDocumentsTasksWorkflow LogOIC
+ New AppealPrintCSVColumn Filters ▾
Related DecisionAppeal LevelStatusDispositionBoard / Panel MemberWritten DecisionRelease DateFurther Appeal?
Decision #1 (PR-1)BORDecidedReversedCrouse, BradleyWhitlatch…6&1.2.docx08/13/2026Yes → ICA
Decision #1 (PR-1)ICADecidedAffirmedCrouse, BradleyICA-mandate.pdf09/04/2026Yes → SC
Decision #1 (PR-1)SCPending—————

Option B: one row per appellate action, so a single decision’s journey through BOR → ICA → SC reads top to bottom. “+ New Appeal” opens the record form below.

Appeals / New Appeal
Decision #1 — PR-1 · Released 08/13/2026
Board of Review
Decided
Reversed
Crouse, Bradley
08/13/2026
Attach…
Yes → ICA

Appeal record form. New fields shaded/outlined. Lookups (Appeal Level, Disposition, Status) are placeholders — the exact values are Q4 below.

new field / column Reversed Affirmed Remanded / pending
Draft acceptance criteria

Starting point for the build (Option B)

Numbered so we can red-line them together at SCRUM. Option A is just AC5 on its own without the new object.

AC1Screens retain current production fonts, sizes, color palette, and box alignment; labels left-justified, inputs vertically aligned.
AC2Add a new Appeal data object as a child of Decision (an appeal is tied to the decision being appealed).AC2.1 — one Decision may have multiple Appeal records (one per appellate action).
AC3Appeal record fields: AC3.1 Related Decision — auto-populated from context, read-only AC3.2 Appeal Level — lookup: Board of Review, Intermediate Court of Appeals, Supreme Court of Appeals AC3.3 Status AC3.4 Disposition — lookup: Affirmed, Reversed, Remanded (confirm full list — Q4) AC3.5 Board / Panel Member AC3.6 Written Decision — document attachment AC3.7 Release Date — date AC3.8 Further Appeal? — Y/N, indicates escalation to the next level
AC4Add a new “Appeals” tab on the Claim, immediately after the Decision tab. AC4.1 Listing columns/order: Related Decision, Appeal Level, Status, Disposition, Board/Panel Member, Release Date, Further Appeal? AC4.2 Default sort: ascending by Release Date, then level order BOR → ICA → SC.
AC5On the Decision Listing, show an Appealed (Y/N) column derived from whether ≥1 Appeal exists for that decision, plus the latest appeal Release Date. (This delivers Option A’s at-a-glance view on top of B.)
AC6Appeal Level, Status, Disposition, Board Member, and Release Date are available as searchable fields and as return columns in Standard & Advanced Searches.
AC7Define roles/permissions for view / create / edit / delete of Appeal records (default: same roles that manage Decisions).
AC8Provide an “Appealed Decisions” report/queue listing decisions with ≥1 appeal, filterable by level and disposition. (Confirm need — Q7.)
Open questions

What we need from you to lock the design

  1. Flag or full record? Do you want a simple “was it appealed?” marker, or a record per appellate action as drawn (our assumption)?Decides Option A vs. B — and how much we build.
  2. Confirm the levels & order: Board of Review → Intermediate Court of Appeals → Supreme Court of Appeals. Any others, or a remand back to the Hearing Examiner?Sets the Appeal Level lookup.
  3. Placement: new Appeals tab (recommended), the indicator on the Decision line, or both?We proposed both via AC4 + AC5.
  4. Field & lookup values: confirm the exact Status, Disposition, and Level values. In your example we saw actions like Statement, Memo, Mandate — are those “Status” values, or something else?These become dropdown options.
  5. What does an appeal attach to — a specific Decision, the Protest, or the Claim overall?We assumed the Decision.
  6. One row per level, or multiple entries per level? e.g. is “ICA memo” then “ICA mandate” two rows or one record you update?Affects data entry and how the chain reads.
  7. Reporting: do you need a searchable “appealed decisions” queue/report, or is on-screen tracking enough?Drives AC6 / AC8 scope.
  8. Workflow: who creates the appeal entry and when — when an appeal is filed, or when it’s decided? Should statuses raise ticklers/tasks?Determines events and reminders.