As Built Documentation: Coordination Between Architect and Supplier
The working rule is simple: as built documentation coordination begins before the product is selected and continues after the last door is handed over. The record must let a future reader identify the installed door, understand what was approved, see what changed on site, and locate the evidence without asking the original team for a meeting. This is not a retrospective summary; it is a controlled trail from intent to installed condition.
Direct answer. Condensed to the essential point, as built documentation coordination turns a request into a decision record. as built documentation coordination and as-built-documentation are the two parts of as built documentation coordination most often skipped. An as built documentation coordination is a tool pack for the specifying side. as built documentation coordination names the artefact the RFQ must produce for as built documentation coordination.
The phrase as built documentation coordination is anchored in as built documentation coordination. For the rest of this article it denotes the conditions and evidence that as built documentation coordination sets out below. Nothing wider than that.
- Frame the requirement — use a template that names the physical constraints in as built documentation coordination
- 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
- This is the sequence as built documentation coordination has to follow, anchored on as built documentation.
The method below gives the architect, Door Hardware Consultant, and supplier a shared sequence for creating that trail. It also separates decisions the supplier can evidence from decisions that belong to the designer, installer, client, or approving authority. For a wider review of the records a smart-lock specification should contain, see As Built Documentation: A Smart Lock Specifier Guide.
Establish the future reader and the design basis
Begin by naming the person who must operate, maintain, repair, or replace the lock without access to the original project team. A client’s facilities manager may need the record years later, while an access-control administrator may need the same information during an equipment change. The future reader should be able to answer four practical questions: which product was installed, where it was installed, how it interacts with the door, and where the supporting evidence is filed. Before the next supplier meeting, read Private Label Glass Door Lock Supplier. What can be supplied is listed in the smart door locks.
The architect and supplier occupy different parts of the coordination triangle. The architect represents the client’s design intent, the supplier must provide evidence for what it supplies, and the installer must record the conditions found on site. As-built documentation succeeds when these contributions meet in a controlled record rather than remaining in separate emails, samples, or site folders.
The design basis should identify the relevant door set: door leaf, frame, hardware, locks, egress route, and locking arrangement. It should also name the current record custodian, the required approval route, and the source of each assumption. A photograph may illustrate a finish, but it does not specify the finish; the record should carry the agreed colour reference and its source.
Map the shared process from intent to archive
The coordination process uses milestone gates rather than an assumed calendar. Each gate produces a record that the next party can rely on. If a milestone is skipped, the following activity will either repeat information requests or create a gap that cannot be reconstructed reliably.
flowchart LR
A["Design basis"] --> B["Information request"]
B --> C["Recorded review"]
C --> D["Approved baseline"]
D --> E["Installation record"]
E --> F["Installed-door verification"]
F --> G["Discrepancy closeout"]
G --> H["Handover transfer"]
H --> I["Controlled archive"]
| Stage | Shared output | Gate before proceeding |
|---|---|---|
| 0 | Design-basis and custody register | Scope and record owner are named |
| 1 | Coordinated information request | Required evidence is defined |
| 2 | Supplier response and review record | Decision is recorded and dated |
| 3 | Approved baseline | Design intent and assumptions are frozen |
| 4 | Installation record | Actual door conditions are captured |
| 5 | Installed-door verification | Observations and exceptions are logged |
| 6 | Discrepancy closeout | Each deviation has a disposition |
| 7 | Handover transfer | Package, index, and custodian are accepted |
Actual dates belong in the project record rather than in this generic sequence. A team may compress stages or run them in parallel, but it should preserve the evidence and decision shown at each gate.
Issue one coordinated information request
The architect should issue a single request that identifies the door or door family and the information needed for evaluation. Separate requests to the supplier for dimensions, finishes, installation support, and approval evidence create opportunities for conflicting answers. The request should also identify where each response will be filed and who will review it.
For fit, the supplier must provide the dimensions required to check the actual door: the backset, meaning the distance from the door edge to the centre of the spindle or cylinder; bore diameter; bolt-to-bore distance; and the matching faceplate and strike information. These are separate checks and cannot be replaced by a general brochure. Confirm on the dated product page for the specific SKU and against the current door drawings.
Each door hardware submittal should name the document, its scope, and the holder of the underlying evidence. A generic statement that an item “complies” does not tell the reviewer what was examined or where the record can be found. The architect defines the evidence requirement; the supplier responds with the material it controls and identifies any field that requires confirmation from the installer or door manufacturer.
Evaluate the supplier response as evidence
The supplier’s response should be checked against the request field by field. The reviewer should distinguish a confirmed dimension, a stated assumption, a document that still needs review, and an item that cannot be closed at that stage. This classification prevents an unresolved assumption from becoming an apparently approved fact.
The submittal is not approved until the review is recorded and dated. The record should identify the reviewer, the accepted items, rejected items, conditions, and required revisions. If the proposed response departs from the specified basis, treat it as an or-equal request rather than silently incorporating it. The decision belongs to the specifier and should be recorded with the reasons and the evidence used.
| Review item | Architect or specifier provides | Supplier provides | Recorded result |
|---|---|---|---|
| Dimensional fit | Current door and frame information | Dated SKU dimensions and limitations | Fit accepted, revision requested, or field left open |
| Finish | Agreed colour reference | Material and finish evidence | Reference confirmed for the selected sample |
| Installation interface | Door-set details and required access | Installation information for supplied item | Installation method identified |
| Authority evidence | Required scope and decision route | Named supporting document | Review status and holder recorded |
| Changed basis | Approved revision request | Reason and effect of proposed change | Revision, rejection, or further review |
Freeze an approved baseline before site work
The baseline is the controlled starting point for construction. It should include the approved door schedule, accepted submittal, recorded review decisions, relevant drawings, selected finishes, outstanding assumptions, and the blank installation record. Marking the package “approved” is not enough; the baseline needs an identifier, revision status, issue date, and named custodian.
Use document control to preserve the relationship between revisions. When a requirement changes, issue a new baseline or a controlled addendum showing the previous value, the new value, the reason, affected doors, and the person who authorised the change. Do not overwrite the earlier decision without retaining its relationship to the new one.
The client’s life-cycle assumptions also belong in the baseline. Record an assumption as an assumption, attribute it to the client who supplied it, and do not present a supplier figure as a project expectation. This gives the future reader a clear boundary between approved design data, site observation, and management assumption.
Convert site work into a structured installation record
The installation team should use a record form tied to door identifiers, not a collection of photographs named by installer or date. For each door, the form should capture the actual door and frame conditions, the installed hardware, the product identifier, and any departure from the baseline. Measurements and observations should state their source and datum so another person can interpret them.
Every installation record should identify who performed or witnessed the work, what was checked, and what remains open. The record should include contextual images where useful, but each image needs a corresponding door identifier, viewing direction, and description. Images alone can conceal the relationship between a component, the door edge, the frame, or an obstruction.
The supplier’s responsibility should match its control of the evidence. It can provide product identification, dated technical information, installation guidance, and responses to technical queries. The installer remains the source for site measurements, installed conditions, and the work performed. When either party discovers a change, the change event should enter the discrepancy log rather than waiting for the final handover package.
Verify the installed door rather than the sample
A mock-up or sample can demonstrate fit, finish, and the presence of interfaces for a particular review. It does not prove how the installed assembly behaves. Installed-door verification therefore records observations from the actual door, including operation, alignment, access, interaction with other hardware, and the condition of the surrounding frame.
Record who conducted the verification, which door was observed, what action was performed, and what result was seen. If the project includes line supervision, an egress interface, a battery backup arrangement, or reader coverage, the record should connect the installed hardware to its designed function. The observation must describe the installed arrangement rather than infer performance from a product description.
Where a door forms part of an escape route, fire-door assembly, or accessible entrance, use the applicable authority’s decision rather than a catalogue statement:
CONFIRM-WITH-LOCAL-BUILDING-CONTROL: Confirm with local building control which installed-door evidence is required and which authority records the decision.
CONFIRM-WITH-FIRE-AUTHORITY: Confirm with the fire authority the scope and evidence required for the particular door assembly and locking arrangement.
CONFIRM-WITH-ACCESS-CONSULTANT: Confirm with the access consultant the installed conditions and verification method for the project’s accessible operation requirements.
The fail-safe or fail-secure state for a lock on power loss is decided by the door’s role, not by a general product label. Record the approved decision and the evidence that connects it to the installed door.
Reconcile discrepancies while they can still be changed
Every difference between the baseline and the installation record needs a disposition. Classify it as a construction correction, an accepted field condition, a design revision, a supplier change, or an unresolved item. The disposition should identify who provided the evidence, who accepted the outcome, and whether the baseline, installation record, or both must be revised.
A useful distinction is between information that was missing and information that was wrong. Missing information can often be supplied without reopening the design. A wrong baseline may affect procurement, installation, testing, or future replacement, so it requires a formal decision. Unresolved differences should remain visible in the issue log rather than being buried in meeting notes.
The consequences of an unresolved record extend beyond administrative tidiness. They can affect later repairs, change requests, and the ability to defend the installed decision. As Built Documentation: Cost and Risk Consequences provides a separate comparison of those consequences; the coordination response is to close each discrepancy while the relevant party can still affect the outcome.
| Discrepancy type | Immediate action | Final disposition |
|---|---|---|
| Missing site dimension | Request measured value and source | Update installation record and affected baseline |
| Unrecorded design change | Pause reliance on the affected decision | Record revision, authority, and affected doors |
| Supplier change after approval | Compare against the accepted basis | Approve revision or replace the affected item |
| Installed condition differs from expectation | Record actual condition and photographs | Accept with rationale or issue correction |
| Evidence not yet available | Name holder and required document | Close only when the named evidence is filed |
Transfer a usable handover record
Before handover, assemble a handover record with an index that follows the project’s door identifiers. The index should link each approved basis, installation record, verification result, discrepancy disposition, and installed-door image to the relevant door. Include native working files where the client’s system can preserve them, together with readable exports for long-term review.
The architect supplier handover should transfer responsibilities as well as files. The architect normally retains the design and approval history, the supplier retains the evidence it controls, and the client or its appointed custodian receives the integrated installation record. The receiving custodian should confirm that the package is complete, openable, indexed, and linked to the project rather than to a temporary folder.
Where several operational teams will use the record, the handover can include indexed extracts for each team, but the master index should remain authoritative. The hotel-specific example in As Built Documentation for a Hotel Project illustrates how operational handovers can be structured without creating multiple uncontrolled versions.
Ownership after handover must be explicit. Record who may approve corrections, where new installation observations are filed, and how the supplier is contacted when historical product information is required. A transfer without a named custodian is an unfinished delivery.
Define who decides, supplies, records, and accepts
A coordination protocol becomes useful when each party can see its boundary. The matrix below separates decision ownership from evidence ownership and prevents the supplier from being expected to attest to site conditions it did not observe.
| Role | Decides or authorises | Provides | Retains in the record |
|---|---|---|---|
| Architect or specifier | Design basis, required evidence, review outcome | Schedule, instructions, review decisions | Approved basis and revision history |
| Door Hardware Consultant | Specification checks and documented recommendations | Comparison, dimensional review, open-item log | Review comments and accepted assumptions |
| Supplier | Product-specific technical response within its control | Dated SKU data, configuration evidence, technical clarifications | Evidence submitted and change notices |
| Installer or installer’s contractor | Installation method and site record | Measured conditions, installed identification, verification observations | Completed installation record and exceptions |
| Client or facilities custodian | Final receipt and future custody | Acceptance comments, maintenance requests, later updates | Controlled handover record and update history |
The signature route should follow the client’s project procedure. The important point is not the shape of the form; it is that every acceptance has a named decision-maker, a date, and a traceable package. If several roles sign one record, the form should make the sequence and purpose of each signature clear.
Run as built documentation coordination as a decision cycle
Treat as built documentation coordination as the name of the recurring decision cycle, not a separate binder exercise. The cycle should activate whenever information changes, while routine administration remains in the document-control system.
- At design issue, the architect confirms the door-set scope, required evidence, and record custodian.
- At each approval decision, the supplier contributes its response and the specifier records the outcome.
- At installation, the installer supplies actual conditions and the supplier answers product-specific queries.
- At discrepancy review, the project team closes, revises, or explicitly carries each open item.
- At handover, the receiving custodian checks the index and accepts the record in its final form.
Meetings should produce decisions, changed records, assigned actions, and due dates. They should not replace the written record. A short decision notice can link the affected baseline item, installation entry, and revision, giving the team one reference instead of three disconnected attachments.
Contain common coordination failure modes
Most failures are visible before handover when the team checks the record against the work rather than against the intended design. The table connects each failure to a containment step that can begin immediately.
| Failure mode | Warning sign | Containment |
|---|---|---|
| Generic brochure accepted as fit evidence | No site dimensions are recorded | Return the dimensional fields and state the required format |
| Sample treated as proof of performance | Review ends at the sample | Add an installed-door observation record |
| Photograph treated as finish approval | No colour reference appears | Obtain the agreed reference and record its source |
| Supplier changes after approval | Baseline and delivered item differ | Open a revision before installation or handover |
| Handover is treated as supplier closure | No receiving custodian is named | Obtain custody acceptance and archive location |
| Door components are reviewed separately | Door, frame, strike, and lock references differ | Reconcile the complete door set |
| Authority decision is assumed | No dated approval record exists | Obtain the named decision and evidence scope |
These are process failures, not supplier-performance labels. The containment step restores the missing link without turning a coordination issue into a dispute. The catalogue of As Built Documentation: Common as Built Documentation Errors that Delay a Project provides a wider error analysis for teams that need to identify the pattern behind repeated requests.
Apply the pre-handover acceptance test
Before accepting the package, ask whether an unfamiliar reader could reconstruct each installed door without a conversation with the architect, supplier, or installer. The answer should be visible in the index, baseline, installation entries, verification observations, and discrepancy decisions.
Use the following acceptance checklist:
- Every door in the handover scope has a stable identifier that links the design basis to the installation record.
- The backset, bore diameter, bolt-to-bore distance, and faceplate or strike information required for fit are recorded from an identified source.
- Product evidence is tied to the specific selected SKU and the dated information used during review.
- The submittal review, design revisions, and discrepancy dispositions are recorded and dated.
- Any escape-route, fire-door, or accessible-operation decision is supported by the evidence named by the deciding authority.
- The record states who owns the handover package and how later corrections are controlled.
- Client life-cycle assumptions are attributed to the client and kept separate from supplier data.
- Native files, exports, images, and links are checked so the package can be opened without access to a supplier’s temporary workspace.
- Open items are either closed or transferred through a documented exception process with a named holder.
The final test is practical rather than visual. Select several doors from different areas of the project and follow each one through the index. If the trail ends at a photograph, an unlinked email, or an unnamed person’s memory, the handover is not yet a controlled record.
Readers comparing approaches usually start with smart lock manufacturer for importers. That is the same question as built documentation coordination has to answer here.
Complete the architect–supplier–installer chain
A reliable as-built documentation record is built through a sequence of small, attributable transfers. The architect defines the design basis and evidence requirement; the supplier supplies controlled product information; the installer captures actual conditions; the specifier reconciles differences; and the client’s custodian accepts the resulting package. Each transfer should preserve the door identity and the link to the previous decision.
This overlaps with the earlier coverage in smart lock manufacturer for system integrators. That is the same question as built documentation coordination has to answer here.A supplier asked to join this process should provide the dated information for the selected SKU, identify the scope and holder of every supporting document, provide an installation record template where requested, and notify the architect of every change. Product-specific dimensions and capabilities must be confirmed on the dated product page for the specific SKU rather than reconstructed from general marketing material.
The architect should provide one coordinated request, maintain the baseline, record review decisions, and close discrepancies with the responsible parties. Together, these actions turn handover from a file-transfer exercise into a durable operational record: one that supports maintenance, replacement, access administration, and the next project without recreating the original coordination effort.
Close the loop with requesting a quote.

