Reader Technology Mapping: The Test Plan a Buyer Should Demand
A reader technology mapping test plan turns a bidder’s technology promise into evidence a buyer can accept, reject, or return for correction. That distinction matters when a system integrator is comparing credential readers for different doors in the same building. Naming a technology is not enough. The buyer needs to know which door receives it, what identity sits behind each credential, how the reader reaches the controller, what happens during an outage, and which team owns the correction.
Direct answer. Condensed to the essential point, reader technology mapping test plan turns a request into a decision record. reader technology mapping test plan and reader-technology-mapping are the two parts of reader technology mapping test plan most often skipped. A reader technology mapping test plan is an integration guide. Every component has an obligation to the next. reader technology mapping test plan is the first one tested for reader technology mapping test plan.
The phrase reader technology mapping test plan is anchored in reader technology mapping test plan. For the rest of this article it denotes the conditions and evidence that reader technology mapping test plan sets out below. Nothing wider than that.
This bid schedule converts those questions into mandatory tests and written evidence. It is intended for the system integrator, access-control engineer, IT team, security reviewer, and client representative evaluating a smart-lock proposal. The bid annex reference is reader-technology-mapping.
How bidders must complete this schedule
The bidder must submit one completed row for every door or approved door group in the pricing and design schedule. A generic statement that the proposed reader is “suitable for the site” does not complete the bid. The bidder must identify the proposed credential technology, controller path, credential lifecycle, event source, offline behavior, and evidence owner for that location.
Use these response codes consistently:
| Code | Meaning | Minimum response required |
|---|---|---|
| C | Complete | Proposed design, test method, evidence, and acceptance owner supplied |
| Q | Qualified | Proposed design supplied with a written limitation and a proposed resolution |
| N | Not proposed | Technology excluded for this door, with a documented alternative |
| D | Deferred | Design deferred pending a named input, dependency, or decision date |
A “to be confirmed” response without a named party, required input, and closure condition is an incomplete response. The bidder must explain whether the proposed reading method is suitable for that door, which credential identities the reader may encounter, and how revocation reaches the reader-to-controller path. Include the configured operating mode and the expected result when the central service is unavailable. What can be supplied is listed in the smart door locks.
The schedule should be submitted with the technical response, not added after clarification. Reader Technology Mapping for Smart Lock Projects: What Buyers Must Define First establishes the input decisions that belong in the bid package. Reader Technology Mapping Requirements Document Template can be used as the working sheet before the bidder prepares its final response.
The integration boundary to test
A reader is not the access-control decision maker. The controller holds the door state and makes the decision; the reader reports the presented credential or other input. The test boundary must therefore begin with the credential source, cross the reader-to-controller path, and finish at the access decision, event record, and door-control output.
flowchart TD
A[Issue the door schedule] --> B[Map candidate credentials]
B --> C[Confirm the reader path]
C --> D[Build the approved test environment]
D --> E[Run normal path tests]
E --> F[Inject credential and service faults]
F --> G[Collect timed evidence]
G --> H[Close exceptions or recommend acceptance]
The bidder must answer five boundary questions for each door group:
| Boundary question | Evidence demanded at bid stage |
|---|---|
| What does each side send? | Message or signal definition, expected frequency, and source of each field |
| What happens when a message does not arrive? | Timeout behavior, local fallback, and operator-visible indication |
| Who owns the clock? | Named time source, synchronization method, and clock-drift handling |
| What is recorded, where does it live, and who can read it? | Event fields, storage location, retention configuration, and access roles |
| Who owns the fix when the path fails? | Named owner by layer and the required diagnostic information |
CONFIRM-PER-SUPPLIER: Confirm on the dated product page for the specific SKU and provide dated written evidence for every proposed reader, controller interface, credential type, and API boundary.
No pass result is valid if the bidder has not identified the decision point for that particular door. The acceptance plan must distinguish a successful physical read from a complete access decision, then trace both through the available event record.
Build the door-by-door credential mapping
The reader selection test plan starts with the door, not with a favored credential technology. Record the door’s use, operating pattern, required access zones, consequence of a missed event, and the people or roles expected to present credentials there. A shared service entrance, an ordinary staff door, and a restricted interior door should not inherit one reader design merely because they appear on the same property drawing.
Credential, identity, and personalisation must remain separate in the bid. The credential is the item presented. Identity is the person or role behind it. Personalisation is the per-person information carried by that credential. The bidder must show how the system associates the three without assuming that possession of a credential proves the identity claim the policy requires.
| Door ID | Door role and use | Expected identity type | Proposed credential | Issue route | Revoke route | Event source | Outage result to test |
|---|---|---|---|---|---|---|---|
| D-01 | Staff entry during occupied hours | Named employee or contractor role | Bidder proposal | Identity source or front desk | Identity source | Reader or controller, as proposed | Local decision behavior |
| D-02 | Shared service and delivery access | Role or time-bound assignment | Bidder proposal | Dispatch or enrollment process | Dispatch or enrollment process | Bidder proposal | No unrecorded access grant |
| D-03 | Restricted interior room | Named role with additional authorization | Bidder proposal | Privileged workflow | Privileged workflow | Bidder proposal | Controlled local behavior |
| D-04 | Public or visitor entrance | Temporary visitor identity | Bidder proposal | Host or visitor workflow | Automatic expiry or manual revoke | Bidder proposal | Expiry remains enforceable |
| D-05 | Emergency or egress route | No reader assumed | Not applicable | Not applicable | Not applicable | Relevant interface, if any | Approved release behavior |
The credential technology matrix should compare the bidder’s proposal against this schedule. Contactless cards, phone-held credentials, PIN entry, and biometric presentation may appear as candidate categories, but the bid must not treat an illustrative category as proof of an available implementation. Each candidate needs its own issuance method, administration path, revocation behavior, audit source, and exception plan.
Door-by-door credential mapping also exposes assumptions hidden in a one-size-fits-all proposal. It forces the bidder to distinguish a credential intended for daily use from one intended for temporary access. It also reveals where a personal device is being used as a temporary carrier rather than as the authoritative identity record.
The reader technology mapping test plan in one page
The bidder response to the reader technology mapping test plan must use the same test sequence for every proposed reader class. A different test method is acceptable when the bidder explains the technical reason and the buyer accepts it in writing.
| Stage | Input from the bidder | Test method | Required evidence |
|---|---|---|---|
| Desk review | Door schedule, credential proposal, interface statement | Trace each proposed path | Signed matrix and unresolved-question list |
| Controlled bench test | Approved reader, controller, credential source, and sample credential | Exercise normal and invalid presentations | Screens, event export, and test sheet |
| Installed-door test | Final reader position, door hardware, network path, controller | Test at the approved operating condition | Site video or still images with matching logs |
| Fault test | Approved service-failure method | Remove, delay, or isolate one named dependency | Fault evidence and recovered state |
| Closeout | Completed evidence package | Review each acceptance criterion | Signed disposition for pass, condition, or fail |
Bench testing establishes whether the proposed components communicate. It does not prove that the reader will behave as intended in its installed position. Installed testing establishes the site condition. Neither test substitutes for a document review of credential issuance, revocation, event retention, and ownership.
The acceptance test must use representative credentials and identities approved by the buyer. The bidder must not replace a proposed credential with a demonstration token while leaving the production issuance route untested. Where multiple reader options are offered, the bidder must show whether each option passes the same criterion or is limited to a specific door class.
Mandatory schedule of access-control tests
The buyer should require the bidder to execute the following schedule against the exact proposed combination of reader, controller, credential, and interface. Every pass statement must identify the tested SKU or documented product configuration and the software version used during the run.
| Test ID | Setup and action | Evidence required | Pass condition |
|---|---|---|---|
| T-01 | Issue a test credential and associate it with an approved identity | Enrollment record and credential identifier | The identity, credential, door access, and issuing source are traceable |
| T-02 | Present the valid credential at the mapped door | Controller decision and source-stamped event | The door decision matches the approved access rule |
| T-03 | Present a revoked or never-issued test credential | Decision, event, and revocation timestamp | Access is refused and the attempt is recorded |
| T-04 | Present a valid credential at a door where that identity has no access | Decision and event | Access is refused without changing the identity’s other access |
| T-05 | Issue, change, then revoke a temporary credential through its stated workflow | Before-and-after records | Each state change is visible to the decision path |
| T-06 | Remove the controller connection while presenting a credential | Fault indication, local decision, and recovery log | The approved fallback or shutdown behavior occurs |
| T-07 | Disconnect the network or central service | Local event, operator signal, and reconnect record | The defined degraded mode is observed |
| T-08 | Present a credential while the event path is unavailable | Event memory or local record and later reconciliation | The event is retained or the gap is explicitly identified |
| T-09 | Trigger a credential update through the client platform | Update record and subsequent decision | The new rule takes effect at the agreed point |
| T-10 | Replace or provision a reader and then decommission it | Identity, door, owner, and removal records | The new device inherits only approved access; the old device is separately removed |
| T-11 | Use a phone-held credential, if proposed, through issue, present, revoke, and return | Device lifecycle and decision evidence | Revocation and expiry remain enforceable through the stated route |
| T-12 | Use PIN or another fallback method, if proposed, after role assignment and disablement | Role state and attempt records | The method cannot bypass the assigned access rule |
Credential and decision-path tracing
For each pass, the evidence must show what the reader reported, what the controller decided, and which source created the event. The lock reports the state; the system decides what the state means. A successful unlock alone is not sufficient because it does not reveal whether an invalid credential was accepted, a cached rule was used, or an event was lost.
The trace must also show the source of the timestamp. If the reader, controller, and central platform use different clocks, the buyer must know which clock stamps the decision and which clock stamps the retained record. A reconciliation rule is required when either source can drift.
Reader-to-controller evidence
Wiegand is a legacy wiring convention between a reader and a controller. It carries a data line and usually a power and a ground, and it says nothing about encryption or device identity. OSDP is a specified, addressed, bidirectional protocol with device addressing and a defined message structure. The bid must state which path is proposed, which messages are required, and how faults are surfaced.
Implementation remains a per-SKU question.
The bidder must supply interface drawings, configuration records, and witnessed test results. A protocol name in a product sheet is not a substitute for showing the path used on this project.
Degraded-mode and recovery tests
The offline case is the design, not the exception. For each reader class, the bidder must identify whether the decision state is centralised or standalone and show what the door does when the network, controller, or server is unavailable. The offline outcome must come from the approved door design rather than from an assumption that a disconnected lock always behaves the same way.
| Fault injected | Observation required | Recovery evidence required |
|---|---|---|
| Network unavailable | Local decision or defined shutdown behavior | Automatic or controlled reconnection |
| Central platform unavailable | Last approved rule, local rule, or approved denial | Reconciliation of missed updates and events |
| Controller unavailable | Door state, lock state, and operator indication | Replacement or restoration record |
| Event memory full or unavailable | Admission behavior and operator notification | Capacity recovery and gap record |
| Credential update interrupted | Version or state visible to the controller | Rollback, completion, or administrator decision |
Installed-door acceptance tests
The final test must occur at the installed reader position with the approved door, lock, controller, power arrangement, network path, and credential population. Office Smart Lock Site Survey provides the site-condition discipline needed before readers are compared. For retrofit work, Smart Lock Retrofit Site Survey should inform the door and frame assumptions used in the test.
| Acceptance ID | Test condition | Evidence | Reader acceptance criteria |
|---|---|---|---|
| A-01 | Reader mounted in its final position | Installation photograph and configuration record | Location, orientation, and identity match the approved design |
| A-02 | Valid credential presented at normal approach positions | Decision log and test observation | Expected decision occurs without manual controller intervention |
| A-03 | Invalid credential presented | Decision and attempt event | Access is refused and the attempt reaches the approved event source |
| A-04 | Door operated after authorization | Door-position state and event | The system observes the expected transition without assigning a false cause |
| A-05 | Network service interrupted at the door | Door behavior and operator indication | The mapped degraded mode matches the approved schedule |
| A-06 | Reader disconnected or removed | Controller and service indication | The failure is visible to the responsible operator |
| A-07 | Recovery from the injected fault | Reconnection and decision evidence | No unexplained access state or lost accepted decision remains |
Use the door-position contact as a state report only. It shows that the door is open or closed; it does not identify why the door opened. If the bidder proposes correlating a door state with a credential event, the acceptance evidence must prove the proposed correlation rather than infer a cause from sequence alone.
CONFIRM-WITH-LOCAL-FIRE-APPROVAL: Confirm the required fail-safe or fail-secure behavior, the release path, and the approval authority for each door before the outage tests are accepted.
CONFIRM-WITH-LOCAL-ACCESSIBILITY-LEAD: Confirm the operable force, motion, hardware arrangement, and assisted-operation expectations for the installed door, then include the agreed manual checks in the acceptance sheet.
The bidder may not substitute a bench cabinet for these installed checks. If weather, lighting, construction, or door movement prevents a test, the bidder must record the condition and schedule a witnessed repeat. An untested door remains an open exception, even when another door of the same class has passed.
Interoperability testing and exception control
Access control interoperability testing must follow a credential through its complete administrative lifecycle. The bidder must show that identity creation, credential personalization, access assignment, presentation, revocation, expiry, event capture, and reporting agree with one another. A successful reader presentation proves only part of that chain.
The bid must also identify whether the relevant integration boundary is a local API or a cloud API. The bidder must describe the request sequence, authentication method, error handling, rate or retry behavior, and point at which a failed update becomes visible. The test must establish whether a credential rule is accepted centrally before the controller can apply it.
| Test path | Required observation | Failure to close |
|---|---|---|
| Identity created, credential issued | Both records can be traced to the same approved identity | Revocation or audit trail may not reach the credential |
| Access role changed | New role behavior is visible at the mapped door | Old access may persist outside the change window |
| Credential revoked | Decision refuses the revoked credential | Access may continue through a stale local rule |
| Event exported | Required fields and source time are present | The platform cannot reconcile the event |
| API call interrupted | Retry or reconciliation behavior is demonstrated | Duplicate, missing, or divergent records |
Every exception needs a unique record. The record must name the failed criterion, door, configuration, evidence, owner, correction, retest date, and buyer disposition. A generic statement that the remaining points are compatible is not an exception closure.
Do not accept a pass that depends on a feature whose availability has not been confirmed. State the missing evidence, limit the proposal, or return it as a qualified bid. Security Questions to Ask About Reader Technology Mapping can extend the bidder’s written answers, but the security responses must still point to evidence in this test package.
Security and privacy controls in the test
The bidder must distinguish the physical credential from the person or role it represents. A read test should therefore include controls for a valid credential, a revoked credential, a credential assigned to the wrong door, and a credential whose identity has been disabled. The same checks should be repeated at the administrative route so the test does not depend on one platform screen.
For temporary access, show how the credential expires, who may extend it, and what happens if the credential is presented before or after its valid window. For front-desk issuance, identify the encoder or issuance device as an administrative dependency and state which records prove that the intended credential was written. These are process controls, not assumptions about any particular product.
The event test must show which source creates the audit record and which fields the buyer can retrieve. Audit log and event memory must not be treated as interchangeable. The former is the retained event with a time and source; the latter is the device buffer used when the server cannot be reached. The buyer must know where each lives and which records reconcile after an outage.
CONFIRM-WITH-LOCAL-PRIVACY-OFFICER: Confirm the retention period, lawful basis, access rights, export controls, and deletion workflow for records that identify who opened which door and when.
Where a proposal includes biometric presentation, treat the template, enrollment source, fallback, and revocation as separate acceptance items. The bid must state what is captured, where matching occurs, and what evidence can be reviewed without exposing reusable biometric material. No conclusion about privacy compliance should be drawn from a successful card or PIN test.
Scoring and the award recommendation
Pass/fail acceptance comes before comparative scoring. A bidder cannot compensate for an unclosed critical defect with a strong score elsewhere. The buyer should mark each mandatory criterion as passed, conditionally accepted, or failed, then apply the agreed weighted criteria to the bidders that remain eligible.
| Evaluation element | What the buyer scores | Credit rule |
|---|---|---|
| Door and credential clarity | Completeness of the door-by-door mapping | No credit for unqualified or generic entries |
| Test reproducibility | Steps, configuration, versions, and evidence | Credit requires another tester to repeat the result |
| Failure behavior | Observed degraded mode and recovery | No credit for an untested outage assumption |
| Event and audit evidence | Source, time, fields, and reconciliation | No credit for screenshots without matching records |
| Documentation quality | Traceability from input to signed result | No credit for an unsupported capability statement |
| Exception control | Owner, correction, and retest closure | Conditional credit requires buyer-approved disposition |
The bidder must include a final deviation register. Each deviation must state whether it changes the reader, credential, controller path, site work, operating procedure, or acceptance scope. The buyer should reject any deviation that removes a mandatory test without an approved written resolution.
The award recommendation should identify the selected bidder, door groups covered, accepted exceptions, conditions, and any excluded doors. It must not imply that unperformed tests passed. If the proposal is conditionally recommended, the condition must identify the evidence still required and who must provide it before final acceptance.
Ownership and change control during testing
The test plan must assign an owner to every layer. That owner is accountable for diagnosis and correction, not necessarily for every component. The boundary still needs to prevent a failure from becoming an unassigned support ticket.
| Layer | Test owner | Correction evidence |
|---|---|---|
| Reader and installation | Bidder technical lead or nominated field engineer | Configuration, installation record, and witnessed retest |
| Credential and identity workflow | Client platform owner plus bidder administrator | Before-and-after identity and credential records |
| Controller and door configuration | System integrator | Configuration export and decision trace |
| Network and service path | IT or platform owner | Fault test, recovery record, and monitoring evidence |
| Acceptance disposition | Buyer’s authorized reviewer | Signed criterion disposition and exception register |
Who Owns Reader Technology Mapping: Supplier, Integrator or Client provides the boundary discussion; this schedule turns that boundary into named test actions and required evidence.
A change to a reader, controller, credential platform, firmware state, door hardware, network path, or event schema triggers a documented impact review. The reviewer decides which tests repeat. A minor administrative correction does not automatically repeat the full schedule, while a changed decision path requires the relevant normal-path and fault tests again.
Final evidence pack and sign-off
Require the evidence package before the buyer signs the acceptance sheet. It must identify the tested configuration, preserve the submitted test plan, and connect each result to the relevant door schedule.
The package should contain:
- the completed door and credential matrix;
- approved reader-to-controller and API drawings;
- the exact test script used for each case;
- credential enrollment, decision, event, and recovery records;
- installed-door photographs or selected site images;
- configuration exports with identifiers and versions;
- fault-injection instructions and the observed result;
- event-memory and audit-log reconciliation evidence;
- the exception register and signed retest records;
- a final traceability sheet from each criterion to its evidence.
Each evidence file should carry the door ID, test ID, date, tester role, configuration state, and result. Redact unrelated personal data without removing the fields needed to verify the test. Keep original machine records where possible so that a reviewer can compare the screenshot with the exported event.
It is worth pairing this with slk 9936s door thickness compatibility. That is the same question reader technology mapping test plan has to answer here.The final sign-off sheet should state the tested scope, the result for every mandatory test, unresolved conditions, and the acceptance decision for each door group. It should distinguish final acceptance from conditional acceptance and from exclusion.
| Sign-off item | Buyer decision |
|---|---|
| Mandatory tests completed | Accept, accept with listed conditions, or return |
| Critical exceptions | Closed, not applicable, or failed |
| Evidence package received | Complete, accepted with named gaps, or incomplete |
| Door groups accepted | Record each group separately |
| Conditions to close | State evidence, owner, and required confirmation |
Do not treat handover documentation as a substitute for missing test evidence. The records must be sufficient for another authorized reviewer to reproduce the decision and understand what remained conditional.
Clauses to issue with the invitation to bid
The buyer should attach the following clauses to the technical bid schedule:
- BR-01 — Mandatory completion: Every door group must have a completed reader technology mapping test plan row with a proposed design and evidence owner.
- BR-02 — Per-SKU proof: Capability, interface, and implementation claims must be confirmed on the dated product page for the specific SKU, with project-specific evidence appended.
- BR-03 — Normal and fault paths: Each proposed reader class must pass both the normal decision test and the approved degraded-mode test.
- BR-04 — Installed condition: Bench evidence may support, but not replace, testing at the installed reader position.
- BR-05 — Event traceability: Every accepted access decision must be traceable to a credential, identity, decision, time source, and retained event.
- BR-06 — No silent qualification: Limitations must be stated in the bid, assigned an owner, and closed before final acceptance.
- BR-07 — Change control: Material changes to the tested path require impact review and the specified repeat tests.
- BR-08 — Acceptance sign-off: Final acceptance requires a completed evidence pack and a door-by-door disposition signed by the buyer’s authorized reviewer.
Issue this schedule with the invitation to bid and require the bidder to return it as part of the technical response. The result is a reader technology mapping test plan that can be executed, challenged, and signed without relying on a product name or an untested promise.
When the file is ready, request a quote against the written requirement.

