Scrivener is the reference tool for structuring long manuscripts — binder, corkboard, synopses, snapshots, compile presets, and a writing rhythm tuned for novels, theses, and screenplays. Lattuce (lattuce.app) is a cloud research-and-writing platform that borrows several of those planning ideas while connecting them to PDF sources, citation-verified compose, and export gates your lab or household can review.

Many graduate students start in Scrivener for chapter structure, then hit friction when literature lives in Zotero, citations must survive export, or a co-supervised thesis needs bilingual translation. Lattuce targets that handoff: keep the sectioned manuscript mental model, add the research pipeline at lattuce.app.

In short: choose Scrivener when binder UX and offline compile are the whole job; choose Lattuce when the manuscript must stay tied to sources, missions, and verified citations through DOCX (and optional EPUB) export.

Quick comparison

When Scrivener fits

• You are writing a novel or screenplay and want mature compile presets, script formats, and decades of community recipes.
• Offline-first desktop is non-negotiable — you draft on a plane with no server dependency.
• Your workflow ends at Compile into Word or ebook formats; you do not need PDF grounding or a shared source library.
• You rely on Scrivener’s binder depth — nested folders, document notes, and split views that Lattuce deliberately does not clone one-for-one.

When Lattuce fits

• The manuscript is research-backed — journal article, thesis, or systematic review where every claim should trace to a PDF in your library.
• You want section approval → DOCX export instead of “compile and hope citations survived.”
• Your lab or household needs shared cloud workspaces with optional BYOK for AI-assisted compose and study.
• You run research missions (evidence export, brainstorm briefs) and want those outputs to land in the same paper outline.
• You need multilingual workflows — e.g. Malay abstract alongside English body — without maintaining two Scrivener projects by hand.
• You are migrating from Scrivener and want binder sections, synopses, and body text imported into Lattuce sections (upload a .scriv zip from Writer).

What Scrivener still wins

• Binder UX depth — drag-and-drop hierarchy, split editor, and decades of muscle memory for fiction writers.
• Compile engine — one-click multi-format output, custom compile formats, and screenplay-specific tooling.
• Offline desktop maturity — no server, no deploy; install and write.
• Ecosystem & tutorials — courses, forums, and templates aimed squarely at novelists and NaNoWriMo cadence.
• Screenplay & Final Draft parity — not a goal for Lattuce Writer.

What Lattuce wins

• Integrated source library — upload PDFs and URLs, highlight, and cite without a plugin stack.
• Grounded compose — AI suggestions constrained to your corpus, with a grounding verifier before export.
• Section approval gate — mark sections approved before DOCX leaves the house; reduces “mystery formatting” surprises.
• Research missions — structured evidence gathering that feeds Writer, not a side folder of loose notes.
• Academic outline templates — IMRaD, five-chapter thesis, systematic review skeletons with planner synopses on the corkboard.
• Scrivener import — bring an existing .scriv project into Lattuce sections (synopsis + body text); replace or merge outlines from the Writer UI.
• Household cloud account — papers, sources, and history on your Lattuce account at lattuce.app.
• Study & Learner — grounded chat, digest artifacts, and language-learning paths over the same corpus (Scrivener has no equivalent).

Workflow: Scrivener → Lattuce

A practical migration path for thesis writers:

1. Finish structure in Scrivener (or export early) — corkboard order and synopses travel well.
2. Import the .scriv zip in Lattuce Writer — sections, synopses, and draft text become paper sections.
3. Attach sources in Library — PDFs, Zotero metadata (rich import when configured), or mission outputs.
4. Draft with citation-verified compose — section editor, writing targets, snapshots for risky rewrites.
5. Approve sections — gate export until supervisors sign off on each chapter.
6. Export DOCX (or EPUB for preprints) — citations tied to the source library, not orphaned footnotes.

You can also run both: Scrivener for early exploratory drafting on a laptop, Lattuce for the supervised, cited, exportable pipeline at lattuce.app.

Writer features Scrivener users will recognise

Lattuce Writer deliberately closes common “why not just use Scrivener?” gaps for academic long-form work — without pretending to be a novelist’s compile studio:

Fair limits: MOBI export on the server needs Calibre (ebook-convert); offline Writer in the notes-shell app is read/cache-first, not a full Scrivener-style offline write queue; realtime co-edit on paper sections is household-scoped and opt-in, not org-wide.

Bottom line

Scrivener remains the best-in-class structure and compile environment for long creative manuscripts on the desktop. Lattuce is the better fit when the manuscript is part of a research pipeline — sources, missions, verified citations, approval, and export at lattuce.app — and when you want Scrivener-like planning tools without giving up PDF grounding.

If you already live in Scrivener, treat Lattuce as the downstream publishing layer, not a binder replacement. If you are starting a cited thesis or lab paper today, starting in Lattuce avoids the Scrivener → Word → citation-fix loop entirely.

Related reading

• Literature review with Lattuce
• Sources to DOCX in Lattuce
• Lattuce vs research and team apps
• Approval gates vs realtime co-edit
• Where you can use Lattuce today

