Data Classification Scheme Builder
Define data levels and handling rules.
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.
Create a data classification scheme. Types of information we handle: [DATA_TYPES]. Where it is stored and shared: [STORAGE_SHARING]. Who needs access: [ACCESS_GROUPS]. Define three or four levels with plain names, a definition, five examples drawn from my data types, and handling rules in a table with columns: Storage | Sharing | Email | Printing | Disposal | Access. Provide a short decision flow of four questions that helps someone classify a document in under a minute. Include labelling guidance, defaults when unsure, a process for reclassifying, and a training plan. Identify where legal retention or privacy obligations in [JURISDICTION] may add rules and mark them [VERIFY]. Close with a rollout plan that starts with the most sensitive data. Add three worked examples of classifying real-looking documents, such as a customer list, a meeting agenda, and a draft contract, showing the reasoning for each level. Include a short note on how to handle documents that combine different levels, and a rule for who may approve a lower classification than the default. Add a labelling and handling example set for three invented documents, with the level assigned, the reasoning, and what the author must do differently because of the level (where it is stored, whether it may be emailed, whether it needs encryption, how long it is kept). Provide a short training outline of twenty minutes for all staff, with a five-question quiz built from realistic documents. Add a section on exceptions and conflicts: what to do when a document combines levels, when a customer demands a different handling, and when the scheme slows urgent work, with an approval path. Close with a measurement plan: a quarterly sample of ten documents checked for correct labels, the target accuracy that I set, and the action when it is missed. Stay on the protective side: hardening, monitoring, training and recovery. Do not describe how to carry out an attack in operational detail.
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.