The Evidence a Site Acceptance Criteria Record Needs
This article follows site acceptance criteria measurement past the invoice, because that is where most lock problems are decided. Handing over a smart-lock installation is not complete merely because the lock responds, a checklist has been marked, and someone has signed a sheet. The handover decision must remain understandable when the people who performed the work are unavailable.
Direct answer. The short answer is that site acceptance criteria measurement is not one decision. It is a sequence. This article takes site acceptance criteria measurement from site acceptance criteria measurement through site-acceptance-criteria to the record you keep. A site acceptance criteria measurement sets out the maintenance record for a system in service. site acceptance criteria measurement carries the early-warning signal for site acceptance criteria measurement.
site acceptance criteria measurement is used here in the sense given under site acceptance criteria measurement. It is a working definition of site acceptance criteria measurement that carries no regulatory weight. The buyer still has to check it against the dated product page.
- Set the period — define how often site acceptance criteria measurement is inspected
- Set the alarm point — name the condition that forces a change to site-acceptance-criteria
- Record the measure — keep one metric that shows clause make acceptance record is healthy
- Treat this as the site acceptance criteria measurement sequence, with site acceptance criteria as the reference.
The discipline of site acceptance criteria measurement supplies that continuity. It connects an identified door, an agreed criterion, a repeatable test, a dated observation and an authorised decision. The resulting site acceptance record is not a decorative certificate; it is the working evidence that a particular condition was tested at a particular point in the installation programme.
This clause handbook defines what that evidence must contain and how a Facility Manager can challenge an incomplete record without reopening every completed test.
Clause 1 — Make the acceptance record an evidence chain
An acceptance decision is only traceable when each part points to the next. Start with the five records below and treat a missing connection as an incomplete record.
| Record element | Question it answers | Minimum trace |
|---|---|---|
| Object | Which door and unit were tested? | Object-schedule identifier, location and installed-unit reference |
| Criterion | What condition had to be met? | Agreed wording, version and source of any stated threshold |
| Method | How was the condition tested? | Test steps, starting condition, tool or evidence source |
| Observation | What actually occurred? | Dated result, reading, image or other supporting record |
| Decision | What was concluded? | Named decision, authority, date and linked exceptions |
The site acceptance criteria measurement is the controlled conversion of an agreed criterion into that dated observation and decision. It is separate from the criterion itself. A criterion says what must be true; the measurement says how the buyer will determine whether it is true. The observation says what happened during the test. The decision says what the authorised party concludes from the observation. The range this procurement eventually buys from is the smart door locks.
This separation prevents two common failures. The first is treating a successful action as a successful result: a technician operated a handle, but the criterion may concern latch engagement from a stated door position. The second is treating a result as a criterion: a reading may show what the instrument displayed, but the agreement must state how that reading maps to acceptance.
An acceptance criteria record becomes evidence when another authorised reviewer can follow the chain without asking the original tester to remember what happened.
Clause 2 — Bind the result to the door and installed configuration
A result detached from its object is not usable acceptance evidence. The record must identify the door through the controlled object schedule, not only through a room label, customer-facing name or informal description. Include the frame or opening reference where location labels are reused. If several units serve one opening, identify the installed unit as well.
Record the model and variant from the physical label or the dated catalogue row. For any criterion that depends on a model-specific feature, dimension, read distance, cycle count, battery duration or other stated capability, confirm on the dated product page for the specific SKU. The label also supports a useful consistency check: if the procurement schedule, delivered equipment and field label do not describe the same variant, resolve that difference before recording a result.
As-built configuration evidence closes the remaining identity gap. It should show the configuration that existed when the test occurred, including the relevant access routes, administrative settings and any change made during commissioning. The exact fields depend on the agreed installation scope, but the record should identify the configuration source, version or change reference, and date of the setting used.
A site acceptance record must also state what changed. If a unit, credential, configuration item or door component was replaced during commissioning, preserve the original test entry and link it to the revised entry. Never overwrite the earlier result as though the door remained unchanged.
Before handover, an observer should be able to match the record to the physical door and the installed configuration without relying on an installer’s memory. That is the purpose of the site-acceptance-criteria identifier: it holds the evidence chain together when a site schedule, a product label and a field test all need to be reconciled.
Clause 3 — Capture the condition that existed before the test
An observation has little meaning without its starting condition. The record must state the conditions likely to influence the result, and it must do so before the result is interpreted. This prevents a convenient baseline from being reconstructed after an unexpected outcome.
For door acceptance testing, the starting condition may include the door’s closed or open position, handle movement, latch or bolt position, visible alignment condition, and any mechanical interference observed by the tester. If the test depends on power or communications, state the condition shown at the test point and the check performed. If it depends on the building context, record that context rather than leaving it in the tester’s notes.
| Condition to capture | Example record entry | Reason for retaining it |
|---|---|---|
| Door mechanics | Closed position, handle movement, visible latch or strike contact | Separates an installation condition from the unit response |
| Power or connection state | State shown and check performed at the door | Identifies the path being tested without assuming a cause |
| Access state | Temporary test arrangement and affected user groups | Shows how continuity was controlled during door acceptance testing |
| Relevant site context | Only conditions that can affect the agreed criterion | Supports repeatability without creating irrelevant detail |
Record an inconvenient condition rather than normalising it away. The tester may then determine whether it falls within the criterion, requires an exception, or requires the agreed method to include that condition. Silence on the starting point leaves the reader unable to distinguish a product result from a site condition.
Where an acceptance test touches locally governed access, egress, accessibility or life-safety requirements, confirm the scope and the responsible approving authority before treating the result as a compliance record.
CONFIRM-WITH-LOCAL-AUTHORITY: Confirm which local requirements apply to the specific site and test, which authority is responsible for sign-off, and which evidence must accompany that decision.
Clause 4 — Fix the method before the result is recorded
The test method belongs in the acceptance agreement or approved site-acceptance-criteria schedule. It should identify the sequence of actions, the controlled variables, the result to be observed, the evidence source and the treatment of a repeated or inconclusive result. A tester should be able to follow it without relying on personal technique or an undocumented interpretation.
Include the following when they apply to the installation:
- The door position and mechanical state at the start.
- The specific operating action or access path being tested.
- The instrument, application view or evidence method used.
- The observation field and the unit in which it is recorded.
- Whether a repeated test is permitted and how its outcome is treated.
- The condition that makes the result inconclusive rather than failed.
Do not import a universal pass threshold into a project agreement. If the criterion uses a tolerance, proportion, reading or other threshold, identify its source, calculation and approved version.
The flow below keeps method, evidence and decision separate while allowing an exception to return to a documented closure step.
flowchart TD
A[Identify the door and acceptance criterion] --> B[Record the starting condition]
B --> C[Run the agreed test method]
C --> D[Capture the dated observation]
D --> E{Does the record support the result?}
E -- Yes --> F[Record the acceptance decision]
E -- No --> G[Record the exception and owner]
G --> H[Rectify or retest the condition]
H --> D
F --> I[Preserve the signed record]
Each arrow should correspond to a field in the completed record. A flow diagram is useful during training, but the completed evidence remains the dated record for each door. A diagram cannot substitute for the method, observation or sign-off it describes.
Clause 5 — Preserve the raw observation beside the interpretation
Field records often combine what the technician saw with what the technician concluded. That combination is convenient, but it weakens later review. Preserve the raw observation, the interpretation and the resulting decision as separate entries.
The observation should use the technician’s own words alongside any measured value. For example, “latch stopped short of the strike” is an observation; “motor fault” is an interpretation that requires supporting tests. If a configuration screen, instrument reading or image supports the conclusion, reference it in the same entry.
Evidence traceability depends on consistent references:
| Evidence item | What to capture | Limitation to state |
|---|---|---|
| Image | Door identity, test point, context and capture time | An image alone may not show the complete method |
| Reading or log | Source, reading, date and time, and export reference | Preserve the source rather than only the typed result |
| Witness note | Name or role, what was witnessed and test context | A recollection does not replace a technical measurement |
| Configuration export | Source, version or change reference and export time | It captures settings, not the complete physical condition |
| Test note | Ordered actions, starting condition and exact observations | Informal notes need a defined link in the record |
A negative result needs the same discipline as a positive one. If a test produces no response, an inconclusive reading or an unavailable evidence source, record that fact and the checks already performed. Do not leave the field blank, because an empty field cannot distinguish an untested item from a test with no observable result.
The complete record should show what each check ruled out before the tester moves to another hypothesis. That sequence is particularly important where mechanical interference, power state, configuration state and credential behaviour can produce different outward symptoms. It keeps the acceptance record useful for later service triage rather than reducing it to “passed” or “failed”.
Clause 6 — Turn every deviation into a controlled exception
A deviation is an observed difference between the agreed criterion and the recorded result. It becomes manageable when the record identifies its scope, owner and required disposition. Without that structure, an incomplete test and an accepted condition can look identical on a handover sheet.
Each exception should contain:
- A unique exception reference linked to the door and test record.
- The criterion not met or not yet proven.
- The dated observation and supporting evidence.
- The immediate operating control, if any.
- The required disposition: rectify, retest, accept with an objective condition, or do not accept.
- The responsible role and the target date or event for closure.
- The closure evidence and the authority that accepted it.
| Exception status | Required entry | What permits movement to the next status |
|---|---|---|
| Open | Criterion, observation, impact and owner | Evidence that the issue has been assessed |
| Rectification in progress | Action started and affected configuration or part identified | The action is complete and the affected scope is stated |
| Ready for retest | Retest method and starting condition | A new dated observation is recorded |
| Closed | Closure evidence and closing decision | The authorised reviewer accepts the closure |
| Deferred by formal decision | Reason, operating condition and review trigger | The deferred scope remains visible in handover evidence |
Conditional acceptance requires an objective condition. “Monitor it” is not a closure criterion. “The opening may remain in service only while the latch engagement condition described in exception EX-01 is present, and the condition must be rechecked at the review event stated in the record” is testable. The acceptance criteria record should also identify any criteria that the project has decided cannot be made conditional.
The supplier’s role should also be written as an evidence request rather than an assumed promise. Ask what written support process applies, what product information can be provided and what remains the installer’s responsibility.
CONFIRM-PER-SUPPLIER: Obtain the supplier’s written support and evidence process for the exact SKU, including the records it can provide for installation, configuration and handover; confirm which activities remain the installer’s contractual responsibility.
Clause 7 — Assign decision rights and capture the sign-off
A signature has little evidential value if the record does not show what the signer was authorised to accept. The acceptance record should identify the prepared, checked and accepted roles separately, even when one person holds more than one role in a small installation.
| Decision | Installer or tester | Facility or site representative | Supplier representative | Authorised acceptance authority |
|---|---|---|---|---|
| Record the method and observation | Performs and signs the test entry | Confirms site context | Provides agreed product information when requested | Confirms completeness |
| Verify the evidence chain | Supplies readings and references | Checks door identity and exception links | Responds to product-specific evidence questions | May reject an incomplete chain |
| Accept a criterion | Recommends the result | Confirms operational context | Provides support evidence within the agreed scope | Accepts, conditionally accepts or does not accept |
| Close an exception | Performs the action and records the result | Confirms the operating control | Supports diagnosis where the agreement places it with the supplier | Authorises closure or directs a retest |
The acceptance authority should be identified by role and, where practical, by named individual. The signature must state the outcome: accepted, accepted with the listed conditions, or not accepted. A signature alone leaves the reader to infer the decision.
For electronic signatures, retain evidence of the signer’s identity, the date and time, and the record version signed. If approval occurs through a workflow, retain the workflow event and its audit trail. A message in a general communication channel may acknowledge receipt, but it should not silently become the acceptance record unless the project agreement explicitly defines that mechanism.
Acceptance also has boundaries. State the criteria version, doors or openings covered, exceptions included and any conditions attached. Acceptance of one door must not be copied into another door’s record merely because the product and test method are similar.
Clause 8 — Control corrections, retests and changes after sign-off
Even a sound acceptance record can be affected by later corrections. Preserve the signed version and manage every subsequent change as a traceable event. A visible amendment is stronger evidence than a cleaner file with no history.
An amendment should identify the original entry, the changed field, the reason for the change, the person making it, the date and the approving role. A correction made because the original transcription was wrong should preserve both the original text and the correction. An amendment made because the test result changed belongs in a linked retest record, not in an edited result field.
| Event | Required record | Effect on acceptance |
|---|---|---|
| Transcription correction | Original value, corrected value, reason and approver | Original evidence remains visible |
| Physical or configuration change | Part, setting or asset reference, reason and affected test | Linked retest establishes the revised state |
| Revised criterion | Criterion version, reason, approval and effective scope | Prior results remain linked to the old version |
| Retest | Original exception, method, starting condition and new observation | Closure is visible only after authorised review |
| Partial withdrawal of acceptance | Affected door, scope, reason and replacement status | The handover register reflects the change |
If the test conditions change, state whether the retest remains comparable with the original method. If a unit or configuration is replaced, link the old and new unit references and repeat any criterion affected by that change. Where a new criterion version applies, ask the agreement owner whether earlier results are carried forward and record the answer.
Do not delete superseded media, logs or configuration exports merely because a new test passed. The purpose of the record is not only to show that the door eventually passed. It is to show which condition changed, what was retested and who accepted the revised evidence.
Worked record — D-17 from observation to closed exception
The following entry is illustrative. It demonstrates the structure of the acceptance criteria record without representing a named site, client or product performance claim.
| Field | Illustrative entry | Evidential purpose |
|---|---|---|
| Record reference | ACC-D17-001 | Connects the door to its test and decision history |
| Object | Door D-17 from the controlled object schedule | Removes reliance on an informal room name |
| Installed configuration | Configuration change reference CF-D17-04, exported before testing | Establishes the configuration used during the test |
| Criterion | From the stated closed position, the latch engages without forced intervention and the configured access path completes | Defines the condition rather than an action |
| Starting condition | Door closed; handle returned freely; visible contact observed at the latch and strike | Preserves the condition that may influence engagement |
| Method | Close from the stated position, observe engagement, then complete the configured access path | Makes the test repeatable |
| First observation | Latch stopped short; image IMG-D17-01 and note OBS-D17-01 attached | Preserves the raw result without assigning a cause |
| Interpretation | Mechanical interference may affect engagement; further check required | Separates hypothesis from observation |
| Action | Release the identified mechanical preload under the approved procedure and repeat the same method | Links intervention to the original result |
| Retest observation | Latch engaged; configured access path completed; IMG-D17-02 attached | Shows the outcome after the condition changed |
| Exception | EX-D17-01 opened for the first observation and closed against the retest evidence | Preserves the deviation rather than hiding it |
| Decision | Accepted against criterion version AC-03; acceptance authority signed the record | Connects the final result to an authorised decision |
The worked entry proves that the agreed method was run against a defined starting condition and that the later result followed a recorded intervention. It does not prove that every similar door will produce the same observation, nor does it identify a product cause. Those limits are useful because they keep the facility manager from generalising beyond the evidence.
The example also shows why the starting condition belongs beside the final observation. Without it, the retest could be mistaken for proof that the original installation was acceptable. With it, the reviewer can distinguish the original condition, the intervention and the evidence that followed.
Decision comparison — acceptance states and required handover
The facility manager needs a decision vocabulary that remains consistent across doors and sites. Use the following comparison in the site agreement and apply it to each completed test.
| Decision state | What the facility manager may record | Required handover evidence | Effect on the door |
|---|---|---|---|
| Accepted | The stated criterion was met | Object, criterion version, method, dated observation and authorised sign-off | The opening enters the accepted operating scope |
| Accepted with conditions | A named deviation is accepted under an objective operating condition | Exception, immediate control, responsible role, review trigger and authorised decision | The scope remains limited and the exception stays active |
| Retest required | The method was run but the evidence does not establish the criterion | Observation, incomplete or failed checks, required change and linked retest record | The opening remains outside final acceptance until the retest is decided |
| Not accepted | The criterion was not met or could not be proven | Failure evidence, impact statement and disposition authorised by the project | The door does not enter the accepted operating scope |
This is a decision-comparison table, not a scoring model. A project may add decision states, but it should define the evidence and authority for each one. The handover evidence must make clear whether a state applies to one criterion, one door or a wider group.
Do not turn conditional acceptance into full acceptance by changing the vocabulary in a later summary. Likewise, do not carry an exception into the operational register without preserving its reference in the acceptance record. For contractual allocation of these decisions and evidence duties, use the structure in Site Acceptance Criteria: Contract Clauses that Make It Work.
Before acceptance, the site survey should also have resolved the physical and operational facts that the test will depend on. The distinction between Office Smart Lock Site Survey and Smart Lock Retrofit Site Survey matters because an existing opening and a retrofit opening can present different baseline conditions even when the same acceptance criterion is used.
Audit the record by retracing its decisions
An audit of acceptance evidence should not begin by counting completed boxes. It should retrace a decision from the signed outcome back to the object, criterion, method and observation. If one of those links cannot be reached, the record reveals a gap even if every field appears completed.
Use the following audit questions against a sample selected from different installers, doors and acceptance stages:
- Can the object identifier be matched to the physical door and object schedule?
- Can the criterion be matched to its approved version?
- Can another competent tester understand and repeat the method?
- Does the dated observation support the recorded result without relying on interpretation alone?
- Can every exception be traced from opening through closure or authorised deferral?
- Does the signatory hold the authority stated for that decision?
- Does the final register reflect every later correction, withdrawal or retest?
| Audit question | Evidence that supports the decision | Warning sign | Corrective action |
|---|---|---|---|
| Object identity | Schedule ID, location and installed-unit reference agree | Only a room name appears | Reconcile against the controlled schedule |
| Criterion control | Version and source of the condition are present | Tester used a remembered threshold | Restore the approved criterion version |
| Method repeatability | Ordered steps and starting condition are recorded | Notes list actions without sequence | Obtain the tester’s method record before relying on the result |
| Observation integrity | Raw value or image is attached and traceable | Conclusion appears without source | Separate observation from interpretation and request evidence |
| Exception control | Owner, disposition and closure link are complete | Open item disappears from summary | Restore the exception reference and status |
| Authority | Role and signature match the decision | Signer role is absent | Obtain confirmation from the authorised decision owner |
| Change history | Original and amended versions remain visible | A signed PDF has overwritten fields | Preserve history and reissue a controlled record |
A useful companion is the Site Acceptance Criteria: A Field Worksheet to Complete. The worksheet helps collect the fields; this handbook defines why those fields form evidence. The broader Site Acceptance Criteria Documentation Set can hold the forms, registers and controlled attachments, while the record itself remains the door-level proof.
For programmes still selecting equipment or support terms, the separate pre-purchase evidence review in Site Acceptance Criteria Evidence to Request Before You Buy is relevant. Pre-purchase evidence cannot replace the observation made after installation, but it can reduce ambiguity about what the installation team is expected to test.
Close the handover with a usable acceptance packet
The handover package should let the operating team locate every decision without reconstructing the programme. At minimum, include a record register, the approved criterion versions, completed door records, the exception and retest file, the signed decision log, and an index of configuration, image, reading and witness references.
The practical counterpart to this point is slk 9936s battery and power. That is the same question site acceptance criteria measurement has to answer here.Keep the register separate from the detailed records, but connect them through stable references. A summary can state that door D-17 was accepted with one closed exception; it should not replace the underlying method, observation and closure evidence. The operating team also needs to know which exceptions remain active and what event triggers their review.
Facility managers can use these clauses as the handover evidence request issued to an installer or supplier. Apply the same field structure to every door so that exceptions, corrections and operating decisions remain visible.
A completed acceptance record should allow another authorised reviewer to reach the same conclusion from the file itself, without oral explanation or an assumption that a similar door produced a similar result.
Close the loop with requesting a quote.

