Lore & LilacSaved views
Your own tables, always in step with the book
Make a table of exactly what you need to see — every character by how often they appear, every scene without a point of view, every detail whose source passage changed — and save it. A view stores only your choices; the rows are worked out from the live records each time you open it, so it can't drift out of date.
No AI involved Views are built from records the studio already keeps. Nothing is sent to an AI provider.
What you get
Saved views, in detail
- Three kinds of view: story-bible records, scenes and details
- Columns you choose, such as appearances, scenes appeared in and last mentioned (records); chapter, POV, status, words, story date and plotlines (scenes); truth, status and citation state, including “Source changed — review” (details)
- Profile fields from your story bible as columns, for example a character's Role
- Filters: is, is not, contains, any of, ranges for numbers and dates, is empty and isn't empty — matching all of them or any
- Sort by several columns, and group by one, for example scenes grouped by chapter
- Click a row to open its record or scene
- Change a few fields right in the table: a scene's status and POV, and a detail's status and truth
- Export CSV of the whole table
- Starter templates: “Characters by appearances”, “Scenes without POV”, “Details that need review”, “Unfinished scenes by chapter”
- Find Views in the Story bible and Plan menus
How it works
In practice
Start from a template or a blank table
Choose what the rows are — records, scenes or details — or begin with a starter view such as “Scenes without POV”.
Choose columns and filters
Add the columns you care about and narrow the rows with filters. Every control works from the keyboard.
Sort and group
Click a heading to sort; Shift-click to add another key. Group by chapter, kind or status to see the book in sections.
Save it and come back
The view keeps your choices, not a copy of the data. Next time you open it, the rows reflect the book as it is now.
Where we draw the line
What it never does
- Keep a copy of your records that can go stale — rows are always computed from the live book
- Change anything except the few fields you edit in the table yourself
- Send anything to an AI provider
These follow from our commitments. The studio never writes, suggests or rewrites your prose, anywhere.
Before you start
Questions writers ask
Is a view a copy of my story bible?
No. A view stores only its settings: kind, columns, filters, sort and grouping. Each time you open it, the rows are worked out from the current records, scenes and details, so a view never disagrees with the book.
What can I edit from a view?
A scene's status and point-of-view character, and a detail's status and truth scope — through the same saves the rest of the studio uses. Everything else opens the record or scene, where you edit it as usual.
How big can a view be?
A view reads up to 5,000 rows from a book; in the rare book with more, it says so and covers the first ones. Each book can hold up to 100 saved views.
Can I take a view into a spreadsheet?
Yes. Export CSV gives you the whole table — every matching row, with the columns you chose — ready for any spreadsheet app.
Can my co-author use views?
Yes. Views belong to the book, so a co-author can open, make and change them too.
Try saved views on your own draft
Import your draft from Word, Scrivener, RTF, EPUB or Markdown, or start on a blank page. The 14-day trial needs no card, and your book is exportable from the first word.