UI Design - DRS | Document Record Enhancements

[liz-govier]

Remove document record

• Ability to remove a document from a document record.
• Access will be restricted to select staff members only.
• Permissions and roles are still being defined.

Design tasks:

• Design the remove document action (trigger, confirmation state, and restricted access indicator)
• Design the permission-gated UI state for staff without removal access

Status: Requirements gathering · Ticket TBA

---

Rescan to overwrite document record

When a document is removed or requires correction, the ability to rescan and overwrite the existing document record will be needed.

Design tasks:

• Design the rescan and overwrite flow (entry point, confirmation, and overwrite state)
• Design error and success states for the overwrite action

Status: Requirements gathering · Ticket TBA

---

Documents table

Update the documents table as part of the post-MVP iteration.

Design tasks:

• Update download component
• Replace stacked card layout with a table view

---

Pages to scan, flagged discrepancy workflow

Issue: Staff enter an expected page count on the document record before scanning. If the scanned count doesn't match, the scanner operator must manually track down the filing staff member to flag the issue. A digital notification or discrepancy-flagging workflow is needed to replace this manual handoff.

Design tasks:

• Design how a page count discrepancy is surfaced in the document record UI (inline alert, banner, or flag)
• Design the notification sent to the filing staff member when a mismatch is detected
• Design the resolution flow, allowing the filing staff member to confirm, correct, or dismiss the discrepancy
• Map the current manual workflow and propose the improved digital equivalent

---

❓ Open question: Should the pages to scan discrepancy workflow be folded into the document ID upgrade work? To be discussed with the team before scoping.