Choose the Right Tool

The Fundamental Distinction

Traditional word processors primarily manage documents.

Project-based writing applications add hierarchy, notes, research and compilation tools around those documents.

Plain-text writing environments prioritise transparency and portability by storing manuscripts as ordinary text files.

SceneWeaver takes a different approach.

It is a Structured Authoring Environment.

Your manuscript prose, structural hierarchy, Characters, Locations, Organisations, Items, Concepts, timeline information, annotations, citations, index entries, Tokens, continuity rules and publication data are all parts of the same interconnected project.

SceneWeaver stores that project in a local SQLite database.

That matters because SceneWeaver does not simply know what text you have written. It can also understand that a particular reference represents a Character, that another refers to a Location, that an Entity should not appear before its introduction point, or that a value appearing repeatedly throughout the manuscript belongs to the same underlying piece of project data.

The result is a writing environment that can automate tasks which would otherwise require notes, searches, spreadsheets or manual checking.

One Project Model, Not a Collection of Separate Tools

A Character in SceneWeaver is not simply a page of notes stored beside your manuscript.

It is structured project data that other parts of SceneWeaver can use.

The same Character can:

• have recognised names, aliases and keywords;
• appear inside prose through dynamic Tokens;
• participate in continuity checking;
• have an introduction and exit point within the manuscript;
• carry images, descriptions and development notes;
• appear contextually while you work on relevant parts of the manuscript;
• contribute to a reader-facing Glossary;
• interact with Signatures and other project rules.

The same principle applies to Locations, Organisations, Items and Concepts.

SceneWeaver's features therefore do not exist as isolated utilities. They operate against the same underlying project model.

That is the architectural difference.

Architectural Comparison

Where SceneWeaver Is Different

Dynamic Entity Tokens

A conventional search-and-replace operation works with text.

SceneWeaver Tokens work with identity.

For example, manuscript text can contain a dynamic reference such as:

≪keyword:attribute≫

That Token can represent information belonging to a Character, Location, Organisation or Item rather than merely containing a fixed sequence of letters.

If the underlying Entity data changes, the Token can render the updated value without requiring the manuscript to be manually searched and edited.

Tokens can also specify:

• the particular Entity attribute to display;
• an optional Entity type;
• text presentation such as proper case, upper case, lower case or capitalisation.

SceneWeaver can also recognise configured Entity names and keywords in existing prose and convert them into Tokens.

This becomes particularly useful in large manuscripts where the same information may appear dozens or hundreds of times.

Context-Aware Continuity Checking

Generic spelling and grammar tools analyse language.

SceneWeaver can additionally analyse the internal rules of your project.

Continuity checks can identify issues such as:

• an Entity appearing outside its expected manuscript range;
• references occurring after an Entity's recorded exit;
• unusual first mentions;
• missing or orphaned project references;
• configured Signature inconsistencies;
• structural references that no longer point to valid manuscript nodes;
• a detail that was true earlier in the book being used where a later value applies; Version 3 — not yet released
• a mention of an Entity inside a period where it was deliberately absent; Version 3 — not yet released
• a character linked to a story event but missing from the material inside that event. Version 3 — not yet released

These are advisory checks.

SceneWeaver does not assume that every unusual occurrence is a mistake. The author remains in control of whether a warning represents an error, an exception or a deliberate narrative choice.

Continuous Transactional Persistence

SceneWeaver does not use the traditional workflow of repeatedly pressing Save while writing.

Normal edits are persisted automatically into the local project database.

SQLite transactions help protect the internal consistency of the project if an operation is interrupted, while SceneWeaver also maintains project snapshots so earlier states can be recovered when necessary.

Version 3 extends this to the dialogs as well as the prose. Version 3 — not yet released Project editors have no Save or Apply button to commit staged changes, because there is nothing staged: a valid change is written when it is made, and closing an editor neither commits nor discards it. A value still being typed, or one that is incomplete, stays on screen to be corrected rather than replacing the last valid stored value.

Also in Version 3, protection before a change is graded, and the grading is yours to set. A word edit counts as superficial, a paragraph operation as minor, and removing or moving a whole piece of content as major; the preferences for minor and major changes are independent of each other. Application-wide preferences keep a separate reversible history, since a manuscript backup cannot restore configuration that lives outside the manuscript.

