Electronic key management cabinet with blue key holders and numbered security key on a retaining cable at Essential Security Supplies NZ.

Vehicle Fleet Key Management: Electronic Cabinets and Audit Trails

Essential Security Supplies

Give each fleet vehicle keyset a uniquely tagged cabinet position, allow collection only by authorised drivers, set a clear return deadline and assign someone to review overdue keys and audit reports. For New Zealand fleets, the cabinet should support the actual shift pattern, vehicle bookings and key-return arrangements, not simply store keys behind a locked door. A key transaction records custody, not proof of who drove the vehicle.

How electronic fleet key cabinets work

An electronic cabinet stores controlled keysets in individually managed positions. Depending on the model and configuration, an authorised person identifies themselves at the terminal, requests an eligible keyset and creates an issue event. Returning the key closes the custody event. Check the manufacturer's current documentation for how credentials, alarms, reporting, connectivity and power-failure recovery work on the exact model.

Start by drawing the everyday sequence: vehicle reserved, driver approved, key collected, condition checked, vehicle used, fuel card returned and key placed back in custody. Also document night-shift handovers, contractor visits, breakdowns and emergency use. The cabinet is only one component in this workflow.

Tag keysets and size the cabinet

Build a register with a unique keyset ID, vehicle asset number, registration, approved user groups and physical storage position. Count spare keys, trailer keys, workshop keys and removable fuel cards separately if each requires an independent custody record. Do not put sensitive driver or vehicle information on exposed labels.

Capacity is based on controlled keysets, not only the number of vehicles. For example, a fleet of 20 vehicles with 20 primary keysets, four spare keysets and two trailer keysets needs at least 26 positions before allowing for future growth. Keep some headroom for replacement vehicles, seasonal hiring and keys with larger fobs.

Example controlled keysets Capacity to consider Planning note
Up to 14 14 or 18 positions Small vehicle pool; allow for spares
15–26 26 or 32 positions Check spare and trailer keysets
27–48 32 or 48 positions Choose capacity above counted demand
49–64 64 positions Allow for roster and fleet changes
65–100 100 positions Consider multiple areas or teams
101–150 150 positions Confirm physical key dimensions
151–200 200 positions Review site distribution and resilience

These are illustrative sizing bands based on the range identified in the ESSL catalogue, not a guarantee that every model supports every workflow. Confirm each model's usable key positions and any RFID tag, fob, licence, software or cabinet expansion requirements before ordering.

FGKM-AS32: FERN360 Key Management System: 32 Keys
Genuine ESSL catalogue photograph: FGKM-AS32 - FERN360 Key Management System - 32 Keys. Verify the model details against the current project specification.

Driver permissions by role, shift and licence class

Set permissions according to job requirements, not a single shared PIN. A supervisor may need access to the full pool; a licensed operator should see only suitable vehicles; a contractor may need time-limited access. Establish a process for new starters, licence-class checks, suspended permissions, temporary assignments and prompt removal of leavers.

Check whether the selected model can implement these restrictions directly or whether a fleet administrator must approve collections externally. Test an approved driver, a driver outside their permitted shift and a user denied access to a restricted vehicle. Keep emergency override privileges narrow, logged and periodically reviewed.

After-hours returns and missing keys

For 24-hour operations, key return must work even when the fleet office is closed. Decide whether drivers return directly to the cabinet or use a controlled drop box for later reconciliation. The FERN360 FGKM-SKD15 automotive electronic key drop box is one product to assess for this use; confirm its security, integration and operational fit with the supplier.

Specify the due time at the point of issue, taking shift length and booking duration into account. A practical exception rule could flag a key 15 minutes after its expected return, alert a designated fleet supervisor and escalate unresolved cases to the next shift. These timings are operating examples, not cabinet features guaranteed on every model.

For keys returned through a drop box, record when custody was accepted and when the key was physically checked back into its assigned position. Establish who handles missing tags, damaged key fobs, vehicle faults and emergency replacement keys.

What an audit trail should record

A useful audit record connects the user, controlled asset and collection event. Where supported, capture at least the driver or credential ID, vehicle or asset ID, keyset ID, issue time, due time, actual return time, approving administrator and an exception or override reason. Verify which fields the cabinet natively stores and which must be maintained in an external booking system.

Driver Vehicle Keyset Issued Due Returned Exception
Driver 014 Pool Van 07 KV-007 07:05 16:00 16:18 Late; reviewed

