Power and Wiring Coordination: Coordination Between Architect and Supplier
This annotated datasheet turns the power and wiring coordination coordination question into a field-level record that can travel with the door schedule. It assigns each gap to the architect or supplier, identifies the closure evidence, and keeps the decision trail available to the installer without another meeting. It is written for the door hardware consultant workflow, particularly when the client, installer and electrical designer need one basis for review. The broader sequence is covered in Power and Wiring Coordination: A Smart Lock Specifier Guide.
Direct answer. The short answer is that power and wiring coordination coordination is not one decision. It is a sequence. This article takes power and wiring coordination coordination from power and wiring coordination coordination through power-and-wiring-coordination to the record you keep. A power and wiring coordination coordination is a tool pack for the specifying side. power and wiring coordination coordination names the artefact the RFQ must produce for power and wiring coordination coordination.
power and wiring coordination coordination is used here in the sense given under power and wiring coordination coordination. It is a working definition of power and wiring coordination coordination that carries no regulatory weight. The buyer still has to check it against the dated product page.
- Write the requirement — use a template that names the physical constraints in power and wiring coordination coordination
- List the evidence — attach the conformity file for the SKU behind power-and-wiring-coordination
- Send it once — issue one complete package per door class, not one per query
- In power and wiring coordination coordination, this sequence is what power and wiring coordination is checked against.
Use the sheet as an ownership instrument, not as a substitute for the supplier’s evidence package. Where submittal contents are the focus, pair it with Power and Wiring Coordination: Documents a Specifier Should Demand. This sheet remains the source for who supplies an answer, who accepts it and which change reopens it.
Ownership codes and the unit of coordination The commercial
Every row is attached to one door set, identified by its schedule reference rather than a generic lock type. The codes show who closes a field; they do not transfer design accountability.
| Code | Accountable closer | Required record |
|---|---|---|
| A | Architect | Design requirement, operating basis and accepted interface recorded against the door-set identifier. |
| S | Supplier | Dated product response tied to the exact specified configuration. |
| J | Architect and supplier | Shared interface decision recorded with its revision, date and named signatory. |
A joint field closes only when both parties have recorded the same boundary. A supplier response can satisfy an S field without approving the A requirement, and a marked route remains open while its entry point is unresolved. Keep Private Label Glass Door Lock Supplier open next to this one. The build options sit in the smart door locks.
Door-set power record
The power supply responsibility field needs a named owner at design stage. The architect identifies the intended building interface and operational dependency; the supplier identifies the product-side requirements for the exact configuration.
| Field | Architect entry | Supplier entry | Closure test |
|---|---|---|---|
| Door-set identifier | Project and schedule reference | Product configuration tied to the same reference | Identifiers match throughout the package. |
| Supply mode | Intended building source or standalone operating basis | Mode and connection method stated for the exact SKU | Both entries describe the same arrangement. |
| Source and connection point | Location, access route and responsible discipline | Connection interface and stated constraints | Source, point and route are coordinated. |
| Power requirements | Available design basis and outage expectation | Required input stated in dated product information | The design basis accommodates the response. |
| Control boundary | Components and doors covered by the control scope | Supplied interface and stated exclusions | No unassigned interface remains. |
| Battery backup | Continuity requirement and operational dependency | Backup arrangement and supporting product evidence | Responsibility and continuity basis are named. |
| Power-loss state | Required outcome for the door’s role | Behavior and configuration options for the exact SKU | The proposed implementation matches the approved outcome. |
| Document revision | Issued schedule and coordination revision | Dated product document and response revision | Every referenced document is current. |
For voltage, current, terminal arrangement, output and backup-duration statements, confirm on the dated product page for the specific SKU. Before release, compare the door schedule, route information and supplier response by identifier rather than by general product name.
Wiring route schedule
The wiring route schedule follows the connection route from its source to the door set. It is an interface record, not a replacement for the project’s electrical drawing. Architect supplier coordination works when each route is named, bounded and handed over in the same revision.
| Route field | Architect-side record | Supplier-side record | Joint closure condition |
|---|---|---|---|
| Route identifier | Unique reference tied to the door set | Same reference used in the product response | One route maps to one door set. |
| Source location | Coordinated origin and access responsibility | Connection point identified for the exact SKU | Locations do not conflict. |
| Intended pathway | Agreed route and affected trades or spaces | Connection path and access constraints stated | Route boundaries are documented. |
| Entry point | Coordinate and frame interface identified | Entry or connection requirement stated | The physical entry can be verified. |
| Interface crossings | Other disciplines and system boundaries recorded | Product-side interfaces and exclusions identified | Every crossing has an owner. |
| Destination | Door-set identifier and intended equipment location | Same endpoint shown in the response | No route ends at an unidentified device. |
| Field variation trigger | Procedure for reporting an installed difference | Procedure for evaluating an alternative | A discrepancy reopens the affected fields. |
Each route ID should appear on the coordination record and the corresponding supplier response. If the installed route differs from the record, raise the affected route ID rather than replacing the original reference.
Battery backup and the power-loss state decision
Battery backup coordination and the power-loss state decision are separate fields. Backup addresses continuity after the building supply is unavailable; the loss-state decision addresses the intended locking arrangement when a defined loss condition occurs. A note saying only “battery backup” does not close either question.
| Decision field | Fail-safe candidate | Fail-secure candidate | Required annotation |
|---|---|---|---|
| State after the defined loss | Released state | Locked state | Record why the outcome suits the approved door role. |
| Decision owner | Architect records the required outcome | Architect records the required outcome | Identify the confirming authority. |
| Product response | Confirm behavior for the exact SKU | Confirm behavior for the exact SKU | Cite the dated product page and configuration. |
Fail-safe and fail-secure describe the outcome to be coordinated; they are not product labels in this sheet. The supplier states whether and how the exact SKU can implement the approved behavior. Battery depletion, controller loss and loss of building supply should not be merged unless the approved design treats them as one condition.
CONFIRM-WITH-LOCAL-BUILDING-CONTROL: Confirm the required power-loss state, controlled-door sequence and release provisions with the local authority having jurisdiction for the installed door.
CONFIRM-WITH-ACCESS-CONSULTANT: Confirm the operating and free-egress implications where the door forms part of an escape route.
The approved decision record should identify any local battery arrangement or independent release provision without turning the datasheet into installation instructions.
Approval flow from issued record to released basis
The sequence below is a gate on completeness and authority, not a construction programme. It prevents a supplier’s completed form from being mistaken for architectural acceptance.
flowchart TD
A[Door set identifiers reconciled] --> B[Architect issues power and routing record]
B --> C[Supplier completes marked fields]
C --> D{Every required field is closed}
D -->|No| E[Return named gaps to the owner]
E --> C
D -->|Yes| F[Joint interface review]
F --> G{Decisions and revisions are recorded}
G -->|No| H[Assign each open decision]
H --> F
G -->|Yes| I[Release approved coordination record]
I --> J[Installer receives the current revision]
At the first gate, the architect has identified each door set and issued the A fields. The supplier completes the S fields against the same references. At the joint review, unresolved questions become assigned decisions, not silent assumptions. The released record carries the current revision into installation information. The submittal is not approved until the review is recorded and dated.
Readers comparing approaches usually start with how many smart locks should i order for a pilot project. That is the same question power and wiring coordination coordination has to answer here.
Gap codes and change triggers
Use a gap code whenever a response is missing, contradictory or attached to the wrong door set. The code keeps the request specific and makes the next owner obvious.
| Gap code | Trigger | Next action | Closure owner |
|---|---|---|---|
| GAP-PWR | Source, point or supply responsibility is absent | Assign the design entry and request the product response | Architect and supplier |
| GAP-ROUTE | Route, pathway or entry point conflicts | Hold a joint interface review against the route identifier | Joint |
| GAP-BACKUP | Continuity requirement or arrangement is missing | State the requirement, then obtain the product evidence | Architect and supplier |
| GAP-LOSS | Loss outcome or deciding authority is unresolved | Record the outcome after the required confirmation | Architect |
| GAP-REV | Schedule, route and product-document revisions differ | Reconcile the references before review | Architect and supplier |
| GAP-FIELD | Installed condition differs from the recorded route | Raise the affected identifier and reopen its fields | Joint |
Reopen affected rows when the door-set identifier, frame, control scope, power source, route, backup arrangement or approved loss-state outcome changes. Record the prior value, proposed value, decision and approving party. A revised schedule alone does not close a gap when the power record remains unchanged.
This overlaps with the earlier coverage in what documents should a smart lock manufacturer provide. That is the same question power and wiring coordination coordination has to answer here.Use Common Power and Wiring Coordination Errors that Delay a Project to diagnose recurring omissions and Power and Wiring Coordination: What Goes Wrong on Smart Lock Projects to test interface failures. Those checklists support this sheet; they do not assign ownership or create approval.
Joint coordination record
The joint coordination record is the index that tells a later reader where to find the decisions. Keep it with the current door schedule and issue it under the same revision as the wiring route schedule.
| Record field | Required entry |
|---|---|
| Project reference | power-and-wiring-coordination plus the project and door-set identifiers |
| Issue and revision | Current issue date and revision applied to every attached schedule |
| Architect signatory | Named reviewer, accepted A fields and confirmed J decisions |
| Supplier signatory | Named reviewer, exact SKU and dated source supporting the S fields |
| Open-item register | Gap code, owner, affected door set and current status |
| Decision log | Power source, route, backup arrangement and loss-state decisions |
A signature confirms only the fields owned by the signing party. Issue the index with the route schedule and supplier response so that a later reviewer can trace each decision without reconstructing it from correspondence.
Illustrative coordination cases
These cases show how the record changes a conversation without claiming a particular product configuration.
| Illustrative situation | Initial gap | Coordination move | Recorded outcome |
|---|---|---|---|
| The power point is in a corridor, but the connection path has no route identifier. | GAP-ROUTE remains open because the path ends only at the door set. | Assign one route ID and connect it to the source, entry point, destination and supplier response. | The joint review can check one continuous interface across both documents. |
| The supplier requests a connection arrangement different from the one issued by the architect. | GAP-PWR and GAP-REV apply to the same door set. | Obtain dated evidence for the exact SKU, compare the proposed interface and record the design decision before revising the route. | The approved arrangement, responsible party and current document revisions remain linked. |
A supplier alternative does not become the design basis merely because it appears in a response. The joint record must state whether the architect accepted it as a coordinated change, rejected it or requested further evidence.
Release conditions for the coordination package
Close the power and wiring coordination coordination record only when the following checks have evidence and a recorded decision. A blank cell is a gap; a verbal answer is not a release entry.
| Release check | Evidence required |
|---|---|
| Identifier alignment | The same door-set reference appears in the schedule, route and response. |
| Supply coordination | Source, connection point and responsibility are recorded. |
| Route coordination | The route identifier covers pathway, entry point and destination. |
| Backup coordination | The continuity requirement and supplier response are aligned. |
| Loss-state decision | The approved outcome and required authority confirmation are attached. |
| Product evidence | Values for the exact SKU are confirmed on the dated product page. |
| Record control | Current revisions, named signatories, dates and open-item status are present. |
Give the supplier the S-marked fields with the issued door-set identifiers and a return date within the project programme; ask for dated evidence for the exact specified SKU. Return the completed sheet to the architect with the route, backup and power-loss decisions highlighted. Both sides can then review, revise and hand over the same controlled record.
Put the answer on paper and request a quote against that document.

