At Peripass, our mission is clear: to make yard operations fully autonomous.
We provide powerful automation tools that streamline every flow on your yard, ensuring that processes run smoothly with minimal human intervention. In an autonomous yard, people step in only when something deviates from the expected — and that’s where the Exception Monitor comes in.
Disruptions are inevitable, but they shouldn’t catch you off guard. The Exception Monitor acts as your early warning system, instantly alerting you when something goes off track. This allows you to respond quickly, reduce downtime, and maintain operational efficiency — even when the unexpected happens.
When you need this
Use the Exception Monitor whenever you want to be proactively notified about delays or bottlenecks in your yard process, such as:
Call-off delays: Drivers take too long to respond to a call-off message.
Extended visitor stays: Visitors are spending more time in the yard than expected.
Dispatch delays: Drivers are waiting too long before being dispatched.
In short: any time a driver or visitor is stuck in the process, the Exception Monitor helps you identify and manage it quickly.
Main idea
Exception scenarios – Visitors are automatically flagged when messages fail to deliver or when they don’t arrive onsite within the configured timeframe. You can also define your own exception rules to suit your operational needs
Stay alerted – Flagged visitors are clearly highlighted across Peripass, ensuring visibility for your team at every step.
Take action instantly – Real-time notifications help you intervene, communicate, or escalate quickly to keep operations running smoothly.
Automatic resolution – As soon as the visitor progresses through the process, the flag clears automatically—no manual follow-up needed.
How does it work
Exception scenarios
Failed Message Delivery
If a text message or voice call to a visitor fails, the visitor will be flagged with an exception indicating that action is required to unblock the visitor.
A visitor is only flagged when we receive an explicit delivery failure from our text messaging provider. If no feedback is received, the system will not flag the visitor. Instead, we rely on the “not onsite after 15 minutes” rule to cover this scenario
The flag is automatically removed once the visitor’s status changes to onsite.
You cannot disable the message delivery failure flag. However, you can turn off notifications for it individually in your My Notifications settings.
Visitor not onsite after 15 minutes
When a visitor is called off but has not entered the site within 15 minutes, they will be highlighted automatically.
This rule only applies to customers using Access Control Systems or PIN-Point solutions, because these systems show us when a driver actually enters the site — for example, when they enter a PIN code at the barrier or their license plate is read by a camera.
👉 You can adjust the delay to your preferred time (see Configuration) or disable the rule entirely — either globally or for specific profiles.
Custom Exception Scenarios
In addition to these default exception scenarios, you can also configure your own rules. For example, you might flag a visitor if they have been waiting for dispatch for more than 30 minutes.
Flagged visitors are highlighted
No matter where you work — in the visitor list, the dispatch dashboard, or visitor details — flagged visitors are clearly highlighted across the entire system.
A visitor flagged on a yard location is highlighted with a black border for easy identification.
👉 Pro-tip: the flag icon in the top menu bar, totals your flags and takes you directly to the flagged visitor list.
Get notified when a visitor is flagged
As soon as a visitor is flagged, every user (with permissions to see this visitor) will be notified in app to take immediate action.
If you prefer not to receive these alerts, you can disable them in your notification settings.
Flags resolve automatically
Flags on visitors are now automatically removed in two cases:
Status update – when the visitor’s status changes and they move forward in the process.
Location change – for example, when the visitor transitions to Onsite.
In both situations, the system detects that the visitor is no longer stuck in the process and clears the flags accordingly.
How to configure
How to Update the 'Visitor Dispatched but Not Arrived Yet' Flag
Update the Flag Name or Resolution Description
Navigate to ⚙️ Configuration > Exception Flag Types
Find and Edit the flag titled 'Visitor dispatched but not arrived yet'
Update the flage name or resolution description as needed
Click Save
Update the Exception Logic
You can adjust the scope or time delay of the trigger as follows:
Select the profile for which the rule applies (by default, it applies to all profiles).
Click Edit.
Open the Exceptions tab.
Edit the trigger: ‘Status checked in for more than 15 minutes’.
Choose one of the following options:
Option 1: Disable the trigger.
Option 2: Change the delay duration.
Option 3: Update the scope (profiles / sites).
Click Save to apply your changes.
Define a custom exception scenario
Go to ⚙️ Configuration > Profiles > Edit > Exceptions tab
The Exceptions tab lists all automations linked to the selected profile that contain a flag action.
From this tab, you can create new Exception Triggers.
Scope of Exception Triggers
When you create an Exception Trigger within a profile, you can extend its scope to other profiles.
Once created, the trigger will automatically appear in the Exceptions tab of every profile included in the scope.
Using Flags
You can either reuse an existing flag or create a new one.
We recommend writing actionable flag descriptions. This helps users understand how to resolve the exception scenario when a flag is raised.
Managing Flags
Navigate to ⚙️ Configuration > Exception Flag Types
Find and Edit the flag titled 'Visitor dispatched but not arrived yet'
Update the icon, flag name or resolve description as needed - Note that you can add translations for every language supported in the portal
Click Save
Manage your notifications
Notifications can be enabled/disabled per flag type.
Click your username
Select "My Notification"
Update your Preferences
More information
Microsoft Teams Integration
Coming soon: When a visitor is flagged, you’ll be able to post a message directly to a Microsoft Teams channel using the Cloud API call action.
Won't do / limitations
The following capabilities are not yet available, but are planned for future releases:
⚙️ Use flags with triggers other than “Time in Status.”
🔄 Combine “Time in Status” triggers with actions other than “Set flag.”
This will eventually enable automated escalation flows, for example:After 15 minutes: automatically resend text message
After 25 minutes: automatically call the driver
After 35 minutes: flag for manual follow-up
💬 Send flagged visitor alerts directly to Microsoft Teams channels.s