Credential Not Recognised Worksheet: What to Write Down and Why
Use this credential not recognised worksheet when a person reports that an issued credential has been rejected at an installed lock. The worksheet turns a smart lock access fault into an operational record: it identifies the credential and door, preserves the state before anyone changes it, and shows which checks were performed in which order.
Direct answer. In short, credential not recognised worksheet is the subject of this piece. credential not recognised worksheet is where the work on credential not recognised worksheet sits. credential-not-recognised is what has to be evidenced before anyone signs. A credential not recognised worksheet is a lifecycle guide. It starts where the invoice ends. credential not recognised worksheet is what has to be measured to keep the credential not recognised worksheet record usable.
credential not recognised worksheet means here what credential not recognised worksheet sets out. It is a working definition of credential not recognised worksheet for this market and product. It is drawn from the evidence below, and it is not a general marketing phrase.
The purpose is not to turn a facility technician into a product diagnostician. It is to make the next action defensible. A complete record should let an access administrator see whether the credential was active, let a technician repeat the test, and let a supplier assess model-specific guidance without relying on a verbal description.
graph TD
A[Reported credential rejection] --> B[Protect access and preserve credential state]
B --> C[Capture credential and door identity]
C --> D[Run checks in fixed order]
D --> E[Select and record the branch]
E --> F[Assemble field service evidence]
F --> G[Record recovery and repeat test]
G --> H{Intended credential path restored}
H -->|Yes| I[Close the incident]
H -->|No| J[Escalate with the evidence packet]
J --> G
I --> K[Maintain the incident log]
Use the worksheet alongside the How to Measure and Record Credential Not Recognised when measurement evidence is required. For teams extending the same procedure across buildings, the Running Credential Not Recognised Across Several Sites provides a portfolio-level frame.
Runbook trigger and required output
Trigger the runbook when any user-facing credential is rejected, including a credential that appears in the issuing system but does not open the intended door. The report may arrive by telephone, email, radio, an operator console or the organisation’s incident system. Whatever the channel, open one record against the door or access-point identifier rather than against a room number or a person’s name. The earlier published note on this is Fingerprint Smart Locks for Facility Managers. The catalogue side of this is the smart door locks.
The credential not recognised worksheet produces six outputs:
- An incident header with stable door, unit and credential references.
- The reporter’s symptom, kept separate from the technician’s observation.
- The credential and entitlement state before any change.
- An ordered test log stating what each check ruled out.
- The recovery action and the evidence that the intended access path worked again.
- An escalation packet if the fault remains open or requires model-specific support.
This credential not recognised runbook also serves as the credential troubleshooting record for audits, repeat-fault reviews and supplier discussions. Do not place access secrets, full credential numbers or unnecessary personal information in the free-text fields. Record the credential reference needed to identify the record, not the secret used to open the door.
Do not close the incident on “fixed” alone. Closure requires a recorded result, an identified owner for any remaining action and enough evidence for another operator to understand what changed.
Ownership at each handoff
The record should have one accountable owner even when several people contribute. The handoff changes the work; it does not erase responsibility for the open record.
| Role | Primary responsibility | Required handover |
|---|---|---|
| Facility manager | Owns access continuity and final operational acceptance | Confirms the approved access route and authorises closure |
| First-line operator or technician | Captures the symptom, runs checks and records observations | States what was tested and what each check ruled out |
| Access administrator | Confirms credential lifecycle and entitlement records | Records the before-and-after state of any access change |
| Security or site-authority representative | Applies the site’s access-control procedure | Confirms any temporary exception or controlled entry |
| Supplier contact | Provides model-specific guidance against supplied evidence | Confirms what the dated product page and support process require |
If the same person fills several roles, record that fact under “observations by”. It prevents the worksheet from implying independent verification where none occurred.
When an alternate route is needed, use only the documented method approved for that site. Do not assume that a mechanical override, attended entry or temporary credential is available on every door.
CONFIRM-WITH-LOCAL-ACCESS-OWNER: Confirm the site’s approved override, escort and temporary-access procedure before applying any exception.
Protect access before changing the record
Begin with access continuity. Confirm whether the person can enter by another approved route, whether the door can remain in its scheduled operating state and whether an occupied or access-sensitive space needs immediate assistance. Record the temporary measure, its owner and the condition that will end it.
Before revoking, reissuing or editing a credential, capture its current state. A state change made at the start of the investigation can erase the evidence needed to distinguish an entitlement issue from a reader or door issue. If the record is already changed, state who changed it, what they believed the reason was and where the prior state can be seen.
Do not reset several nearby doors or replace a unit simply because one credential was rejected. Those actions may destroy useful comparisons. The Clause Bank: Common Mistakes in Credential Not Recognised explains why broad changes can turn one report into an uncontrolled recovery effort.
Keep door access recovery separate from fault replacement. If the approved alternative route restores the person’s entry while investigation continues, record that outcome as an interim control, not as proof that the credential path works.
Capture the credential and door identity
Write identifiers exactly as they appear in the controlled schedules. The table below shows the minimum identity record and the reason each field matters.
| Field | What to write | Why it matters |
|---|---|---|
| Door or unit identifier | Object-schedule ID for the door or access point | Connects the incident to the installed asset rather than a room description |
| Model and variant | Exact label entry | Prevents features or instructions being carried across unlike units |
| Credential reference | Controlled reference and credential type as displayed | Distinguishes the tested credential from the reported one |
| Issuing record | Relevant account or person reference, using minimum necessary data | Allows the access administrator to trace the record without exposing secrets |
| Door mapping | The access point shown in the credential entitlement | Separates a credential-state fault from a door-mapping fault |
| Report time | Date and time received through the agreed channel | Starts the buyer’s own incident chronology |
| Observation time | Date and time the symptom was observed | Prevents the report time from being mistaken for the failure time |
| Symptom | Reporter’s words followed by the operator’s exact observation | Keeps the original complaint visible after interpretation begins |
| Door state | Locked, unlocked, held open or other recorded state | Provides context for the reader response and operating mode |
| Indicator or console entry | Exact light, sound, message or event shown | Supports comparison with another credential or door |
Read the model and variant from the physical label or the controlled asset record. If a model-specific feature affects the next step, confirm on the dated product page for the specific SKU; do not transfer a capability from a similar unit.
Use “not shown” when the portal or reader supplies no state. Do not turn an absent display into a conclusion such as “offline” or “failed”. The absence may be part of the observation and should remain distinguishable from a confirmed state.
Run checks in a fixed order — credential not recognised
Each check must contain an observation and a rule-out statement. “Checked the badge” is an action, not evidence. “Credential reference C-207 matched the reference in the active entitlement record; the presented credential was therefore the one intended for this test” is a recorded observation that narrows the fault tree.
Use the following order unless the site’s approved procedure requires an earlier safety action. Do not skip a step silently. If a step is not performed, record the reason and the person who authorised the omission.
Confirm identity. Compare the presented credential reference with the reported reference and the issuing record. Record any mismatch. This rules out the possibility that two credentials were discussed as one, but it does not prove that the presented credential is valid.
Run the credential issuance check. Record whether the credential is active, inactive, expired, revoked, pending or not found, using the local system’s exact vocabulary. Capture who confirmed that state and when. This rules out an ineligible credential as the immediate explanation, although it does not exclude a separate reader or door fault.
Confirm entitlement. Record the assigned door, zone, schedule, access level and validity period where those fields exist. Check the intended access point against the entitlement rather than against another door in the same building. This rules out a simple access-map or schedule mismatch when the correct field is absent.
Capture the reader response. Write the exact light, sound, message, event or lack of response. Do not translate “amber flash” into “low battery” unless a dated source for the specific unit supports that interpretation. This step rules out an undocumented response, not the underlying cause.
Compare one variable at a time. Where approved, test another valid credential at the same door and the original credential at another approved access point. Record the controls and results separately. These comparisons help separate credential-record behaviour from door-specific behaviour; they do not identify the component responsible.
Check the physical and operating context. Record door alignment, obstruction, scheduled state and visible reader condition only when these can be observed safely. Do not infer that the credential subsystem is defective because the door is misaligned.
Check power and synchronisation context. Record what the unit displays and what the authorised console shows. A status message may justify a defined diagnostic step, but it does not replace the credential checks.
Repeat the intended test. Repeat with the original credential after any approved change, using the same access point and stated conditions. A single successful presentation after a change establishes the observed result; the record must still explain which earlier check ruled out the competing branches.
Keep hypotheses in a separate column from observations. If the technician writes “reader failed” before collecting the comparison evidence, another operator cannot tell whether that is a diagnosis or an expectation. The Credential Not Recognised: Which Branch Do You Take provides a separate way to structure the branch choice.
Select and record the branch
A fault can pass through more than one branch. Record each branch separately rather than forcing the incident into a single label.
| Recorded result | Evidence to preserve | What this rules out | Next recorded action |
|---|---|---|---|
| Credential reference does not match the reported item | Reference comparison and issuer search | A simple mismatch between reported and tested credentials | Correct the reference or repeat with the intended credential |
| Credential is known but not active or not eligible | Current state, reason shown and confirming role | The credential’s present eligibility as the immediate explanation | Refer to the access administrator; preserve the prior state |
| Credential is active but not entitled to the door | Entitlement and door-mapping snapshot | A missing permission for the tested access point | Request an authorised mapping correction |
| Credential is entitled but the reader rejects it | Before-state, response and ordered test log | An absent credential record or missing entitlement | Escalate with the evidence packet |
| Credential works at another approved access point | Successful test location, identifier and timestamp | A portfolio-wide credential-record absence | Compare the failing door’s context and configuration |
| Credential fails at more than one approved access point | Both test records and current entitlement state | A failure isolated to one reader, subject to further evidence | Escalate as a shared-record or shared-service issue |
| Another credential works at the same door | Credential reference and successful response | A complete inability to read any credential at that door | Inspect the door and operating context before replacing a unit |
| No credential is accepted at the door | Response from each tested reference and console state | The hypothesis that one credential record alone explains the report | Escalate with power, context and reader evidence |
| Intermittent result | Timestamped attempts, conditions and exact responses | A stable, always-reproducible result | Keep the incident open until the observation window and owner are recorded |
Write “not established” where evidence does not support a firm conclusion. For example, successful use at another door rules out a complete absence of the credential record, but it does not prove why the original door rejected the credential.
Do not use branch names as a substitute for observations. “Wrong credential” must be followed by the two references compared. “Access issue” must identify the missing or mismatched field. “Reader fault” must identify the checks that failed to support it.
Assemble the field service evidence
Field service evidence should let another person repeat the result or understand why repetition was not possible. Preserve the original file where the source system permits it.
For each item, record its source, capture time and relation to the incident:
- A photograph of the whole door with the object identifier visible.
- A close photograph of the reader or indicator, with the exact displayed state.
- A screenshot or exported view of the credential state and entitlement.
- The technician’s test log, including the checks not performed.
- A note describing the approved recovery action and its result.
- The access administrator’s before-and-after record for any change.
Do not photograph a secret credential value merely to prove possession. If an image is prohibited or unsafe, record why no image was taken and rely on a controlled reading or export. A photo of an indicator can support an observed response, but it cannot prove the credential’s lifecycle state.
Use filenames that connect the evidence to the incident without exposing personal data. A simple convention is the door identifier, incident identifier and evidence type. Retain the source, not only a cropped copy, when local records permit.
The Credential Not Recognised Documentation Set can be used when the incident needs to become part of a wider evidence set. Keep the worksheet as the index so that later additions do not obscure the original test order.
Record recovery and close the incident
A recovery entry must distinguish restored electronic access from temporary physical entry. “Door opened with key” does not show that the credential works; “credential accepted” does not show that every intended door or entitlement now works.
| Recovery measure | Before | After | Evidence reference |
|---|---|---|---|
| Credential state | Exact recorded state | Exact state following the authorised change | Controlled console view or record |
| Entitlement | Door or zone mapping | Revised mapping, if changed | Administrator record |
| Reader response | Exact indicator, sound, message or event | Exact response to the repeat test | Test log and image where applicable |
| Door operability | Method by which the door was usable | Method by which the intended path was restored | Operability timestamp and access note |
| Temporary control | Approved alternate route, if used | How and when the exception ended | Local procedure reference |
Record the date and time the door became operable again, but do not attach a service target or promise to that observation. The buyer’s incident plan sets any target; the worksheet supplies the underlying timestamps.
Before closure, confirm that the original credential was tested where relevant, every check has a rule-out statement, evidence points to the claimed observation, and any access change was authorised. If only an attended or alternate route restored access, mark the credential fault as unresolved and assign the next action.
Escalate without losing the case
Escalate when no branch has adequate evidence, the same symptom appears on more than one door, all tested credentials fail at one access point, the physical unit shows damage, or an authorised correction does not restore the intended credential path.
The escalation message should contain:
- The door or unit identifier and model variant.
- The exact symptom and the time it was observed.
- The credential state and entitlement before testing.
- The ordered checks, each with its result and rule-out.
- The recovery action and its present result.
- Attachments or references for the readings, images and administrator record.
- The specific unanswered question.
Ask the supplier what evidence it requires for a support or return-authorisation review. Confirm what the return route authorises, what must be shipped and what must be returned with the unit. Do not describe a replacement, credit or service outcome as guaranteed.
CONFIRM-PER-SUPPLIER: Confirm the support route, required fault evidence and model-specific diagnostic steps on the dated product page for the specific SKU.
For repeated reports across buildings, use the same evidence fields so the facility team can compare patterns without merging unlike doors. The Credential Not Recognised Training Outline is useful when several operators must use the worksheet consistently.
Maintain the access credential incident log
The access credential incident log is the index of individual worksheets and their evidence. Keep the door identifier, incident identifier, current owner, state, evidence location and next action. It should show the chronology without replacing the individual records.
Use the buyer’s own definitions when calculating operational measures:
| Measure | Definition from the records | What it does not establish |
|---|---|---|
| Response time | From the agreed report channel receiving the fault to acknowledgement | Whether anyone attended the door |
| On-site attendance time | From acknowledgement to the recorded attendance at the door | Whether the fault was corrected |
| Resolution time | From fault report to the door being operable again | Why the interval occurred |
| MTTR | Mean resolution interval across a defined population and period | The tail of the distribution or unreported cases |
| Availability | Operable time divided by scheduled time for a stated population and period | Whether the population reflects the doors that matter |
| First-time fix | A visit ends with the door operable and no repeat visit for the same symptom | Whether the underlying cause was identified |
| Repeat rate | Share of failures that return within a stated window | The severity of each fault |
Always record the population, period and window used for a measure. Never place a target in the observation field or present a calculated measure without its denominator. The worksheet supplies consistent inputs; the facility team computes and interprets the results.
Worked example of a completed record
The following example is illustrative. It uses placeholder identifiers rather than an actual site or customer.
Door D-014 and access point AP-03 use credential reference C-207. The reporter states: “This credential worked at the staff door earlier and is now rejected at AP-03.” At the door, the operator records the lock state, the exact reader response and the existing entitlement snapshot before changing anything.
The practical counterpart to this point is smart lock replacement without door modification. That is the same question credential not recognised worksheet has to answer here.
| Step | Observation | What it rules out | Result |
|---|---|---|---|
| Identity comparison | C-207 matches the credential reference in the reported entitlement record | A mismatch between the reported and tested references | Proceed |
| Credential state check | C-207 is active in the issuing record | An inactive or revoked credential as the immediate explanation | Proceed |
| Entitlement check | C-207 is mapped to AP-02 but not AP-03 | An existing door mapping for the tested access point | Request authorised mapping correction |
| Same-credential comparison | C-207 is accepted at AP-02 | A complete absence of the credential record | Preserve comparison result |
| Another-credential check | A credential mapped to AP-03 is rejected | The possibility that any credential works at AP-03 | Escalate the door-specific observation |
The access administrator captures the mapping before the correction, applies an authorised request for AP-03 and exports the updated state. The operator then repeats the test at AP-03. The recorded result is an accepted response from C-207, and the door is operable through the intended credential path.
Readers comparing approaches usually start with the smart lock battery technology. That is the same question credential not recognised worksheet has to answer here.The worksheet conclusion states: “Entitlement mapping did not include AP-03. The credential was active and accepted at AP-02. After the authorised mapping correction, the same credential was accepted at AP-03.” It does not claim that the reader was defective, because the recorded comparison does not establish that conclusion.
The recovery entry links the administrator’s before-and-after records and the repeat-test result. The incident can then close with the door identifier, test order, cause supported by the evidence and recovery action intact.
Supervisor closeout checklist
Before accepting the worksheet, the facility manager should confirm that:
- The door, unit and credential references are stable and controlled.
- Report and observation times are both recorded.
- The symptom is separated from the diagnosis.
- Every performed check states what it ruled out.
- Any skipped check has a reason and owner.
- Credential state and entitlement were captured before changes.
- Evidence supports each material conclusion.
- Recovery identifies how the intended access path worked.
- Temporary controls have a recorded end condition.
- Open actions retain an owner and next review point.
Use the same worksheet when asking a supplier for model-specific help. Provide the observations and dated product-page reference, then ask which additional evidence the supplier needs. This keeps the request anchored in recorded facts rather than a loosely applied fault label.
The next step is to request a quote.

