Trauma-Informed Digital Evidence Collection: A Design Inquiry into Evidence Practices for Technology-Facilitated Abuse in Intimate Partner Violence
A strong CHI contribution: it shifts TFA evidence collection from survivor burden to trauma-informed collaborative practice, but its strongest claims are about design guidance and early feasibility rather than proven legal impact at scale.
Axes Lens
Rare contribution shape, typical evidence profile. The point here is not a score. It is to show what kind of claim the paper makes, and whether the evidence pattern is unusual or baseline in this 268 -review set.
Contribution shape
- Knowledge form
- method knowledge typical · 29/268
- Novelty type
- tool typical · 14/268
- Abstraction level
- practice typical · 85/268
- Generalization target
- methodological argument typical · 16/268
- Validation mode
- mixed methods typical · 136/268
Evidence profile
- Evidence strength
- moderate typical · 105/268
- Claim alignment
- strong typical · 231/268
- Overclaim risk
- medium typical · 210/268
Review Summary
This paper stands out because it does not merely introduce another evidence repository or forensic utility; it rethinks where and how digital evidence collection should happen for survivors of technology-facilitated abuse. The key move is organizational and methodological: evidence collection is embedded in trauma-informed tech clinic consultations rather than delegated to survivors as an individual documentation task. That is an important departure from common practice because the paper explicitly identifies survivor-facing repositories as burdensome and potentially retraumatizing. Sherloc operationalizes this alternative by covering the full evidence-collection pipeline and by combining technical findings with survivor experience in a single interpretable report. The contribution is strongest as a situated HCI design inquiry and practice-oriented tool contribution. The legal-expert evaluation and early pilot provide credible evidence that the approach is useful, legible, and promising in real support settings. The paper also appears careful about iteration: expert feedback changed the system, pilot use exposed bugs and wording problems, and the authors trimmed technical detail when it reduced clarity. That responsiveness strengthens the paper’s practical value. At the same time, the paper should not be read as definitive proof of legal efficacy or broad deployability. The pilot is still small, geographically situated, and the authors explicitly note that they have not yet received survivor follow-up surveys indicating whether reports were actually used in legal proceedings. So the most defensible takeaway is that the paper offers a compelling trauma-informed model and an early validated tool for collaborative TFA documentation, along with design guidance that other HCI researchers can build on. Its importance lies in reframing evidence collection as a survivor-support practice, not just a technical capture problem.
What Changed
Canon before
Existing digital evidence documentation tools for technology-facilitated abuse mainly function as repositories requiring survivors to bear the burden of identifying and recording abuse on their own; expert testimony is often required for legal use; and many tools lack accessibility or flexibility across evidence types and use cases.
Departure from common sense
The paper rejects the default model in which survivors themselves must identify and record abuse evidence. Instead, it places evidence collection inside trauma-informed tech clinic consultations, where trained consultants collaboratively identify, capture, and document TFA with survivors, reducing burden and potential retraumatization.
Actual novelty
The main contribution is Sherloc, a trauma-informed evidence-collection framework for TFA used in tech clinic consultations. It spans all five evidence-collection steps, combines technical findings with survivor experience in one report, and yields design guidelines for trauma-informed digital evidence collection grounded in expert feedback and an early pilot.
Evidence
Evidence comes from the paper’s explicit contrast with prior survivor-facing repositories, the concrete description of Sherloc as covering all five evidence-collection steps in clinic consultations, evaluation with Wisconsin legal experts, and an early pilot with three consultations plus participant feedback. The paper also states clear current limits on legal-robustness assessment because no survivor follow-up surveys had yet been received.
“Toward our goals, we designed Sherloc, an evidentiary framework encompassing all of the five steps of evidence collection [53, 70]. Sherloc is a Python program with a Flask [80]-based user interface that runs on a designated clinic laptop. It is designed to be used during a tech clinic consultation and run primarily by the tech clinic consultant, in close collaboration with the client”
actual novelty · 5 Sherloc: An Evidence-Collection Framework for Survivors of TFA · confidence 0.98
“ [102] and Goyal et al. [60]’s tools for documenting online harassment. Unfortunately, existing methods for documenting digital evidence fall short of survivors’ needs. Sophisticated investigative tools are rarely accessible to individual survivors [92, 100], and academic prototypes are not publicly available [60, 77, 102]”
departure from common sense · 1 Introduction · confidence 0.97
“Thus far, we have not received follow-up surveys from any survivors, so we have not been informed whether they have used their investigation report in legal proceedings (or other use cases). This limits our ability to assess legal robustness at this time. However”
limitation · 7.5.2 Findings related to legal robustness. · confidence 0.98
“ We performed interviews and focus groups with 19 legal support providers, ranging from attorneys and law clinicians to a police officer, and distributed a feedback survey to 12 judges”
validation scope · 1 Introduction · confidence 0.95
Limits
Method limits
The implementation relies on ISDi and prior work for scan accuracy, includes platform-specific constraints such as iOS Developer Mode and sudo for screenshots, and the pilot surfaced bugs and report-design issues such as noisy technical detail, disruptive prompts, and incomplete inclusion of consultant recommendations.
Deployment limits
Validation is still early: the pilot is small, situated in Wisconsin tech clinic practice, and the authors report that they have not yet received survivor follow-up surveys about downstream legal use. Access also depends on trained consultants and clinic infrastructure rather than standalone survivor use.
Boundary conditions
The contribution is most applicable to technology-facilitated abuse documentation in intimate partner violence contexts where trauma-informed tech clinic consultations are available. Claims about legal usefulness are bounded by jurisdiction-specific practice, case details, and the fact that legal relevance and downstream courtroom use were not yet fully observed in the pilot.
Position in field
This paper extends trauma-informed computing from clinic coordination and survivor support into the concrete design of digital evidence collection. Its significance is less a universal forensic breakthrough than a situated HCI contribution showing how evidence practices can be redesigned around survivor safety, interpretability, and collaborative consultation workflows.