Overview

In Valzotra, every checklist is inherently a reusable template. When you create a checklist, you define its steps once and then apply it across multiple properties. Checklist groups take this further by letting you bundle related checklists together and apply the entire set to properties at once.

How it works

Reusing checklists across properties

A single checklist definition can be applied to multiple properties:

  1. Create a checklist with the steps you need (see Creating a Checklist).
  2. Go to each property's Checklist Config tab and add a configuration pointing to that checklist.
  3. Each property configuration has its own trigger event, due offset, and default assignee -- so the same checklist can behave differently at each property.

When a checklist run is created, Valzotra copies the current steps from the checklist definition into the run. This means the run is a snapshot: if you later edit the checklist, existing runs are unaffected. Only new runs pick up the changes.

Checklist groups

Groups let you bundle multiple checklists that should run together:

  1. Navigate to Checklist Groups and click New Group.
  2. Give the group a name (e.g., "Full Turnover") and optionally set a default trigger event, due offset, and assignee role.
  3. Add checklists to the group as members. You can reorder them to control the sequence.
  4. Apply the group to a property. This creates a property checklist configuration for each member checklist, inheriting the group's settings.

You can apply a group to multiple properties at once using bulk apply. The system skips any checklists that are already configured on a property to avoid duplicates.

Propagating changes

When you update a group's settings (trigger event, due offset, assignee role, or auto-create), you can propagate those changes to all property configurations that reference the group:

  1. Edit the group's settings.
  2. Valzotra shows you how many property configurations would be affected.
  3. Click Propagate and confirm. All linked configurations are updated to match the group's new settings.

If you add a new checklist to a group, propagation also creates new configurations on properties that already use the group. If you remove a checklist from a group, the corresponding configurations are detached (orphaned) from the group but not deleted.

Editing without affecting existing runs

Changes to a checklist or group affect only future runs:

  • Adding or removing steps from a checklist only changes the steps in newly created runs.
  • Renaming a checklist updates the display name everywhere but does not alter existing run data.
  • Changing group settings and propagating updates only the property configurations, not runs that are already in progress.

Limits & requirements

  • Only owners and admins can create, edit, or delete groups and manage group members.
  • A group must have a name.
  • Each checklist can only appear once in a group (no duplicates).
  • Each checklist can only be configured once per property.
  • Deleting a group removes all its member associations but does not delete the individual checklists.
  • An active paid subscription is required for group management.

FAQ

Is there a separate "template" feature in Valzotra? No. Every checklist functions as a template. You create a checklist once and reuse it across properties. There is no distinction between a "template" and a "checklist" -- they are the same thing.

What happens if I delete a checklist that belongs to a group? The checklist is removed from the group and from all property configurations that reference it. Completed runs that used the checklist are preserved in your history.

Can I apply a group to some properties but not others? Yes. You choose which properties receive the group. You can also remove a group from a specific property without affecting other properties.

Do I need to propagate every time I change a group? No. Propagation is an explicit action you confirm. If you change a group setting but do not propagate, existing property configurations keep their current settings. Only new apply operations use the updated group settings.