boltBuild from live responses
Pulls the latest survey responses in automatically. Review, then publish.
cloud Worker connection Not connected expand_more
Every publish keeps a backup of the version it replaced. If a publish went out wrong, put the previous one back — the swap is itself reversible, so this is safe to try.
One-time setup: upload your CSVs in the tabs, then send their history to the live store so "Build from live responses" has the full picture.
A response missing from the workbook? Search the live store for a name, email or any answer text — this reports whether it arrived, and if it did, exactly which check drops it.
Step 1 — Upload C20 CSV

Export from the Academic Expectations Survey Google Sheet as CSV.
Required columns: Partner Code · Module as expected (1-5) · Is there anything we can do to help you with your studies?

upload_file
Click to choose or drag & drop

C20 CSV — Academic Expectations Survey

Step 1 — Upload C65 CSV

Export from the Completion Survey Pulse Google Sheet as CSV.
Required columns: Partner · Score · Feedback

upload_file
Click to choose or drag & drop

C65 CSV — Completion Survey Pulse

Step 1 — Upload C40 CSV

Export from the Testimonial Request sheet (Google Sheets or Notion export).
Required columns: Partner · Score · Consent · Full Quote

upload_file
Click to choose or drag & drop

C40 CSV — Testimonial Request

A30 — Non-starter survey Work in progress

Responses come straight from the live form, survey a30, so there is no CSV to upload. Email figures come from the Email Metrics tab: name the campaign with A30, for example "ABER A30 - Non-starter".

Step 1 — Load live responses

Use Build from live responses at the top of the page. A30 is read with the rest, and its answers appear below.

Stored responses

Every A30 response in the live store. Removing one stops it counting from the next build; the workbook only changes when you publish. A removed record is kept and can be restored.

Step 1 — Upload the Email Reporting CSV Once, for all three surveys

The Pardot export already contains C20, C65 and C40 rows, so it only needs uploading here — this tab splits it by survey code and writes each survey's Delivered / Opens / Clicks into its funnel automatically.
Columns: Name · Delivered · HTML Opens · Total Clicks. Leave every row in — no filtering needed. Where to find this arrow_outward

mail
Click to choose or drag & drop

Email Reporting CSV — all surveys, unfiltered

infoOpens and clicks are totals, not unique students. Pardot counts every open and click, so one person opening five times is five opens. Open rate and click-through are engagement indicators, not reach — they can top 100%, and a later stage can look bigger than an earlier one. Delivered and completions are true counts.
Step 1 — Build prompt from current data

Generates a structured prompt from whatever CSVs you've uploaded. Copy it, paste into Claude, and paste the response below. The prompt also asks Claude to read the response-level source files in Survey Reporting\Data for module-level, per-programme and cycle-on-cycle detail — so paste it into Claude Code (or another Claude with file access). Pasted into claude.ai it still works, just from the snapshot alone.

Step 2 — Paste Claude's response

Paste the full JSON response from Claude here, then click Apply. This will populate the So What, HEP Own & Act, and Partner Conversations sections before you publish.

Saves into the payload — publish when ready