In most formal information-handling schemes, non-sensitive public information — general brainstorming, drafts, open meeting notes, marketing ideas — falls into the public or unclassified color category, typically green under traffic-light labeling systems or white/clear in classification markings. The boundary matters: the moment a brainstorm captures a customer name, a salary figure, or an unreleased product spec, it leaves that category. The color names differ by system, but the logic is shared — color tracks who may see the data, not how polished it is.
What "Public Information" Actually Means in a Color Scheme
Public information is data that can be shared with anyone inside or outside the organization without harm — published prices, press releases, general meeting logistics, and untethered brainstorming. In government classification schemes, this sits at the lowest tier, below Confidential, Secret, and Top Secret in the US system, or at "Unclassified" in NATO and UK handling caveats. Commercial schemes borrow the same ladder but name the bottom rung differently.
Under a traffic-light protocol such as the one published by the UK's Information Commissioner's Office for data sharing, green means "open sharing" and is the only tier intended for unrestricted circulation. Amber allows sharing within a defined group, and red restricts it to named recipients. That three-color language became popular because it maps onto how people already read signals.
The key distinction is between confidentiality and sensitivity of content. A highly sensitive topic — layoffs, for instance — doesn't automatically make the file confidential; the data inside the file does. A general brainstorm about "how do we communicate a restructure" with no names and no figures is still public-tier material until someone pastes in the actual list.
Check your organization's own policy before assigning a color. Classification authority usually rests with the data owner, not the person who created the document, and a wrong label is the most common source of both over-sharing and over-restriction.
Green, White, or Clear: Why the Label Differs Across Systems
There is no single global color for public information, and that trips people up. In a traffic-light data-sharing scheme, green is the open tier. In US government classification markings, documents are marked by their highest classification level, and unclassified documents carry no color banner at all — the absence of a banner is the signal. UK government handling instructions use "OFFICIAL" as the baseline, with color-coded subsets for OFFICIAL-SENSITIVE.
Commercial document management systems vary further. Some use white for public, green for internal, amber for confidential, and red for restricted. Others invert green and blue. The one consistent rule: the open, freely shareable tier sits at the bottom of the scale and is never marked with a restrictive caveat.
If you're building a scheme from scratch, borrow the traffic-light convention. It matches the mental model most staff already carry from road signals, which is why the UK's data-sharing guidance adopted it. Document the mapping in one page and publish it, because staff who can't find the definition will guess — and guesses skew toward over-classification.
The Brainstorm Boundary: When a Whiteboard Note Becomes Amber
Brainstorming is the clearest test case for the public tier because it starts open and drifts. A flip-chart page reading "campaign ideas: humor, nostalgia, celebrity" is public-tier. The same page with "celebrity — check if the contract with [name] allows it" just became internal at minimum, because it references a contract term.
Three triggers move a brainstorm up the ladder: named individuals, commercial terms, and unreleased plans. Add any one of those and the document needs at least the internal (amber) tier. Two of them together — a named client and a price — typically warrant confidential handling.
Practical rule for facilitators: capture ideas in one place and notes in another. The ideas board stays green; the notes board carries the higher label. Mixing them is how a fun session ends up as a data incident.
The Logistics of a Meeting: Which Parts Are Public
Meeting materials split across tiers more than any other common artifact. An agenda with times and room numbers is public. A pre-read containing staffing plans is not. The minutes usually land in between, because they record decisions but often also record who said what.
Take a quarterly all-hands. The date, location, and slide deck headline are public-tier. The financial results inside the deck are confidential until published, at which point the published version becomes public. The internal discussion about the results — the "what did we really think" conversation — stays internal even after publication.
Build a document register that maps each recurring artifact to a tier. All-hands deck: internal until release, then public. Board minutes: confidential. Project brainstorm: internal or public depending on content. That single register prevents most mislabeling, because staff stop deciding from scratch each time.
Five-Second Test: Sorting Data Before You Assign a Color
Ask five questions in order. Stop at the first "yes."
| Question | If Yes → Tier |
|---|---|
| Would publishing this cause harm to a person, customer, or the organization? | Confidential or higher |
| Does it contain personal data under GDPR or similar law? | Confidential or higher |
| Does it reveal unreleased commercial plans, pricing, or contracts? | Internal at minimum |
| Is it bound by an NDA or third-party agreement? | Confidential |
| None of the above | Public / green |
The order matters. A brainstorm about a fun office event that names attendees trips question two and leaves the public tier. A published press release passes all five and stays green. Walk through the test once with your team, then post it where documents get created.
Legal teams will add jurisdiction-specific rows — for example, health data under HIPAA in the US carries its own top tier — so treat the table as a starting template and hand it to whoever owns your data policy for local additions.
How Traffic-Light Protocols Handle Data Sharing
Traffic-light protocols exist primarily to govern sharing, not internal storage, which is why their color definitions are so explicit about recipients. Under the UK Information Commissioner's Office guidance on data sharing, green permits sharing with anyone, amber restricts sharing to a defined organization or group, and red limits it to named individuals. The tier governs the action, not the file.
That distinction changes how you label a brainstorm. A green document can be stored anywhere and sent anywhere. An amber one can be stored internally but needs a sharing agreement before it leaves the building. Apply the label to the sharing permission and the storage question answers itself.
Mistakes cluster at the boundaries. Sending an amber document to a partner without a data-sharing agreement is the most common failure. The second most common: treating a green document as unclassified and posting it publicly without checking for embedded personal data in the attachments.
When "Doesn't Contain Sensitive Data" Needs a Second Check
"Nothing sensitive in here" is a claim, not a verification. Three hidden vectors routinely smuggle sensitivity into documents that look clean: metadata, attachments, and comments. A spreadsheet of public pricing might carry a hidden column of cost figures; a public slide deck might retain speaker notes discussing layoffs; a PDF might carry an author name you'd rather not publish.
Run a quick check before downgrading any document to public. Strip metadata, delete hidden columns, remove comments, and check for embedded objects. Most office suites have a "document inspector" or equivalent that reports hidden content in one pass.
The second check is about recipients, not content. A document intended for the public and one intended for a specific journalist are both public-tier, but the second carries relationship risk and sometimes an embargo. Label the content public and manage the timing separately — the color doesn't capture embargoes.
Common Mistakes: Over-Classification and Accidental Leaks
Over-classification is the more frequent error and the more expensive one. When everything is marked confidential, nothing is, because staff stop reading the labels. A 2023 UK National Audit Office review of government classification found that the volume of OFFICIAL-SENSITIVE documents made the marking less useful as a signal. Commercial organizations repeat the pattern.
The opposite error — under-classification — produces incidents. The classic case is a brainstorm document that starts green and later accretes sensitive detail without a relabel. The file keeps the green marking even though its contents have moved up a tier. Label drift is the most common cause of accidental disclosure.
Fix both with a review trigger: relabel any document whenever its contents change containing personal data, commercial terms, or third-party names. Set the trigger in your collaboration tool if it supports it, and put it in the document header if it doesn't.
Building a Simple Color Scheme for Your Own Team
Start with four tiers, not more. Public (green), internal (amber), confidential (red), and a restricted tier for regulated data (often black or purple). Four tiers cover 95% of documents; adding seven ensures nobody remembers which one is which.
Publish one page per tier with three examples and three counter-examples. For the public tier, list "general brainstorming, open meeting notes, published marketing copy" and counter-list "anything with a customer name, anything marked draft with internal comments." Staff need the examples more than the definitions.
Run a labeling audit once a quarter on a sample of documents. Count the over-classified, the under-classified, and the unlabeled. Use the results to refine examples, not to discipline staff — the goal is calibration, not compliance theater.
FAQ
Is brainstorming always public information?
No — the category depends on content, not activity type. A brainstorm containing no personal data, commercial terms, or unreleased plans is public-tier; one that references a named customer or an internal cost figure moves to internal or confidential. Facilitators should split idea capture from sensitive notes so the open board stays green. Check the document for named people and figures before assigning the tier.
Does the color scheme change for documents shared with external partners?
Yes, sharing rules override the base color. Under a traffic-light protocol, amber documents require a data-sharing agreement before they leave the organization, while green documents can be shared freely. The label governs the sharing action, so a green document shared with a partner stays green but an amber one does not. Confirm the agreement exists before sending.
What is the difference between public and unclassified?
"Unclassified" is a government classification term meaning the document is not Confidential, Secret, or Top Secret; it can still be internal or sensitive. "Public" means freely shareable with anyone, including people outside the organization. A UK OFFICIAL document, for example, is unclassified but not public. Use the stricter of the two labels when in doubt.
How do I stop confidential brainstorms from leaking?
Relabel on content change, not on creation date. The most common leak path is a document that starts green and accumulates sensitive detail without a new label. Set a rule that any document gaining personal data, commercial terms, or third-party names is relabeled before it's shared again. Run a quarterly sample audit to catch drift.
Do personal names in a brainstorm change the category?
Yes, in most jurisdictions. Personal data under GDPR or similar law pushes the document to at least the confidential tier. A general brainstorm about customer service is public; one listing specific customer complaints with names is confidential. Anonymize names where possible and label the rest confidential.
Is a published press release still tracked under the color scheme?
Once published, the release is public information and the public tier applies. The draft was internal or confidential because it contained unreleased plans and named spokespeople. Keep the published version in the public tier and archive the draft under its original label. Don't downgrade the draft just because the final version is public.
Can a green document contain personal data if it's been anonymized?
Only if the anonymization is genuinely irreversible. Pseudonymized data — a name replaced with an ID, with the key still held internally — remains personal data under GDPR and stays confidential. Aggregated, non-reversible data can drop to public if the group size is large enough to prevent re-identification. Confirm with your data protection officer before downgrading.
What tier applies to open meeting notes shared in a public forum?
If the notes contain only agenda items, decisions, and open discussion without personal data, they sit in the public tier. Notes that record attributed comments, customer names, or commercial terms move to internal or confidential. The venue where the notes are shared doesn't change the tier; the content does. Publish only notes that pass the five-question test.