Document classes
GOB separates controlled policies and official notices from operational guides, programme materials, research outputs and general editorial content. The distinction helps readers understand what is mandatory and what is advisory.
The document library is intended to make current institutional materials easier to find, distinguish controlled documents from editorial content, and preserve a clear public record.
The document library is intended to make current institutional materials easier to find, distinguish controlled documents from editorial content, and preserve a clear public record.
Institutional library for GOB public documents, policies, guides, reports, notices and programme publications.
GOB separates controlled policies and official notices from operational guides, programme materials, research outputs and general editorial content. The distinction helps readers understand what is mandatory and what is advisory.
Where a document governs participation or public use of the GOB identity, the current public version should be accessible from the relevant policy page and, where appropriate, the Trust Center.
Operational resources are designed to help organizations improve governance, digital capacity, partnership readiness, programme design and communication without confusing guidance with legal or regulatory advice.
Research and reporting may summarize network themes, organizational needs or programme learning when sufficient evidence exists. GOB should distinguish observed results from targets or future ambitions.
Publications should identify authorship or institutional responsibility, publication date and source material when these are material to understanding or reuse.
Policies and formal notices
Guides, toolkits and templates
Reports and analytical publications
This section explains how the public framework is expected to work in practice and how GOB protects clarity as the project grows.
These pages are intended to give members, partners, journalists and external institutions a stable source of public information. Where a role, policy or partnership can affect external reliance, GOB should direct readers to the current controlled page rather than asking them to infer status from a social-media post, old presentation or informal message.
A strong institutional record separates the existence of a structure from the status of a person or agreement. Appointments are published after formal confirmation, active benefits identify their provider and terms, and policies are linked from the relevant operational page so readers can verify the rule that applies.
Institutional information can change as the project grows. Material changes should be reflected consistently across the website, structured data, public directories and notices. Where an earlier statement has been superseded, the current page should make the new status clear without creating a misleading impression that the older state never existed.
Member organizations participate inside the GOB framework without losing their own legal identity or management responsibility. The project can set conditions for use of its name, programmes, partner benefits and institutional introductions, while the member remains responsible for its own decisions, finances, staff, volunteers and public positions.