Electric Strike Selection: The Test Plan a Buyer Should Demand
An electric strike selection test plan is the controlled acceptance record for one installed door. It turns the approved door role, power-loss behavior, mechanical fit, electrical design, and system interfaces into pass-or-fail evidence. The plan belongs in procurement and commissioning rather than after the hardware is already fixed to the opening.
Direct answer. For a system integrator
Use a controlled electric-strike-selection record for every opening. Capture the door schedule entry, drawings, selected strike, controller, power source, safety approvals, and test evidence under one reference. Use the Electric Strike Selection Requirements Document Template as the input document, not as a substitute for installation evidence.
Where responsibilities are disputed, the Who Owns Electric Strike Selection: Supplier, Integrator or Client framework helps assign the boundary. For recurring commissioning defects, consult Electric Strike Selection Failure Patterns and How to Recover. The final evidence package should follow Documenting Electric Strike Selection for Handover and Audit.
Regulatory boundary: This handbook does not assert a universal opening-force threshold, fire-alarm sequence, or egress requirement. It specifies the approvals and evidence a buyer should demand before accepting an installation.
CONFIRM-WITH-LOCAL-AUTHORITY: Confirm the applicable opening-force, accessibility, egress, and fire-interface requirements with the authority having jurisdiction and the client's designated safety approver.
Clause register: what each acceptance decision must prove
| Clause | Decision under test | Required evidence | Pass owner |
|---|---|---|---|
| 1 | The test boundary matches one physical door | Door schedule, drawings, photographs, device register | Integrator |
| 2 | The required fail state is defined and observed | Approved matrix, state photographs, event records | Client approver |
| 3 | Mechanical and electrical installation fit the approved design | Installation checklist, electrical readings, alignment record | Installer |
| 4 | Release and re-lock timing meet the operating requirement | Timestamped measurements and controller logs | Integrator |
| 5 | Installed door operation remains within the approved force criterion | Method record, readings, door and hardware condition | Client approver |
| 6 | Door-state signals and events are accurate | Signal trace, event samples, log extracts | Controls engineer |
| 7 | Credential-to-release integration behaves predictably | Scenario results, failure responses, recovery records | Integrator |
| 8 | Power and communications failures produce the approved degraded mode | State table, interruption records, recovery result | Supplier and installer |
| 9 | The approved safety interface releases and reports correctly | Interface authorization, scenario record, supervision result | Safety approver |
| 10 | Results repeat and survive handover | Acceptance-test set, version record, signed evidence package | Integrator |
| 11 | Exceptions have an owner, disposition, and retest | Deviation record, corrective action, closed retest | Contract administrator |
flowchart TD
C1["Clause 1: Bind the test to one physical door"] --> C2["Clause 2: Define the electric strike fail state"]
C2 --> C3["Clause 3: Verify mechanical fit and electrical capability"]
C3 --> C4["Clause 4: Measure release timing against a stated clock"]
C4 --> C5["Clause 5: Measure the installed door opening force"]
C5 --> C6["Clause 6: Verify door-state signals and record ownership"]
C6 --> C7["Clause 7: Prove the access control integration path"]
C7 --> C8["Clause 8: Exercise power loss, communications loss, and restoration"]
C8 --> C9["Clause 9: Test the approved safety interface and egress arrangement"]
C9 --> C10["Clause 10: Make acceptance repeatable and handover-ready"]
C10 --> C11["Clause 11: Govern exceptions and preserve failed evidence"]
C11 --> D["Acceptance dossier and final disposition"]
Clause 1 — Bind the test to one physical door
The plan shall identify the opening by a unique door reference, not merely by a room name or strike model. The record shall include the door leaf and frame identifiers, handing, swing direction, latch type, frame construction, hinge condition, closer and latch hardware, strike location, controller, reader, power supply, and any door position or exit-related device connected to the same opening.
A useful scope statement reads: “This test covers the electric strike, mounting assembly, latch interaction, controller output, connected door-state inputs, and approved safety interface for door reference [ID].” It excludes unrelated readers, lifts, alarm zones, and network paths unless the test depends on them.
The door role shall be stated in plain English before any electrical condition is tested. Examples include an ordinary controlled entrance, a door subject to a different loss-of-power decision, or an opening governed by a separately approved egress and alarm arrangement. The statement is not a conclusion that every door in the same category must behave identically.
| Required record | What it prevents |
|---|---|
| Door reference and revision | Evidence assigned to the wrong opening |
| Approved operating role | A test default substituting for a design decision |
| Connected-device list | Missing a dependency between controller, strike, and sensors |
| Responsible parties | A failed result with no accountable owner |
| Test exclusions | Scope disputes during commissioning |
The acceptance condition is a complete scope signed by the installer and acknowledged by the integrator. Any material drawing change after the first test requires the affected clauses to be marked for retest. A changed lock body, frame, power arrangement, controller output, or safety interface can invalidate evidence even when the original strike remains installed.
Clause 2 — Define the electric strike fail state as a condition
The plan shall use the term electric strike fail state to identify the required physical condition, the event that causes it, the affected supply, the expected door condition, and the recovery sequence. A term such as “fail-safe” or “fail-secure” is not sufficient by itself because supplier documents and project specifications may define the words differently.
For this handbook, fail-safe versus fail-secure means the following working definitions, subject to the approved project and supplier wording: fail-safe describes an electric strike that releases the latch when its defined power is removed; fail-secure describes one that retains the latch when its defined power is removed. The test plan shall record the actual observed behavior rather than treating either label as proof.
| Condition tested | Required record | Evidence of result |
|---|---|---|
| Normal control state | Approved drawing and controller command | Strike state and door-position indication |
| Removal of the strike’s defined input power | Electrical isolation method | Latch condition at the opening |
| Controller output held inactive | Command or circuit state | Latch condition at the opening |
| Loss of communications without removal of strike power | Link status and local power state | Latch condition and system state |
| Return from the tested failure | Restoration sequence | Re-locking, release, and event behavior |
The distinction between electrical failure and communications failure is essential. Loss of a network path may leave local strike power present, so it need not produce the same latch condition as loss of the strike’s power. The acceptance matrix shall state each condition separately and shall not infer one result from another.
The physical check shall include an observer at the opening. Record the latch position, strike indication, controller state, and door-position input before the condition is introduced. After restoration, record whether the strike returns to its approved normal state, waits for a defined command, or remains under an approved manual intervention state.
CONFIRM-WITH-LOCAL-AUTHORITY: Confirm the required loss-of-power and loss-of-control behavior for each door with the authority having jurisdiction and the client's designated egress or safety approver.
Clause 3 — Separate mechanical fit from electrical capability
Mechanical acceptance precedes functional acceptance. The installer shall verify frame rigidity, strike alignment, latch engagement, bolt clearance, hinge movement, door closer interaction, and the movement of the latch when the door is operated without a release command. The door shall not scrape, bind, rebound into the strike, or depend on force from the latch to remain in the expected position.
The electrical acceptance shall be recorded separately from the mechanical result. Record the installed supply source, protective arrangement, conductor routing, controller output method, connection points, and the values required by the approved submittal and project drawings. Compare those installed values with the selected equipment’s dated documentation rather than carrying a value from another product or project into this one.
CONFIRM-PER-SUPPLIER: Obtain the exact SKU’s dated product page, installation instructions, electrical requirements, monitoring outputs, and written fail-state definition; do not transfer those statements to another strike.
The functional check shall use a valid test credential or an authorized commissioning method. Observe the full movement from command to latch release, including any change in the door-position indication. Repeat the check with the door in its normal operating condition, then repeat it after restoring the door closer and latch hardware to their approved settings. A strike that operates while the door is open but binds during normal closing is not mechanically accepted.
| Check | Acceptance basis | Evidence |
|---|---|---|
| Strike-to-latch alignment | Approved frame and latch condition | Marked photograph or witnessed observation |
| Powered release and return | Selected SKU instructions and approved timing | Controller record and physical observation |
| Installed electrical values | Project drawing and dated product documentation | Installer readings |
| Normal door operation | Approved hardware adjustment | Movement and return observation |
| Monitoring connection | Project interface schedule | Signal trace and controller event |
A pass in one column does not compensate for a fail in another. Electrical release cannot excuse poor alignment, and satisfactory mechanics do not prove that the monitoring or fail-state requirement has been met.
Clause 4 — Measure release timing against a stated clock
The project shall define what “release” means before testing. Use separate measures for the interval from an accepted authorization command to the first observable latch movement, the interval from that movement to usable latch retraction, and the interval from the door closing to re-locking. A vendor may use a different event boundary, so the buyer’s definition and the evidence source shall be recorded together.
| Timing measure | Start event | Stop event | Evidence source |
|---|---|---|---|
| Release latency | Controller accepts the authorization | First latch movement | Controller timestamp plus physical observation |
| Latch-retraction interval | First latch movement | Latch clears the strike | Timed observation |
| Re-lock interval | Approved door-closed event | Latch returns to the extended position | Controller and strike observation |
| Command dwell | Release command begins | Re-lock command becomes eligible | Controller log |
The test shall run under normal operating conditions and under the worst defined power condition approved for the project. The buyer should not invent a voltage, current, or timing threshold in the field. Use the approved schedule and the supplier’s dated instructions, and record any deviation for review.
The clock owner shall be named. A controller timestamp, a test instrument, and an installer’s watch may disagree. Before the test, establish which clock supplies the acceptance time, check that it is synchronized with the systems being compared, and preserve the synchronization evidence. If physical observation is required, capture it in the same log window rather than reconstructing it later from memory.
Acceptance requires the measured result to fall within the project criterion for every defined measure. It also requires no unintended re-lock while the latch remains engaged and no delayed release after a valid authorization is accepted. A visually quick release does not pass a test whose controller or safety sequence requires a different event definition.
Clause 5 — Measure the installed door’s opening force
The door opening force shall be measured on the assembled opening, with the approved latch, strike, closer, hinges, seals, hardware, and strike power state recorded. A reading taken from the strike in isolation cannot demonstrate the operability of the installed door.
The plan shall identify the testing method, side of the door, starting position, number of observations, and treatment of repeated readings. The method shall come from the approved project requirement rather than from a convenient measurement taken after installation. Any local accessibility or egress requirement that determines the threshold shall be confirmed before the result is judged.
| Test condition | Record | Reason |
|---|---|---|
| Door closed and latched | Measured force and door condition | Confirms the installed operating condition |
| Door operated after an authorized release | Measured force and strike state | Separates access release from manual operation |
| Door after normal hardware cycling | Measured force and any binding | Exposes adjustment or wear effects |
| Relevant access and escape sides | Separate results where required | Prevents one result from masking another |
Do not conceal a failed result by changing the measurement method, removing approved hardware, or testing an opening other than the one referenced in the schedule. If a hardware adjustment is needed, record what changed, repeat the complete force test, and link the original failure to the corrective action.
CONFIRM-WITH-LOCAL-AUTHORITY: Confirm the applicable door opening force and accessibility criterion, including the method and sides to be tested, with the authority having jurisdiction and the client's designated accessibility approver.
Clause 6 — Verify door-state signals, event sources
A door position switch reports whether the door is open or closed; it does not report why the door moved. The test shall distinguish the switch transition from the action that caused it. For example, an open event may follow an authorized release, manual egress, propping, obstruction, or a fault. The access-control record may identify the event source, but it shall not be described as proof of the physical cause unless another approved sensor establishes it.
A request-to-exit signal reports operation from the escape side. It is not a release command, and the default release behavior belongs to the approved exit arrangement. The test plan shall state whether an exit device is present, what it controls, and whether its signal is being observed. The signal shall not be repurposed as a substitute for the strike’s normal authorization path.
| Stimulus | Expected observations | Required record |
|---|---|---|
| Door moves from closed to open | Door-position transition and correct source association | Event sample with controller time |
| Door returns to closed | State transition and re-lock sequence | Event and physical result |
| Exit device is operated | Request-to-exit meaning remains distinct from release authority | Signal trace |
| Door is held open | Configured alarm or event behaves as approved | Controller configuration and event |
| Communications are interrupted | Event handling follows the approved degraded design | Offline event-memory record |
Every event used as acceptance evidence shall identify its time, source, event type, door reference, and storage location. The plan shall also state who can read the record, who may export it, and how long it remains available. An audit log and an event-memory buffer are different: the audit log is the retained event record, while event memory holds recent activity when the lock or connected device cannot reach its server. The plan shall identify where an event moves between them and who investigates an apparent gap.
If access events can identify a person or role, the owner shall apply the project’s approved access, retention, and disclosure rules.
CONFIRM-WITH-LOCAL-PRIVACY: Confirm retention, access, disclosure, and local legal requirements for access-event data with the client's privacy or legal owner.
Clause 7 — Prove the access control integration test path
The access control integration test shall trace the complete path from credential presentation to the controller decision, controller output, strike movement, and returned system state. The controller holds the door state and makes the release decision; the reader reports the presented credential. The test shall verify that division of responsibility rather than assuming that a reader directly controls the opening.
Each scenario shall identify what the reader sends, what the controller returns, what reaches the strike, and what happens when the expected message does not arrive. If the project uses a local API or cloud API, the plan shall identify the actual boundary being tested and shall not treat equivalent behavior at one boundary as proof of the other.
| Scenario | Required action | Expected result | Recovery evidence |
|---|---|---|---|
| Valid credential | Present through the approved reader | Controller accepts the request and the strike releases | Authorization and release events |
| Invalid credential | Present an unassigned or invalid credential | No release occurs and the event matches policy | Denial event |
| Locked door | Present a credential outside the assigned area | No release and no hidden temporary grant | Controller decision record |
| Forced-door state | Simulate the approved contact condition | Alarm or event follows the approved rule | Event and notification record |
| Controller unavailable | Remove or isolate the controller path | Opening follows the approved degraded mode | State and operator record |
| Server unavailable | Disrupt the upstream service | Local controller behavior matches the design | Local event and recovery record |
| Service restored | Restore the interrupted path | Queued or locally held events are handled as approved | Reconciliation record |
The missing-message case deserves its own result. For each message, document whether the sender retries, the receiver times out, a local rule continues, an operator is prompted, or the system enters a defined unavailable state. A network disconnection that appears to preserve the door can still fail the test if monitoring is lost, a required event is discarded, or recovery creates an unauthorized release.
The acceptance record shall name the party that owns the controller configuration, the party that owns the credential platform, and the party that owns the strike and power installation. Where the evidence crosses those boundaries, one integrator should remain responsible for reconciling the scenario result even though each specialist corrects its own equipment.
Clause 8 — Exercise power loss, communications loss
Fail-state testing and degraded-mode testing answer different questions. The fail state asks what the latch does when a defined power condition occurs. Degraded-mode testing asks what the entire opening, controller, and record path do when a service disappears. Both belong in the plan, but neither can substitute for the other.
| Scenario | Inputs to record | Required observations | Pass basis |
|---|---|---|---|
| Normal operation | Power and communications healthy | Release, re-lock, monitoring, and event capture | Approved normal sequence |
| Strike input power removed | Electrical condition and controller state | Latch position and event behavior | Approved fail-state matrix |
| Controller output inactive | Output state and local power | Latch position and local indication | Approved control-loss rule |
| Network unavailable | Link state and server state | Local release rule, monitoring, and event memory | Approved degraded mode |
| Controller restarted | Start state and recovery sequence | Temporary state, reset behavior, and reconciliation | Approved restart procedure |
| Server unavailable | Local service state | Credential decision path and local records | Approved local policy |
| All services restored | Restoration order | Queue handling, event reconciliation, and normal return | Approved recovery sequence |
For every interruption, record when the condition was introduced, what an operator saw, what the door did, and what event was created. The observer should be positioned to verify the latch and door state, not only the software screen. The software may display an intended output while the physical strike is mechanically held or improperly wired.
The offline case is the design, not the exception. The approved specification shall say which functions continue locally, which are suspended, and which require an operator. It shall also say whether a locally cached credential may be used after the relevant service becomes unavailable. The project shall not leave the installer to infer that outcome from a generic offline setting.
Recovery is a separate acceptance event. The test shall confirm that the opening returns to its defined state, the controller and strike agree, required events are reconciled, and no duplicate or unintended release occurs. The named owner shall sign the recovery result with the interruption result.
Clause 9 — Test the approved fire alarm interface and egress
A fire alarm interface may connect an approved safety system to the access-control or door-control arrangement, but the selected architecture and signal path shall come from the approved design. The integrator shall not improvise a release connection because the strike has a convenient input. The interface scope, release authority, supervision behavior, reset sequence, and relationship to the exit arrangement shall be identified in writing.
The test plan shall obtain the client’s authorization before exercising the interface. Use the approved test method at the designated interface boundary, and never simulate a fire-alarm release with an unrelated credential command. Record the initiating source, the message or relay transition, the strike and latch response, the door-position response, the controller event, and the restoration behavior.
| Interface question | Evidence to demand |
|---|---|
| Which system initiates the approved release? | Approved interface schedule and drawing |
| Does the interface issue a release or only report state? | Written sequence definition |
| What happens if the interface wiring is interrupted? | Supervision test and approved response |
| What happens if access control sends a conflicting command? | Priority and reconciliation test |
| Is release automatically re-armed after restoration? | Approved reset procedure and observation |
| Which event proves the sequence occurred? | Timestamped source-specific record |
The exit-side arrangement shall be tested as its own condition. A request-to-exit signal tells the system that the exit device was operated; it does not command the strike to release. The plan shall avoid describing that signal as evidence that the fire-alarm interface worked.
CONFIRM-WITH-LOCAL-AUTHORITY: Confirm the fail state, egress arrangement, fire-alarm release sequence, interface scope, reset behavior, and restoration test with the authority having jurisdiction and the client's designated fire-safety approver.
A failed or ambiguous safety-interface result blocks acceptance of the affected opening. It shall not be converted into a conditional pass through a note that says the behavior will be checked later.
Clause 10 — Make the acceptance test repeatable and handover-ready
The electric strike acceptance test shall be repeatable by a competent technician who did not perform the original installation. The evidence package shall contain the door reference, test date, test method, measured values, pass criteria, observed result, instrument or tool reference, installer, witness, and approved drawings in force during the test.
Repeatability shall be demonstrated across the defined operating conditions. Include normal release, the approved power condition, door-position feedback, credential denial, communications interruption, and restoration. After any strike, frame, closer, latch, controller, firmware, interface, or power adjustment, repeat the affected clauses rather than relying on the original result.
| Evidence item | Required content |
|---|---|
| Acceptance-test sheet | Signed result for each clause |
| Measured results | Units, method, clock or instrument, and comparison criterion |
| Event extracts | Door reference, event type, source, and time |
| Installation record | Hardware revisions, adjustment, wiring, and power source |
| Exception record | Cause, owner, due disposition, and retest |
| Handover index | Location and revision status of every supporting file |
Photographs may support the record but shall not replace a measurement or event. They should show the installed strike, frame relationship, cable route, indicator state, and any defect without capturing credentials, personal access information, or unrelated occupants.
Configuration records matter as much as physical records. Preserve the controller output definition, monitoring interpretation, event mappings, offline rule, and approved safety-interface version. If any value cannot be recovered from the handover package, the opening is not ready for reliable maintenance.
The acceptance sheet should also name the party authorized to change a result, the party who may approve a deviation, and the technician who must execute a retest. A correction made in the field without a revised test record leaves the original failure and its resolution disconnected.
Clause 11 — Govern exceptions without hiding failed evidence
An exception record shall preserve the failed observation, the criterion it failed, the immediate containment, the suspected cause, the accountable owner, the approved corrective action, and the retest result. Do not overwrite the original result with a later pass. The history is evidence that the defect was found, assigned, and closed.
| Disposition | Use | Required decision |
|---|---|---|
| Open failure | Result is outside an acceptance criterion | Block acceptance of the affected function or opening |
| Corrective action pending | Repair is defined but not verified | Name owner and required retest |
| Retest passed | Corrective action has been demonstrated | Preserve both original failure and passing retest |
| Approved deviation | The proposed result departs from the stated criterion | Obtain the designated written approval and rationale |
| Not applicable | The clause does not govern this door | Record the scope basis and approver |
A deviation is not a repair and shall not be used to normalize a result the plan could not achieve. The approving party must have authority over the affected criterion. Safety, egress, monitoring, and fail-state deviations require the designated safety or client approver, not only the installer or integrator.
Root-cause work should identify whether the defect came from a requirement, product document, installation, configuration, interface, test method, or operating condition. Correct the source as well as the symptom. If the failure resulted from ambiguous wording, amend the requirement and identify other openings affected by the same clause.
No affected clause closes until the retest uses the same method and acceptance basis as the original test. A changed test method creates a new result that must be reconciled with the previous evidence. The contract administrator shall track the exception to closure and confirm that the handover index includes the complete history.
Acceptance dossier: the one-page decision for each opening
A complete electric strike selection test plan ends with an auditable decision rather than a general observation that the door works. The following record should summarize the detailed evidence without replacing it.
| Field | Entry required |
|---|---|
| Door reference and drawing revision | Unique opening identifier |
| Selected strike and installed components | Exact identified items |
| Approved role and fail state | Approval source and revision |
| Mechanical, electrical, timing, and force results | Pass, fail, or approved deviation with evidence reference |
| Access-control and degraded-mode results | Scenario-level result |
| Safety-interface result | Authorized witness and approval record |
| Event and clock verification | Clock owner and sample records |
| Open exceptions | Owner and required retest |
| Final disposition | Accepted or not accepted, signed and dated |
The final commercial action should be equally disciplined. Before a production order or final payment, send the completed clause sheet, door schedule, and exception register to the selected supplier for written confirmation against the exact proposed SKU and installation configuration. Give the integrator a signed list of unresolved conditions, and give the client an evidence package that identifies which openings are ready for service.
The buyer’s request is simple: do not accept a strike because its intended behavior appears on a datasheet. Demand the installed-door result, the failure result, the interface result, the records, and the named owner for every unresolved condition. That is what turns electric strike selection into controlled acceptance rather than hopeful commissioning.
The requirement is ready for request a quote once it is written down.

