legal-hold

To draft a legal hold notice, you provide custodian scope, date range, and systems coverage, which generates a .docx notice draft and updates the legal_hold fields in your _log.yaml file. A short-name gate validation and preview confirmation are enforced before writing.

Releasing a legal hold instruction involves generating a release notice draft and setting the released field within the _log.yaml file. The workflow applies a short-name gate validation and requires preview confirmation before finalizing the document.

A legal hold refresh captures custodian and scope changes to generate a new version draft, marking departed individuals while maintaining the ongoing retention discipline. This process updates the active legal_hold log state accordingly.

Yes, you can generate a portfolio-wide status report summarizing active legal holds and risky delays from a KVKK and evidence loss perspective. This report presents retention compliance data in a structured table format.

Yes, the workflow enforces a pre-publication legal and IT-KVKK review gate before writing the retention instruction draft. This gatekeeping step requires short-name log validation and preview confirmation to ensure compliance.

You should use legal hold procedures under HMK m.400 when you need an operational reminder for evidence preservation preparation during litigation. This ensures company records and potential evidence are retained in a controlled manner across the dispute lifecycle.