Learn how to create a patrol task, assign checkpoint actions, set subtasks, and prepare a guard’s scheduled patrol inside Trinity Guard®.
In Trinity Guard®, a task is the actual patrol work that a guard must complete during a scheduled shift. The task can be created with a map, connected to an existing checkpoint template, and divided into subtasks for individual checkpoint actions.
The setup order matters. First, add the site. Then add checkpoints. After that, add the guard user and create the shift. Once the shift exists, you can add the patrol task that belongs inside that working period.
In this guide, the task is created for the NorthGate Logistics Site – Dallas, TX test environment. The task name is NorthGate Logistics Patrol, the task starts at 2026-06-22 10:15, and the assigned checkpoint template is NorthGate Logistics Patrol Checkpoints.
The task includes checkpoint subtasks such as Main Gate Check, Warehouse Entrance Check, Loading Area Check, and East Fence Line Check.
The Add Task step belongs after Add Shift in the onboarding flow. This is important because a patrol task should be scheduled inside a real guard shift.
Follow the real Add Task workflow inside the Trinity Guard dashboard. Click any step to view the related screen.
After Add Shift is completed, the onboarding checklist shows Add Task as the next setup step. Click Add Task to create the first patrol task for the guard’s scheduled shift.
After the site, checkpoints, user, and shift are created, the onboarding panel shows the next operational step: Add Task.
Click Add Task in the onboarding checklist. This opens the task creation page connected to the selected guard and shift context.
The order is intentional. The shift creates the working time window, and the task defines what the guard must complete during that window.
The Add Task page opens with the Task Type field, task name, task description, task start time, and map-based preview area.
If no saved task template exists yet, the template selector will show that there is no task template to display. That is normal for the first setup.
For this guide, use With Map, because the task will be connected to checkpoint locations.
Use a task name that clearly describes the patrol route. In this example, the task name is:
NorthGate Logistics Patrol
The description explains the purpose of the task:
Regular patrol task for the NorthGate Logistics Site, including the assigned GPS checkpoints.
Then enter a start time that falls inside the assigned shift. In this example, the task starts at 2026-06-22 10:15.
In the Select checkpoints (template) field, choose the checkpoint route that belongs to the site.
For this example, the selected checkpoint template is:
NorthGate Logistics Patrol Checkpoints
The map preview shows the assigned checkpoint points. These points become the locations where the guard must complete the task actions.
Select Point 1, choose the subtask type, and enter the subtask name.
For the first checkpoint, use:
Main Gate Check
In the screenshot, the subtask type is Stay in point. This is useful when the guard should remain at a location for a defined period before the point is considered completed.
Continue adding checkpoint actions for the remaining points on the route.
In this guide, the additional subtask names are:
Warehouse Entrance Check, Loading Area Check, and East Fence Line Check.
You can use different subtask types depending on what the guard must do at the checkpoint. For example, Touch Point can be used when the guard only needs to confirm the point, while Stay in point is used when a duration is required.
Before saving, review the task preview on the right side of the screen.
The preview should show the task name, task description, map, start status, and the added subtasks.
If more subtasks are added than fit in the preview area, the remaining items can be expanded with the Show more link.
After the subtasks are added, click the green Add task button.
You can also check Save as task template if this patrol structure should be reused later.
This is useful for recurring patrols where the same route, checkpoint actions, and subtask structure will be used again.
After saving, Trinity Guard® shows a confirmation message: Task added successfully.
The confirmation proves that the task has been created and connected to the selected guard shift.
From the confirmation window, you can open the guard’s tasks or close the message.
The created task card shows the task name, description, map preview, subtasks, and current state.
In this example, the task appears as Not started. That is expected before the guard begins the patrol.
The card also includes operational actions such as Edit task, Delete task, and Copy Task.
After the task is created, the onboarding checklist marks Add Task as completed.
This confirms that the site now has a user, a shift, checkpoints, and a patrol task connected to the shift.
From here, you can continue with QR code setup or start testing the patrol flow with the guard mobile app.
These statements summarize the logic behind task setup in Trinity Guard®.
A shift only tells the system when a guard is scheduled to work. A task tells the guard what must be completed during that working period.
With a map-based task, administrators can connect patrol work to real checkpoint locations. This makes the patrol easier to verify, easier to review, and easier to explain to clients.
Trinity Guard® separates scheduling from patrol verification. The shift defines the working window. The task defines the required activity. The checkpoint confirms the guard reached the required location. The subtask defines the action expected at that location.
This structure helps security companies build cleaner documentation, stronger accountability, and better client-facing proof of patrol activity.
A task is the patrol assignment that tells the guard what must be completed during a scheduled shift.
No. A shift defines when the guard is on duty. A task defines what patrol activity the guard must complete during that shift.
The recommended onboarding flow is to add the user, add the shift, and then add the task. This keeps the patrol task connected to a real working time window.
With Map means the task is connected to checkpoint locations. The administrator can select a checkpoint template and create subtasks for the points on the map.
A checkpoint template is a saved set of checkpoint points for a site. It lets the administrator reuse the same patrol route structure when creating a task.
A subtask defines what the guard must do at a selected checkpoint point, such as staying at the point for a duration or touching/confirming the point.
Stay in point is a subtask type used when the guard should remain at the selected checkpoint point for a defined duration.
Touch Point is a subtask type used when the task requires the guard to confirm or touch the selected checkpoint point without a stay duration.
No. Checkpoint order is not enforced by design.
The system saves the patrol task and shows a success confirmation. The created task can then be reviewed as a Not started task before the guard begins the patrol.
Yes. If the task structure should be reused later, check Save as task template before saving the task.
After the task is added, the site has the core onboarding structure needed for a basic patrol test: site, checkpoints, user, shift, and task.
The user account identifies who performs the work. The shift defines when the guard is on duty. The patrol task defines what must be completed during that shift.
Start with one simple map-based task, review the result, and then expand the task structure after the first patrol test has been completed.
