Complete a field-ready site acceptance criteria worksheet to verify door readiness, test access paths, capture evidence, and assign closure actions.

Publisert tidligere: sep 04, 2024

Site Acceptance Criteria: A Field Worksheet to Complete

Site Acceptance Criteria: A Field Worksheet to Complete

Use a site acceptance criteria worksheet to convert installation handover into an evidence-based release decision for each smart-lock door. Rather than accepting a visual walk-through, the worksheet names the condition to be demonstrated, the evidence required, the person responsible for the result, and the action that remains open when the door is not ready. This is a post-award operations record: it governs the transition from installation work to normal use.

Direct answer. The one-line answer — site acceptance criteria worksheet is the working record for site acceptance criteria worksheet. site acceptance criteria worksheet is worthless until site-acceptance-criteria is attached to it as evidence. A site acceptance criteria worksheet is a lifecycle guide. It starts where the invoice ends. site acceptance criteria worksheet is what has to be measured to keep the site acceptance criteria worksheet record usable.

site acceptance criteria worksheet means here what site acceptance criteria worksheet sets out. It is a working definition of site acceptance criteria worksheet for this market and product. It is drawn from the evidence below, and it is not a general marketing phrase.

  • Set the period — define how often site acceptance criteria worksheet 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 control worksheet as handover is healthy
  • For site acceptance criteria worksheet, the order below is fixed and site acceptance criteria is the reference point.

The smart lock handover checklist must remain specific to a door, not just a model or building. A single line such as tested and working cannot show what was tested, which operating state was observed, or whether an exception was closed. Keep the door identifier aligned with the object schedule, then attach photographs, readings, configuration records, or other agreed evidence to the same site-acceptance-criteria record.

Complete one set for every door in the handover scope. Separate physical readiness, access administration, and operational release so that a technical pass is not mistaken for a final site decision. The worksheet may be copied into the work order or controlled as a standalone form; the critical requirement is that the completed copy can reconstruct the acceptance decision later.

1. Define the decision before testing starts

A site acceptance criteria worksheet is useful only when its final states are unambiguous. Use one of the three decisions below for each door. Do not create vague outcomes such as minor issue, to follow, or generally satisfactory; each phrase leaves the next operator to infer whether the door may enter normal service.

Decision stateRequired evidence stateOperational effectRequired record action
Ready for serviceEvery mandatory check for the door has a pass result and its supporting evidence is linked.The handover lead may release the door to the operating team.Sign the sheet and record the acceptance timestamp.
HoldAt least one mandatory check remains open, or the door has not demonstrated the required operability.Do not treat the door as accepted; keep temporary access arrangements under the site’s approved plan.Open a snag with an owner and due date.
Escalate for reviewA result conflicts with the approved design, required evidence is unavailable, or the same symptom appears on comparable doors.Pause the affected acceptance scope until the decision authority reviews the evidence.Record the question, supporting evidence, and review outcome.

A pass applies only to the checks and conditions recorded on that sheet. It is not a conclusion about future performance, and it does not transfer responsibility for later maintenance to the acceptance team. Equally, a hold does not automatically mean that the lock must be replaced. The recorded observation determines whether the door needs adjustment, configuration work, further testing, supplier evidence, or a formal design review. The catalogue side of this is the smart door locks.

2. Control the worksheet as a handover record

Give the worksheet a document identity before testing begins. This prevents observations from different doors, revisions, or handover rounds being merged into one incomplete record.

Header fieldEntry rule
Worksheet ID and revisionUse a unique controlled reference and show which revision was completed.
Door or object identifierMatch the identifier to the approved object schedule rather than using a room name alone.
Model and variantRecord what appears on the physical label and the corresponding product record.
Dated product-page referenceCite the page used to set any model-dependent acceptance condition.
Handover packageIdentify the design, configuration baseline, and credential matrix used for the test.
Test rolesName the technician, credential owner, site reviewer, and any product specialist.
Evidence locationState where photographs, readings, exports, and signed records are stored.

For any threshold that depends on dimensions, door preparation, power input, read range, cycle count, finish compatibility, emergency input, or a named access method, confirm on the dated product page for the specific SKU. Do not copy a value from another model, another site, or an earlier project revision. The header should identify the source so a later reviewer can distinguish an approved condition from an undocumented assumption.

CONFIRM-PER-SUPPLIER: Confirm the documented handover tasks, configuration evidence, and product references applicable to the supplied model and variant.

