Simple document classification for your company without a complex policy
This guide is for teams that need a practical way to classify company documents for privacy and data protection without building a heavy governance program. You will set up a four-level scheme, label common document types, and give staff a one-page rule they can follow immediately.
TL;DR — If your team is stuck because document classification feels too complicated, use four labels only: Public, Internal, Confidential, and Restricted. The fastest way to finish this is to create one classification table, apply it to your common document types, and publish a short handling rule so people know where each document goes. Reading time: ~5 min
Goal
When you finish, your company will have a simple document classification scheme that staff can actually use: four labels, a list of common document types mapped to those labels, and a short handling rule that tells people where documents may be stored and shared.
Prerequisites
- A company document tool you can edit today, such as Google Docs, Microsoft Word, Notion, Confluence, or your internal wiki
- Permission to publish an internal policy or team page
- A list of your common document types, for example: contracts, invoices, HR files, sales decks, product specs, support exports
- 30 minutes with one person who knows legal, HR, or security requirements in your company
- A spreadsheet tool or document editor for the classification table
- Optional: access to your file storage admin area so you can create folders or labels after the policy is published
Steps
Step 1: Create the four-label scheme
Open your document editor and paste this exact table into a new page called Document Classification Standard.
| Label | Use for | Share with | Storage rule |
|---|---|---|---|
| Public | Information approved for anyone to see | Anyone | Public website or shared externally |
| Internal | Normal business information not meant for the public | Employees and approved contractors | Company tools only |
| Confidential | Sensitive business or personal information | Only people who need it for work | Company tools with limited access |
| Restricted | Highest-risk information that could cause serious harm if exposed | Named individuals only | Approved system with the smallest possible access |
You should see a one-page table with exactly four labels and no extra sub-levels.
Step 2: Add plain-language rules for each label
Under the table, paste these exact rules.
## Handling rules
- Public: You may share this outside the company.
- Internal: Do not post this on public websites or public chat channels.
- Confidential: Share only with specific people who need it for their job.
- Restricted: Share only with named people approved by the document owner.
## Default rule
If you are unsure, use Confidential until the document owner changes the label.
## Minimum labeling rule
Put the classification label in the document title or first line.
Examples:
- [Internal] Q3 hiring plan
- [Confidential] Customer pricing proposal
- [Restricted] Payroll file May 2026
You should see short rules that a non-expert can follow without reading a long policy.
Step 3: Map your common document types to a label
Create a second table on the same page and paste this template. Replace the examples only where they do not fit your business.
| Document type | Label |
|---|---|
| Marketing website copy | Public |
| Published case study | Public |
| Team meeting notes | Internal |
| Product roadmap | Internal |
| Sales deck not yet shared externally | Internal |
| Supplier contract | Confidential |
| Customer contract | Confidential |
| Invoice with company address only | Confidential |
| Employee file | Restricted |
| Payroll export | Restricted |
| Government ID copy | Restricted |
| Bank account details | Restricted |
| Customer data export | Restricted |
You should see your most common document types assigned to one of the four labels.
Step 4: Add the decision rule people will actually use
Paste this exact decision guide below the table.
## How to choose a label
1. If the document is approved for the public website or public sharing, use Public.
2. If it contains personal data (information that identifies a person) or sensitive business terms, use Confidential.
3. If it contains payroll, bank details, ID documents, health data, security secrets, or a full customer data export, use Restricted.
4. If none of the above apply, use Internal.
You should see a four-line checklist that lets someone classify a document in under 30 seconds.
Step 5: Publish one official location for the rule
In your document system, move or publish the page in your internal policy area.
Use your provider's dashboard or editor path, for example:
Internal wiki or document tool → New page → Title: Document Classification Standard → Paste the tables and rules → Publish
If your tool supports a short link, create one such as:
/classification
You should see a published internal page that staff can open without asking where the policy lives.
Step 6: Roll out the label format in document names
Send this exact message in your company chat or email.
Starting today, add one of these labels to document titles: [Public], [Internal], [Confidential], or [Restricted]. If you are unsure, use [Confidential] and ask the document owner later. Policy: <paste your internal link here>
You should see staff using the same four labels in new document titles.
Step 7: Apply the scheme to storage locations
If you manage shared folders, rename or create top-level folders with these exact names.
Shared drive / document library
- Public
- Internal
- Confidential
- Restricted
If your storage tool supports permissions, apply them like this:
Public → company-wide edit or approved publishing group
Internal → all employees
Confidential → limited team or project group
Restricted → named individuals only
You should see storage locations that match the labels in the policy.
Verify it works
Use these checks end to end:
- Open your published policy page and confirm it contains all four labels:
Public,Internal,Confidential,Restricted. - Pick five real documents from different teams and check that each title starts with one of these labels.
- Ask one coworker this question:
Where would you put a payroll export?The expected answer isRestricted. - Ask one coworker this question:
What label do I use if I am not sure?The expected answer isConfidential. - Open your shared storage and confirm there is a matching folder, label, or location for each classification level.
A successful result is: staff can classify a new document in under 30 seconds, and two different people give the same label for the same example document.
Common pitfalls
Using too many labels
Mistake: Creating six, eight, or ten labels with subtle differences.
Symptom: People stop labeling documents or choose labels inconsistently.
Fix: Delete the extra levels and keep only Public, Internal, Confidential, and Restricted.
Mixing sensitivity with retention
Mistake: Using one label to mean both how sensitive a document is and how long it must be kept.
Symptom: Staff ask whether Confidential means keep for 7 years.
Fix: Keep classification separate; put retention rules in a different table or policy.
No default for uncertain cases
Mistake: Telling staff to classify documents but not telling them what to do when unsure.
Symptom: Documents stay unlabeled because people wait for approval.
Fix: Add the exact default rule: If you are unsure, use Confidential until the document owner changes the label.
Labeling documents but not storage
Mistake: Adding labels in titles while leaving all files in one open shared folder.
Symptom: A document says [Restricted] but everyone in the company can still open it.
Fix: Create matching storage locations or permission groups for Confidential and Restricted.
Treating all personal data as Internal
Mistake: Putting customer lists, employee files, or support exports under Internal because they are "inside the company."
Symptom: Too many people can access personal data.
Fix: Change the rule so personal data is at least Confidential, and full exports, payroll, IDs, and bank details are Restricted.
Writing a policy nobody can use
Mistake: Publishing a long policy full of legal terms and no examples.
Symptom: Staff ask the same classification questions repeatedly.
Fix: Keep the one-page table, the four-line decision rule, and the document-type examples on the same page.
This article was written by an AI system and published pending human review. Verify anything you intend to act on.
Have a project in mind?
Get an instant AI price estimate for it, or talk directly to our team.
One email a month on what we learn building with AI