As Built Documentation: What Goes Wrong on Smart Lock Projects
As built documentation what goes wrong is the resource this piece provides for the people who specify it. This bid and specification sheet defines the handover evidence a bidder must provide for smart lock work at [project], and the checks a specifier applies before accepting it. It is designed to put the client, installer and supplier on one documentary basis.
Direct answer. The one-line answer — as built documentation what goes wrong is the working record for as built documentation what goes wrong. as built documentation what goes wrong is worthless until as-built-documentation is attached to it as evidence. An as built documentation what goes wrong is a resource for whoever writes the requirement. as built documentation what goes wrong turns a request for as built documentation what goes wrong into something a supplier can price.
as built documentation what goes wrong is used here in the narrow sense set out in as built documentation what goes wrong. It is a working definition built for as built documentation what goes wrong. It is not a statutory one, and it has to be read against the market and product concerned.
- Frame the requirement — use a template that names the physical constraints in as built documentation what goes wrong
- Catalogue the evidence — attach the conformity file for the SKU behind as-built-documentation
- Deliver it in one request — issue one complete package per door class, not one per query
- In as built documentation what goes wrong, this sequence is what as built documentation is checked against.
The recurring question behind as built documentation what goes wrong on smart lock projects is not whether a folder was delivered. It is whether a future reader can identify the installed door set, trace every field change to a recorded decision, locate the credential and interface records, and know who may maintain them.
Complete every bracketed field. Return the schedules as one controlled package, not as disconnected files or photographs.
1. Document issue and response particulars
Use this section as the control sheet for the returned package. An unanswered field identifies an unresolved handover issue rather than a neutral omission.
| Control field | Bidder response |
|---|---|
| Document type | Bid and specification sheet |
| Project identifier | [Insert project name and identifier] |
| Contract package | [Insert package or tender reference] |
| Door scope | [Insert doors, frames and access-control interfaces included] |
| Bidder | [Insert bidder’s legal name] |
| Document revision | [Insert revision and issue date] |
| Response due | [Insert date, time and time zone] |
| Response format | [Insert file format and delivery method] |
| Handover medium | [Insert controlled repository or transfer method] |
| Nominated record custodian | [Insert role, organisation and contact channel] |
Each response must identify the door set to which it applies. A document marked “latest,” “final” or “as installed” without a door identifier is not traceable. The bidder should use the identifiers assigned in the tender documents and should not create a second numbering system.
Where a field cannot be completed, the bidder must state the missing evidence, the party responsible for supplying it and the date by which it will be available. Silence must not be interpreted as confirmation that the item is not required. For a buyer who needs that comparison in writing, use As Built Documentation: How Suppliers Respond. What can be supplied is listed in the smart door locks.
2. Required response schedules
For a smart lock as built documentation response, separate the offer, the approved technical record, the installed-condition evidence and the post-handover control record. A bid may state an intention; only evidence tied to a door identifier can demonstrate what was installed.
| Ref. | Required response | Minimum content | Acceptance test |
|---|---|---|---|
| R-01 | Door schedule | Door identifier, leaf and frame reference, lock case type, opening direction and finish reference | Every identifier reconciles to installation evidence |
| R-02 | Product reference | Supplier, SKU, technical revision, dated product page and approved submittal reference | All references identify the same product version |
| R-03 | Installed door dimensions | Backset, bore diameter, bolt-to-bore distance, faceplate and strike information | Values represent the installed door or a recorded deviation |
| R-04 | Lock installation evidence | General, detail and interface images linked to a door identifier | Images show the installed condition and visible identifiers |
| R-05 | Door set verification record | Leaf, frame, hardware and locks reviewed as one assembly | Every review field is signed and dated |
| R-06 | Credential configuration record | Roles, access zones, hierarchy, effective dates and exceptions | Roles reconcile to the approved access schedule |
| R-07 | Electronic interface record | Device addressing, controller relationship, supervision and egress interface mapping | Entries reconcile to commissioning records |
| R-08 | Deviation log | Proposed and installed differences, reasons and decision references | No open item lacks an owner or due date |
| R-09 | Authority decisions | Written decisions on project-specific building, fire or access matters | Decision maker, scope and date are visible |
| R-10 | Custody index | File inventory, revision, custodian, storage location and transfer date | Every delivered file has an identified holder |
Submittal traceability depends on repeating the same door identifier in every schedule. Renumbering a door during installation, or identifying a product only by its enclosure colour, breaks the chain between the offer and the handover record.
Every product-specific statement must be checked against the dated product page for the specific SKU and the approved submittal. Where the sources differ, the bidder must raise a deviation rather than select the more convenient value.
3. Where as built documentation what goes wrong appears
The failure is often visible before site inspection. Reviewers can identify missing fields, disconnected images and undocumented changes by comparing the offered record against the required schedules.
| Failure | Observable symptom | Required correction |
|---|---|---|
| Generic brochure used as the installed record | The brochure carries a dimension or finish that was never measured on site | Replace it with a door-specific record and retain the brochure only as reference material |
| Photographs without door references | The image could belong to several similar doors | Add the door identifier, view direction and capture reference to every image |
| Partial dimensional record | Backset is present, but bore diameter or bolt-to-bore distance is absent | Complete each dimension as a separate field or record why it does not apply |
| Lock and door recorded separately | The lock schedule and installation images use unrelated references | Create one cross-reference between product, door set and evidence file |
| Change accepted during a meeting | The installed item differs from the schedule, but no dated decision exists | Record the change, decision maker, reason and affected door |
| Credential export omits exceptions | Temporary access, restricted areas or inherited roles cannot be reconstructed | Supply the controlled configuration with exceptions identified |
| Project decision held only as an email attachment | The file does not show who decided the matter or its scope | Attach the written decision and a short evidence index |
| Handover link without custody | The recipient may receive an obsolete copy after further edits | Transfer a read-only baseline and name the record custodian |
These failures share a pattern: the package looks complete but cannot support an independent check. A missing reference is therefore more serious than a cosmetic formatting defect because it prevents the client from determining which decision still governs the door.
A bid review should return a numbered deficiency schedule rather than resolve the omission through an informal conversation. The bidder then supplies the missing evidence or identifies the responsible party and completion date. The review record should state which response items remain open.
CONFIRM-WITH-LOCAL-BUILDING-CONTROL: Verify the project-specific building-control, inspection and record-acceptance requirements, and retain the named decision before handover.
CONFIRM-WITH-FIRE-AUTHORITY: Confirm the treatment of any fire-rated door assembly with the authority having jurisdiction and retain its written determination.
CONFIRM-WITH-ACCESS-CONSULTANT: Confirm the installed locking arrangement and operable-part decisions for escape routes with the appointed access consultant.
4. Door set and dimensional schedule
A door set is the leaf, frame, hardware and locks considered as one assembly. Backset is the distance from the door edge to the centre of the spindle or cylinder. Bore diameter and bolt-to-bore distance are separate dimensions, while faceplate and strike describe the two halves of the closing edge that must match.
| Schedule field | Required entry |
|---|---|
| Door identifier | [Use the controlled project reference] |
| Assembly type | Mortise, rim lock or multipoint arrangement |
| Leaf and frame reference | [Type, thickness and frame condition where measured] |
| Backset | [Door-specific value and unit] |
| Bore diameter | [Door-specific value and unit] |
| Bolt-to-bore distance | [Separate measured value and unit] |
| Faceplate and strike | [Matched references and condition] |
| Product reference | [Supplier, SKU and technical revision] |
| Door thickness and handing | [Verified values] |
| Finish | [RAL or other approved colour reference] |
| Hardware relationship | [Existing hardware retained, removed or adjusted] |
| Egress role | [Escape route and locking arrangement] |
The dimension the installer needs is the door-specific backset, stated in the unit and format used by the approved door schedule. A catalogue dimension cannot close the field. The installed door dimensions must reflect the delivered door, including any site modification.
Where a mortise lock, rim lock or multipoint arrangement is proposed, the case type and locking points must be explicit. For escape routes, identify the egress route, any panic hardware and the locking arrangement. The arrangement is a door-specific decision rather than a label copied from a product description.
A photograph shows the finish; it does not specify it. Record the approved RAL or other colour reference and use the photograph only as supporting evidence of the installed appearance.
5. Installation evidence schedule
Lock installation evidence is an indexed set of observations, not a gallery of unlabelled images. Each item must show what was installed, where it was installed and which approved decision governed the work.
| Evidence ref. | Evidence view | Required detail |
|---|---|---|
| E-01 | Pre-installation condition | Door identifier, existing leaf, frame, hardware and visible site conditions |
| E-02 | Door preparation | Bore locations, backset reference, edge preparation and strike preparation where accessible |
| E-03 | Installed lock | Overall position, case, spindle or cylinder area, trim and escutcheon |
| E-04 | Closing interface | Faceplate, strike, door edge and latch engagement area |
| E-05 | Electronic interface | Installed reader, controller relationship, wiring route or power arrangement |
| E-06 | Close-out image | Complete door set after adjustment, with identifier visible in the record index |
Field capture may follow the format of the Office Smart Lock Site Survey for office doors and the Smart Lock Retrofit Site Survey for retrofit conditions. The bid record must still reconcile those observations to the accepted door set.
Images should carry a stable file reference, capture date and description. The description should identify what the image proves; it should not claim performance from appearance alone. Close-ups without a general view are traceable only when the index identifies the door.
A broader submittal review may be found in As Built Documentation: A Smart Lock Specifier Guide. The acceptance test remains the same: every image must lead to one approved record.
6. Electronic handover record
The handover record for electronic access control must describe both the intended configuration and the controlled records that allow it to be administered later. A statement that access was configured is not enough.
| Record component | Required content | Control |
|---|---|---|
| Credential configuration record | Credential types, roles, access zones, effective periods and exceptions | Export under controlled access |
| Key control schedule | Doors inside or outside the hierarchy and reasons for exclusions | Reconcile to the approved schedule |
| Device register | Device identifier, door reference, controller relationship and installed revision | Match commissioning records |
| Line supervision record | Controller relationship and monitored open or closed states | Identify any unmonitored point |
| Egress interface record | Exit-device operation signals and associated controller mappings | Match the approved locking arrangement |
| Power-state record | Battery backup arrangement, operating state and test result | Tie each result to a door |
| Administration record | Administrative roles, access-change process and record owner | Exclude secret material |
Key control decides who may hold a key. A master key opens a group of locks, and a hierarchical system defines the levels below it. The handover should identify deliberate exceptions so that a later reader does not treat every installed cylinder as part of the same system.
The fail-safe or fail-secure state is determined by the door’s role and the approved arrangement, not by the lock’s product description. Record the approved state, test method and result for each door.
CONFIRM-PER-SUPPLIER: Verify each capability or holding claim against a named, dated document, state its scope and retain the source with the submittal.
CONFIRM-WITH-ACCESS-CONSULTANT: Confirm the locking arrangement, panic-hardware release behavior and free-egress outcome for each escape route, and retain the signed decision in the handover package.
7. Deviation and decision register
Every difference between the approved schedule and the installed condition needs a traceable entry. The purpose is not to disguise the difference; it is to preserve the decision trail that allowed the work to proceed.
| Register field | Required entry |
|---|---|
| Decision reference | Unique controlled reference |
| Affected door | Door identifier and affected component |
| Field changed | Schedule, product, finish, interface or configuration field |
| Proposed change | Description of the requested condition |
| Reason | Installation or project-specific explanation |
| Decision maker | Role and organisation |
| Date | Approval or rejection date |
| Disposition | Approved, rejected or superseded |
| Supporting evidence | Submittal, test, drawing or written decision reference |
| Affected records | Files requiring revision after the decision |
If a field change requests a different item, treat it as an or-equal request rather than an installation fact. The specifier decides whether the proposal is equal and records the reasons. The installer should not close the register entry merely because the alternative item is already attached.
The submittal is not approved until the review is recorded and dated. The same principle applies to a deviation: an installed condition does not amend the approved schedule by itself. Design and supplier coordination should also follow As Built Documentation: Coordination Between Architect and Supplier.
8. Responsibility and custody matrix
A handover is a transfer of responsibility for a controlled record, not merely a shared-folder notification. The matrix identifies who must create, review and retain each part.
| Role | Tender response | Installation record | Handover and custody |
|---|---|---|---|
| Specifier | Define schedules and acceptance tests | Review deviations and door-set evidence | Accept the baseline and record open items |
| Installer | Confirm required evidence and access | Create site observations and close deviations | Deliver indexed files against the schedule |
| Supplier | Provide product and submittal references | Support technical clarification | Supply controlled configuration exports |
| Client representative | Confirm record recipients | Review operational requirements | Confirm receipt and nominate the custodian |
| Access-control operator | Define required roles and exceptions | Verify configuration and interfaces | Accept administration and update records |
The handover index should list every file, its revision, location, responsible party and permitted update status. The nominated custodian must receive the baseline, known exceptions and the current deviation register in the same transfer.
Where a later correction is necessary, the custodian should issue a new revision rather than overwrite an accepted file. The revision history must connect the replacement to the decision that caused it.
9. Review and acceptance workflow
The review moves from presence to relationship, then from relationship to field verification and formal acceptance.
flowchart TD
A[Response received] --> B{Schedules complete}
B -->|No| C[Issue clarification schedule]
B -->|Yes| D[Desk review]
D --> E{Door evidence linked}
E -->|No| F[Record deficiency]
E -->|Yes| G[Site verification]
G --> H{Authority record present}
H -->|No| I[Hold handover]
H -->|Yes| J[Accept baseline]
J --> K[Assign record custodian]
Desk review checks that every required schedule exists. Technical review checks that identifiers, product revisions and decision references agree. Site verification samples the physical condition against the recorded door and interface evidence.
| Review criterion | Accept when | Return when |
|---|---|---|
| Completeness | Every required schedule is present | A required schedule is absent |
| Traceability | The same door identifier appears across all records | References change without explanation |
| Site fit | Recorded dimensions and conditions match the door | The record contains only catalogue information |
| Decision basis | Each deviation and project decision is dated | A change rests on an informal instruction |
| Electronic handover | Roles, devices and interfaces reconcile | Exceptions or mappings are omitted |
| Custody | The index names files, revisions and holder | The package is delivered without control |
A conditional acceptance must name the open item, owner and required evidence. It must not be represented as full acceptance. Handover remains on hold when an unresolved item could change the installed door, its operation or the applicable project decision.
10. Clarification and deficiency schedule
Return deficiencies in a structured schedule so that each response can be closed without searching through meeting notes. The reviewing party should identify the applicable reference, the submitted location, the missing evidence and the required response.
| Field | Clarifier entry |
|---|---|
| Deficiency reference | [Controlled response reference] |
| Schedule or clause | [Required response reference] |
| Submitted location | [File name and section or page] |
| Deficiency | [Statement of what cannot be verified] |
| Evidence required | [Specific record or correction] |
| Responsible party | [Bidder, installer, supplier or client] |
| Response date | [Required date] |
| Review disposition | [Accepted, further evidence required or closed] |
A general statement that the matter will be confirmed does not close a deficiency. The reviewer should be able to navigate from the schedule to the evidence and from the evidence back to the schedule. This is also the basis for recording any later revision.
Readers comparing approaches usually start with smart locks for factory offices. That is the same question as built documentation what goes wrong has to answer here.
11. Bid comparison criteria
The commercial evaluation should compare the maturity of the documentary response, not merely whether each bidder mentions a handover file. The following table gives the specifier’s decision record.
| Evaluation criterion | Meets the requirement | Partially meets the requirement | Does not meet the requirement |
|---|---|---|---|
| Schedule alignment | Every response maps to the required schedule | Mapping is present but contains gaps | No mapping is supplied |
| Identifier discipline | One identifier links offer, site and installed record | Identifiers are inconsistent in minor items | Records cannot be connected to a door |
| Exception transparency | Deviations are complete, dated and decision-linked | Deviations are listed but lack decisions | Variations are concealed in photographs or prose |
| Handover readiness | The custody index and controlled exports are ready | A named party must complete minor items | Ownership and file control are undefined |
| Evidence durability | The package can be reviewed without the installer | Context depends partly on an individual | The package relies on undocumented knowledge |
For the commercial consequences of weak evidence, compare As Built Documentation: Cost and Risk Consequences. Delay-specific error patterns are covered separately in Common as Built Documentation Errors that Delay a Project.
The review record should explain the decision, identify any conditional item and name the document that supplied the evidence. That record remains part of the handover history.
12. Handover index and file-control schedule
Use one as-built-documentation-register as the index for the accepted package. A descriptive folder hierarchy may separate door schedules, product submittals, installation evidence, electronic records, decisions and custody documents.
Recommended file references follow this pattern:
[project-code]_[door-identifier]_[record-type]_[revision]_[date]
For example, a reference may combine the project code, a controlled door identifier, an installation-evidence label, a revision and the capture date. The file name supplements the index; it does not replace it.
| Index field | Required entry |
|---|---|
| File reference | Unique file or archive reference |
| Door identifier | Related door or project-wide record |
| Record type | Schedule, submittal, image set, configuration export or decision |
| Revision | Issued revision and supersession status |
| Date | Capture, issue or decision date |
| Source | Person, system or party that created the record |
| Location | Controlled repository or archive path |
| Custodian | Role responsible for the accepted baseline |
| Update process | Method for issuing a revised copy |
| Relationship | Supersedes, supports or is required by another reference |
The transfer should include the index, the accepted baseline and any open-item schedule. The custodian should confirm that the package opens, that references resolve and that no required file remains in a personal working folder.
13. Draft clauses and bidder sign-off
The following language can be inserted into the tender or specification. It defines the documentary outcome without assigning an unverified product capability or making a project decision that belongs to the appointed authority.
| Clause | Required language | Purpose |
|---|---|---|
| Documentation scope | The bidder shall deliver the schedules, evidence, controlled exports and decision records listed in this sheet | Defines the complete handover response |
| Door identifiers | Every record shall cite the controlled door identifier and applicable revision | Prevents orphaned files |
| Product confirmation | Product information shall be checked against the dated product page for the specific SKU and accepted submittal | Separates approved data from marketing material |
| Installation evidence | Evidence shall show the installed door, lock, closing interface and electronic connection | Demonstrates physical integration |
| Deviations | No installed condition shall amend an approved field without a dated decision record | Preserves the decision trail |
| Electronic records | Credential and interface records shall be supplied in a controlled export and shall not contain secret material | Supports administration without exposing credentials |
| Authority decisions | Relevant project decisions shall identify the deciding authority, scope, date and repository reference | Makes external decisions auditable |
| Custody | The accepted baseline, index and open-item schedule shall be transferred to the nominated custodian | Establishes responsibility after handover |
The bidder should complete the declaration below. An authorised representative should sign it, and the response should be returned with the schedules identified in Section 1.
| Declaration item | Bidder response |
|---|---|
| All required schedules included | [Yes / No] |
| Door identifiers reconcile across the package | [Yes / No] |
| Product references checked against the accepted submittal | [Yes / No] |
| Deviation register contains no undisclosed change | [Yes / No] |
| Controlled electronic exports are ready for transfer | [Yes / No] |
| Open items identify an owner and completion date | [Yes / No] |
| Nominated record custodian | [Role and organisation] |
| Authorised representative | [Name, role and signature] |
The commercial response should return the completed schedules, the indexed evidence package and the signed declaration as one controlled submission. Any item not available at submission must appear in the clarification schedule with its owner and date, rather than being left as an implied promise.
Close the loop with requesting a quote.