3. Gate the start of testing on handover readiness

A technician should not invent missing acceptance criteria at the door. Before beginning, check that the handover package contains:

  • The current object schedule and unique identifier for each door.
  • Approved design criteria and project-defined pass or fail rules.
  • The model, variant, and dated product-page references in scope.
  • Approved credential methods and the role or permission matrix.
  • The plan for transferring administrative access to the operating team.
  • Agreed evidence formats, file naming, and storage location.
  • A written route for product questions, deviations, and unresolved observations.

If an input is missing, mark the relevant test as held or not verified rather than quietly filling the gap from memory. The worksheet can still record physical observations, but the final decision must show that the missing input prevented full verification. This protects the operating team from mistaking an untested function for a failed function and prevents a supplier question from being lost between the site and the project office.

Keep the request for missing evidence specific. Identify the door, the criterion affected, the information required, and the decision waiting on that information. A general request to confirm the product is insufficient because it does not say which condition must be established.

4. Establish the door-specific physical baseline

Start with identity and physical readiness before testing electronic functions. The technician should record observations against the unique door identifier, not simply mark each item as acceptable.

Check and record the following:

  • The physical label matches the model and variant listed for the door.
  • The door, frame, strike, latch, and related moving parts show no visible damage or obstruction.
  • The door closes and latches from the positions required by the approved design without forcing.
  • The handle and other approved operating parts move freely through their expected travel.
  • Alignment does not leave the lock preloaded against the door or frame.
  • The installed position matches the approved door schedule and intended operating direction.
  • No visible installation condition prevents a safe test of the access path.

Record what was observed, not merely whether a check passed. For example, record the movement seen, the starting position, and whether force was required. Do not set acceptance thresholds from memory.

Use the Office Smart Lock Site Survey and Smart Lock Retrofit Site Survey as planning inputs where an existing door or retrofit condition needs assessment. Those survey records help define the handover question; they do not replace the door-specific acceptance result.

5. Run functional checks in a sequence that separates causes

A failed function should lead through an ordered test sequence, not directly to a replacement instruction. The order below helps the technician identify what each observation rules out for the current visit.

OrderCheck at the doorWhat a pass or useful result indicates for this visit
1Confirm the visible operating state and whether the handle moves freely.Separates a preloaded or obstructed door from a later electronic or drive symptom.
2Test the approved manual path, if the specific SKU provides one.Helps distinguish a freely moving mechanism from a failure that appears only through the electronic path.
3Read the local indicator and relevant administrative view, if each is present in the supplied configuration.Separates a stated alert from no visible response or an unexpected state.
4Check the power source in the manner approved for that installation.Identifies a simple power-state issue without assuming the cause of every subsequent symptom.
5Compare the physical door state with the state recorded by the controller.Reveals a mismatch that belongs in configuration or synchronization review.
6Test the approved credential or other access path and observe the response.Locates the issue to the access, authorization, or response layer where evidence permits.
7Compare the observation with a comparable door using the same approved configuration.Helps distinguish an isolated door condition from a pattern that needs broader review.

Write both the result and the reason for moving to the next check. A record that says battery checked, app checked, door aligned contains actions but not diagnostic evidence. The more useful entry explains what the observation ruled out and what remained unresolved.

If a check cannot be completed because the door, configuration, evidence, or approved test identity is unavailable, record that limitation. Do not convert a missed test into a pass, and do not infer a component cause from a symptom alone.

6. Verify access administration and event handling

Complete door acceptance testing in the sequence defined by the approved operating procedure. Test each credential method that the door is intended to use, without assuming that every installed lock supports the same methods.

For each approved access path, record the test identity, the expected result, the observed result, and the authorization state before and after the test. Confirm that an enabled path behaves as intended for the approved role. Where a denied result is part of the test, use a designated test identity and preserve the expected and observed outcomes rather than relying on verbal assurance.

The credential owner should also confirm the administrative handover. Record who receives control of the relevant role, which configuration elements were transferred, and which items remain open. Do not place reusable secrets in the worksheet. The record should point to the approved handover method and identify the completed transfer without reproducing sensitive access data.

Power and alert checks belong in the same functional sequence. An alert can indicate a condition that needs attention, but it does not by itself prove that the door will remain operable through the operating period. Apply the site’s approved route for acknowledging and escalating an alert, and capture that route as part of the operational handover.

7. Build evidence that survives handover

