Editing a template while you're standing in the inspection has always worked. Rename a field whose label never quite fit, drop one you never fill in, add a photo field for the attic hatch, drag the sections into the order you actually walk the house.
What didn't work was keeping any of it. Those edits lived on that one inspection. The next job started from the same unchanged template, and the only way to make an improvement permanent was to remember it and re-make it by hand in the template editor.
Inspections where you changed something now get a fifth step in the journey, after Deliver. It lists what you changed, one line per change:
Each has its own checkbox, because most inspections mix the two kinds of edit. The renamed field was a real improvement worth keeping. The extra text field you added to explain something specific to that house was not. Tick the first, leave the second.
Then pick where they go: update the template this inspection came from, or save as a new template — useful when you've quietly evolved a variant and would rather have both.
Eave compares against your template as it is right now, not as it was when the inspection started. So if you renamed a field on site, and meanwhile you (or someone else on your team) renamed the same field in the template editor, that's a conflict. It's shown with both versions and left unchecked, so applying it is a deliberate choice rather than something that happens to your teammate's work by accident. Everything else in the list stays clean and selectable.
Changes your template already has simply don't appear. Apply half the list today and come back later: the applied half is gone, the rest is still waiting.
This never touches the report you delivered. It only ever writes to templates — your client's report is exactly what you published.
Inspections created before this shipped don't have a record of which template they came from, so instead of guessing, the step asks you to pick the destination template yourself.