Guide contents
On this page
Main flow · Trigger
Trigger
An event, signal or condition that starts the process.
Three ways to start
A time-based trigger is linked to an agreed schedule: access rights might be reviewed quarterly. An event-based trigger responds to an observation, such as a service level breach. A demand-based trigger is a request or order, such as a business change request.
Starting requires ownership
Alongside the starting condition, record who receives the situation and when processing begins. If an observation remains in a shared mailbox without an owner, the process has not truly started. Distinguish an individual observation from the actual starting condition: not every deviation necessarily triggers the same handling procedure.
The trigger explains why work starts now. The input explains what the work processes.
Practical example
A service threshold breach
A critical system's response time exceeds the agreed threshold for three consecutive days. In this example, the service management team starts a capacity investigation and records the observation time and responsible person. The three-day limit is an illustrative starting condition, not a general requirement.
Include in your process description
- What exact event or time starts the work?
- Who detects the trigger and takes responsibility?
- Where are the start time and reason for starting recorded?
- How is an unclear starting condition resolved?
Connections to other components
Based on the Generic Process Model materials. Questions and practical guidance have been structured for reading on the web. Sources and clarifications.