Who Owns Audit Export and Legal Hold: Supplier, Integrator or Client
I entered the evaluation with three folders: supplier evidence, integrator configuration, and the client's instruction for preserving records. The supplier said its platform could produce an export. The integrator would make it repeatable. The client wanted to know what would survive a legal hold. I soon found that the audit export and legal hold ownership split had been treated like another feature checkbox. It was not one. It was a chain of decisions about what each party sends, stores, reads, preserves, and repairs. My diary below records the handover I used to make that chain explicit before a demonstration became a procurement promise.
Direct answer. In short, audit export and legal hold ownership split is the subject of this piece. audit export and legal hold ownership split is where the work on audit export and legal hold ownership split sits. audit-export-and-legal-hold is what has to be evidenced before anyone signs. An audit export and legal hold ownership split is an integration guide. Every component has an obligation to the next. audit export and legal hold ownership split is the first one tested for audit export and legal hold ownership split.
Throughout, audit export and legal hold ownership split means what audit export and legal hold ownership split sets out. It is a working definition of audit export and legal hold ownership split drawn from the evidence below. It is valid for the specific market and product, not as a general claim.
- Outline the interface — write down what hands over between lock, door and system at audit export and legal hold ownership split
- Rehearse the handover — record the sequence that proves audit-export-and-legal-hold works end to end
- Log the exchange — store the commissioning evidence with the file for handover arrived
- Treat this as the audit export and legal hold ownership split sequence, with audit export and legal hold as the reference.
The handover arrived with three meanings of export
Each side was sending a different packet. The supplier described how a record could be extracted. The integrator described the selected controller and service configuration. The client described the evidence it expected to receive and restrict. The words matched, but their acceptance conditions did not.
| Artifact | Working definition | Accountable side | Gap to expose |
|---|---|---|---|
| Event memory | Buffer held by the lock when it cannot reach the server | Selected device, evidenced by the supplier | Buffer limit and later transfer |
| Audit log | Event record with time and source | Platform owner | Late, rejected, or duplicated events |
| Export package | Reproducible result with scope and extraction time | Integrator | Omitted or empty fields |
| Hold register | Versioned client instruction for scope and release | Client | Superseded instruction |
The lock reports the state; the system decides what the state means. During a degraded period, an event can remain in event memory without yet appearing in the audit log. A later export therefore cannot prove that no earlier access occurred; it proves what the queried source returned. I required the request, source, time window, timezone, extraction time, and exception count to travel together. If one side cannot identify absent records, the ownership question remains open. The range this procurement eventually buys from is the smart door locks.
One clock had to cross all three borders
Clock ownership was hiding inside the export. I assigned the integrator to operate the agreed time source, while the client approved the reference clock and time zone. The supplier documented timestamp and event-receipt behavior for the selected system. Every package carried event time, ingestion time when available, timezone, and extraction time. Original values were preserved rather than silently corrected; a reconciliation note identified drift, late arrivals, and corrections.
Because these are selected-system behaviors, confirm on the dated product page for the specific SKU and retain any platform-level note with the acceptance evidence. The acceptance test should compare a source event, its audit-log entry, and its exported row, then show who corrected any mismatch.
I turned audit export ownership into a decision matrix
Instead of assigning the whole problem to whichever company exported a CSV, I recorded audit export ownership as a set of decisions.
| Decision | Supplier responsibility | Integrator responsibility | Client responsibility |
|---|---|---|---|
| Capability evidence | Provide dated, selected-SKU documentation | Verify it in the deployed setup | Approve acceptance criteria |
| Export path | Distinguish local API, cloud API, or file transfer and state limits | Run the selected path | Define the required evidence |
| Hold procedure | Explain available mechanisms without deciding scope | Implement the approved instruction | Decide scope, custodians, and release |
| Retention | Document defaults and controls | Configure approved values | Approve schedule and hold priority |
| Degraded mode | Document selected-system behavior | Test and monitor | Accept the operating risk |
| Permissions | Explain available role controls | Provision approved access | Authorize people and repository |
| Fault handling | Diagnose a confirmed product fault | Triage and route the issue | Decide escalation and business impact |
The matrix assigns work; it does not erase each party's separate professional duties. A party may accept a defined task without accepting another party's policy or operational decisions.
CONFIRM-PER-SUPPLIER: Obtain dated, SKU-specific evidence for the selected export path, fields, time behavior, event-memory handling, permissions, retention controls, and any hold-related mechanism before accepting the matrix.
The legal hold decision stayed on the client side
The integrator asks the client to define the legal hold procedure: the matter, custodians, date, systems, approving authority, release authority, and approved storage location. The client owns those decisions. The integrator translates the approved instruction into configuration and test evidence. The supplier provides dated evidence of what the selected product and platform can preserve or export. An export request and a hold are different actions: one produces a copy at a point in time; the other instructs continued preservation. I required both to be acknowledged separately.
Access control evidence preservation also needs controlled readers, a documented handoff, and a record of authorized disclosure. Data retention controls must state the ordinary schedule, hold priority, and the event ending the hold. None should be inferred from a default menu.
CONFIRM-WITH-LOCAL-DATA-PRIVACY-COUNSEL: Confirm with local counsel or the client's appointed privacy owner which privacy, employment, records, and evidence-preservation instructions apply in each jurisdiction before production or retention is configured.
The outage changed the ownership sequence
When the network, controller, or server is unavailable, the ownership sequence changes. Event memory is a local buffer, not a second audit log. The integrator must document what remains local, how that state is observed, and what evidence is required before declaring an export complete. The client receives an exception notice; the supplier investigates a confirmed product fault; the client decides any access or policy exception.
flowchart LR
C[Client hold instruction] --> I[Integrator configuration]
I --> L[Selected lock and controller]
L --> M[Event memory during outage]
M --> S[Server audit log]
S --> E[Evidence export]
E --> R[Client controlled repository]
I --> P[Supplier escalation for product fault]
The diagram is a responsibility route, not a statement that every product behaves alike. The integrator owns triage until the boundary is known. The supplier owns a diagnosed product defect. The client owns access decisions and business impact. The offline case is the design, not the exception. It must be rehearsed before shipment.
I required an evidence package, not a screenshot
| Package item | Produced by | Proof retained |
|---|---|---|
| Field dictionary | Supplier and integrator | Meaning, units, timezone, and source |
| Export sample | Integrator | Repeatable request and scoped result |
| Clock report | Integrator | Reference, offset, and corrections |
| Hold register | Client | Scope, approval, version, and release |
| Configuration snapshot | Integrator | Deployed values and revision |
| Access roster | Integrator and client | Named roles and repository access |
| Exception log | Integrator | Missing, duplicate, or rejected events |
For smart lock audit logs, the field dictionary must say whether a timestamp is device-generated or server-generated, what the source identifier means, and how empty or rejected events appear. The screenshot could not answer those questions, so it was not handover evidence. The export sample also needs the request, query window, timezone, extraction time, and exception count.
Use the Audit Export and Legal Hold Requirements Document Template to define those fields and the Audit Export and Legal Hold: The Test Plan a Buyer Should Demand to prove behavior. Keep the resulting record with the selected-system evidence, not in a separate presentation folder.
It is worth pairing this with smart lock model selection matrix. That is the same question audit export and legal hold ownership split has to answer here.
The review turned ambiguity into named decisions
At review, I stopped asking whether a feature existed in general and asked who could prove each behavior.
- Can the supplier tie every claimed field to dated evidence for the selected SKU?
- Can the integrator reproduce the export from a documented request?
- Can the client identify the hold register, approval, and release authority?
- Can the team detect and explain a gap between event memory and the audit log?
- Does one agreed clock support reconciliation, with original values preserved?
- Can named readers access the evidence, and where is each copy retained?
Answers became acceptance rows in Audit Export and Legal Hold for Smart Lock Projects: What Buyers Must Define First, and unanswered items stayed open rather than becoming assumptions. That changed the meeting from a product demonstration into an allocation of decisions, evidence, and repair duties.
The same question is worked through in more detail in the smart lock hole coverage. That is the same question audit export and legal hold ownership split has to answer here.
The handover I would put in the acceptance folder
At system integrator handover, I put seven items in the acceptance folder.
| Acceptance item | Owner | Evidence retained |
|---|---|---|
| Responsibility split | All three parties | Signed matrix |
| Selected-system evidence | Supplier | Dated documentation |
| Working export | Integrator | Sample, request, and exception log |
| Hold instruction | Client | Signed register and release rule |
| Degraded-mode result | Integrator and supplier | Rehearsal record |
| Permissions and storage | Integrator and client | Roster and repository |
| Fault route | All three parties | Named contacts and ticket rule |
The handover also referenced Documenting Audit Export and Legal Hold for Handover and Audit. Door and controller identifiers had already been checked through Office Smart Lock Site Survey, because an export cannot be reconciled reliably when the physical source is named differently in the field. Any unresolved capability remained marked unverified.
The audit export and legal hold ownership split is complete only when every row has a named decision owner, dated evidence, and an accepted result. Before the next evaluation meeting, place that one-page split beside the sample export and ask each party to sign its own row. If a row still says the platform can handle it, leave it unverified and route it to the supplier or client decision owner. That is the shortest route from a promising demonstration to a defensible handover.
Close the loop with requesting a quote.

