Define routes, checkpoints and required observations, then review visits and exceptions in chronological context.
The capabilities presented are part of the MeridCore™ offering and are configured for each organization’s context, permissions and processes.
The module supports teams that patrol sites and perform checks at specific locations. Each patrol has its own progress, contributors and route version, even when several patrols occur during one shift.
Define required, optional or conditional checkpoints, strict or flexible ordering, visit windows and instructions. Updating a template does not rewrite patrols already in progress.
Use native NFC or QR fallback according to device capabilities. A checkpoint can require an answer, photo or action. Each event retains its timestamp, author and scanning method.
Download the authorized route before losing connectivity. Scans and media await synchronization; provisional validations, rejections and conflicts remain visible when the connection returns.
Review missed checkpoints, out-of-sequence visits or replaced tags. Preserve the raw event, explanation and supervisor decision, then link anomalies to reports and follow-up actions.
During a prepared patrol, an officer scans a QR checkpoint and notices a leak. The observation and photo are recorded offline. After synchronization, the supervisor can review the visit, initiate follow-up and verify resolution.
Distinguish visited checkpoints, missed mandatory points, incomplete patrols and evidence awaiting synchronization. Reports preserve the actual sequence of events.
A scan alone is neither infallible evidence nor an automatic finding of misconduct. A patrol does not replace a compliance inspection. Continuous GPS tracking is excluded.
Describe your current process, the people involved and the expected result. An initial discussion helps confirm the relevant scope.
Request a demo