Request Assessment →
Request Assessment
›FDCAPABILITY · FRONT DESK

The front desk,
on the record.

Most guard platforms stop at the patrol. Operations don't. Reception logs visitors, holds parcels and packages, hands out keys and signs them back in — and every one of those is a liability if it lives on paper. FieldOps runs the front desk on the same record as the field.

›FD.00WHY IT MATTERS

A reception desk is where accountability quietly leaks: a visitor who was never logged, a key handed over and never returned, a parcel received by someone who has gone home. Each is small until it is the thing in dispute — and each lives, on most sites, on a clipboard.

FieldOps treats reception as part of the operation, not an afterthought. Visitors, stored items and keys are tracked objects on the same record as patrols and incidents — built for GDPR from the start.

›01VISITOR MANAGEMENT

Every visitor, logged
against site, host and time.

Log every visitor against the site, the host and the time — individually or as a group. Templates pre-fill the common visit types and enforce the fields that matter, and a visit can open a linked report automatically. Built for GDPR from the start: configurable retention, anonymisation or deletion, a stated legal basis and a full audit trail.

  • Group visits, templates and mandatory fields
  • Auto-created visit reports and exit handling
  • Export to spreadsheet; category and step builder
  • GDPR retention, anonymisation, legal basis, audit
›02RECEPTION & STORAGE

What reception holds,
tracked back to the event.

Define what reception holds — packages, equipment, left luggage — with custom fields per item type. Track loans, losses, archiving and administrative returns, with due dates and overdue alerts, linked back into the event record.

  • Item types with custom fields
  • Loans, losses, archive, administrative return
  • Due-date and overdue alerting; full audit
›03KEY MANAGEMENT

A real key cabinet,
not a notebook.

Issue keys against a person and a return date, take them back in full or in part, flag a loss and recover it later — and run inventories that reconcile the count against the record and route differences for approval. No competing guard platform offers this.

  • Issue / return (full or partial) / lost / found
  • Folder tree, availability vs. total, change history
  • Inventories: count, pause, complete, review, approve
›04TENANTS & BUILDING DIRECTORY

In a multi-tenant building, reception works against a directory: who occupies which unit, who receives their mail and parcels, who authorises their visitors. FieldOps keeps that directory on the same record, so a parcel, a visit and a key all resolve to the right tenant — and the desk is not guessing.

Visits and keys connect — a visit template can draw a key from the cabinet and return it on exit. Parcels for a tenant flow into mail & parcels, on the same chain.

›FD.05WHERE IT FITS

The front desk is not a separate product. It is one face of the same system of record — which is why a visit, the key it draws, the parcel it receives and the report it opens are a single chain.

Mail & parcelsIncoming and outgoing parcels handled by the same desk, on the same record. Data, residency & GDPRWhere the most personal-data-heavy part of the operation lives, and under whose rules. All capabilitiesThe whole map — field, front desk and back office on one record.
›FD.FAQFRONT DESK — COMMON QUESTIONS

What buyers ask about
the security front desk.

Does FieldOps handle visitor management?
Yes. Reception logs every visitor against the site, the host and the time — individually or as a group — using templates that pre-fill common visit types and enforce the fields that matter. A visit can open a linked report automatically, and the whole log is built for GDPR: configurable retention, anonymisation or deletion, a stated legal basis and a full audit trail.
Can reception track left luggage and stored items?
Yes. You define what reception holds — packages, equipment, left luggage — with custom fields per item type, then track loans, losses, archiving and administrative returns, with due dates and overdue alerts, all linked back into the event record.
Does FieldOps include key management?
Yes — a real key cabinet, not a notebook. Keys are issued against a person and a return date, taken back in full or in part, flagged as lost and recovered later. Inventories reconcile the physical count against the record and route any difference for approval. No competing guard platform offers this.
Is the front desk on the same system as the guard force?
Yes. Visitors, stored items and keys live on the same record as patrols, incidents and shifts — so a visit, the key it draws and the report it opens are one chain, not three disconnected tools.
Is visitor data handled to GDPR standards?
Yes. Visitor records carry configurable retention, anonymisation or deletion, a stated legal basis and a full audit trail by default — the front desk is the most personal-data-heavy part of an operation, so it is GDPR-native rather than retrofitted.
NEXT STEP

The desk is part of the operation.
Run it on the same record.

Twenty minutes is enough to see how visitors, storage and keys fit the rest of your operation.

Request Operational Assessment → Explore capabilities