Hinsley Documentation
Publishing Questions to a Network
Publish a question to a forecaster network to request estimates from its members. Choose who can see it and who should receive a request. For sharing with anyone who has a URL, see Publish a Question with a Public Link.
Both forecasting questions and scenario sets can be published to a network - a scenario set asks forecasters to distribute likelihood across a set of futures rather than answer a single question.
Publishing
From a question's actions menu (or the scenarios page for a scenario set), choose Forecaster Network. The publish flow runs in two steps.
Step 1: Who and What
- Network - which of your account's networks to publish to. Networks the question is already on are not offered again, so you can see at a glance where it already stands.
- On behalf of - the sponsor the question is being asked for. Their name and logo appear on the question and in the forecaster's queue. Leave it as "no sponsor" and forecasters see your handle as who is asking.
- Topics - tag the question so forecasters can filter for it and so it lines up with the expertise they declared.
- Note for the network - optional context shown to forecasters alongside the question: why the forecast is being requested, what is at stake, and what the answer will be used for.
Audience and Forecast Requests
If the network has active cohorts, choose Who can see this question and Who receives forecast request notifications separately. You can show a question to the whole network while requesting forecasts only from selected cohorts. Members outside those request cohorts can still forecast if they can see the question.
For a cohort-only audience, choose request cohorts from the audience cohorts. A member only needs to belong to one selected cohort to qualify.
Set up cohorts and membership rules
Step 2: How Often to Ask
Choose between a one-time ask and a recurring one:
- One-time - forecasters are asked now, with responses due by a date you pick. Presets cover the common windows (a week, two weeks, 30 days, end of month).
- Recurring - forecasters are asked now and again on a cadence: weekly, monthly, quarterly, or a custom number of days. Each round has its own response window, and you set a date the recurrence stops.
Each new round of a recurring question re-queues it for the members being asked, including people who already forecast it. Successive rounds build a time series of the network's view. Rounds stop automatically once a question resolves, is voided, or reaches its end date.
What Happens on Publish
Publishing opens the first request round. Eligible members see it in their request queue once the question opens for forecasting. Request emails follow each member's delivery preferences and wait until the question's briefing material is ready. A question with selected request cohorts notifies only those members.
Publishing also kicks off research on the question if it has none yet, so the briefing material forecasters rely on - the state of play report, key sources, and base rate brief - is generated and appears shortly after.
Managing a Published Question
Changing Publication Settings
On a published network question, open its manage drawer and the Forecaster Network tab. The Presentation section lets you change its sponsor and topic or challenge tags. The Forecast request section lets you change its audience, request cohorts, schedule, and note without retracting and republishing.
Retracting
Retracting removes a question from the network. It disappears from forecasters' queues and lists, and no further recurring rounds open. Forecasts already submitted are kept. Publishing it again opens a fresh round.
Clarifications
If a question turns out to be ambiguous, post a clarification rather than editing the question underneath people who have already answered. Clarifications appear on the question page under Official Clarifications, and you can notify everyone who has forecast it. Their existing forecasts stand; the email tells them to revise if the clarification changes their thinking.
Voiding
When a question can no longer be resolved fairly - the world moved on, the wording was broken, the resolution source disappeared - void it. A voided question closes for forecasting and is never scored, so nobody's accuracy is affected by it. Forecasters who took part are notified and told their record is untouched. Voiding can be undone.
Voiding and clarifying are also available to network admins directly on the network, so neither requires access to the analysis the question came from.
Creating Questions on the Network
Network admins can also write a question directly on the network with New question on the questions page, without going through an analysis first. The question is attached to the network's owning account and published to that network in one flow. The form has the same Autofill with Hinsley, Save draft, and Validate Question actions as in the analyst workspace. Drafts appear on the Drafts tab of the Questions page under Staff. That page lists every question posted to the network, including hidden and voided ones, with its validation status and number of open problems, status, publish date, start and end dates, and audience. Filter it by status, validation status, topic, or challenge. See Question Drafts and Validating a Question.
A question that comes from an analysis is edited in that analysis. On the network, its Question and Classification pages say which analysis owns it, and link to the analysis's edit page if you can open the analysis. Changes made there show on every network the question is posted to.
A question created this way is not attached to an analysis, so its crowd forecast has no analysis to feed back into. Questions created inside an analysis do feed back into it.
What Comes Back
As forecasters respond, their estimates aggregate into a crowd forecast that appears on the question in the analyst workspace alongside AI forecasts and any internal estimates. When the question resolves, everyone who forecast it is scored, notified, and their accuracy record and the network leaderboard update.