download dots

🗄️ Set Retention Periods and Actually Apply Them

Track every licence, certificate, permit, and calibration you are responsible for in one live register that flags a renewal before it lapses. These compliance prompts build the operational layer around the credentials your business runs on: what you hold, when it expires, who owns the renewal, and what gets blocked if it slips. Built for operators who would rather find an expiry in a dashboard than in an audit.
  • Tested prompts
  • Edit for your use case
  • Works across models
  • Save in Taskade
Set Retention Periods and Actually Apply Them

Copy

We keep every record forever because nobody has decided otherwise. Build me a retention app. Keep one record per record type with where it is held, the retention period, the reason for that period whether legal, contractual or operational, the owner, and what happens at the end whether deletion, anonymisation or archiving. Apply the schedule on a run I schedule rather than relying on anyone remembering, and log every action with the record type, the volume, the date and who or what performed it. Support legal holds that suspend the schedule for specified records, recording who applied the hold and why, and make sure a hold cannot be silently bypassed. Show me record types with no period set at all, and holdings currently past their period. Add an AI agent that reviews the schedule, flags record types with no period, identifies where two record types with different periods appear to cover the same information, and drafts the justification for a proposed period. Automate two things: the scheduled retention run, and a report of pending deletions to owners before they happen. Two logins: a record owner, and a compliance owner who sets periods and applies holds.

STATUS · LIVE
v1

01 / Spark - intelligence awakens

Set Retention Periods and Actually Apply Them

Set and apply retention periods per record type on a schedule, with legal holds that override and a full deletion log.

// the spark catches · intelligence awakens · the answer unfolds

Most organisations keep everything because deciding is harder than storing. This sets a period per record type, applies it automatically, and proves it happened.

What's Included

  • A period per record type with the reason recorded.
  • Applied on a schedule not when someone remembers.
  • Legal holds that override and cannot be missed.
  • An assistant that finds record types with no period set.

How To Use

  1. Record the reason for each period. It will be questioned.
  2. Apply on a schedule. Manual deletion is applied inconsistently.
  3. Support holds that override the schedule and cannot be bypassed.
  4. Log deletions. Proving deletion is often the actual requirement.

Coordinate with document control, and with the retention schedule manager.