Considerations when creating a template

If the desired device configuration differs significantly (firmware, features, file structure), creating a net new template from a model device is usually more efficient than modifying an existing device configuration.

If the goal is to establish or enforce a standardized baseline, a model device–driven workflow is preferred. If only minor variations are needed, copying an existing device configuration is faster.

If an existing device configuration is well-tested and validated, it’s a strong candidate for reuse. If there’s any uncertainty (for example, configuration drift, unknown changes), starting from a model device reduces risk.

Copying an existing template is typically quicker and requires less setup. Creating a net new template may take longer but results in a cleaner, more controlled baseline.

Templates that will be widely reused or maintained long-term benefit from being built from a clean model device. One-off or short-lived use cases may justify copying and modifying an existing configuration.

Differences between environments (e.g., development, staging, production, or customer-specific deployments) may require either a fresh model device or a derivative of an existing device configuration.

In more regulated or controlled environments, creating a template from a validated model device may be required to ensure traceability and consistency.

If minimizing risk is critical, customers tend to favor creating a net new template from a known-good model device. If speed is prioritized and risk is lower, copying an existing configuration is often acceptable.