records-management
Design records management so required information is retained, protected, findable, and disposed of according to policy and law. Use when building retention schedules, responding to discovery/exams, or reducing ROT (redundant, obsolete, trivial) data risk.
- License 许可
- MIT
- 最近更新
- 2026-07-22
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- records-management
- description
- Design records management so required information is retained, protected, findable, and disposed of according to policy and law. Use when building retention schedules, responding to discovery/exams, or reducing ROT (redundant, obsolete, trivial) data risk.
03 SKILL.md 正文
Records Management
Overview
Records management ensures the organization keeps what it must, protects it appropriately, and disposes of what it should — on schedule and with evidence.
When to Use
- Retention schedule design and rollout
- Exam, litigation, or investigation hold processes
- Reducing over-retention and storage risk
- Migrating systems with historical records
Core Practices
- Classify record types and map to retention periods
- Define authoritative systems of record
- Apply legal holds that suspend destruction
- Control access and integrity of retained records
- Execute disposition with approval and logging
- Train staff on what is a record vs working material
Principles
- Keep-everything is not a retention strategy — it is risk
- If you cannot find it, you effectively did not retain it
- Holds override normal disposal — process must be reliable
- Privacy and retention must be designed together
Verification
- [ ] Retention schedule covers material record types
- [ ] Legal hold process is tested
- [ ] Disposition is authorized and auditable
04 同仓库更多 Skills
compliance-monitoring
Design compliance monitoring and testing programs that verify controls work in practice and surface issues before regulators do. Use when building monitoring plans, compliance testing, or continuous control monitoring.
complaints-handling
Operate complaints-handling processes that meet regulatory standards — logging, timely resolution, root-cause analysis, and fair outcomes. Use when designing or improving regulated complaints frameworks or analyzing complaint themes for conduct risk.
aml-kyc-basics
Apply AML/KYC fundamentals — customer due diligence, monitoring, suspicious activity escalation, and recordkeeping — for financial crime compliance. Use when designing onboarding controls, transaction monitoring concepts, or AML program components in financial services.
ai-model-compliance
Apply compliance controls to AI and automated decision systems — transparency, fairness, human oversight, documentation, and regulatory alignment. Use when deploying AI in regulated processes (credit, fraud, customer decisions) or responding to AI governance expectations.
data-quality-management
Manage data quality end-to-end — dimensions, rules, remediation, and prevention — beyond one-off cleaning scripts. Use when building sustained data quality programs or fixing systemic accuracy, completeness, or consistency problems.
data-lineage
Capture and use data lineage — where data comes from, how it transforms, and what depends on it — for impact analysis, debugging, and trust. Use when tracing metric origins, assessing change impact, or diagnosing broken pipelines.