Create intermediate Works with: Any AI

Backup Policy and Responsibilities

Table output Has example

Define what is backed up, how often, and who checks.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.

Write a backup policy. Systems and data: [SYSTEMS_DATA]. Current practices: [CURRENT_BACKUPS]. Recovery needs: [RECOVERY_NEEDS]. Budget: [BUDGET].

Define scope, backup frequency and retention per data category in a table, storage rules (separate location, encryption, protection from deletion), responsibilities, monitoring of backup success, restore testing schedule and success criteria, and exceptions process. Provide a simple version of the 3-2-1 approach explained in plain words and adapted to my situation. Add a quarterly checklist and a one-page summary for managers. Include a section on personal devices and cloud services that may not be covered. Note where retention periods depend on legal requirements in [JURISDICTION] and mark them [VERIFY].

Add a table of backup failure scenarios (ransomware encrypting a share, accidental deletion, cloud account compromise, hardware failure) with the control that addresses each and the gap that remains. Provide a sample entry for the backup log and an annual review agenda with five questions.

Only advise on securing assets that belong to me or my employer. Avoid offensive instructions, and flag any step that needs written approval from a system owner.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Scope: finance data, customer database, shared drive.
Data | Frequency | Retention | Location
Finance | Daily | 7 years [VERIFY] | Encrypted cloud copy plus off-site
Customer DB | Hourly | 30 days | Separate account
Shared drive | Daily | 90 days | Cloud
3-2-1 in plain words: 3 copies, 2 types of storage, 1 off-site.
Restore tests: quarterly, results logged.
Responsibilities: IT owns backups; data owners confirm what matters.
Failure scenarios: ransomware (immutable copies), accidental deletion (version history), account compromise (separate credentials).
Exceptions: personal devices not covered.

• policy