Skip to content
  • There are no suggestions because the search field is empty.

Clone an Induction

Use this when you need to clone an existing induction so you can create a new version for a specific site, project, or any other variation without building it again from the beginning. Cloning keeps the original structure in place, making it easier to create a tailored version while saving time and reducing setup effort.

 

What this means 

  • Cloning creates a duplicate of an existing induction template.
  • The cloned induction can then be renamed and edited (questions, announcements, settings) without changing the original.

 

When you’ll use this

  • You want a site-specific induction that’s almost the same as an existing one.
  • You need a variation (for a different site, region, or workflow) but want to keep the original induction unchanged.

 

Step-by-step


     

    Common issues

    Multiple copies of inductions are confusing

    What to check

    • The cloned induction title still matches the original

    What to do

    • Rename it using a consistent naming pattern (site name, project code, or “v2”)

    Wrong scope after cloning (site specific vs company wide)

    What to check

    • Type/scope on the cloned induction

    What to do

    • Update scope so it matches the intended rollout (site-only vs across all sites)

    It looks like existing workers need to redo everything

    What to check

    • Whether you’re planning to swap a cloned induction in place of an existing one for an active site

    What to do

    • Only swap in a cloned induction if you really want everyone to complete the full induction again; otherwise, consider using the revision/request-revision workflow instead of replacing the induction. If you only want an edit to come into effect from that point onwards, update the existing induction (it will change for new inductees, but already inducted-workers won't be affected).

     

    Why this matters

    • Cloning saves time and reduces setup errors when building similar inductions.
    • Keeping the original induction unchanged avoids unintended impacts on other sites or workflows.

     

    Need help?

    If you’re not sure whether to clone vs revise an existing induction (especially on a live site), check with the foreman or GC site team before making changes, so you don’t accidentally force everyone to re-complete the induction.

    If you require any assistance or have a question, please contact our Support Team on +44 7400 977 382 or email us at support@breadcrumb.co, and we'll be happy to help.