How Should I Use LoreVia After Uploading a Draft?

Use the first session after an upload to orient yourself, not to chase every possible finding. Confirm that the manuscript and chapters were processed as expected, review the major cast and structural map, then bring one real revision question. Verify the answer against the cited chapters before changing the draft.

Confirm the source before interpreting it

Check that you uploaded the intended version. Compare the manuscript title, chapter count, opening, and ending with your working file. If chapters were split incorrectly or front matter became a chapter, address that before treating the analysis as reliable.

Processing creates a view of the submitted text. It does not know that a later file on your laptop contains the ending you prefer. Record the version date in your revision notes.

Take a structural tour

Begin with three questions:

1. Are the chapters and their order recognizable?
2. Are the central characters present and named sensibly?
3. Do the broad relationships, timeline points, and locations resemble the book you wrote?

This is a calibration pass. If an alias appears as a separate character or an unnamed role is misidentified, note it. Do not mistake extraction noise for a flaw in the novel.

Resist the impulse to inspect every minor name. Start with people and facts that affect multiple chapters.

Choose one editorial problem

Turn a concern into a bounded question. Instead of “Is my novel consistent?” ask “When does Nila learn that the western gate is sealed, and do any earlier actions assume that knowledge?” Instead of “Does the romance work?” ask “Which scenes change trust between Nila and Corren, and what does each one cost?”

Specific questions produce evidence you can inspect. They also keep the session connected to the revision you are prepared to make.

Follow the evidence into the chapter

When an answer identifies a scene, open the cited chapter and read around the passage. Confirm who is speaking, whether the statement is true in context, and whether a later reveal changes its meaning.

Suppose the answer says Corren knew about the gate in chapter six. The line may actually be another character’s suspicion. Or Corren may hear a rumour without believing it. The difference matters. Chapter grounding gets you to the relevant evidence quickly; close reading establishes canon.

Keep a small verification label: confirmed, ambiguous, intentional, false positive, or needs broader review.

Turn confirmed findings into edits

For each accepted issue, record:

• the chapter and scene;
• the observed problem;
• the canon or intended effect;
• the smallest edit likely to solve it;
• other scenes that may depend on the change.

Prioritize by consequence. A knowledge error that breaks the climax comes before a minor appearance inconsistency. Limit the active queue so you can complete and verify changes.

After editing the manuscript, mark the finding resolved in your notes. If the change is structural, revisit downstream evidence and consider processing the new version when the pass is complete.

Use views as lenses, not obligations

Character, relationship, timeline, chapter, and advisor views answer different questions. You do not have to inspect all of them during every session. Choose the lens that matches the current pass.

During a character pass, follow one person across the book. During a continuity pass, compare dates, objects, injuries, and knowledge. During beta preparation, look for dropped promises and confusing handoffs. This keeps the interface subordinate to the edit.

Common mistakes

Do not start by asking for a verdict on the whole novel. Broad answers are harder to verify and act upon.

Do not edit from a summary alone. Open the chapter evidence, especially for high-impact claims.

Do not confuse extracted entities with editorial importance. A frequently named guard may matter less than a letter mentioned twice.

Do not rerun analysis after every sentence. Finish a coherent pass, save a stable manuscript version, then refresh the project.

Do not preserve old findings without their source version. A correct warning can become obsolete after a rewrite.

A productive first outcome

Your first LoreVia session has succeeded when you understand the project’s shape, trust where the important evidence came from, and leave with a short queue of verified edits. The purpose is not to explore every screen. It is to return to the manuscript with less uncertainty.

The full cadence is in How to Use LoreVia During a Revision Week, with a repeatable weekly version in How Do I Use LoreVia in a Weekly Revision Routine?.

A useful stopping point

End the session while the queue is still comprehensible. Save the cited evidence and the decision you made, then close the analysis view and edit the manuscript itself. The product is useful when it shortens that return to the page.

That is the work.

Keep the manuscript version beside every finding you decide to retain.

Broader guide: How to Use LoreVia During a Real Revision Week