No storage system can guarantee immunity from hardware failure, filesystem damage or software defects, but SceneWeaver's persistence model is designed to minimise dependence on manual saving and reduce the risk of partially written project data.

Real Page Layout Inside the Writing Environment Version 3 — not yet released

Many writing applications estimate manuscript pages from word counts until the project is compiled or exported.

SceneWeaver's Page View can render the manuscript using the actual geometry of the intended book.

It can account for:

• selected trim size;
• physical page margins;
• facing left and right pages;
• inner gutter margins;
• gutter scaling based on total page count;
• outer-edge page numbers;
• Roman-numeral front matter;
• Arabic-numbered body pages;
• actual line wrapping from the rendered text;
• running heads and page numbers, planned once and used by Page View, PDF, DOCX and print preview alike.

The result is a paginated representation based on layout rather than a simple words-per-page estimate.

Version 1 and Version 2 estimate the page count from the word count, which is what is available today; the paginated Page View described above arrives with Version 3, and the estimator remains available there for anyone who does not need full pagination.

A World Bible That Participates in the Manuscript

Many writing tools let you keep character sheets, location notes or research documents beside your prose.

SceneWeaver goes further by treating these as data that can participate in the manuscript itself.

SceneWeaver currently supports five Entity types:

Characters

People or characters within the project.

Locations

Places important enough to track independently.

Organisations

Groups, companies, governments, institutions, factions and other organised bodies.

Items

Significant objects including documents, vehicles, artefacts, machines, weapons and other recurring physical things.

Concepts

Non-physical ideas such as religions, belief systems, philosophies, laws, theories, traditions, doctrines or recurring abstract principles.

Because these are structured Entities rather than disconnected notes, other SceneWeaver systems can work with them directly.

In Version 3, an Entity is also allowed to change. Version 3 — not yet released A character sheet in most tools holds one set of details, which quietly becomes whichever version the author last edited. In SceneWeaver a recorded detail — a rank, an allegiance, a marital status, an appearance — can hold one value early in the manuscript and another later, added as a new state rather than overwriting what was true before. A token that prints that detail resolves to the value which applies where it sits, so chapter one keeps saying what was true in chapter one.

Also in Version 3, an Entity's presence in the book becomes a list of ranges rather than a single span, so a character who appears, leaves and returns can be described as they actually are, and a mention that falls in a deliberate absence is something SceneWeaver can notice.

Structure Beyond Chapters

SceneWeaver provides a hierarchical manuscript structure containing Chapters, Scenes, Sections and specialist book material.

The same manuscript can be viewed and managed through several perspectives, including:

• the Structure tree;
• Corkboard;
• Timeline;
• Smart Collections;
• Index;
• contextual Entity views;
• Page View.

These are different views of the same project rather than independent copies of the manuscript.

You can therefore reorganise how you inspect the project without maintaining several parallel planning systems.

Publication Structure

Books contain more than numbered Chapters.

SceneWeaver supports dedicated Special Chapter types for material such as:

• covers;
• title pages;
• dedications;
• forewords;
• prefaces;
• introductions;
• prologues and epilogues;
• contents;
• epigraphs;
• acknowledgements;
• appendices;
• bibliographies;
• indexes;
• author information;
• other front and back matter.

Special Chapters can behave differently from ordinary manuscript Chapters where appropriate.

For example, covers use dedicated image handling, front matter can use Roman page numbering, and generated material such as bibliographies or indexes can be incorporated into the publication structure.

Version 3 adds two more generated chapters: a Glossary assembled from the Entities marked for inclusion, and a Dramatis Personae drawn from the cast. Version 3 — not yet released Both carry a reader-facing description held separately from the author's own notes, so private planning material is not exposed in the finished book.

Annotations That Remain Connected to the Writing

SceneWeaver supports both general manuscript-node annotations and annotations attached directly to selected prose.

A selection-based Annotation records the text that was originally selected while maintaining its attachment to the evolving manuscript range.

