Policy-area application
How different policy areas apply to the SIF's standards and criteria.
Designing and running pilots for the Lab. A pilot takes one or more elements of the Lab and tests it with participants - meaningfully simulating, at some proportion, what the full National Conversation could be.
A pilot is any engagement that takes one or more elements of the Lab to be tested with participants, in an interaction that meaningfully simulates - at some proportion - what the full National Conversation could be.
Pilots can take many forms: in-person or digital, a single session or a series, a survey question embedded in a broader instrument, or a facilitated deliberative workshop. What makes something a pilot is not its format but its purpose - a pilot tests something in order to determine whether and how it should be included in the Lab's final model and Shared Inquiry Framework (SIF).
How different policy areas apply to the SIF's standards and criteria.
Tools and methods for reaching and engaging participants.
Specific question wording, phrasing or sequencing from the SIF.
Facilitation approaches and the structure of face-to-face engagement.
The language and context provided to participants.
Whether questions are pitched at the right level for the audience.
The structure and shape of the session itself.
We strongly recommend limiting the number of things being tested at once - the more variables tested simultaneously, the harder it is to isolate what is working.
A conversation purely about the Lab itself - its design, governance or purpose - is a valuable touchpoint, but it is not a pilot. A pilot requires that an element of the Lab's methodology, questions, framing, format or technology is being tested with participants in a way that simulates the National Conversation experience.
A student can test questions with peers; a community organisation can embed a pilot in an existing program; a group or individual can initiate an entirely new event; a researcher can include a pilot within an approved survey instrument.
As part of their contribution to the Lab's design process.
Where piloting is within the scope of their engagement.
In alignment with their local implementation work.
As approved by the Secretariat.
All pilots must be run in accordance with the Lab's Terms of Reference and Code of Conduct. By agreeing to the Terms of Reference, pilot runners commit to the Lab's operating principles, its assumptions of participation, and its code of conduct.
Pilots demonstrate a focus on quality of engagement over volume of participation, with transparent and visible feedback loops. Inclusion of community members is designed from the outset.
All pilots must be approved by the Secretariat before they run, designed in alignment with the principles of the Lab, and reported fully upon completion.
Pilots may surface perspectives across policy areas - but must not represent outcomes as a final policy conclusion or position of the Lab or the National Conversation.
Pilots are a space to practice how we make decisions, not to reach and then advocate for particular positions. Care must be taken to stay within the Lab's non-partisan guidelines.
If a runner holds an advocacy position on the policy area being tested, it must be disclosed at registration. Failure to disclose may result in a pilot's findings being excluded.
Pilots must be reported honestly, including what did not work. All pilots must provide raw data to the Secretariat within four weeks of completion. Your own analysis is encouraged, but must accompany - not replace - the raw data.
Work through each step before submitting your pilot for approval. You should have a clear answer to every question - the Secretariat will review your responses as part of the approval process.
All pilots must consider output quality and usability, assessed against the Lab’s output quality criteria (under development).
Match length to depth - set the duration to suit the format, and always leave time for a debrief.
All pilots must provide raw data to the Secretariat within four weeks of completion. This is a firm requirement - holding raw data across pilots lets the Secretariat compare and synthesise findings in a methodologically consistent way.
All pilots must be approved by the Secretariat before they run.
Do not begin participant recruitment, distribute any materials, or make commitments to participants until written approval has been received.
Get in touch via our contact form with a short outline of the pilot you have in mind, and confirmation that you've read this guide and agree to the Lab's Terms of Reference.
The Secretariat works through it with you and reviews it against the requirements in this guide, including alignment with the Lab's principles and the RECIG standards.
The Secretariat confirms approval, conditional approval with required changes, or a decline with reasons, in writing.
Once approval is confirmed in writing, you may proceed. Do not run your pilot before written approval is received.
Share your raw data and any accompanying analysis with the Secretariat.
To get started, get in touch via our contact form with a short outline of your pilot. The Secretariat will work through the design, alignment and reporting with you from there.
get in touch via our contact form →Every pilot must have a responsible person and an organisation. The responsible person is accountable for:
By submitting a pilot for approval, the responsible person confirms they have read this guide, agree to its requirements, and accept responsibility for the pilot's conduct and reporting.
There’s no form to fill in. Get in touch via our contact form with a short outline of your pilot — what you’re testing, the format and scale, how you’ll test effectiveness, and the support you’re seeking. The Secretariat will be in touch to work through design, SIF alignment and reporting. All pilots are reviewed and approved before they run.
get in touch to register a pilot