[{"data":1,"prerenderedAt":112},["ShallowReactive",2],{"changelog-\u002Fchangelog\u002Fkeep-the-template-edits-you-make-on-site":3},{"id":4,"title":5,"body":6,"date":92,"description":93,"emailSummary":94,"extension":95,"highlights":96,"image":102,"imageWidth":102,"meta":103,"navigation":104,"path":105,"seo":106,"stem":107,"tags":108,"__hash__":111},"changelog\u002Fchangelog\u002F0014.keep-the-template-edits-you-make-on-site.md","Keep the template edits you make on site",{"type":7,"value":8,"toc":85},"minimark",[9,13,16,21,24,46,49,61,65,72,75,79,82],[10,11,12],"p",{},"Editing a template while you're standing in the inspection has always worked.\nRename a field whose label never quite fit, drop one you never fill in, add a\nphoto field for the attic hatch, drag the sections into the order you actually\nwalk the house.",[10,14,15],{},"What didn't work was keeping any of it. Those edits lived on that one\ninspection. The next job started from the same unchanged template, and the only\nway to make an improvement permanent was to remember it and re-make it by hand\nin the template editor.",[17,18,20],"h2",{"id":19},"the-template-step","The Template step",[10,22,23],{},"Inspections where you changed something now get a fifth step in the journey,\nafter Deliver. It lists what you changed, one line per change:",[25,26,27,31,34,37,40,43],"ul",{},[28,29,30],"li",{},"Renamed \"Type\" to \"Roof Type\"",[28,32,33],{},"Made \"Roof Type\" required",[28,35,36],{},"Added the field \"Attic photos\"",[28,38,39],{},"Removed the field \"Age\"",[28,41,42],{},"Edited the \"Roof\" description",[28,44,45],{},"Reordered the subsections in \"Exterior\"",[10,47,48],{},"Each has its own checkbox, because most inspections mix the two kinds of edit.\nThe renamed field was a real improvement worth keeping. The extra text field\nyou added to explain something specific to that house was not. Tick the first,\nleave the second.",[10,50,51,52,56,57,60],{},"Then pick where they go: ",[53,54,55],"strong",{},"update the template this inspection came from",", or\n",[53,58,59],{},"save as a new template"," — useful when you've quietly evolved a variant and\nwould rather have both.",[17,62,64],{"id":63},"when-your-template-has-moved-on","When your template has moved on",[10,66,67,68,71],{},"Eave compares against your template as it is right now, not as it was when the\ninspection started. So if you renamed a field on site, and meanwhile you (or\nsomeone else on your team) renamed the same field in the template editor,\nthat's a ",[53,69,70],{},"conflict",". It's shown with both versions and left unchecked, so\napplying it is a deliberate choice rather than something that happens to your\nteammate's work by accident. Everything else in the list stays clean and\nselectable.",[10,73,74],{},"Changes your template already has simply don't appear. Apply half the list\ntoday and come back later: the applied half is gone, the rest is still waiting.",[17,76,78],{"id":77},"worth-knowing","Worth knowing",[10,80,81],{},"This never touches the report you delivered. It only ever writes to templates —\nyour client's report is exactly what you published.",[10,83,84],{},"Inspections created before this shipped don't have a record of which template\nthey came from, so instead of guessing, the step asks you to pick the\ndestination template yourself.",{"title":86,"searchDepth":87,"depth":87,"links":88},"",2,[89,90,91],{"id":19,"depth":87,"text":20},{"id":63,"depth":87,"text":64},{"id":77,"depth":87,"text":78},"2026-08-25","A new Template step at the end of an inspection collects every change you made to the template while filling it out, and lets you fold the ones worth keeping into your template for next time.","You can already edit a template while you're filling out an inspection — rename a field that never made sense, delete one you never use, add a photo field for the attic, drag a section into the order you actually work in. Until now all of that stayed inside the one inspection. The next job started from the same unchanged template, and the only way to make an improvement stick was to remember it and re-make it by hand in the template editor. There's now a Template step at the end of the inspection journey that closes that loop. It appears only on inspections where you actually changed something, and it lists every change as its own line — 'Renamed Type to Roof Type', 'Added the field Attic photos', 'Reordered the subsections in Exterior' — with a checkbox each, so you keep the two that were real improvements and leave the three that were one-off notes for that house. Apply them to the template the inspection came from, or save the whole set as a brand-new template. Eave also checks your template as it stands right now, not as it was when you started the inspection: if you or a teammate has edited the same field since, that change is flagged as a conflict, shown with both versions, and left unchecked so you decide rather than silently overwriting their work. Anything already in your template quietly drops off the list, so the step empties itself out as you go. Your report is never touched — this only ever changes templates.","md",[97,98,99,100,101],"A Template step that appears when you edited the template on the fly","Every change listed separately, with a checkbox each","Apply to the source template, or save the set as a new one","Conflicts flagged with both versions when the template has changed since","Changes already in your template drop off the list automatically",null,{},true,"\u002Fchangelog\u002Fkeep-the-template-edits-you-make-on-site",{"title":5,"description":93},"changelog\u002F0014.keep-the-template-edits-you-make-on-site",[109,110],"Templates","Inspections","XftMv1DhLEkZDt89kXWe2VAr9qN-nofBxbsrVyZ6J2M",1787848600243]