This means an editorial note can retain the wording that prompted it even if the manuscript is subsequently revised.

Annotated text is highlighted in the editor, overlapping annotations remain visually distinguishable, and selection annotations can navigate back to their source.

Integrated Citations

SceneWeaver includes citation management for projects that require formal source attribution.

Supported citation styles include:

• Harvard;
• Chicago;
• APA;
• MLA.

Citation Tokens can be inserted into manuscript text, while bibliography information can feed directly into the project's Bibliography or References section.

SceneWeaver can also work with Zotero-linked reference information.

This makes the citation system useful for non-fiction, academic writing and fiction projects containing substantial documented research.

Glossary and Index Generation

SceneWeaver can use project information to create reader-facing reference material.

The generated Glossary is part of Version 3 and is not in any released version yet. Version 3 — not yet released Entities can be selectively included in it and given dedicated public-facing descriptions rather than exposing the author's internal notes; an Entity's description can be copied across as a starting point and then edited independently; and manual entries can be added for terms that no Entity represents.

The Index is available now, and operates separately: it tracks configured terms and their occurrences throughout the manuscript.

Both systems therefore derive publication material from data already maintained during the writing process rather than requiring the author to rebuild everything at the end.

Where Other Applications May Be the Better Choice

SceneWeaver is intentionally designed for long-form and structurally complex writing.

That means there are many situations where another application is the more appropriate tool.

You Mainly Write Short Pieces

If you are writing:

• short stories;
• blog posts;
• journal entries;
• notes;
• isolated articles;

then SceneWeaver may provide considerably more structure than you need.

A lightweight Markdown editor or distraction-free text editor may let you start writing faster with almost no project-management overhead.

You Want Your Manuscript Stored as Ordinary Text Files

Some authors specifically want every part of their manuscript to exist as human-readable files that can be opened with any text editor.

That is a genuine advantage of tools such as novelWriter.

SceneWeaver deliberately chooses a database-backed model instead because its features depend on relationships between manuscript structure, Entities, Tokens, annotations, continuity data and other project information.

SceneWeaver can export into portable formats, but its native project format is not intended to be edited outside SceneWeaver.

If plain-text transparency is your highest priority, a plain-text writing environment may suit you better.

You Need Highly Prescriptive Plotting Methods

Some applications provide structured workflows based around particular planning techniques such as the Snowflake Method.

If you want the software to lead you through a fixed plotting process before you begin writing, an application such as Manuskript may be a better fit.

SceneWeaver provides planning and structural tools, but it does not require you to follow one prescribed method of constructing a story.

You Already Have an Established Scrivener Workflow

Scrivener is a mature long-form writing environment with particularly strong Binder organisation and compilation tools.

If your existing workflow already handles your project effectively and you do not need SceneWeaver's semantic Entities, dynamic Tokens, integrated continuity modelling or database relationships, migrating may offer little practical benefit.

Software should solve a problem you actually have.

You Need Collaborative Document Review Above Everything Else

If your primary workflow involves several people simultaneously editing, commenting on and reviewing the same document, collaborative document platforms may currently be more appropriate.

Applications such as Word and Google Docs are deeply established in editorial and business review workflows.

SceneWeaver's emphasis is on the author's structured project rather than real-time multi-user document collaboration.

You Need Maximum Conventional Page-Layout Control

A dedicated word processor or desktop-publishing package remains the right choice when your principal task is detailed visual page construction rather than manuscript development.

SceneWeaver provides book-oriented pagination and export tools, but it is not intended to replace specialist desktop-publishing software for complex graphic layout.

Which Type of Writer Is SceneWeaver For?

SceneWeaver is most useful when the difficulty of your project is no longer simply writing the words.

It is designed for projects where you also need to manage things such as:

• large casts;
• recurring Locations and Organisations;
• complex fictional worlds;
• long timelines;
• non-linear narrative structures;
• changing terminology;
• repeated factual information;
• continuity across many Chapters;
• extensive annotations;
• research and citations;
• indexes and glossaries;
• detailed front and back matter;
• multi-book projects;
• publication layout.

You can ignore the systems you do not need.

But when a project becomes complicated enough to require them, they are already part of the same environment.