<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Case-Management on Whistleblowing Software</title><link>https://whistleblowing-software.pages.dev/tags/case-management/</link><description>Recent content in Case-Management on Whistleblowing Software</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 15 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://whistleblowing-software.pages.dev/tags/case-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Inside a Whistleblowing Platform: 7 Components and the Data Flow</title><link>https://whistleblowing-software.pages.dev/posts/whistleblowing-platform-7-components-and-data-flow/</link><pubDate>Wed, 16 Jul 2025 00:00:00 +0000</pubDate><guid>https://whistleblowing-software.pages.dev/posts/whistleblowing-platform-7-components-and-data-flow/</guid><description>&lt;p&gt;A whistleblowing platform is built from seven cooperating components: an intake layer that accepts reports over web, Tor, hotline, voice, and mobile channels; a triage and routing engine that classifies and assigns each case; a case management subsystem that owns the investigation lifecycle; an investigator workspace where authorised staff decrypt evidence and write findings; a two-way messaging channel that lets the platform talk back to anonymous reporters via a 16-digit receipt; an audit trail and reporting subsystem that records every action; and an admin and configuration plane that controls retention, encryption, and access policies. The reference architecture used here is grounded in publicly available application-security documentation from mature open-source whistleblowing software (verified April 2026) and the four lifecycle stages defined in &lt;a href="https://www.iso.org/standard/65035.html"&gt;ISO 37002:2021&lt;/a&gt;. The data flow is intake into encrypted submission storage, then routing to a recipient or audit committee, then case work over the receipt channel, then closure with a structured outcome and an audit trail that survives the reporting record after retention deletion.&lt;/p&gt;</description></item></channel></rss>