The completed field service record should allow another person to understand the result without relying on the technician’s memory. Link evidence to the worksheet entry it supports, and use the door identifier in the file name or metadata.

Evidence itemMinimum content
Door photographDoor identifier and enough context to establish location; add a close view where the defect or detail requires it.
Reading or captured valueSource of the reading, observation context, and recorded date and time.
Configuration snapshotDoor or unit reference and the settings relevant to the criterion being accepted.
Credential test resultTest identity, expected and observed outcome, and the authorization state before and after.
Signed test checklistTest performed, result, what the observation ruled out, and the tester’s identity.

A photograph without context may not establish which door was inspected. A configuration export without a unit reference may not establish which installation was tested. Attach only the evidence needed to support the decision, while retaining the original source in the controlled evidence location.

Site Acceptance Criteria: The Evidence a Site Acceptance Criteria Record Needs provides a deeper view of evidence design. For the wider handover package, use Site Acceptance Criteria Documentation Set to confirm that the worksheet references the right design, configuration, credential, and operating records.

8. Convert results into one controlled decision

The site acceptance criteria worksheet should end with a decision, not an open-ended test list. Every mandatory criterion must be marked pass, fail, not verified, or not applicable, and every not-applicable entry needs a reason.

flowchart TD
    A[Receive handover package] --> B[Complete door identity and baseline]
    B --> C[Run required checks]
    C --> D[Attach supporting evidence]
    D --> E{All mandatory checks pass}
    E -->|Yes| F[Sign and release for service]
    E -->|No| G[Raise or update snag]
    G --> H[Assign owner and due date]
    H --> I[Retest affected check]
    I --> C
    E -->|Scope unclear| J[Escalate for review]
    J --> C

The release decision requires the completed test results, linked evidence, and authorized signatures. A hold requires at least one open snag, while an escalation records the unresolved question and pauses the affected scope. The sheet should show the path followed, including any retest, because the final pass may have been reached only after a specific defect was corrected.

Keep the worksheet with the handover package even when every test passes. It is the baseline against which later operational records can be compared.

9. Carry exceptions through snag and punchlist management

An acceptance exception must remain visible until evidence closes the failed criterion. Snag and punchlist management works only when every item connects a failed condition to an owner, an action, a retest, and a closure decision.

Snag fieldRequired entry
Snug identifierUnique reference linked to the door and worksheet.
Door identifierObject-schedule identifier for the affected door.
Failed criterionThe exact worksheet requirement that was not met.
Observed conditionFactual description, including what was checked and what it ruled out.
Evidence referencePhotograph, reading, export, or signed test result supporting the observation.
Operational effectWhether release is held and what interim arrangement applies.
OwnerPerson or role accountable for the corrective action.
Due dateDate by which action or status review is required under the project plan.
Retest and closureResult of the affected check, evidence, and the person closing the item.

A closure statement such as fixed or now working is insufficient. Close the item only when the retest addresses the original failed criterion and the evidence is attached. If the correction changes another part of the door, such as physical alignment, configuration, or access administration, determine which dependent checks must also be repeated.

For a repeatable route from failed check to decision, use Site Acceptance Criteria: Decision Tree for Field Teams. The tree should support the worksheet, not replace the door-specific evidence.

10. Sign the handover and transfer operating ownership

A completed test sheet is not enough if the operational owner has not accepted the door. The sign-off structure should separate technical completion, access administration, and site release.

  • The commissioning tester signs for the checks performed and the evidence recorded.
  • The credential or administrative owner signs for the access handover and the resulting account state.
  • The Facility Manager signs for release of the door within the site’s operating arrangements and for the visibility of any remaining exception.

Record the date and time the door became operable separately from the date and time it was accepted. The first supports operational measurement; the second identifies when the handover decision was made. Keep any unresolved snag visible on both the worksheet and the site exception list.

Treat the completed lock commissioning record as the baseline for later maintenance and fault reports. A future technician should be able to identify the installed configuration, approved access path, evidence location, and acceptance exceptions from that baseline.

Service commencement, failed-on-arrival boundaries, support routing, and claim handling should be defined by the written agreement rather than inferred from the signature. Site Acceptance Criteria: Contract Clauses that Make It Work helps place those responsibilities in the contract structure.

CONFIRM-PER-SUPPLIER: Confirm which handover activities define the start of the agreed support and claim process for the supplied scope.

CONFIRM-WITH-LOCAL-SITE-OWNER: Confirm the local access, egress, security, and operating constraints for each door before the Facility Manager signs its release.

