Published Updated

An employee reports that a colleague viewed customer records outside their assigned work. The investigator needs the original complaint, the approved scope, access logs, role history, interview notes and a reviewed finding. The manager responsible for a corrective action needs the accepted action and due date. Those responsibilities call for different views of the same case.
An investigation case file should connect the report, authority to investigate, evidence, analysis, decisions and follow-up. Give every item a clear role, source, version and permitted audience. Use a shared case identity to follow the matter from intake to closure while keeping sensitive documents restricted.
Preserve the intake and approve the questions, scope, investigator and collection plan.
Register source material, explain gaps and connect proposed findings to the exact evidence considered.
Record the review, assign actions and verify the required results before approving closure.
| Record group | What it establishes | What to preserve |
|---|---|---|
| Report and scope | What was reported, which questions are authorised and who may investigate. | Original intake, triage decision, investigator assignment, approved scope and later changes. |
| Source evidence | The material available for examination, with its source and collection context. | Collected files, statements, export criteria, time range, custodian, integrity checks and transfer records. |
| Analysis and proposed findings | How the investigator interpreted the evidence, including conflicts and unanswered questions. | Working notes, evidence references, report versions and the explanation submitted for review. |
| Decisions and follow-up | What the authorised reviewer accepted and whether the required response was completed. | Decision and reasons, action owner, due date, completion evidence, effectiveness check and closure approval. |
A dossier model helps connect these documents without collapsing them into a single file. References should identify the version used for a decision, so a later correction does not silently change the basis of an earlier finding.
For an exported log, keep the source system, collector, collection time, query or selection criteria, covered period and time zone. For a statement, identify who supplied it and whether the retained record is a recording, transcript, signed statement or investigator's note. Record limitations such as an unavailable period or a filtered export alongside the material they affect.
Keep annotations, redacted copies and analysis linked to the collected original. Record transfers and any integrity verification required by the collection procedure. For digital investigations, NIST's IT-forensics guide provides collection and handling guidance; use the procedure approved for the organisation and matter.
Repository activity and source provenance answer different questions. FormKiQ's activity reporting exposes user, document and resource activity for review. Connect those records to collection and transfer evidence from outside the repository. An upload timestamp alone cannot explain how an external export was produced.
An action owner may need the approved finding and remediation task while an investigator needs the underlying logs and interviews. Restrict reporter identities, medical information and legal advice according to the approved access model. Let the responsible legal reviewer determine how advice should be handled; a folder label does not establish its legal status.
Test search results, previews, downloads, exports and linked documents under the intended identities. Include authorised administrators and integrations in the access review. When the case is reassigned or an external reviewer leaves, change access on the relevant delivery paths and review outstanding shares.
In this fictional case, INV-204 concerns access to customer records during a defined two-day period. The following identifiers illustrate a case register, rather than FormKiQ API fields or prescribed document types.
Retain the original complaint as R-01. The case owner approves S-01, naming the systems, period, investigator, questions and permitted collections. The allegation remains a reported concern while the evidence is examined.
Register the access-log export as E-01. Its time zone is missing, so the investigator records the gap and requests a documented export. Retain the first collection and link the corrected one as E-02, including its query window and source details. Record which export is used in the analysis.
Link E-02 to role-change history E-03 covering the same period and the relevant work assignments. A current role snapshot would not establish the employee's historical authority. Finding F-01 identifies the supported access events, contradictory material and remaining uncertainty, with exact evidence references.
The authorised reviewer accepts or returns the findings report with reasons. Accepted action A-01 assigns an owner to correct an excessive entitlement. The owner receives the approved task and necessary context; access to restricted interviews remains governed separately.
The owner supplies the change record and access-test results. A reviewer checks the required outcome and records any further work. The closure summary links the accepted finding, action evidence, required response and retention or hold instructions. An unresolved item retains a named owner and an explicit decision about whether closure may proceed.
A service ticket or security alert can identify work that needs an investigation. Keep service-restoration status and high-volume security telemetry in their operational systems. Connect the selected evidence and case through stable references, and return only the approved status or technical action needed by the receiving team. A linked case ID does not grant ticket users access to restricted interviews or findings. Configure and reconcile the handoff, including duplicate or delayed status events.
Test evidence retrieval before an incident: recover a scoped export from both recent and archived log storage, check its time range and time zone, and record any collection gaps. A saved source link is useful only while the required evidence remains retrievable under its access and retention rules.
For a vulnerability investigation, keep patch verification separate from assessment of possible earlier compromise. The deployed version and a confirming test can establish remediation of the identified weakness. They do not establish what happened before the patch. Retain the triage scope, findings, limitations and any linked incident decision where that review is required by the organisation's process.
Retain the approved report and its review history. If later evidence changes the assessment, create a linked reconsideration or reopened case under the organisation's process. Preserve the explanation of the original decision as well as the later correction. The closed-case routing guide compares reopening the same matter with creating a linked case for a separate occurrence, including the effect on ownership and reporting.
For a customer complaint, sending the approved response and completing the corrective action can be separate outcomes. Give each an owner, next step and completion criteria. Keep the response version and available delivery evidence connected to the investigation. Closing a CRM ticket does not establish that the underlying fix worked; track the corrective action through its agreed completion and effectiveness review.
Assign the applicable retention and hold controls to the case records and relevant copies. Closing an investigation does not itself authorise destruction. Likewise, an action marked complete needs the required verification before it can support an approved closure.
A useful investigation file lets an authorised reviewer follow what was reported, how evidence was collected, why a finding was accepted and whether the agreed response worked. Connect those records through the case while preserving their versions, responsibilities and access controls.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.