Working Start something skill
Create a personal records system
Design a maintainable workflow for capturing, naming, reviewing, retaining, and retrieving personal records.
Build the lifecycle, not just folders. Every incoming record needs a route from capture to decision, storage, update, and eventual disposal.
When to use
- Use when multiple people, devices, paper files, inboxes, or life domains create recurring recordkeeping friction.
- Use
organize-important-documentsfor a one-time cleanup; use this for the ongoing system.
Procedure
- List record-producing channels, users, devices, physical locations, recurring tasks, and failure points.
- Define a small set of record classes and the decisions each class supports.
- Create one capture inbox per practical channel and one regular processing cadence.
- Specify naming, dates, ownership, version status, source, and stable identifiers.
- Define the system of record for each class and rules for links versus copies.
- Add retention, review, renewal, and destruction rules with an “unknown—review” state.
- Design access by role and need; separate daily convenience from high-sensitivity storage.
- Add encrypted backup, restore testing, offline or offsite resilience, and emergency handoff.
- Migrate a representative sample before bulk filing and measure retrieval success.
- Document a one-page operating guide and review the system after real use.
Failure plan
- Do not duplicate sensitive records across tools merely for convenience.
- If two systems both appear authoritative, choose one or document a synchronization owner.
- Do not automate destruction without review for holds, disputes, or legal requirements.
- Reduce categories when filing decisions remain inconsistent.
--- name: create-a-personal-records-system category: start description: Design a maintainable workflow for capturing, naming, reviewing, retaining, and retrieving personal records. Use when documents repeatedly become lost, duplicated, or outdated. --- # create-a-personal-records-system Build the lifecycle, not just folders. Every incoming record needs a route from capture to decision, storage, update, and eventual disposal. ## When to use - Use when multiple people, devices, paper files, inboxes, or life domains create recurring recordkeeping friction. - Use `organize-important-documents` for a one-time cleanup; use this for the ongoing system. ## Procedure 1. List record-producing channels, users, devices, physical locations, recurring tasks, and failure points. 2. Define a small set of record classes and the decisions each class supports. 3. Create one capture inbox per practical channel and one regular processing cadence. 4. Specify naming, dates, ownership, version status, source, and stable identifiers. 5. Define the system of record for each class and rules for links versus copies. 6. Add retention, review, renewal, and destruction rules with an “unknown—review” state. 7. Design access by role and need; separate daily convenience from high-sensitivity storage. 8. Add encrypted backup, restore testing, offline or offsite resilience, and emergency handoff. 9. Migrate a representative sample before bulk filing and measure retrieval success. 10. Document a one-page operating guide and review the system after real use. ## Failure plan - Do not duplicate sensitive records across tools merely for convenience. - If two systems both appear authoritative, choose one or document a synchronization owner. - Do not automate destruction without review for holds, disputes, or legal requirements. - Reduce categories when filing decisions remain inconsistent. ## Done - Capture, processing, storage, review, backup, retrieval, and disposal have owners and rules - Each record class has one clear system of record - A second authorized person can use the guide and pass a retrieval-and-restore test