# Semantic changes > Differences between two versions shown at story structure level — this dialogue line rewritten, that scene moved — instead of a noisy character-by-character redline. Also known as structural changes, scene-level changes ## In practice Semantic changes describe differences the way a room already talks: this dialogue line rewrote, that scene moved, this slugline shifted — not a fog of character-level redlines. Because Plot stores screenplays as structured elements, comparisons can stay readable when an entire act relocates overnight. Use them after notes, after a skill pass, and before you decide an experiment won. A moved scene should look like a moved scene, not thousands of tiny inserts that hide the real decision. That clarity is what makes review of proposed edits feel like story work instead of proofreading noise under time pressure. When you preview an incorporate, you read the same semantic changes before the whole draft lands. Skill markup goes change by change: accept what should land, reject what should not. Nothing in a skill pass applies without your say-so, and the change view preserves your editorial control while still moving fast when a deadline is real. [See change tracking](https://www.inkwell.software/features) ## Common questions ### Why not just use Track Changes like a word processor? Word-processor marks are built for continuous prose. Screenplays are element trees — cues, dialogue, sluglines — so scene moves should not look like a thousand tiny edits. ### Where will I see semantic changes in practice? When comparing save points or draft lines, reviewing skill suggestions, and checking what an incorporate would bring across before you confirm the landing. ### Do semantic changes replace reading the pages? No. They focus attention on what moved so you can re-read the right scenes. Structure-aware diffs are a map, not a substitute for taste. ### Can collaborators review changes together? Yes — comments and presence stay on the draft while you inspect what moved. On Team, roles help keep who can accept structural landings clear. ## Related terms - [Save point](https://www.inkwell.software/glossary/save-point): A named, unchanging snapshot of your draft at a moment you choose — “Table read,” “Before studio notes.” Unlike autosave, it never quietly overwrites itself, so you can always return to exactly that version. - [Draft line](https://www.inkwell.software/glossary/draft-line): A parallel version of the same document — explore an alternate ending or rebuild an act without overwriting the draft you may still need, then land the winning line when you decide. - [Incorporate](https://www.inkwell.software/glossary/incorporate): Land a winning draft line onto the line you keep. Today the whole document moves. For one scene, use a take, or Agent Mode for a scene or an act; incorporate selected scenes is how the land is planned to get finer. - [AI skill](https://www.inkwell.software/glossary/ai-skill): A structured AI pass that reads your document and proposes edits or findings in place — dialogue polish, continuity flags, coverage — as reviewable markup you accept or reject. --- Canonical page: