ºÚÁϳԹÏÍø

Purpose of demo processes

Demo processes are used during training to:

• show how process mapping works
• demonstrate ShiftX features
• let people practise safely

They should never be treated as real processes.

Naming demo processes

Use clear names so demo processes are easy to spot.

Start the process name with Test.

• example: Test_Student Registration

Outside training, learners should use their own School, Unit or project name instead of Test.

Tagging demo processes

Always apply the Test tag to demo processes as this:

• clearly shows the process is not live
• makes it easy to filter and find demo content

For non‑demo work, make sure processes are also tagged with the correct School or Unit.

Cleaning up after training

This is an important step that ensures no demo processes are left on the system.

Leaving demo processes behind:

• makes it harder to find approved processes
• reduces trust in the process library
• can affect analysis and reporting

Demo processes may include linked roles, systems or information. Removing them keeps reports accurate.

After a training session always:

• delete all demo processes created for the session
• check that no processes with the Test tag remain