---
id: KB-TL-005
url: https://app.codecontract.io/help/trackline/duplicating-a-template
idioma: en
categoria: trackline
subcategoria: plantillas
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-TL-001, KB-TL-006]
citadoPor: [KB-TL-006, KB-TL-013, KB-TL-018, KB-CF-004]
enLaApp: https://app.codecontract.io/trackline/schemas
---

# Duplicating a template

_Reuse a process that already works without touching the original._

**Responde a:** duplicate a process in trackline · copy an existing template · make a variant of a process · reuse a schema for another client

When you need a process almost identical to one you already have — the same supplier onboarding but for another country, or another product family — there is no need to rebuild it: duplicate it and edit the copy.

**En corto**

- The copy is independent: editing it does not touch the original.
- Running cases on the original are unaffected.
- You can rename it, add phases and remove requests freely.

## How to do it

1. **Go to Trackline → Schemas.**
2. **On the schema's row, open the three-dot menu.**
3. **Click "Duplicate".**
4. **Rename the copy to something that tells it apart from the original.**

## When to duplicate and when not to

| Situation | What to do |
| --- | --- |
| A variant by sector, country or product family | Duplicate and edit |
| The process has changed for everyone | Edit the original, do not duplicate |
| You want to try a change safely | Duplicate, test on the copy, then decide |
| One client asks for something different | Add it to their running case, do not create a schema |

_One schema per client is the sign something went wrong: the template is what repeats._

> [!WARNING]
> Duplicating copies the structure, not the cases. Anything already running keeps the version it was created with.

**Does the copy inherit changes to the original?**

No. From the moment you duplicate, they are independent.

**Can I duplicate a copy?**

Yes, as many times as you like.

**Are participants copied too?**

The structure of who is asked for what is copied; the specific contacts are chosen when you run it.

## Ejemplos

**A food business needs the same supplier onboarding but asking importers for a certificate of origin.**

- Duplicates "Supplier onboarding"
- Renames it to "Supplier onboarding — imports"
- Adds the certificate of origin request

→ Two processes side by side, and the original keeps working for domestic suppliers.

**The good template is edited for a one-off variant.**

- Duplicates it and edits the copy

→ The original still serves the usual case.

**There are four copies with the same name.**

- Names each copy after the case it solves

→ Nobody launches from the wrong one.

**An improvement is applied to only one copy.**

- Decides which is the main one and updates the rest

→ Variants do not fall behind for good.

**It is duplicated for a client who asks for one extra document.**

- Adds only that document in the copy

→ The difference is visible at a glance.

**Unused copies pile up.**

- Archives those not launched in months

→ The template list stays readable.