The row above is a fictional example, not a report exported from a FERN360 product. A named fleet administrator should review overdue and override events daily during a rollout, then adopt a regular documented review schedule, such as a weekly exception report. Record the reviewer, resolution and any unresolved keyset. For detailed reporting and lost-key workflows, see Electronic Key Cabinets: Audit Trails and Access Control NZ.

Connect key records to bookings and telematics carefully

Electronic key issuance can support a fleet booking process, but a key issue does not establish who actually drove a vehicle, its mileage or whether it sustained damage. Where required, pair the return workflow with driver-completed mileage and condition checks, and use approved booking or incident records for any further investigation. The availability of exports, APIs and integrations depends on the specific cabinet and software configuration.

Key transactions linked to identifiable staff, and any linked GPS or telematics records, may be personal information under New Zealand's Privacy Act 2020. Explain to staff what is collected and why, document who may view or export reports and the retention period, and consult staff before introducing or materially expanding vehicle monitoring. Consult the Office of the Privacy Commissioner guidance on GPS in work vehicles and Employment New Zealand's employee privacy guidance.

FGKM-AXL100: FERN360 Key Management System: 100 Keys
Genuine ESSL catalogue photograph: FGKM-AXL100 - FERN360 Key Management System - 100 Keys. Verify the model details against the current project specification.

Choosing a FERN360 cabinet for a vehicle fleet

The FGKM-AS32 is listed as a 32-key system, the FGKM-AXL100 as a 100-key system, and the FGKM-MK26 as a 26-key cabinet with an API-related listing. Select by validated keyset count, user roles, reporting needs, physical footprint and the confirmed capability of the precise model and software version. An API-related product title alone does not establish compatibility with a particular telematics platform.

Ask the supplier to confirm exact cabinet capacity, vehicle fob dimensions, credential options, administration rights, supported export fields, backup arrangements, power-loss behaviour, available maintenance support and whether multiple cabinets can be managed as required. The Intelligent Key Management Systems collection provides the wider range for comparison.

FGKM-MK26: FERN360 Key Management System Key Cabinet System API
Genuine ESSL catalogue photograph: FGKM-MK26 - FERN360 Key Management System Key Cabinet System API. Verify the model details against the current project specification.

Commissioning and handover checklist

  • Enrol every actual vehicle, spare and trailer keyset and confirm its cabinet position matches the asset register.
  • Create driver roles and shifts, then test permitted, denied and revoked collection scenarios.
  • Issue and return a vehicle keyset; confirm the recorded driver, keyset, timestamps and report fields.
  • Test overdue reminders and the named person's escalation and exception-close process, if supported.
  • Test after-hours key return and reconcile any drop-box transactions to physical custody.
  • Confirm how the system behaves during network loss and power interruption, including safe recovery and data retention.
  • Export or review a sample report, verify report access permissions and document privacy retention settings.
  • Record installed model, configuration, administrator handover, exceptions, maintenance procedure and signed acceptance.

Run a pilot with a small set of frequently used vehicles before expanding. Measure search time, late returns, unresolved keysets and operator feedback over a stated period. Check whether records are complete before using them for decisions about staffing or operating procedures.

Related fleet key management guides

For a deeper cabinet specification, read Electronic Key Cabinets: Audit Trails and Access Control NZ. Fleets replacing a paper sign-out book should compare Electronic Key Management vs Manual Key Registers. The FERN360 cloud-based key management overview explains the broader product range.

Frequently asked questions

Does a key cabinet record who drove a vehicle?

No. It records the credential or person associated with a key issue and return, subject to the cabinet configuration. It does not by itself prove who drove the vehicle. Use vehicle booking and other properly authorised records when a driving history is required.

How should after-hours vehicle key returns work?

Specify a secure return process accessible to authorised shift workers, including an approved key drop box where appropriate. Test how returned keys are reconciled to cabinet positions and who resolves unmatched or late returns.

How many cabinet positions does a fleet need?

Count each independently managed vehicle keyset, spare, trailer keyset and other controlled item. Allow for seasonal fleet changes and future growth, then check actual usable positions, key dimensions and accessories against the selected manufacturer model.

Can key cabinet logs be used to monitor staff?

Key transactions relating to identifiable drivers may be personal information. Under New Zealand privacy and employment requirements, explain collection and permitted uses to staff, consult as appropriate, restrict report access and establish a documented retention and review policy.

Next step for a New Zealand fleet

Prepare your vehicle count, keyset register, shift pattern, driver permission matrix, overdue process and reporting requirements before requesting a trade specification review from Essential Security Supplies. Confirm the chosen cabinet's current manufacturer documentation and operational features before procurement. This guide is planning advice, not a guarantee of availability, compatibility or specific model functionality.