Contractor and vendor access ownership split: this playbook splits contractor and vendor access between supplier, integrator and client, with numbered.

Offentliggjort den: maj 18, 2026

Who Owns Contractor and Vendor Access: Supplier, Integrator or Client

Who Owns Contractor and Vendor Access: Supplier, Integrator or Client

Three teams can install the same door and still disagree, a year later, about whose job it was when a tiling contractor's credential kept working after the tiling contract ended. Nobody recorded a fault; nobody broke a rule. The operation had belonged to nobody, and unowned operations are how a contractor and vendor access ownership split gets discovered late, expensively and during an incident review.

Direct answer. The short answer is that contractor and vendor access ownership split is not one decision. It is a sequence. This article takes contractor and vendor access ownership split from contractor and vendor access ownership split through contractor-and-vendor-access to the record you keep. A contractor and vendor access ownership split is an integration view. Lock, door, reader and system have to behave together. contractor and vendor access ownership split is where the first interface behind contractor and vendor access ownership split fails.

contractor and vendor access ownership split is taken here as contractor and vendor access ownership split, deliberately narrowly. It is a working definition of contractor and vendor access ownership split. It is specific to this market and product, and it is not a statutory or certified term.

This playbook draws that split before the first credential is issued: roles stated first, numbered protocols next, IF-THEN rules inside each protocol, and an exception register for what the rules cannot settle. It assumes three parties — a supplier who sells the lock and answers capability questions, an integrator who connects the lock to the building's systems, and a client who owns the estate, the trades and the consequences. A boundary that is not drawn becomes a phone call that lasts a year, so every operation here gets one named owner.

The three parties and what each one actually holds

Parties are described by what they hold, not by what they are called on an invoice. The same company can play two roles on one project; the test is custody.

PartyWhat this party holdsWhat it can never hold
SupplierThe product, its documented capabilities and its firmwareThe client's access decisions; the building's procedures
IntegratorThe connections between lock, controller, platform and the client's systemsThe authority to decide who gets in
ClientThe list of people, the windows of work, the risk acceptance and the fix budgetThe supplier's engineering answers

Two consequences follow. The client holds the decision, because access is a property right and not a device feature. The supplier holds capability statements, each arriving in writing: any answer a door behaviour depends on is CONFIRM-PER-SUPPLIER territory, and model-level detail is confirm on the dated product page for the specific SKU. Everything between those poles is integration work, assigned to a named human on one of the three sides. The commercial end of this decision is the smart door locks.

Protocol 01: draw the split before the first grant

Run this once, at project definition.

1.1 List every operation in the contractor and vendor access lifecycle as a verb: approve, issue, schedule, monitor, extend, expire, revoke, record, read back, fix.1.2 Assign each verb exactly one party from the custody table. Two owners is one too many; zero owners is how incidents happen quietly.1.3 State, per verb, what the other parties must provide, and attach the local API versus cloud API question to it — "the system should do it" means different work on each side of that line.1.4 File the completed sheet with the project's access documentation before commissioning.

IF a verb has no named owner, THEN the project should not be in procurement yet. IF an owner cannot act without a second party, THEN that handover is itself an operation and needs its own owner.

Protocol 02: grant — the paperwork a credential inherits

