An ESD access record should begin with the identity of the employee being tested and the test mode assigned to that person. The system then retains the actual wrist-strap, left-foot and right-foot results and their individual decisions, together with the time, device, entrance, area permission and final passage outcome. A single “pass” or “door opened” entry is not enough to show which tests were required, which item failed, or whether the employee actually passed through the controlled entrance.
Why a single pass result is insufficient
People using the same entrance may have different approved test modes. The record must distinguish an item that was not required from an item that was required but missed.
Where separate traceability is needed, left and right footwear results should remain distinct. The project defines the actual measured-data format and decision rules; they are not assumed here.
Bind the test to the correct employee
The employee identifies by the approved method, allowing the system to create one test transaction and load the role, validity, area permission and assigned mode.
The wrist, left-foot and right-foot results then join that same transaction with the person, terminal, entrance and time. Independent logs should not be joined merely because their timestamps are close.
Recommended record layers
- Person and permission: stable employee identifier, approved organisational data, target area, permission state and test mode.
- Test event: required and completed items, measured results, item decisions, overall decision, device, direction and time.
- Passage: whether release was requested, available gate or lock feedback, and reasons for denial, offline operation or manual review.
Handle records for each deployment
- Stand-alone operation: verify local storage, export and identity binding; an indicator lamp alone is not traceable data.
- Networked entrance: define offline storage, recovery upload and duplicate handling.
- Multiple entrances: maintain stable device, entrance, direction and time references.
- Retained access system: use a shared transaction identifier where possible; otherwise state clearly what each separate record proves.
Confirm before implementation
- The stable personnel identifier and its relationship to cards or face records.
- Assigned test modes and authority for temporary changes.
- Required retention for measured results, decisions, devices, direction and passage status.
- Offline storage, retransmission, duplicate control and query permissions.
- Identifiers and time fields available when linking access or attendance events.
Frequently asked questions
Can the system retain only pass or fail?
Not when separate wrist and footwear traceability is required. The implementation scope should define the measured results, item decisions and overall decision to retain.
Does a missing left-foot result always mean a missed test?
No. First check the assigned mode. It is missed only when the item was required and no valid result was produced.
Can a passed ESD test be treated as attendance?
Not by default. A test event and an attendance event use different shift, direction and validity rules; any exchange must be agreed separately.