Scrivener is the reference tool for structuring long manuscripts — binder, corkboard, synopses, snapshots, compile presets, and a writing rhythm tuned for novels, theses, and screenplays. Lattuce (lattuce.app) is a cloud research-and-writing platform that borrows several of those planning ideas while connecting them to PDF sources, citation-verified compose, and export gates your lab or household can review.

Many graduate students start in Scrivener for chapter structure, then hit friction when literature lives in Zotero, citations must survive export, or a co-supervised thesis needs bilingual translation. Lattuce targets that handoff: keep the sectioned manuscript mental model, add the research pipeline at lattuce.app.

In short: choose Scrivener when binder UX and offline compile are the whole job; choose Lattuce when the manuscript must stay tied to sources, missions, and verified citations through DOCX (and optional EPUB) export.

Quick comparison

When Scrivener fits

• You are writing a novel or screenplay and want mature compile presets, script formats, and decades of community recipes.
• Offline-first desktop is non-negotiable — you draft on a plane with no server dependency.
• Your workflow ends at Compile into Word or ebook formats; you do not need PDF grounding or a shared source library.
• You rely on Scrivener’s binder depth — nested folders, document notes, and split views that Lattuce deliberately does not clone one-for-one.

When Lattuce fits

• The manuscript is research-backed — journal article, thesis, or systematic review where every claim should trace to a PDF in your library.
• You want section approval → DOCX export instead of “compile and hope citations survived.”
• Your lab or household needs shared cloud workspaces with optional BYOK for AI-assisted compose and study.
• You run research missions (evidence export, brainstorm briefs) and want those outputs to land in the same paper outline.
• You need multilingual workflows — e.g. Malay abstract alongside English body — without maintaining two Scrivener projects by hand.
• You are migrating from Scrivener and want binder sections, synopses, and body text imported into Lattuce sections (upload a .scriv zip from Writer).

What Scrivener still wins

• Binder UX depth — drag-and-drop hierarchy, split editor, and decades of muscle memory for fiction writers.
• Compile engine — one-click multi-format output, custom compile formats, and screenplay-specific tooling.
• Offline desktop maturity — no server, no deploy; install and write.
• Ecosystem & tutorials — courses, forums, and templates aimed squarely at novelists and NaNoWriMo cadence.
• Screenplay & Final Draft parity — not a goal for Lattuce Writer.

What Lattuce wins

• Integrated source library — upload PDFs and URLs, highlight, and cite without a plugin stack.
• Grounded compose — AI suggestions constrained to your corpus, with a grounding verifier before export.
• Section approval gate — mark sections approved before DOCX leaves the house; reduces “mystery formatting” surprises.
• Research missions — structured evidence gathering that feeds Writer, not a side folder of loose notes.
• Academic outline templates — IMRaD, five-chapter thesis, systematic review skeletons with planner synopses on the corkboard.
• Scrivener import — bring an existing .scriv project into Lattuce sections (synopsis + body text); replace or merge outlines from the Writer UI.
• Household cloud account — papers, sources, and history on your Lattuce account at lattuce.app.
• Study & Learner — grounded chat, digest artifacts, and language-learning paths over the same corpus (Scrivener has no equivalent).

Workflow: Scrivener → Lattuce

A practical migration path for thesis writers:

1. Finish structure in Scrivener (or export early) — corkboard order and synopses travel well.
2. Import the .scriv zip in Lattuce Writer — sections, synopses, and draft text become paper sections.
3. Attach sources in Library — PDFs, Zotero metadata (rich import when configured), or mission outputs.
4. Draft with citation-verified compose — section editor, writing targets, snapshots for risky rewrites.
5. Approve sections — gate export until supervisors sign off on each chapter.
6. Export DOCX (or EPUB for preprints) — citations tied to the source library, not orphaned footnotes.

You can also run both: Scrivener for early exploratory drafting on a laptop, Lattuce for the supervised, cited, exportable pipeline at lattuce.app.

Writer features Scrivener users will recognise

Lattuce Writer deliberately closes common “why not just use Scrivener?” gaps for academic long-form work — without pretending to be a novelist’s compile studio:

Fair limits: MOBI export on the server needs Calibre (ebook-convert); offline Writer in the notes-shell app is read/cache-first, not a full Scrivener-style offline write queue; realtime co-edit on paper sections is household-scoped and opt-in, not org-wide.

Bottom line

Scrivener remains the best-in-class structure and compile environment for long creative manuscripts on the desktop. Lattuce is the better fit when the manuscript is part of a research pipeline — sources, missions, verified citations, approval, and export at lattuce.app — and when you want Scrivener-like planning tools without giving up PDF grounding.

If you already live in Scrivener, treat Lattuce as the downstream publishing layer, not a binder replacement. If you are starting a cited thesis or lab paper today, starting in Lattuce avoids the Scrivener → Word → citation-fix loop entirely.

Related reading

• Literature review with Lattuce
• Sources to DOCX in Lattuce
• Lattuce vs research and team apps
• Approval gates vs realtime co-edit
• Where you can use Lattuce today