Skip to main content

Creating a Guide Template from Scratch

Written by Taylor Stewart

Create a practice Guide template when you want a reusable client-deliverable structure. Open Templates from the practice navigation and choose New Template. The New Template dialog offers Build with Dora and Start blank. To copy an existing practice template, use its separate Duplicate action in the template list.

Choose the right starting point

  • Start blank when the structure is simple or deliberately different.

  • Duplicate an existing template from the list when you want to preserve a proven layout and change only the purpose or detail.

  • Edit a copy of a Kerdora template when the built-in layout is close but should become practice-owned and editable.

  • Build with Dora when you want an initial component arrangement from a brief. Review every proposed component and setting.

Name the template for its client conversation, such as Annual Review, Retirement Check-In, or Tax Planning. Avoid names that only make sense internally.

Build the layout

  1. Open the new template in the editor.

  2. Search or browse the component library.

  3. Add a component to a row or create a new row.

  4. Arrange related components together.

  5. Open settings for components that support configuration.

  6. Use the household preview selector to test the layout with real data.

  7. Wait for the autosave state to complete, then return to the template list and reopen the template to verify a material change.

Use full-width components for information that needs horizontal space. Use side-by-side components only when the comparison remains readable. Dividers and spacers can establish hierarchy, but they should not compensate for an unclear sequence.

Configure data scope

Component settings can control fields, status, selected Goals, planning scope, display mode, and other behavior. Investment components can often be scoped to the full portfolio or a more specific goal, horizon, or tax status. Tax components may depend on a selected scenario when used for an actual client.

Practice templates do not know every household's final data. Preview with more than one representative household and watch for empty states, long labels, and missing planning modules.

Add reusable explanation

Use Template Text and Template Image for content that should remain consistent across reusable templates, such as a process explanation or disclosure. Link them to a template field so one practice-level update can flow to every use.

Use Custom Text and Custom Image for client-owned, one-off content. Do not put client-specific facts into a reusable practice field.

Plan Notes and General Notes can bring selected existing notes into a Guide. Confirm the note is eligible and intentionally client-facing before adding it.

Set visibility and defaults

Templates do not become client-visible solely because they exist. From the template list, review visibility for the households that should receive the template. Use the new-client default controls only when the template should be included for future households.

Changes to practice-wide visibility or defaults can affect many clients. Review the selected households and preview before applying broad changes.

Quality check

Before using the template:

  • confirm the first section explains the purpose;

  • remove duplicate components;

  • verify component settings and headings;

  • test households with different data completeness;

  • confirm no internal instruction appears in client content;

  • preview desktop and narrow layouts when possible; and

  • confirm Changes and Tasks appear only where intended.

The template should reduce repeated work without turning every client conversation into the same generic report.

Practice-template edits autosave; there is no separate Save button. Do not close the editor while it is still showing a pending save state.

Did this answer your question?