1. What does “public-safe” mean?
“Public-safe” means that a statement, summary, output, agenda item, profile, recap, release, or communication has been reviewed or prepared in a form that can be shared publicly without creating avoidable risk, confusion, misrepresentation, improper attribution, confidentiality breach, procurement confusion, political misuse, endorsement claims, or institutional overclaiming.
A public-safe output should be accurate, bounded, non-sensitive, non-confidential, non-defamatory, non-promotional, non-partisan, and free from claims that could be misunderstood as approval, certification, procurement status, financing, insurance, government endorsement, UN affiliation, or authority to represent GRF, GCRI, GRA, Nexus Consortium, the Country Desk, the Council, or any country.
Public-safe does not mean “everything can be shared.” It means the specific item has been shaped for public use. The underlying submissions, participant names, meeting notes, controlled annexes, stakeholder leads, institutional signals, conflicts, technical details, sponsor information, and sensitive context may remain restricted even when a public-safe summary exists.
A public-safe item should answer: Can this be seen by a member of the public, a journalist, a government official, a sponsor, a university, a company, a community member, or another participant without causing misunderstanding or harm?
In simple terms, public-safe means safe for public communication because the content has been stripped of restricted details, overclaims, improper attribution, and misleading signals.
2. What does “controlled” mean?
“Controlled” means that the material is not public and may only be accessed, used, discussed, stored, or shared under GRF’s official handling rules.
Controlled materials may include Council submissions, Priority Slates, agenda proposals, member lists, stakeholder leads, institutional leads, sponsor leads, internal meeting notes, controlled annexes, technical details, finance-readiness inputs, public-sector signals, community concerns, corrections, conflict disclosures, conduct matters, draft outputs, and materials that require review before publication.
Controlled material is not necessarily secret, but it is restricted. It should be treated as internal to the official GRF process and shared only with people who have a legitimate role, correct access, and permission to receive it. Controlled content should not be forwarded, screenshotted, copied into private chats, uploaded to personal drives, pasted into external tools, sent to employers, or shared with public officials, companies, sponsors, media, or other third parties without authorization.
Controlled handling protects participants and institutions. It prevents early, incomplete, sensitive, or context-dependent information from becoming public claims.
In simple terms, controlled means not public, not casual, and not freely shareable. It must stay inside approved GRF channels and access rules.
3. What is the difference between public-safe outputs and controlled outputs?
A public-safe output is designed for external communication. A controlled output is designed for limited internal or permissioned use.
A public-safe output may include a general summary, public-facing recap, approved announcement, public release memo, non-sensitive briefing note, profile text, or high-level explanation that has been prepared to avoid improper claims and unnecessary exposure.
A controlled output may include detailed meeting notes, internal submissions, controlled annexes, stakeholder lists, participant lists, sponsor or institutional leads, unresolved concerns, sensitive technical content, public-sector signals, finance-readiness materials, security-relevant information, conflict disclosures, or draft material not ready for public use.
The difference is not only sensitivity. It is also purpose. Public-safe outputs communicate responsibly. Controlled outputs allow serious work to happen without premature exposure, politicization, commercial misuse, or reputational harm.
A public-safe output may be derived from controlled work, but the controlled work itself does not become public just because a summary is published.
In simple terms, public-safe outputs are prepared for the outside world; controlled outputs are restricted materials used inside the official GRF process.
4. Who determines whether an output is public-safe or controlled?
GRF determines the handling classification through the appropriate official process.
A participant should not independently decide that a controlled Council submission, meeting note, stakeholder lead, docket item, annex, or discussion is public-safe. Classification should be made by GRF’s authorized operations, records, communications, Chair, Lead, handling, governance, or publication process, depending on the item.
Where uncertainty exists, the default should be controlled. Public release should happen only after the item has been reviewed for accuracy, permission, attribution, confidentiality, claims integrity, competition-safety, institutional risk, and handling posture.
A Chair may manage meeting boundaries and indicate that certain topics are controlled, but public release should still follow the official GRF publication or communications pathway. Participants should not rely on informal comments such as “this is probably fine to share.”
In simple terms, GRF determines public-safe status. If you are not sure, treat the material as controlled until GRF confirms otherwise.
5. What types of outputs can be public?
Outputs that can be public are those that have been reviewed, classified, and approved as public-safe.
Examples may include:
- general descriptions of GRF, the Council pathway, Nexus Universe, or National Council formation;
- approved participant title language;
- public-safe meeting recaps;
- public-safe House Briefing summaries;
- approved event announcements;
- approved agenda themes;
- high-level program summaries;
- public release memos;
- public-safe scoreboards;
- approved publications;
- public-safe adoption notes;
- non-sensitive community learning summaries;
- official calls to participate where authorized;
- approved sponsor or partner recognition where permission has been recorded.
Even public outputs must be careful. They should not disclose controlled details, overstate status, imply endorsement, list organizations without permission, expose participant names without consent, or suggest that a submitted item has been approved.
In simple terms, public outputs are materials GRF has prepared or approved for external use, usually at a high level and without controlled details.
6. What types of outputs must stay restricted?
Outputs must stay restricted when they contain sensitive, incomplete, permissioned, controlled, confidential, or high-risk information.
Examples include:
- raw Priority Slate submissions;
- Agenda Proposal submissions before review;
- nomination materials;
- conflict-of-interest disclosures;
- protected concern reports;
- claims or conduct dockets;
- participant lists where not publicly approved;
- stakeholder, sponsor, host, anchor, or institutional leads;
- internal meeting notes;
- Board materials;
- controlled annexes;
- security, handling, or incident materials;
- technical vulnerability information;
- sensitive public-sector or government-facing information;
- procurement-sensitive or market-sensitive information;
- finance, insurance, or investment-sensitive materials;
- community information that could expose people or places;
- drafts not approved for release;
- private correspondence or support records;
- materials marked controlled, restricted, no-forward, or similar.
Restricted material may later produce a public-safe summary, but the restricted material itself remains restricted unless GRF reclassifies it.
In simple terms, materials involving people, institutions, conflicts, sensitive details, drafts, submissions, or controlled annexes must stay restricted unless GRF explicitly makes them public-safe.
7. Can Council discussions be quoted publicly?
No, Council discussions should not be quoted publicly unless GRF has authorized the quote and any required consent has been obtained.
Council discussions are part of a controlled governance environment. Participants may speak candidly, raise concerns, describe blockers, discuss sensitive institutional issues, test ideas, or contribute specialized knowledge. Publicly quoting those discussions without authorization could expose individuals, distort context, create reputational risk, imply institutional positions, or violate handling rules.
Even if a statement seems harmless, quoting it publicly can create problems. A quote may be interpreted as GRF’s position, the Council’s position, a participant’s institutional position, or an endorsement of a project, sponsor, policy, technology, or public authority claim.
Participants may share only approved public-safe summaries or approved personal participation language.
In simple terms, do not quote Council discussions publicly unless GRF has approved the quote and attribution is permitted.
8. What does Chatham House Rule mean in this pathway?
In this pathway, Chatham House-style rules mean that information from a discussion may be used only if it is not attributed to the speaker, their organization, or other participants, unless explicit permission is given.
However, GRF’s handling rules are stricter than ordinary Chatham House practice. Chatham House Rule does not automatically make controlled information shareable. If a session or material is controlled, restricted, confidential, or not public-safe, participants may not disclose it simply by removing names.
For GRF Council purposes, Chatham House-style attribution discipline may help protect candor, but it does not override handling classes, confidentiality, public-safe review, access controls, publication rules, or correction discipline.
A participant should assume that Council discussions remain controlled unless GRF issues a public-safe summary or authorizes specific use.
In simple terms, Chatham House-style rules protect attribution, but they do not give permission to publish controlled Council information.
9. Can direct quotes from Council sessions be used?
Direct quotes from Council sessions should not be used unless all required permissions are in place.
A direct quote may require approval from the speaker, GRF, and any relevant institution if the quote could be interpreted as representing an organization. It may also require handling review to confirm that the quote does not reveal controlled content, sensitive context, confidential information, public-sector signals, community details, or unresolved claims.
Even if a speaker personally approves use of a quote, GRF may still determine that the quote is not public-safe because it creates broader institutional risk or misrepresents the session.
Direct quotes are especially sensitive when they involve public officials, regulators, diplomats, sponsors, community representatives, technical experts, companies, universities, or participants discussing national priorities.
In simple terms, direct quotes require explicit permission and GRF public-safe review. Without both, do not use them.
10. When is explicit consent required for attribution?
Explicit consent is required whenever a person, organization, institution, community, sponsor, public body, company, university, government office, or participant would be named, quoted, listed, photographed, identified, or otherwise associated with a statement, meeting, output, proposal, Council role, project, or public communication.
Consent is especially important for:
- direct quotes;
- photos or screenshots;
- participant lists;
- organizational names;
- logos;
- public officials or public institutions;
- community or frontline contributors;
- vulnerable groups;
- sponsor, anchor, host, or partner references;
- professional titles or employer affiliations;
- statements that may imply support, endorsement, participation, approval, or affiliation.
Consent must be specific. Permission to attend a meeting is not permission to be publicly named. Permission to be contacted is not permission to be listed. Permission to speak is not permission to be quoted. Permission to share a document internally is not permission to publish it.
In simple terms, explicit consent is required before naming, quoting, listing, photographing, attributing, or publicly associating a person or institution with Council work.
11. Are outputs attributed to individuals or to the Council?
Outputs may be attributed to individuals, committees, working groups, the Council, GRF, or no named author only if the attribution has been approved through the proper process.
Many Council outputs should be institutional or public-safe summaries rather than individual statements. This reduces the risk that a participant’s personal view is mistaken for GRF’s position, a government view, an institutional endorsement, or a Council decision.
Where individual authorship or contribution is appropriate, the attribution should be precise. It may say “prepared by,” “contributed by,” “submitted by,” “reviewed by,” “participant input,” or another approved description. Those terms should not be inflated into endorsement, official representation, or decision authority.
Council attribution should also be used carefully. A document should not be described as a Council output unless it has passed the appropriate Council process and record-valid handling.
In simple terms, outputs are attributed only as approved. Contribution does not automatically mean authorship, endorsement, Council approval, or GRF position.
12. Can I publish screenshots from Council meetings?
No. Participants should not publish screenshots from Council meetings unless GRF has explicitly authorized the screenshot and every visible person, name, chat item, document, slide, caption, participant list, meeting title, and displayed material is cleared for publication.
Screenshots are risky because they can reveal participant identities, attendance, private chat, controlled materials, meeting links, internal documents, draft language, time zones, institutional affiliations, or sensitive context. They can also imply that a meeting was official, public, endorsed, or open when it was controlled.
Even a celebratory screenshot can create reputational, safety, or attribution risk.
If GRF wants to publish visuals from a meeting, it should do so through an approved public-safe communications process with consent, cropping, redaction, caption control, and claims review.
In simple terms, do not publish Council screenshots. Only GRF-approved public-safe visuals may be shared.
13. Can I share meeting notes outside the official system?
No. Meeting notes should not be shared outside the official GRF system unless GRF has issued or approved a public-safe recap or authorized distribution.
Personal notes taken during a Council session may contain controlled information, participant statements, sensitive issues, unfinished decisions, draft ideas, institutional leads, conflicts, or context that is not safe to circulate. Sharing those notes with employers, colleagues, officials, sponsors, media, or other participants outside the official system can create serious risk.
If someone needs a summary, use the official recap or ask GRF whether a public-safe version is available. Participants should not create their own unofficial minutes.
In simple terms, meeting notes stay inside the official system unless GRF provides or approves a public-safe version.
14. Can I forward controlled materials?
No. Controlled materials should not be forwarded unless GRF has explicitly authorized the distribution.
Controlled materials may include submissions, agendas, dockets, annexes, meeting notes, stakeholder lists, drafts, technical materials, finance-readiness materials, participant information, and internal summaries. These materials may be subject to access controls, handling classes, no-forward rules, distribution logs, expiry dates, watermarking, and need-to-know restrictions.
Forwarding controlled materials can break the record chain, expose participants, compromise confidentiality, create unauthorized reliance, and damage institutional trust.
If someone else needs access, they should request access through the official GRF pathway rather than receiving a forwarded copy.
In simple terms, do not forward controlled materials. Access must be granted through the official system.
15. Can I share controlled materials with my employer?
No, not unless GRF has authorized that specific sharing and the material is cleared for that recipient.
A participant’s employer does not automatically have access to Council materials. Even if the employer paid the participant’s subscription, supported their time, or is professionally connected to the subject matter, controlled Council materials remain governed by GRF’s handling rules.
Sharing controlled materials with an employer may create organizational overreach, confidentiality breach, conflict-of-interest risk, procurement risk, sponsor influence risk, or unauthorized institutional use. It may also expose other participants’ information without consent.
Where an employer needs information, the participant should request a public-safe summary or ask GRF whether an institutional pathway, approved briefing, or controlled access permission is available.
In simple terms, your employer does not automatically inherit your Council access. Controlled materials may only be shared with employer permission if GRF specifically authorizes it.
16. Can I share controlled materials with government officials, sponsors, companies, or media?
No. Controlled materials may not be shared with government officials, sponsors, companies, media, public institutions, universities, investors, insurers, partners, or other third parties unless GRF has authorized that specific distribution.
This rule protects everyone. Government officials may interpret material as an official submission. Sponsors may interpret material as privileged access. Companies may interpret material as procurement or partnership opportunity. Media may interpret drafts as public positions. Investors or insurers may interpret materials as finance or insurance signals. Public institutions may be exposed to unauthorized claims or sensitive information.
If a third party asks for information, provide only approved public-safe material or route the request through GRF.
In simple terms, controlled materials stay controlled. Third parties receive only public-safe or specifically authorized materials.
17. Can GRF publish public-safe summaries?
Yes. GRF may publish public-safe summaries where appropriate.
Public-safe summaries allow GRF to communicate progress, themes, priorities, outputs, lessons, agendas, and public-interest findings without exposing controlled materials. They may summarize Council work, House Briefings, Action Week outputs, Country Desk themes, committee progress, or portfolio-level insights in a form that is suitable for broad distribution.
Before publication, GRF should review the summary for accuracy, evidence basis, handling class, attribution, confidentiality, claims integrity, competition-safety, public reliance risk, and correction readiness.
A public-safe summary should not imply endorsement, certification, government approval, procurement status, investment readiness, insurance status, or participant consensus unless that status is explicitly recorded.
In simple terms, yes, GRF can publish public-safe summaries, but they must be reviewed and bounded before release.
18. Can GRF publish anonymized or aggregated Council outputs?
Yes. GRF may publish anonymized or aggregated Council outputs where the material can be made public-safe and where aggregation does not create re-identification, attribution, confidentiality, or claims risk.
Anonymized or aggregated outputs may include patterns across Priority Slates, common blockers, regional themes, sectoral signals, high-level participation trends, public-safe lessons, or non-sensitive scoreboard information.
However, anonymization must be real. If a small country pathway, unique institutional role, specific community, unusual event, or distinctive technical detail makes it easy to identify the source, the material may still require controlled handling. Aggregated output should not expose sensitive community information, public-sector signals, sponsor leads, project submissions, conflicts, or individual positions.
In simple terms, GRF may publish anonymized or aggregated outputs, but only when they are genuinely public-safe and cannot be used to identify or misrepresent participants or institutions.
19. What happens if controlled information is disclosed improperly?
Improper disclosure of controlled information may trigger containment, review, correction, access restriction, participant warning, removal of materials, suspension, termination, or other action depending on severity.
GRF may require the person who disclosed the information to stop further sharing, identify recipients, preserve evidence, delete or retrieve materials where appropriate, issue corrections, notify affected parties, and cooperate with review. If the disclosure involved sensitive personal information, public institutions, community risk, security information, controlled annexes, sponsor matters, or reputational harm, stronger action may be required.
If the disclosure creates public confusion, GRF may issue a public-safe correction or clarification. If it involves misuse of GRF or Nexus names, logo, endorsement claims, procurement claims, or unauthorized attribution, takedown may be required.
The response should be proportionate, but the default posture is serious. Controlled handling is central to trust.
In simple terms, improper disclosure can lead to containment, correction, access restriction, suspension, or termination, depending on risk and intent.
20. What should I do if I accidentally share restricted information?
If you accidentally share restricted information, act immediately and do not try to handle it privately.
You should:
- Stop further sharing immediately.
- Notify the appropriate GRF handling, support, or protected reporting channel as soon as possible.
- Preserve evidence, including what was shared, when, how, to whom, and whether it has been forwarded or downloaded.
- Do not delete records in a way that prevents review, unless GRF instructs you to remove a public post or take down exposed material.
- Ask the recipient not to forward, copy, publish, or rely on the material.
- Follow GRF instructions on containment, takedown, correction, notification, access restriction, or replacement materials.
- Submit a correction or incident update through the official process if required.
Accidental disclosure is different from intentional misuse, but it still must be contained quickly. Delay can increase harm.
In simple terms, report accidental disclosure immediately, preserve the facts, stop further distribution, and let GRF manage containment and correction through the official process.