11. Reopen acceptance when the door changes

An accepted door remains a live operational object. When a replacement, relocation, credential-role change, door-hardware change, or applicable configuration change could affect an accepted criterion, issue a linked revision rather than editing the original result without explanation.

The revision should identify what changed, which earlier checks remain valid, which checks must be repeated, and who accepted the revised state. Retain the original observations so later reviewers can distinguish commissioning evidence from post-acceptance changes.

When the same symptom appears on comparable doors, preserve each door’s observations and compare the configuration and installation records. Similar symptoms may justify a broader review, but similarity alone does not establish a common cause. The worksheet should route that pattern through the agreed escalation process and preserve the evidence needed for a technical decision.

Likewise, a later repeat fault should not be backfilled into the original acceptance sheet as though it had been observed at handover. Add a linked operational record, compare it with the baseline, and reopen the affected criterion only when the evidence shows that acceptance should be reconsidered.

12. Assign authority without blurring accountability

Give each role a clear decision and a corresponding signature. This prevents a general project approval from replacing a missing technical, credential, or site decision.

RoleDecision or responsibilityExpected sign-off or evidence
Handover coordinatorControls worksheet revisions, evidence links, and the decision log.Complete and traceable handover package.
Commissioning technicianPerforms the assigned checks and records observations in sequence.Signed test entries and supporting evidence.
Credential or administrative ownerConfirms access roles, test identities, and administrative transfer.Before-and-after authorization states and transfer confirmation.
Facility ManagerDecides whether the door can enter normal site operation.Site-release signature and visibility of open exceptions.
Product or supplier specialistResponds to written product and support questions with dated evidence.Source reference and a written response retained with the record.

Review the completed forms at intervals defined in the operating plan. Examine closed snags, not-verified entries, repeat observations, and doors with more than one revision. A form may be complete on paper while still containing weak evidence or unclear ownership. The review should correct the system that produced the record, not simply replace one ambiguous phrase with another.

13. Use a compact field form at the door

The final section of the guide provides a field-ready form. Copy it into the controlled work order or use it as the structure for a dedicated digital form. Do not remove failed or not-verified rows; their presence is part of the evidence.

Field or checkEntry
Worksheet ID and revision
Door or object identifier
Door location and schedule reference
Model and variant from label
Dated product-page reference
Physical fit and door condition
Free movement and alignment observation
Approved manual path result, if applicable
Power-state observation, if applicable
Physical and recorded state agreement
Approved credential test and result
Additional access method, if applicable
Administrative access handover
Alert destination and acknowledgement route
Evidence references
Open snag identifiers
Final decision state
Door operable date and time
Acceptance date and time
Testing technician signature
Facility Manager signature

At the door, write the observation while it is fresh. Use the same identifier on the photograph, export, and snag. If a result changes after corrective work, preserve both the original entry and the retest so the record explains how the final decision was reached. Store the signed sheet with the handover package rather than leaving it only in a technician’s local notebook.

14. Ask the supplier for evidence, not assurances

The final handover questions should be written early enough to resolve a missing acceptance input. Send the supplier or product specialist a specific list such as:

  • Which dated product page applies to the installed model and variant?
  • What documented conditions define installation and handover acceptance for that SKU?
  • Which configuration evidence confirms that the approved settings were applied?
  • What administrative handover evidence is required for the supplied access design?
  • What written route should the site use for a technical question or deviation?
  • How does the agreement define failed-on-arrival handling, service commencement, and claim evidence?

Ask for dated documents or written responses that can be filed with the specific door. A general assurance that the product is suitable does not establish the condition being accepted. When the answer depends on a product capability, preserve it as supplier evidence and confirm it on the dated product page for the specific SKU.

The practical counterpart to this point is private label smart lock warranty. That is the same question site acceptance criteria worksheet has to answer here.CONFIRM-PER-SUPPLIER: Confirm the written evidence, responsible role, and revision date for every product-specific handover criterion.

For a production rollout, request a controlled version of this site acceptance criteria worksheet aligned with the object schedule, dated product references, credential matrix, and site approval route. Keep the master form unchanged, add site-specific annexes only where the door type requires them, and version every annex with the handover package it supports.

The next step is to request a quote.

Handlekurven din
Din opplevelse på dette nettstedet forbedres ved å tillate informasjonskapsler. Informasjonskapselpolicy
Chat on WhatsApp