A credential is the thing the person holds; the identity is the person or role behind it; personalisation is the per-person data tying the two together. The split assigns each separation to a party.

  • Approve (client only). Which trade, which doors, which window, escorted or unsupervised. The supplier has no view on this, and the integrator must not improvise it.
  • Enable (integrator or the client's trained operator). The mechanical act of issuing, following the written procedure.
  • Confirm capability (supplier, in writing). Whether the platform can carry a dated window at all, and where that window is enforced. CONFIRM-PER-SUPPLIER.

IF the grant comes from a work order, THEN the work order reference belongs in the issuance record — the only thing that will explain the credential eighteen months later. IF the supplier's answer on enforcement is vague, THEN treat the capability as absent until written confirmation says otherwise. The duties assigned here should match the buyer-side promises in Smart Lock Temporary Access.

Protocol 03: change — when the job runs past its window

The tiling contract is extended, and three parties now believe one of the other two handled it. The rule prevents the belief.

IF the work window changes, THEN the client's authoriser records the new end date against the original work order before any credential is touched; THEN the party who enabled the credential applies the change and files the confirmation back to the same record. Nobody extends a credential from memory, from a phone call, or at the door.

Custody, not convenience, decides the owner: a client-operated platform makes extension a client duty, with the integrator's job being that the platform makes it possible and proves it after; a supplier-hosted integration leaves the approval with the client and the execution with the hosting party. The effort behind each arrangement is examined in Contractor and Vendor Access Cost and Effort Drivers Without Quoting Prices.

Protocol 04: expiry, revocation and decommissioning are three

A credential whose window lapses, a credential pulled early by a human, and a device or account taken permanently out of service are three events with three records. A scheme that treats them as one cannot say afterwards which happened.

  • Expiry is scheduled and automatic. Owner: whoever owns the schedule, usually the client's platform, verifiable without contacting the supplier.
  • Revocation is unscheduled and authorised. Owner: the client authoriser decides, the enabling party executes, the record names both.
  • Decommissioning is a separate, recorded operation — the same discipline as provisioning a device with its identity, its door and its owner. Owner: the integrator at handover, the client afterwards.

IF a revoked credential still opens a door, THEN the question is not whether the system is broken but who owned the last trusted copy of the schedule — an answer that lives on Protocol 01's sheet or nowhere. The symptoms are catalogued in Contractor and Vendor Access Failure Patterns and How to Recover; this playbook owns the assignment, that catalogue owns the recovery.

The decision the door has to make without a meeting

flowchart TD
    A[Credential presented at the door] --> B{Inside the agreed window}
    B -->|No| C[Refuse and record the attempt]
    B -->|Yes| D{Role still active on the client list}
    D -->|No| E[Refuse and raise the exception]
    D -->|Yes| F{Platform reachable}
    F -->|Yes| G[Release and write to the audit log]
    F -->|No| H{Door carries a stored local rule}
    H -->|Yes| I[Apply the last stored window]
    H -->|No| J[Follow the approved degraded behaviour]
    C --> K[Named owner reads the record]
    G --> K
    I --> K
    J --> K

The reader reports; the controller decides; neither knows why. The degraded branches therefore need pre-assigned owners: reachability is a design question, approved degraded behaviour an approval question answered in writing.

Protocol 05: the outage branch and its owner

The offline case is the design, not the exception. When the network, the controller or the server is unavailable, the door does whatever somebody chose in advance.

IF a door's fallback is to enforce the last stored window, THEN whoever wrote that window owns the risk of it going stale, and a written rule must state how long a stale window is honoured. IF the fallback is a fixed state, THEN fail-safe or fail-secure is decided by the door's role and by the client's approval, not by the product — a door that fails locked is an approval question escalated before commissioning, not after an incident. IF egress is involved, THEN the question is jurisdictional before it is technical: CONFIRM-WITH-LOCAL-EGRESS applies, and the integrator raises it rather than answers it.

Degraded-mode ownership belongs to whichever party holds the fallback decision: the platform operator in centralised state, whoever configured the stored rule on a standalone device. Both are defensible; unassigned is not.

Who owns the clock and who owns the record

Events with two clocks cannot be reconciled, so the split names the time source. One party owns the reference clock; behaviour after a power loss is a supplier statement, CONFIRM-PER-SUPPLIER; and events buffered in a device's event memory carry the time they happened, not the time they arrived — the ingesting party owns keeping that straight.

The audit log raises three custody questions with separate answers: who can produce it, who can read it, who may hold it unaltered under a legal hold — often three different parties, and the packet around them is handled in Documenting Contractor and Vendor Access for Handover and Audit. A record of who opened which door, when, is personal data about identifiable people: who may hold it and for how long is CONFIRM-WITH-LOCAL-PRIVACY territory, with one named owner for retention and one for read access.

The ownership matrix in full

This is the default contractor and vendor access ownership split — the sheet Protocol 01 tells you to produce.

OperationSupplierIntegratorClientWho owns the fix
Approve a trade and its window——DecidesClient
Confirm the platform carries dated windowsStates in writingVerifiesRecordsSupplier for the statement, integrator for the check
Issue and personalise the credential—Enables or trainsAuthorisesIntegrator in rollout, client after handover
Own the reference clockDiscloses per deviceConfiguresAccepts drift riskClient, with the integrator's numbers
Extend a window—ExecutesApprovesClient approves, integrator executes
Expire automaticallyGuarantees behaviourConfiguresAuditsSupplier if the rule misfires as designed
Revoke early—Executes on requestDecides and requestsClient
Handle the degraded branchDiscloses fallback designImplementsApproves the riskClient carries what client approved
Produce, read and hold records—Enables exportGoverns accessClient
Decommission devices and accountsAdvisesPerforms at handoverInherits afterwardsClient after the handover date

Read the last column with the ground rule of this playbook: the lock reports the state; the system decides what the state means; the party who decides is the party who fixes. Capability statements stop being anybody's problem once filed in writing, and handover moves custody on a dated line.

Exception register: what an unsigned split looks like

Three arguments recur; each is evidence that Protocol 01 was skipped.

ExceptionWhat it really isThe rule that fixes it
Client asks the supplier directly to revoke a contractor mid-jobA shadow approval path around the client's own authoriserRoute every unscheduled revocation through the platform and the named authoriser; standing questions in Security Questions to Ask About Contractor and Vendor Access
Integrator extends a window because the authoriser is unreachableThe client's decision taken by the party least accountable for the doorA written deputy rule for unreachable authorisers, agreed before rollout
A new supplier cannot read the previous scheme's expiry rulesDecommissioning of the old scheme was never completedClosure of the old custody as a dated, recorded operation, specified via Contractor and Vendor Access Requirements Document Template

The third exception surfaces years late, which is why the split is drawn alongside the project definition itself — Contractor and Vendor Access for Smart Lock Projects: What Buyers Must Define First. Property type changes who staffs the identical split — Contractor and Vendor Access for a Hotel Property — and the session that proves the sheet matches reality is Contractor and Vendor Access: The Test Plan a Buyer Should Demand.

It is worth pairing this with the smart lock bolt mechanism. That is the same question contractor and vendor access ownership split has to answer here.

Running the playbook before the contract is signed

This document is meant to be marked up, not admired. Name the three parties, run Protocol 01 until every verb in the matrix has exactly one fix-owner, send the CONFIRM- lines to the parties who owe the answers, and keep the completed sheet as the first page of your access documentation. Bring your trades list, window rules and disputed doors to us and we will map each operation against them, with every capability statement confirmed on the dated product page for the specific SKU — the working relationship is described in Smart Lock Manufacturer for System Integrators and starts at request a quote.

Din kurv
Din oplevelse på dette websted forbedres ved at tillade cookies Cookiepolitik
Chat on WhatsApp