+
+
+ );
+}
diff --git a/lib/response-exports.ts b/lib/response-exports.ts
new file mode 100644
index 0000000..dd0b02a
--- /dev/null
+++ b/lib/response-exports.ts
@@ -0,0 +1,188 @@
+import { utils, write } from "xlsx";
+
+import { isQuestionBlock, serializeBlock, type SerializedBlock } from "@/lib/blocks";
+import { db } from "@/lib/db";
+import { AppError } from "@/lib/errors";
+import { slugify } from "@/lib/utils";
+
+export type ResponseExportFormat = "csv" | "xlsx";
+
+type OwnedFormExportRecord = Awaited>;
+
+type ExportAnswerValue = string | string[] | undefined;
+
+export type ResponseExportColumn = {
+ key: string;
+ label: string;
+ blockId?: string;
+};
+
+export type ResponseExportRow = {
+ values: Record;
+};
+
+export type ResponseExportDataset = {
+ columns: ResponseExportColumn[];
+ rows: ResponseExportRow[];
+};
+
+const METADATA_COLUMNS: ResponseExportColumn[] = [
+ { key: "submissionNumber", label: "Submission #" },
+ { key: "submittedAt", label: "Submitted at" },
+ { key: "responseId", label: "Response ID" },
+];
+
+export async function loadOwnedFormResponsesForExport(userId: string, formId: string) {
+ const form = await db.form.findFirst({
+ where: {
+ id: formId,
+ userId,
+ },
+ include: {
+ blocks: {
+ orderBy: {
+ position: "asc",
+ },
+ },
+ responses: {
+ orderBy: [{ submittedAt: "asc" }, { id: "asc" }],
+ },
+ },
+ });
+
+ if (!form) {
+ throw new AppError("Form not found.", 404);
+ }
+
+ return form;
+}
+
+function createQuestionColumnLabel(block: SerializedBlock, questionIndex: number, seenLabels: Map) {
+ const baseLabel = block.title.trim() || `Question ${questionIndex}`;
+ const occurrence = (seenLabels.get(baseLabel) ?? 0) + 1;
+ seenLabels.set(baseLabel, occurrence);
+
+ return occurrence === 1 ? baseLabel : `${baseLabel} (${occurrence})`;
+}
+
+export function serializeExportAnswer(value: ExportAnswerValue) {
+ if (Array.isArray(value)) {
+ return value.join(" | ");
+ }
+
+ return typeof value === "string" ? value : "";
+}
+
+export function buildResponseExportDataset(form: OwnedFormExportRecord): ResponseExportDataset {
+ const questionBlocks = form.blocks.map(serializeBlock).filter((block) => isQuestionBlock(block.type));
+ const seenLabels = new Map();
+
+ const columns = [
+ ...METADATA_COLUMNS,
+ ...questionBlocks.map((block, index) => ({
+ key: block.id,
+ label: createQuestionColumnLabel(block, index + 1, seenLabels),
+ blockId: block.id,
+ })),
+ ];
+
+ const rows = form.responses.map((response, index) => {
+ const answers =
+ typeof response.answersJson === "object" && response.answersJson && !Array.isArray(response.answersJson)
+ ? (response.answersJson as Record)
+ : {};
+
+ const values = columns.reduce>((accumulator, column) => {
+ if (column.key === "submissionNumber") {
+ accumulator[column.key] = String(index + 1);
+ return accumulator;
+ }
+
+ if (column.key === "submittedAt") {
+ accumulator[column.key] = response.submittedAt.toISOString();
+ return accumulator;
+ }
+
+ if (column.key === "responseId") {
+ accumulator[column.key] = response.id;
+ return accumulator;
+ }
+
+ accumulator[column.key] = serializeExportAnswer(answers[column.key]);
+ return accumulator;
+ }, {});
+
+ return { values };
+ });
+
+ return {
+ columns,
+ rows,
+ };
+}
+
+function escapeCsvCell(value: string) {
+ if (!/[",\n\r]/.test(value)) {
+ return value;
+ }
+
+ return `"${value.replaceAll('"', '""')}"`;
+}
+
+export function createCsvExportBuffer(dataset: ResponseExportDataset) {
+ const headerRow = dataset.columns.map((column) => escapeCsvCell(column.label)).join(",");
+ const dataRows = dataset.rows.map((row) => dataset.columns.map((column) => escapeCsvCell(row.values[column.key] ?? "")).join(","));
+ const content = [headerRow, ...dataRows].join("\r\n");
+
+ return Buffer.from(`\uFEFF${content}`, "utf8");
+}
+
+export function createXlsxExportBuffer(dataset: ResponseExportDataset) {
+ const worksheet = utils.aoa_to_sheet([
+ dataset.columns.map((column) => column.label),
+ ...dataset.rows.map((row) => dataset.columns.map((column) => row.values[column.key] ?? "")),
+ ]);
+ const workbook = utils.book_new();
+
+ utils.book_append_sheet(workbook, worksheet, "Responses");
+
+ return write(workbook, {
+ type: "buffer",
+ bookType: "xlsx",
+ });
+}
+
+export function getResponseExportFilename(slug: string, format: ResponseExportFormat) {
+ const safeSlug = slugify(slug) || "form";
+ return `${safeSlug}-responses.${format}`;
+}
+
+export function getResponseExportContentType(format: ResponseExportFormat) {
+ return format === "csv"
+ ? "text/csv; charset=utf-8"
+ : "application/vnd.openxmlformats-officedocument.spreadsheetml.sheet";
+}
+
+export function parseResponseExportFormat(value: string | null): ResponseExportFormat {
+ if (value === "csv" || value === "xlsx") {
+ return value;
+ }
+
+ throw new AppError("Unsupported export format.", 422);
+}
+
+export async function createOwnedFormResponseExport(userId: string, formId: string, format: ResponseExportFormat) {
+ const form = await loadOwnedFormResponsesForExport(userId, formId);
+ const dataset = buildResponseExportDataset(form);
+ const filename = getResponseExportFilename(form.slug, format);
+ const contentType = getResponseExportContentType(format);
+ const body = format === "csv" ? createCsvExportBuffer(dataset) : createXlsxExportBuffer(dataset);
+
+ return {
+ filename,
+ contentType,
+ body,
+ dataset,
+ form,
+ };
+}
diff --git a/openspec/changes/archive/2026-04-09-export-form-results/.openspec.yaml b/openspec/changes/archive/2026-04-09-export-form-results/.openspec.yaml
new file mode 100644
index 0000000..98d7681
--- /dev/null
+++ b/openspec/changes/archive/2026-04-09-export-form-results/.openspec.yaml
@@ -0,0 +1,2 @@
+schema: spec-driven
+created: 2026-04-09
diff --git a/openspec/changes/archive/2026-04-09-export-form-results/design.md b/openspec/changes/archive/2026-04-09-export-form-results/design.md
new file mode 100644
index 0000000..46627ba
--- /dev/null
+++ b/openspec/changes/archive/2026-04-09-export-form-results/design.md
@@ -0,0 +1,85 @@
+## Context
+
+Lively Forms already stores anonymous responses and gives creators an authenticated response review surface, but that data currently stays inside the product. Exporting responses is a cross-cutting addition because it touches creator UI, ownership checks, response shaping, and file generation for multiple output formats.
+
+The current codebase already has server-side form ownership checks and response retrieval in `lib/forms.ts` plus creator-facing response pages under `app/(creator)/forms/[id]/responses/`. The new export flow should fit that model: exports are generated on the server for owned forms only and downloaded from the creator surface.
+
+## Goals / Non-Goals
+
+**Goals:**
+- Let creators export responses for forms they own.
+- Support two practical spreadsheet-oriented formats in the first release: CSV and XLSX.
+- Produce stable, readable exports that include submission metadata and one column per answerable block.
+- Keep export authorization aligned with existing response review ownership rules.
+- Avoid database schema changes.
+
+**Non-Goals:**
+- Building a generic reporting system or analytics dashboard.
+- Supporting every possible format in v1 (PDF, JSON, XML, etc.).
+- Exporting per-question aggregates or charts.
+- Persisting generated export files for later retrieval.
+
+## Decisions
+
+### 1. Add export actions to the creator responses surface
+The responses list page is the most natural place to export because it already represents the form-level response dataset. This keeps export discoverable and avoids duplicating controls elsewhere.
+
+**Alternatives considered:**
+- Add export actions in the form builder only: rejected because exports belong to response data, not structure editing.
+- Add export on each single-response page: rejected because the goal is dataset export, not one-off answer download.
+
+### 2. Generate exports on the server per request
+CSV/XLSX generation should happen in a server route or equivalent server-only handler after ownership verification. This avoids exposing raw response shaping logic to the client and keeps sensitive data authorization centralized.
+
+**Alternatives considered:**
+- Client-side export from already rendered response data: rejected because the full dataset may not be loaded and authorization should remain server-enforced.
+- Background job + stored files: rejected as unnecessary complexity for an on-demand export feature.
+
+### 3. Scope v1 formats to CSV and XLSX
+CSV gives a universal, low-dependency format for imports and scripts. XLSX covers common spreadsheet workflows and preserves a cleaner multi-column experience for non-technical creators.
+
+**Alternatives considered:**
+- CSV only: simpler, but does not satisfy spreadsheet-first users who expect native Excel-compatible downloads.
+- Add JSON in v1: useful for integrations, but weaker product fit than spreadsheet exports for the current audience.
+- Add PDF in v1: poor fit for tabular response datasets.
+
+### 4. Shape exports as one row per submission with derived columns
+Each exported row should represent one submission. Columns should begin with submission metadata (submission number, submitted timestamp, response ID) followed by one column per answerable block in saved form order. Column labels should use the block prompt when present, with a deterministic fallback for untitled questions.
+
+This mirrors how creators think about submissions and makes the data immediately usable in spreadsheets.
+
+**Alternatives considered:**
+- One sheet/tab per question: rejected because it complicates analysis and breaks the simple spreadsheet mental model.
+- Raw JSON blobs per submission: rejected because it reduces usability in CSV/XLSX.
+
+### 5. Serialize complex answers into readable cells
+Short and long text answers export as plain text. Single choice exports as the selected option. Multiple choice exports as a delimited string in a single cell for both CSV and XLSX so both formats share the same conceptual schema.
+
+**Alternatives considered:**
+- Expand multiple choice into one boolean column per option: powerful, but couples exports to mutable option sets and increases column sprawl in v1.
+- Store arrays in XLSX but flatten only CSV: rejected because differing schemas by format would be harder to explain and test.
+
+### 6. Reuse existing response/domain mapping helpers where possible
+The implementation should centralize export row construction in shared server-side helpers so CSV and XLSX use the same data shaping logic. Format writers should consume the same normalized export dataset.
+
+**Alternatives considered:**
+- Separate CSV/XLSX shaping paths: rejected because it invites drift and duplication.
+
+## Risks / Trade-offs
+
+- **Wide forms can produce wide exports** → Use saved block order and straightforward headings; accept width as a natural consequence of flexible forms.
+- **Untitled or duplicate question prompts can create confusing columns** → Provide deterministic fallback labels and preserve order so columns remain understandable.
+- **CSV formatting can be lossy for multiline text or separators** → Use a proper CSV serializer/escaping strategy rather than hand-built strings.
+- **New XLSX dependency increases bundle and maintenance surface** → Keep workbook generation server-only and use a minimal, well-supported library.
+- **Large response sets may increase request time** → Start with on-demand synchronous exports and monitor; optimize later if volume warrants it.
+
+## Migration Plan
+
+- No database migration is required.
+- Ship the server export handler and creator UI together so the control is only visible when the backend exists.
+- If rollback is needed, remove or disable the export action while leaving response review unaffected.
+
+## Open Questions
+
+- Whether the exported timestamp should use UTC ISO strings or a more human-readable format. Initial recommendation: use a stable machine-friendly timestamp value.
+- Exact filename convention. Initial recommendation: include form slug and format, e.g. `-responses.csv` and `-responses.xlsx`.
diff --git a/openspec/changes/archive/2026-04-09-export-form-results/proposal.md b/openspec/changes/archive/2026-04-09-export-form-results/proposal.md
new file mode 100644
index 0000000..848b8e0
--- /dev/null
+++ b/openspec/changes/archive/2026-04-09-export-form-results/proposal.md
@@ -0,0 +1,27 @@
+## Why
+
+Creators can review responses inside Lively Forms today, but they cannot take that data into spreadsheets, reporting workflows, or external tools. Adding export support now unlocks a practical next step for real form usage and addresses a common expectation for form products.
+
+## What Changes
+
+- Add creator-facing export actions for form responses from the response review area.
+- Support exporting responses in CSV and XLSX formats for owned forms.
+- Export one row per submission with stable columns derived from the form structure.
+- Include submission metadata such as submission number and submitted timestamp in the export output.
+- Serialize multi-select answers into a readable cell value for spreadsheet use.
+- Prevent exporting responses for forms the current creator does not own.
+
+## Capabilities
+
+### New Capabilities
+- `response-export`: Allow creators to export owned form responses in spreadsheet-friendly formats.
+
+### Modified Capabilities
+- `response-review`: Extend response review so creators can trigger exports for owned forms from the responses surface.
+
+## Impact
+
+- Affected areas: response review pages, form/response data shaping, export route or server action, and download UI.
+- Likely code: `app/(creator)/forms/[id]/responses/`, `lib/forms.ts`, shared response/domain types, and API/server export logic.
+- Likely dependencies: XLSX generation library or equivalent workbook writer.
+- Security: ownership checks must apply to every export request.
diff --git a/openspec/changes/archive/2026-04-09-export-form-results/specs/response-export/spec.md b/openspec/changes/archive/2026-04-09-export-form-results/specs/response-export/spec.md
new file mode 100644
index 0000000..7a512cd
--- /dev/null
+++ b/openspec/changes/archive/2026-04-09-export-form-results/specs/response-export/spec.md
@@ -0,0 +1,48 @@
+## ADDED Requirements
+
+### Requirement: Creator can export owned form responses in CSV and XLSX formats
+The system SHALL allow an authenticated creator to export responses for a form they own in CSV and XLSX formats.
+
+#### Scenario: Creator exports owned form responses as CSV
+- **WHEN** an authenticated creator requests a CSV export for a form they own
+- **THEN** the system downloads a CSV file containing that form's responses
+
+#### Scenario: Creator exports owned form responses as XLSX
+- **WHEN** an authenticated creator requests an XLSX export for a form they own
+- **THEN** the system downloads an XLSX file containing that form's responses
+
+### Requirement: Export requests are restricted by form ownership
+The system SHALL allow response exports only for forms owned by the authenticated creator and SHALL deny export access for forms owned by others.
+
+#### Scenario: Creator exports another creator's form
+- **WHEN** an authenticated creator requests an export for a form they do not own
+- **THEN** the system denies access and does not return response data
+
+### Requirement: Export output uses one row per submission with stable columns
+The system SHALL export one row per submission and SHALL include submission metadata plus one column for each answerable block in the form's saved order.
+
+#### Scenario: Form contains multiple question types
+- **WHEN** a creator exports responses for a form with multiple answerable block types
+- **THEN** the export contains submission metadata columns followed by one column per answerable block in saved order
+
+#### Scenario: Form contains text-only blocks
+- **WHEN** a creator exports responses for a form that includes non-answerable text blocks
+- **THEN** the export excludes those text blocks from answer columns
+
+### Requirement: Exported answers are spreadsheet-readable
+The system SHALL serialize answers into readable cell values suitable for spreadsheet use across supported formats.
+
+#### Scenario: Submission contains a multiple choice answer
+- **WHEN** a creator exports responses that include a multiple choice answer
+- **THEN** the selected options are written as a readable delimited value in the exported cell
+
+#### Scenario: Submission contains long text content
+- **WHEN** a creator exports responses that include long text answers
+- **THEN** the exported file preserves the answer content as text in the corresponding cell
+
+### Requirement: Exports remain available when a form has no submissions
+The system SHALL allow a creator to export an owned form even when it has no submissions and SHALL generate a file with headers only.
+
+#### Scenario: Creator exports an owned form with no responses
+- **WHEN** an authenticated creator exports a form they own that has no submissions
+- **THEN** the system downloads a valid export file containing column headers and no submission rows
diff --git a/openspec/changes/archive/2026-04-09-export-form-results/specs/response-review/spec.md b/openspec/changes/archive/2026-04-09-export-form-results/specs/response-review/spec.md
new file mode 100644
index 0000000..ee6dca6
--- /dev/null
+++ b/openspec/changes/archive/2026-04-09-export-form-results/specs/response-review/spec.md
@@ -0,0 +1,8 @@
+## ADDED Requirements
+
+### Requirement: Creator can start response exports from the responses view
+The system SHALL present response export actions in the responses view for a form owned by the authenticated creator.
+
+#### Scenario: Creator opens responses for an owned form
+- **WHEN** an authenticated creator opens the responses view for a form they own
+- **THEN** the system displays available export actions for the supported response export formats
diff --git a/openspec/changes/archive/2026-04-09-export-form-results/tasks.md b/openspec/changes/archive/2026-04-09-export-form-results/tasks.md
new file mode 100644
index 0000000..f52d41a
--- /dev/null
+++ b/openspec/changes/archive/2026-04-09-export-form-results/tasks.md
@@ -0,0 +1,27 @@
+## 1. Export data shaping
+
+- [x] 1.1 Add shared server-side helpers that load an owned form with its responses for export.
+- [x] 1.2 Build a normalized export row shape with submission metadata and one column per answerable block in saved order.
+- [x] 1.3 Implement answer serialization rules for short text, long text, single choice, and multiple choice responses.
+- [x] 1.4 Add deterministic fallback column labels for untitled or duplicate questions.
+
+## 2. File generation
+
+- [x] 2.1 Add or configure the XLSX dependency needed for workbook generation.
+- [x] 2.2 Implement CSV file generation using the normalized export dataset and proper escaping.
+- [x] 2.3 Implement XLSX file generation using the same normalized export dataset.
+- [x] 2.4 Add filename generation for exported files based on the form slug and selected format.
+
+## 3. Creator export flow
+
+- [x] 3.1 Add a server export endpoint or server action that validates form ownership before generating a download.
+- [x] 3.2 Wire CSV and XLSX export actions into the creator responses view.
+- [x] 3.3 Handle empty-response exports so creators can still download header-only files.
+- [x] 3.4 Show loading and error states that fit the existing creator UI patterns.
+
+## 4. Verification
+
+- [x] 4.1 Verify owned-form exports succeed in both CSV and XLSX formats.
+- [x] 4.2 Verify export requests for non-owned forms are denied.
+- [x] 4.3 Verify exported column order and values match the saved form order and response content.
+- [x] 4.4 Run the production build and fix any type or route issues introduced by the change.
diff --git a/openspec/specs/response-export/spec.md b/openspec/specs/response-export/spec.md
new file mode 100644
index 0000000..7a512cd
--- /dev/null
+++ b/openspec/specs/response-export/spec.md
@@ -0,0 +1,48 @@
+## ADDED Requirements
+
+### Requirement: Creator can export owned form responses in CSV and XLSX formats
+The system SHALL allow an authenticated creator to export responses for a form they own in CSV and XLSX formats.
+
+#### Scenario: Creator exports owned form responses as CSV
+- **WHEN** an authenticated creator requests a CSV export for a form they own
+- **THEN** the system downloads a CSV file containing that form's responses
+
+#### Scenario: Creator exports owned form responses as XLSX
+- **WHEN** an authenticated creator requests an XLSX export for a form they own
+- **THEN** the system downloads an XLSX file containing that form's responses
+
+### Requirement: Export requests are restricted by form ownership
+The system SHALL allow response exports only for forms owned by the authenticated creator and SHALL deny export access for forms owned by others.
+
+#### Scenario: Creator exports another creator's form
+- **WHEN** an authenticated creator requests an export for a form they do not own
+- **THEN** the system denies access and does not return response data
+
+### Requirement: Export output uses one row per submission with stable columns
+The system SHALL export one row per submission and SHALL include submission metadata plus one column for each answerable block in the form's saved order.
+
+#### Scenario: Form contains multiple question types
+- **WHEN** a creator exports responses for a form with multiple answerable block types
+- **THEN** the export contains submission metadata columns followed by one column per answerable block in saved order
+
+#### Scenario: Form contains text-only blocks
+- **WHEN** a creator exports responses for a form that includes non-answerable text blocks
+- **THEN** the export excludes those text blocks from answer columns
+
+### Requirement: Exported answers are spreadsheet-readable
+The system SHALL serialize answers into readable cell values suitable for spreadsheet use across supported formats.
+
+#### Scenario: Submission contains a multiple choice answer
+- **WHEN** a creator exports responses that include a multiple choice answer
+- **THEN** the selected options are written as a readable delimited value in the exported cell
+
+#### Scenario: Submission contains long text content
+- **WHEN** a creator exports responses that include long text answers
+- **THEN** the exported file preserves the answer content as text in the corresponding cell
+
+### Requirement: Exports remain available when a form has no submissions
+The system SHALL allow a creator to export an owned form even when it has no submissions and SHALL generate a file with headers only.
+
+#### Scenario: Creator exports an owned form with no responses
+- **WHEN** an authenticated creator exports a form they own that has no submissions
+- **THEN** the system downloads a valid export file containing column headers and no submission rows
diff --git a/openspec/specs/response-review/spec.md b/openspec/specs/response-review/spec.md
index 46820ee..166c3ea 100644
--- a/openspec/specs/response-review/spec.md
+++ b/openspec/specs/response-review/spec.md
@@ -21,3 +21,10 @@ The system SHALL allow an authenticated creator to open an individual response a
#### Scenario: Creator inspects response with text blocks in the form
- **WHEN** an authenticated creator views a response for a form that includes text blocks
- **THEN** the system shows only answerable block responses while preserving the form order context for the submission
+
+### Requirement: Creator can start response exports from the responses view
+The system SHALL present response export actions in the responses view for a form owned by the authenticated creator.
+
+#### Scenario: Creator opens responses for an owned form
+- **WHEN** an authenticated creator opens the responses view for a form they own
+- **THEN** the system displays available export actions for the supported response export formats
diff --git a/package.json b/package.json
index a8f2f6d..c06868c 100644
--- a/package.json
+++ b/package.json
@@ -42,6 +42,7 @@
"react": "^19.2.4",
"react-dom": "^19.2.4",
"tailwind-merge": "^3.5.0",
+ "xlsx": "^0.18.5",
"zod": "^4.3.6"
}
}