FAQ
Quick answers PatrolCall is built around one operational record: requisitions, scheduling, field operations, financials, reporting, and admin governance/audit—supported by role-based access and consent-aware location posture.
Modules
Requisitions, scheduling, check-in/out, messaging/relief, inventory, financials, reports.
Governance posture
Permissions, audit logs, and reviewable change history.
Field workflows
Check-in/out and optional map/GPS workflows designed around consent posture.
General
High-level questions about who PatrolCall is for and how it fits.
Who is PatrolCall for?
PatrolCall is designed for agencies, coordinators, officers, and clients. Each role gets a view aligned to responsibilities while staying connected to one operational record.
What problem does PatrolCall solve?
PatrolCall connects request → staff → operate → invoice/report so schedules, field events, reporting, and billing align—reducing manual reconciliation and “spreadsheet drift.”
Can we start with one area and expand later?
Yes. Many teams start with staffing (requisitions and scheduling) or check-in/out, then expand into messaging/relief, inventory chain-of-custody, financials, reports, and admin governance/audit.
Modules
How the PatrolCall modules map to daily operations.
What are “requisitions” in PatrolCall?
Requisitions capture staffing requests with requirements, roles, approvals posture, and constraints. The goal is to preserve context as the request becomes staffed shifts and scheduled coverage.
How does check-in/out work?
Check-in/out captures attendance and shift activity as events, including exceptions with reasons. The intent is to support field speed while keeping records reviewable for operations and reporting.
What do you mean by “messaging + relief”?
Messaging threads keep context with the job, and relief handoffs help maintain continuity across shift changes so teams avoid “start over” moments.
What is “inventory + chain-of-custody”?
Inventory and chain-of-custody track assigned gear and custody events with an accountability posture—helpful for dispute reduction and operational consistency.
What’s included in financials?
Financials include rate tables, invoices, and exports designed to align billing outputs to schedules and operational records used to run the job.
What kinds of reports are supported?
Reporting includes operational and client-ready views, with saved reports supporting repeatable oversight. Common categories include compliance and performance reporting.
Security & posture
Questions we hear during evaluation and rollout planning.
Do you support role-based access and portals?
Yes—PatrolCall is designed with role-based views and permissions posture so agencies/admins, coordinators, officers, and clients can access what they need based on responsibilities.
How do you approach auditability?
PatrolCall emphasizes consistent event capture and change history so operational actions can be reviewed. Review workflows and governance configurations depend on your policies.
How does live map / GPS work from a consent perspective?
Location-related workflows are designed with a consent-aware posture and configurable visibility. Use depends on your use case and operational policies.
Still have questions?
A demo is the fastest way to answer “how would this work for us?” We’ll walk through a real workflow and align modules to your operating model.