Inside a survey: roster, results, and actions

What this is

Every survey you send from Forms, whether it is a full multi-question vendor check-in or a one-tap Lightning pulse, opens into the same detail view: a slide-over panel with a roster tab and a results tab. This is where you watch a survey run, chase down the people who have not answered yet, read what came back, and close the loop when you are done.

Nothing here replaces asking your team directly. Verinode is reading the invites and responses you already generated and laying them out so you do not have to reconstruct who answered what from an inbox.

Where to find it

Open Forms from the sidebar (iq.verinode.ai/forms). Every survey in your list, active, closed, or draft, opens this same detail panel when you click its row. The panel title bar shows the survey's title, and a close (X) returns you to the Forms list.

The header strip

Right under the title, a row of badges tells you what kind of survey this is at a glance:

• Type badge: one of Vendor, Tool, Process, Supply, Carrier, TPA, Tool Stack, Team, Team Pulse, or Work Style, each in its own color so you can scan a busy Forms list quickly.
• Lightning badge: appears only on Lightning surveys, the single-question, one-tap format.
• Status badge: Active, Closed, or Draft, uppercase.

If the survey has a subject (a specific vendor, tool, or process it is about), that subject's name appears at the right edge of the strip.

The stats strip

Below the badges, for any survey that has actually gone out (not a draft), three numbers sit side by side:

• Sent to: the invite count, how many people this survey went to.
• Responded: how many of those invites have a response on file.
• Response rate: responded divided by sent, as a percentage.

These three numbers are the same ones a draft survey does not show yet, because a draft has no invites.

Two tabs: Setup and Results

The panel has two tabs. Setup is the roster, the questions, and the invite-management controls. Results is what came back.

The Setup tab

Participation bar. For any non-draft survey with at least one invite, a bar shows "X/Y responded" and a percentage underneath, for example "3/8 responded" and "38% response rate." The bar fills proportionally as responses land.

The no-responses nudge. If a survey is active, has invites, has zero responses, and it has been more than 24 hours since it was sent, a banner appears: "No responses yet, it's been over 24 hours. Consider resending to your team." A Resend to all N button sends a fresh invite to everyone who has not answered. Once you click it, the banner changes to a confirmation: "Resent to all N invitees."

Questions. Every question on the survey is listed in order, numbered, with its label and its answer type spelled out underneath: Rating 1-5, a list of the binary options (defaulting to Yes / No), or Open text.

Recurrence panel. If this survey is a recurring series (weekly, every 2 weeks, monthly, quarterly, every 6 months, or annually), a panel shows the cadence and either "next fires [date]" or "paused." A Pause button stops the series without deleting anything, the parent record, every past response, and the invite roster all stay intact. Pausing simply stops the next scheduled send. A Resume button restarts it, and the next fire date is recomputed from today forward, not from the original schedule, so a series paused for months does not dump a stack of backdated sends the moment you resume it.

Add invitees. A panel labeled "Need to add someone?" with a + Add invitees link. Click it to pull your current team roster, and Verinode filters out anyone already invited to this survey (or without an email on file). Check the teammates you want to add and click Add N. This is idempotent: re-adding someone already on the invite list is a silent no-op, so there is no risk of double-inviting. If the survey is still active, new invitees get the actual invite email or Lightning prompt sent immediately; if the survey is a draft, they simply join the roster and go out whenever you send it. A confirmation line reads "Invite sent to 1 new teammate." or "Invites sent to N new teammates." If your entire team is already invited, the panel reads: "Everyone with an email on your team is already invited. Add new teammates from /team and they'll show up here."

Invitees list. Every person on the roster, in the order they were sent to. Each row shows their name (or email if no name is on file), their email, and their phone number if one was captured. A small tag marks delivery method when it is not plain email: SMS or E+SMS (email and SMS both). On the right:

• If they responded, a Responded tag in green, plus their reply rating (e.g. "4/5") if the survey captured one.
• If you already clicked resend on them this session, a Resent tag.
• Otherwise, a Resend link you can click to send them a fresh invite one at a time.

The Results tab

If nobody has answered yet, this tab reads: "No responses yet. Results will appear here once team members start responding." Nothing else shows until at least one person has answered.

Once responses start coming in, a summary line at the top reads "Responses received" alongside "N of M, X%," the same counts as the stats strip, restated for context inside the results view.

AI Analysis. For full surveys (not Lightning) with two or more responses, an AI Analysis card appears above the results. While it is generating, it reads "Analyzing responses…" in italics. Once ready, it shows a short written summary, three to four sentences on team sentiment, any notable patterns or outliers, and one actionable takeaway. This is generated by a language model reading the actual ratings and (for the first, satisfaction-style question) the actual names attached to each rating, not a canned template. The summary is cached for an hour, so opening the panel again shortly after does not regenerate it or use another decision unit; it only refreshes past that window. Because this is an operator-initiated AI action, generating (or regenerating past the cache window) a summary draws on your monthly intelligence allowance.

