Skip to main content
iBlow logo
iBlow Logo
  • About
  • Services
  • Features & Packages
  • Resources
  • Contact
  • FAQ
  • Request a demo
  • EnglishEnglish
    • PortuguêsPortuguês
  • About
  • Service
  • Features & Packages
  • Resources
  • Contact
  • FAQ
iBlow logo
  • About
  • Services
  • Features & Packages
  • Resources
  • Contact
  • FAQ
  • Request a demo
  • EnglishEnglish
    • PortuguêsPortuguês

Triage, Evidence and Chain of Custody: An Investigation Playbook for SMEs

Illustration for: Triage, Evidence and Chain of Custody: An Investigation Playbook for SMEs

Topic of this article: chain of custody.

Who this playbook is for — and why it matters?

If you’re the internal auditor, legal counsel, or compliance lead of a small or mid-sized enterprise, you are likely to wear multiple hats. When a whistleblowing report lands, you need a disciplined process that protects people, preserves evidence, and reaches fair outcomes — without paralysing the business. This playbook distils proven practice into practical steps, ready-to-use checklists and clear roles so you can move from intake to closure with confidence.

The investigation workflow at a glance

  1. Intake & acknowledgement — log the report, protect confidentiality, and confirm receipt.
  2. Triage — quickly assess scope, risk, conflicts, and legal basis; decide whether to investigate or refer.
  3. Plan — define hypotheses, roles (RACI), sources, interviews, timeline and SLAs.
  4. Collect & preserve evidence — structured registers, hashes, storage controls.
  5. Interview — fair, documented, and proportionate.
  6. Analyse & conclude — test hypotheses, weigh credibility, link findings to policy.
  7. Outcome & remediation — corrective actions, control improvements, notifier feedback.
  8. Close & learn — metrics, KPIs and programme improvements.

Step 1 — Triage with discipline

Objective: decide fast, fairly and defensibly.

Checks (use the downloadable triage sheet):
  • Eligibility & scope: does the allegation fall under your policy and the EU whistleblowing framework?
  • Conflicts & independence: confirm case owner and escalation path (consider external counsel if needed).
  • Risk rating: people safety, data/privacy exposure, financial impact, legal/press risk.
  • Legal basis (GDPR): document purposes, minimisation and retention; involve the DPO when needed.
  • Proportionality: is a formal investigation necessary or will a targeted management review suffice?

Decision options:
(a) acknowledge & log;
(b) escalate to formal investigation;
(c) refer/decline with rationale.

SLA tip: acknowledge within 7 days and provide an update/closure within 3 months (as a programme norm).

Step 2 — Assign roles and create a RACI

Clarity prevents drift. At minimum, assign:

  • Case Owner (Responsible): runs day-to-day activities.
  • Sponsor (Accountable): approves scope and conclusions.
  • Advisers (Consulted): HR, DPO, IT forensics, external counsel.
  • Observers (Informed): leadership, audit committee where proportionate.

RACI sample activities: intake & logging, triage decision, planning, evidence collection, reporting & outcomes.

Step 3 — Build your investigation plan

A good plan saves hours later. Include:

  • Allegation statement & hypotheses to test (what would confirm/deny them).
  • Evidence map: systems, documents, witnesses, and cut-off dates.
  • Interview list & order: start with neutral context, then corroborative, then subject.
  • Safeguards: confidentiality, retaliation prevention, and wellbeing.
  • Timeline & SLAs: who does what by when, with escalation points.
  • Data handling: legal basis, minimisation, retention, cross-border transfers (link to iPrivacy.eu for guidance).

Use the Investigation Plan table in the downloadable template to track tasks, owners, and due dates.

Step 4 — Evidence handling that stands up

Evidence must be authentic, complete and preserved:

  • Register everything: create a unique Evidence ID, description, source, date/time, who collected it, and where it is stored.
  • Integrity controls: hashes/checksums for digital files; tamper-evident seals for physical media.
  • Versioning: never edit originals; work on copies with write-protection.
  • Access control: least privilege; log who sees/handles what.
  • Retention & deletion: tag personal data categories; follow policy-defined periods.

See the Evidence Register and Chain of Custody tables in the template.

