Template fields are the named variables your Guide templates reference — text blocks like "recap from last meeting" or an image like "household photo" that a template inserts by name instead of hard-coding. You define the fields once at the firm level; each client gets their own values for each field.
The Template Fields panel on Office > Notes is where you edit a single client's values in one place, instead of hunting for them inside the Guide editor. It's also where you see the edit history for each field.
Where to find it
Open any client, click Office in the sidebar, then Notes. The page has two rows:
Top row — Notes on the left, Account Notes on the right (the two editorial surfaces for the client).
Bottom row — a wide Template Fields panel with every field the firm has defined.
If you haven't defined any fields yet, you'll see "No template fields defined yet." Add fields from the firm-level template settings and they'll show up here for every client.
What's in each field card
Each card has:
Field name and a small type tag (TEXT or IMAGE).
The current value — a rich text editor for text fields, an image thumbnail with upload/replace controls for image fields.
View History button in the top-right. Disabled (grayed out) when there are no previous versions yet.
Text fields are listed first, then image fields.
Editing a value
Click into the text editor and type. Or drag a new image onto the image uploader. Changes save automatically — there's no save button.
The value you enter here is what every Guide template uses for this client. Edit it, open any Guide that references the field, and the new value is there.
Viewing history
Click View History on a field. A modal opens showing previous values, newest first. Each entry has a timestamp and the value as of that edit. Text entries show the rendered rich text; image entries show a thumbnail.
The modal shows prior values only — the current one you see in the panel isn't listed again. If there's only one value on file (the current one), View History is disabled.
The 30-second coalesce rule
If you edit a field multiple times within 30 seconds, Kerdora rolls those edits into a single history entry instead of logging every keystroke. So fixing a typo, saving, then rewriting a sentence two seconds later shows up as one history row with your final text.
If you pause longer than 30 seconds between edits, the next save starts a new history entry. This keeps the timeline readable — you'll see the distinct "versions" of the field instead of a noise log.
When to use this vs. editing inside a Guide
Template Fields panel (Office > Notes) — fastest when you want to set or update values outside the context of a specific Guide. Ideal for prepping a client before a meeting: run through the panel, update the fields that changed, and every Guide that uses them picks up the new values.
Guide editor — best when you're actively building or tweaking a Guide and want to see the value in context. You can still edit template field values inline inside the Guide, and the change lands in the same place (and creates the same history entry).
Either way, changes are client-specific. Editing a template field value on one client doesn't affect any other client.