What the rest of the tab shows depends on whether this is a Lightning survey or a full survey.

Lightning surveys

Lightning surveys are the single-question, fast-tap format. Results show:

• A Team Responses header with the average rating across everyone who answered, formatted as "X.X/5 avg."
• One row per respondent, sorted lowest rating to highest so the people flagging a problem surface at the top. Each row shows the respondent's name, their delivery method if not plain email, how long after the invite went out they responded (e.g. "Responded in 2h"), and their rating in large type, colored red at 2 or below, green at 4 or above.
• Anyone who has not answered yet appears below, dimmed, with an Awaiting tag.
• A Rating Distribution block underneath shows the same 1-through-5 histogram you would see on a full survey's rating question: five bars, one per star value, each labeled with its count, so you can see the shape of the responses (a cluster at 5 reads very differently from a spread across 2 through 5, even at the same average).

Full surveys

Full surveys show a person-selector row of pills: All (N) plus one pill per respondent, first name only. Click All (the default) to see the aggregate across everyone; click a name to switch to that person's individual answers, question by question.

Aggregate view, per question:

• Rating questions: the average score in large type ("4.2 / 5"), followed by a five-row bar chart, one bar per star value 5 down to 1, each with a count. The bar length is proportional to how many respondents gave that rating.
• Binary questions: one small tile per option (Yes / No by default, or whatever custom options the question defines), each showing the percentage of respondents who chose it and the raw count ("3 responses").
• Open text questions: every text answer, quoted in its own block, so you read verbatim what people wrote rather than a summarized version.

Individual view (when you click a specific person's pill):

• Rating questions show that person's number, and if it differs from the group average by half a point or more, a "+X.X vs group avg" or "-X.X vs group avg" tag appears beside it, colored red for notably below average, green for notably above.
• Other question types show that person's raw answer as written.
• If that person did not answer a particular question, it reads "No answer" in italics.

Below the question results, anyone still outstanding is listed under Awaiting Response, name or email only, no rating, since they have not answered.

Closing, deleting, and exporting

The footer of the panel carries the survey's lifecycle actions and its send date, "Sent [date]," when applicable.

• Close survey: available on any active survey. This flips its status to Closed and records the close time. Closing does not delete anything, the roster and every response stay intact; it simply stops treating the survey as open for new responses. You would close a survey once you have what you need and do not want stray late answers changing the picture, or once a one-time survey has run its course.
• Delete: available on every survey, active, closed, or draft. This is a hard delete of the survey row itself. There is no undo confirmation dialog in the panel, so use it deliberately, particularly on a survey with real responses attached.
• Export CSV: appears once at least one response exists. Downloads a CSV with one row per respondent who answered: name, email, phone, delivery method, sent date, responded date, reply rating, and then one column per survey question holding that respondent's answer. The filename embeds the survey ID and the export date.
• Export PDF: appears only once the survey is Closed and has at least one response. This produces a formal PDF record of the survey and its results, useful for handing to a vendor, keeping in a compliance file, or archiving a completed self-audit.

What feeds the numbers you see

A few things worth knowing about how these numbers are built, so you read them correctly:

• Response rate and counts are computed straight from the invite roster: how many invites exist for this survey, and how many of those invites have a response recorded. There is no rounding trick or estimation, these are exact counts.
• Rating averages only include numeric rating answers, 1 through 5. A blank or malformed answer is excluded from the average rather than counted as a zero.
• The AI Analysis reads the same underlying ratings and names you see in the roster; it does not have access to anything outside this survey.
• Ratings you collect here also flow, in anonymized and aggregated form, into Verinode's peer benchmarks for the vendor, carrier, TPA, or tool the survey was about, alongside every other operator's contribution. Your team's individual names, ratings, and comments are never shared outside your account. Only the resulting peer pattern comes back to you as a benchmark, and Verinode never sells any of this to carriers.

Empty states, summarized

| Where | Empty-state copy | |---|---| | Results tab, zero responses | "No responses yet. Results will appear here once team members start responding." | | Add invitees, everyone already invited | "Everyone with an email on your team is already invited. Add new teammates from /team and they'll show up here." | | No-responses nudge (after 24h, zero responses) | "No responses yet, it's been over 24 hours. Consider resending to your team." |

Related reading

• The decision workspace
• How benchmarks work
• Benchmarks overview
• Clients and carriers