How can clients receive clear proof that patrols were completed?

A completed patrol that only lives in a phone call or a paper notebook is hard to defend later. Clients want to know what was checked, when it was checked, and whether the route was finished. Security companies need a practical way to show that work, without inventing a separate admin process after every visit.

NightWarden is built so patrol activity can be captured in the field and made visible afterwards. The security guard software page describes site-specific patrol run sheets with completion timestamps, and a white-labelled client portal with live shift status and completed run sheets. The NightWarden homepage also states that clients can see reports, activity records, checkpoint history, photos and service records as proof of service.

What gets captured during a patrol

Proof starts with what staff record while they are on site.

1. Patrol run sheets: site-specific task checklists generated at shift start, completed on the field staff app with timestamps, and with photos where the task requires them.

2. Checkpoint scans: NFC tags, GPS checks, or both, depending how each checkpoint is set up for that site.

3. GPS timestamps and photo evidence tied to the field activity being recorded.

4. Staff identity against the completed work, so the record shows who completed the tasks or scans.

On the partner side, completed tasks and run sheet entries are logged with the date and time, the staff member, and associated evidence such as form submissions, checkpoint scans and photos. Checkpoint scans appear in Scan History under Operations. Completed forms appear in Reports, where partners can view them, download a PDF, or share a secure link with an optional expiry.

That partner trail is the operational record. It is not the same as a client logging into their own portal.

How clients can see completed patrol work

For clients, NightWarden describes a branded portal that carries the security company's brand rather than NightWarden's. Product copy says clients can:

1. View live shift progress or live shift status.

2. See completed run sheets.

3. Download inspection reports.

4. View checkpoint scan history, activity records, photos and service records.

5. Raise queries without relying only on update calls to the control room.

Compliance reports tied to each shift are also described for insurance audits and client SLA reviews. Use those where the contract expects a periodic evidence pack, not as a substitute for checking whether tonight's patrol was finished.

Partners can still send a completed form report by secure link when a client needs a specific PDF outside the portal. Treat that as a separate partner-sharing channel. Do not present a one-off share link as the same as ongoing portal access.

How checkpoint evidence is built on site

Clear proof depends on the route being set up before staff arrive.

Partners create checkpoints per site in Operations, with a verification type of GPS Only, NFC Only, or Both NFC and GPS. Patrol routes can group checkpoints in order. Field staff then complete a checkpoint patrol in the NightWarden Field app: they start scanning, present the phone to each NFC tag or use the GPS scan action where required, and watch green ticks accumulate until the required checkpoints are done. A checkpoint set for both NFC and GPS must pass both checks. Completing all checkpoints can finish a scheduled checkpoint task automatically; an ad-hoc patrol is saved with Complete or Done.

If a scheduled patrol cannot be finished because a tag is broken or inaccessible, the unfinished-task paths in the app include pausing to resume later, or closing the task with a required note. That matters for honest records. A green tick history for completed points is useful; an unfinished patrol should not be described to a client as a full completion.

What proof does not replace

Captured timestamps, scans and photos help show what was recorded. Human judgement, risk assessment and the site procedures your company already uses still apply when something is wrong on site.

Live client or control-room visibility also depends on the work having been captured and synced from the field. The field app is described as offline-capable and able to sync automatically, but a draft or pending item still on a phone is not already a completed client-facing report. Confirm the completed run sheet, scan history or report in the correct history before telling a client the patrol pack is ready.

Service Reports exports can include patrols and checkpoint information where available and generate a PDF on demand. Use the same date range and service filters when comparing an export with operational records. That export is operational reporting, not a payroll calculation.

Practical shortlist for client-ready patrol proof

When you brief managers and account contacts on patrol evidence:

1. Set checkpoints and patrol routes before the shift, with the right NFC, GPS or combined verification.

2. Expect field staff to complete run sheet tasks and checkpoint scans in the NightWarden Field app during the visit.

3. Use partner Scan History and Completed Reports to check the operational record before client conversations.

4. Point clients to the branded portal for shift status, completed run sheets, checkpoint history, photos and downloads where that access is enabled.

5. Use secure partner report sharing when a specific completed form needs to be sent outside the portal.

6. Do not describe an unfinished or paused patrol as fully completed.

7. Keep site instructions, escalation contacts and risk assessment separate from the software record.

Next step

Review how your patrol routes, run sheets and client portal access line up with NightWarden's Patrol Run Sheets and Client Portal features on the security guard software page, or start from the NightWarden homepage if you want a demonstration against your own mobile patrol and client reporting process.