Useful context
Name, organisation, role, broad problem area, geography at a non-sensitive level and the kind of conversation you want.
Submission Guidelines
Public submissions should help route a serious conversation without exposing sensitive material.
These guidelines apply to contact messages, contributor interest, solution review requests, public notes and future Collective submissions.
What to share
Give enough context to understand the pathway, not enough to create risk.
The current website is static and mailto-based. It is appropriate for introductions, expressions of interest and non-sensitive summaries.
For solution review
Share the problem addressed, evidence summary, adoption conditions, where it has worked, known limits and a responsible contact.
For contributors
Share your experience area, role, broad geography, type of learning you can contribute and whether you prefer public or private follow-up.
Do not submit sensitive material
Public forms and email links should not be used for operational logs, confidential government documents, personal records, identifiable citizen information, passwords, procurement material or politically sensitive details.
Public use
GI may use non-sensitive submissions to route a conversation, decide whether to follow up and prepare a private discussion.
Publication review
No submitted material should become public until a human reviewer checks evidence, consent, attribution, sensitivity and public-claim discipline.
Intake routing
Every submission should have a clear next step.
The launch website should route serious interest without pretending that public email is a secure repository or a publishing workflow.
Route
Identify the pathway: government conversation, funder briefing, practitioner interest, solution review, academic collaboration, advisory interest or media query.
Screen
Check whether the message contains sensitive, confidential, identifiable or politically risky material that should move out of public email.
Assign
Give each serious submission a responsible reviewer before requesting additional detail or scheduling a private conversation.
Decide
Classify the next action: respond, request private follow-up, route to curation, defer, or decline if the submission is outside GI's scope.
Future Collective submissions
Every public knowledge object needs review before publication.
Future playbooks, solution pathways, requests, profiles, learning capsules and downloadable notes should follow the content schema and be reviewed before public release.
Evidence
Submissions should separate observation, assumption, claim and verified result.
Conditions
Describe where an approach may work, where it may not work and what institutional conditions matter.
Attribution
Contributor names, organisations and partner references should appear only after explicit confirmation.
Publication gate
Public knowledge requires consent, evidence and sensitivity review.
GI should treat publication as a deliberate editorial decision, not the automatic result of receiving a message.
Consent and attribution
Confirm who may be named, what organisation may be referenced and whether the contributor wants public, private or anonymous handling.
Evidence and limits
Record the evidence level, source material, failure modes and adoption conditions before converting a submission into a case or pathway.
Sensitivity and claim review
Remove restricted details, unconfirmed state or partner claims and any material that could identify citizens, frontline workers or confidential operations.