Step 5 — Interviews that are fair and reliable

  • Preparation: objectives, open questions, and a standard script (notice of purpose, confidentiality, and rights).
  • Setting: private, neutral space; offer a companion if policy allows.
  • Technique: start broad, drill down, seek documents, avoid leading questions.
  • Records: contemporaneous notes; if recording, obtain explicit consent and store securely.
  • Follow-ups: confirm facts and outstanding items within 48–72 hours.

Step 6 — Analysis and findings

  • Triangulate documents, data and testimonies; track contradictions.
  • Apply standards: weigh credibility, corroboration and plausibility; tie to your code/policies.
  • Draft findings: fact pattern → policy breaches (if any) → root causes → impact.
  • Quality check: legal counsel/DPO review for due process and privacy adherence.

Step 7 — Outcomes, remediation and notifier feedback

  • Proportionate actions: ranging from coaching and policy updates to disciplinary measures.
  • Control improvements: patch process gaps (segregation of duties, access reviews, training).
  • Notifier feedback: respectful, non-retaliatory, and limited to what is lawful to share.
  • Close the loop: log conclusions, store records securely, update KPIs.

Risks & how to avoid them

  • Scope creep: lock the plan; any expansion requires sponsor approval.
  • Evidence contamination: always preserve originals and document handling steps.
  • Privacy violations: collect only what is necessary; document legal basis and retention.
  • Retaliation: monitor for adverse changes in terms/conditions for involved parties.
  • Timeline slippage: track SLAs; escalate early.

Mini-scenario (real-world style)

A purchasing officer is alleged to be favouring a supplier.

  • Triage confirms relevance and moderate risk.
  • Plan defines hypotheses: (H1) unusual purchase patterns; (H2) personal ties; (H3) policy breaches.
  • Evidence: procure-to-pay logs, emails (targeted search), supplier master data, and interviews (requestor, finance, officer).
  • Findings: two approvals bypassed; hospitality not recorded; email suggests undue pressure.
  • Outcome: written warning, mandatory training, and tighter secondary approval controls.
  • Notifier feedback sent within policy timelines.

Measure what matters (KPIs)

Leverage our internal article on Compliance KPIs to track: case acknowledgment time, triage decision time, plan sign-off time, average investigation duration, ratio of substantiated findings, remediation completion rate, and stakeholder satisfaction. Link improvements to your annual compliance plan.

Tools to speed you up

  • iCompliance.eu — custom made services to tailor your implementation to your needs, CCO services.
  • iComply.pt — technology platform for intake, case management, evidence logs and audit trails.
  • iPrivacy.eu — GDPR guidance, DPO services and data-handling templates.
  • iBlow.eu resources — comparative EU law analyses and SME-oriented guidance.
  • iBlow.eu resources — download triage sheet

👉 Be part of the conversation that’s shaping the future of work! Book a meeting!

See other articles that may be of interest to you.

We hope you enjoyed this article.

Thank you!

Constantino Ferreira

iBlow.eu

Drawing of a green paper aeroplane, to ask to be part of the iBlow.eu community Subscribe to receive future articles

Chain of custody: further reading

To go deeper on chain of custody, see also:

  • Navigating the Challenges of Whistleblowing in Small and Medium Enterprises (SMEs)
  • Whistleblowing triage vs HR Grievance vs Ethics vs H&S Incident: How to Route Every Report Correctly
  • New normative for the prevention of corruption

Official source: Directive (EU) 2019/1937.

Make compliance a confident part of how you grow.

Tell us what your organisation needs. We’ll help you find the right next step.
Talk to our team
Stylized text with abstract design
Secure reporting and practical compliance support for organisations that want to build trust and act with confidence.

Explore

About iBlow
Services
Features & packages
Resources
Law 93/2021 in 9 points
FAQs

Choose your next step

Book a demonstration
Request a proposal
Get the practical guide
Request a free trial

Contact

+351 210 987 308
[email protected]
Rua Mouzinho da Silveira 32
Lisboa, Portugal

Privacy policy · Terms · Cookies
© 2026 iBlow Europe. All rights reserved.
iBlow Europe
Manage Consent

To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.

Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
O armazenamento ou acesso técnico é necessário para criar perfis de utilizador para enviar publicidade, ou para localizar o utilizador num site ou em vários sites para fins de marketing semelhantes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
View preferences
  • {title}
  • {title}
  • {title}