Broadcast: reaching your whole network

What Broadcast is

Broadcast is HQ's outbound dispatch channel: the one place you push something out to every membership in your network at once, and see how the network responds. It is not a job board, not a CRM, and not a place where you read a franchisee's private numbers. It is the send-and-listen layer that sits on top of the network: you author a payload, it lands in every active member's IQ deck, and Verinode rolls the response back up to you as an aggregate, never as a named individual's private business detail (with one narrow exception described below, which requires the member's explicit consent).

Broadcast holds five payload types, one per tab:

• Announcements: plain-text updates that land in every active member's IQ feed, with read receipts rolling back to you as a count.
• Initiatives: playbooks, directives, recommendations, and experiments you author for the network to see and (where applicable) adopt.
• Surveys: multi-question pulses. Members answer from their own IQ deck; you see only the aggregated distribution per question.
• Polls: one-question, five-second pulses for a fast read on network sentiment.
• Consent: requests asking a specific member to opt in to sharing named data (for a leaderboard, a case study, or a deeper look), which the member can approve, decline, or scope down.

Across all five, the pattern holds: Broadcast is how HQ speaks to the network and how the network's aggregate response speaks back. It is never a door into a single member's private books.

Where to find it

Open Broadcast from the HQ sidebar (it sits under Playbooks in the nav) at hq.verinode.ai/broadcast. The Announcements tab is the default landing view; the other four tabs live at their own URL:

• Announcements: /broadcast (no query string)
• Initiatives: /broadcast?tab=decisions
• Surveys: /surveys (its own clean route, so a direct nav shortcut can highlight it)
• Polls: /broadcast?tab=polls
• Consent: /broadcast?tab=consent

The tab strip

All five tabs sit in one pill-shaped capsule directly under the page title: Announcements, Initiatives, Surveys, Polls, Consent. Click a pill and the page swaps its hero, its rows, and its create button, but the capsule itself stays put so you always know which payload type you are looking at. Whichever tab is active is filled solid in copper; the rest sit transparent until you click them.

Admin-only authoring

Every send, create, and author action on Broadcast (Send broadcast, New initiative, New survey, New poll, New consent request) is gated to group admins. If your role is not admin, the tabs and their tiles still render in full, read-only: you can see every announcement, initiative, survey, poll, and consent request the network has, but the button to create a new one simply is not there. There is no separate "view-only" mode to switch on; the button's presence is the tell.

The privacy boundary

This is the rule that makes Broadcast trustworthy: outbound reach never grants HQ a member's private data. Sending something to the whole network does not open a door back into any one member's business. Concretely, per tab:

• Announcements: you get a read count and, once at least two snapshots exist, a trend line ("+3 reads vs Jul 4"). You never get a list of who has or has not opened it.
• Initiatives: you see status and, for Recent Activity, an updated timestamp. Adoption and outcome numbers (where they exist) are network aggregates, not a member-by-member ledger.
• Surveys: HQ sees only the aggregated distribution per question, computed by a background aggregator from the responses members submit in their own IQ deck. Individual responses never surface on the HQ side, for either survey pattern (the standard multi-question survey to members, or a template a member uses with their own crew, where even the template author-side response data stays with that member).
• Polls: same rule as surveys, aggregated vote counts only.
• Consent: this is the one path where HQ can eventually see something specific and named, and it exists precisely because it is opt-in. HQ asks; the member approves, declines, or narrows the scope from their own IQ deck. Nothing named moves without that explicit yes.

Announcements

What it is. The plain-text channel: a subject line and a short body that lands in every active member's IQ feed. Use it for the kind of update you would otherwise send as a mass email, quarterly rollup ready, a policy change, a heads-up before a bigger initiative goes out.

The hero. At the top: a headline count of broadcasts sent in the last 30 days, with a pill reading either "N sent 30d" or "Nothing sent recently." Below it, three secondary figures:

• Operator reads 30d: the sum of read receipts across everything sent in the window.
• All-time broadcasts: the lifetime total, with when the last one went out.
• Avg reads / broadcast: total reads divided by broadcasts sent in the last 30 days, rounded to a whole number (reads zero if nothing has gone out in that window).

If nothing has ever been sent, the hero explains the feature instead of showing zeros: it reads that sending a broadcast pushes a text message into every active member's IQ feed, and that receipts post back as read counts.

Recent broadcasts. Below the hero, up to 12 tiles, most recent first. Each tile shows the read count as its label ("4 reads"), the subject as its headline, the first 80 characters of the body as its sub-line, and when it was sent. Once a tile has at least two read-count snapshots, the meta line also carries a delta against roughly a week earlier, for example "Sent 3 days ago (+2 reads vs Jul 4)." Click a tile to open the full detail: the complete body and its read trend.

Sending one. Click Send broadcast (admin-only). A modal opens with two fields:

1. 1Subject: a short line, for example "Quarterly rollup ready."
2. 2Body: plain text only, one short paragraph. The helper text under the field reminds you it lands in every active member's IQ feed and that read receipts roll back up to this tab.
3. 3Click Send to network. The button stays disabled until both fields have content.
4. 4On success the modal confirms "Sent, delivered to N operators," then closes itself after a moment and refreshes the page so your new broadcast appears at the top of Recent broadcasts.

Empty state. With no broadcasts authored yet, the Recent broadcasts row reads: "No broadcasts authored yet. Use the Send broadcast button to push a text update into every active operator's IQ feed."

Initiatives

What it is. Initiatives are the outbound decision channel: playbooks, directives, recommendations, and experiments you author for the network. The tab pill reads "Initiatives," but this is one payload type with four flavors, called plan kinds underneath:

• Playbook: a canonical, multi-step play for the network to follow.
• Directive: a one-shot instruction from the franchisor: do this, by this date.
• Recommendation: a soft nudge with no enforcement, surfaced as guidance rather than an order.
• Experiment: a network-level test, the seed for a future A/B comparison.

The hero. A headline count of currently active initiatives, with a pill reading "N live," or "N in draft" if nothing is active yet, or "No decisions yet" with nothing authored at all. Three secondary figures: Drafts (pending activation), Completed 90d (closed out in the trailing 90-day window), and Plan kinds (how many of the four kinds are actually in use across your authored set).

The rows. Four stacked rows, each a horizontal tile strip:

• Active: initiatives currently live, up to 12, newest first. Each tile carries the plan-kind label as its badge, the title as its headline, the first 60 characters of the body (or "No description"), and either "Activated N days ago" or "Activation pending."
• In Draft: up to 8 tiles awaiting activation, same shape, meta reads "Created N days ago."
• Recently Completed: initiatives closed within the last 90 days, up to 8, meta reads "Completed N days ago."
• Recent Activity: the cross-cut view, up to 12 tiles spanning every status, sorted by last update. The sub-line here reads plainly as "Status: active" (or draft, or completed), and the meta line reads "Updated N days ago."

Creating one. Click + New initiative (admin-only). A modal opens where you pick a plan kind (each with its own hint text explaining what it is for), a title, and an optional body, or start from a Verinode-curated template via the "Browse templates" toggle, which pre-fills the kind, title, and body for you to edit before saving.

Empty states. Each row has its own message when it has nothing to show:

• Active: "No active decisions. Activate a draft from its detail view to deploy it across the network."
• In Draft: "No drafts in flight. Start a new decision to author a playbook or directive for the network."
• Recently Completed: "No decisions have closed inside the last 90 days. Completed playbooks surface here as proof of network-level action."
• Recent Activity: "Decisions surface here as you author them."

If you are not an admin and nothing has ever been authored, the hero itself explains the tab instead: "Decisions appear here as the franchisor authors playbooks, directives, and recommendations for the network."

Surveys

What it is. Multi-question pulses. You author a short set of questions (rating, yes/no, or free text), send it to every active member, and members answer from their own IQ deck. Verinode's background aggregator computes the distribution per question; that aggregate, never a per-member answer sheet, is what shows up here.

There is a second, template pattern living in the same table: a survey you author as a template for members to run with their own teams. The response data for a template survey stays entirely on the member's side; HQ only ever sees how many members adopted the template, never what their teams answered.

The hero. A headline count of surveys sent in the last 30 days, with a pill reading "N active" (if any are currently open), or "N sent 30d," or "Nothing sent recently." Three secondary figures: Responses 30d (aggregated across every survey sent in the window), Active surveys (sent and not yet closed), and All-time surveys.

With nothing ever sent, the hero explains the feature: sending a multi-question pulse reaches every active member, members answer from their own IQ surveys section, and HQ sees only the aggregated distribution per question, never per-member responses.

The list. Up to 12 tiles, newest first. Each carries a status label (Draft, Active, or Closed; a template survey adds " · template" to the label so the two patterns stay visually distinct), the survey title as its headline, and a sub-line that depends on state: unsent surveys read "N questions," a sent template survey reads "N members adopted, N questions," and a sent standard survey reads "N responses, N questions." The meta line reads "Not yet sent," or "Closed N days ago," or "Sent N days ago."

Authoring one. Click + New survey (admin-only). A two-step modal: give it a title, add questions one at a time (each is Rating (1-5), Yes / No, or Free text), optionally start from a Verinode-curated template pack instead of a blank form, then either Save Draft (it appears as a Draft tile, sendable later) or send it immediately, which flips it to Active and notifies every active member right away.

Empty state. "No surveys authored yet. Use the New survey button to draft a multi-question pulse, then send it to the network."

Polls

What it is. The fast, single-question sibling to Surveys: a one-question, five-second pulse for a quick sentiment read, rollout readiness, vendor feedback, a training sign-off check. Polls and Surveys share the same underlying table but are filtered into separate tabs so the two stay visually and conceptually distinct.

The hero. A headline count of polls sent in the last 30 days, with a pill reading "N open," or "N sent 30d," or "Nothing sent recently." Three secondary figures: Votes 30d (aggregated across every poll sent in the window), Open polls (sent and not yet closed), and All-time polls.

With nothing ever sent, the hero explains the feature: polls are one-question, five-second pulses; send one to every active member and their answers roll up into an aggregated distribution.

The list. Up to 12 tiles. Unlike Initiatives and Surveys, polls have no draft state, they ship the moment you send them, so the status label is only Open or Closed. Each tile's sub-line reads "N votes," and the meta line reads "Closed N days ago" once closed, or "Sent N days ago, closes N days ago" while open.

Sending one. Click + New poll (admin-only). A single-step modal: type the Question (the helper text reminds you polls are five-second pulses, so keep it short), choose the answer type (rating or yes/no), and pick how long it stays open: 1 day, 3 days (the default), or 1 week. Click send and it goes out immediately, there is no separate save-for-later step.

Empty state. "No polls sent yet. Use the New poll button to ship a 5-second pulse to the network."

Consent

What it is. The one Broadcast tab where HQ can end up seeing something specific and named about a single member, and it only ever happens because that member said yes first. A consent request asks one named member to share a particular piece of data for a particular purpose. The member sees the request in their own IQ deck and can approve it, decline it, or approve a narrower scope than what was asked for.

Four request kinds:

• Named on a leaderboard: for example, appear as #3 by margin on the network leaderboard with the member's name attached, instead of anonymized.
• Named in a specific view: let HQ see a particular metric, named, for a specific time window.
• Case study / publication: feature the member's data in a research publication or case study.
• Deep data access: job-level detail in support of a specific initiative, for example a margin-lift push.

The hero. A headline count of requests currently pending a member response, with a pill reading "N pending" or "Nothing pending." Three secondary figures: Approved 30d (member opt-ins), Declined 30d (member refusals), and All-time (total requests authored over the group's lifetime).

With nothing ever requested, the hero explains the feature directly: consent requests let HQ ask members to share specific named data for rankings, case studies, or deep dives, and members see each request in their own IQ deck where they approve, decline, or customize scope.

Pending operator response. Up to 12 tiles for requests still waiting on the member. Each shows the request kind as its label (a shorter form of the kind name: "Named leaderboard," "Named view," "Case study," or "Deep data"), the member's name as its headline, the specific metrics asked for as its sub-line ("Metrics: Margin, Cycle time" or "No metrics specified" if none were attached), and when it was asked, plus an expiry date if one was set.

Recently resolved. Up to 12 tiles for requests answered in the last 30 days, tagged Approved, Declined, or Withdrawn, with the same request-kind and metrics detail, and a meta line showing when that resolution happened.

Creating one. Click + New consent request (admin-only). Pick the member from your roster, pick a request kind, attach the specific metrics you are asking about, and optionally a time range and an expiry date. The request goes to that member's IQ deck; nothing is shared until they respond.

Empty states.

• Pending: "No requests waiting on an operator response. Use the affordance in the header to ask an operator to share named data for a specific metric, time window, or case study."
• Recently resolved: "No responses landed in the last 30 days."

Best-practice example

Say you are rolling out a new drying-equipment vendor across the network. Start with an Announcement ("New preferred vendor for drying equipment, details inside") so every member sees the heads-up land in their IQ feed. A day later, author an Initiative as a Recommendation (a soft nudge, not a mandate) with the vendor's terms and onboarding steps, so members who want to switch have a concrete play to follow. A week in, send a one-question Poll ("Have you started using the new vendor yet? Yes/No") to get a fast aggregate read on adoption without asking anyone to identify themselves. If the aggregate looks strong and you want to feature a specific member's before-and-after numbers in your next investor update or franchisee newsletter, that is where Consent comes in: send that one member a "Case study / publication" request naming the metrics you want to use, and only proceed once they approve. At no point in this sequence does HQ see a member's private numbers without that member choosing to share them.

Related help articles

• /help/hq-overview: what HQ is and how its sections fit together
• /help/network-health: the aggregate network-wide health view Broadcast's Initiatives and outcomes feed into
• /help/hq-programs: the Playbooks scoreboard that ranks adoption and outcomes across every initiative you have shipped
• /help/hq-benchmarks: the peer-benchmark surfaces that share the same privacy boundary as Consent
• /help/hq-standards: compliance tracking across the network
• /help/hq-compliance: the compliance-specific aggregate view
• /help/hq-report-library: where sent announcements and reports are archived for reference
• /help/discovery-day: onboarding new members into the network
• /help/item-19: franchise disclosure and financial-performance reporting

Data sources