A plain-English audit log definition for B2B buyers, with the evidence to demand and the points where record-keeping changes a shipment.

Publicado em: fev 12, 2025

Smart Lock Glossary: Audit Log Definition for B2B Buyers

Smart Lock Glossary: Audit Log Definition for B2B Buyers

Day one, and the first thing I found in the quotation appendix was two words with no definition attached: audit log. My operations lead read it as a promise of a security report. My installer read it as the last fifty events sitting in the device. The supplier's engineer meant something narrower than either. This diary follows the audit log definition from that appendix across a border, into a submittal, onto a live door and finally into the handover file, because a term nobody defines at the border gets defined badly on site, and by then the doors are already drilled.

Direct answer. In brief, this article covers audit log definition from audit log definition to audit-log. It states what to confirm about audit log definition on the dated product page where a figure is involved. An audit log definition is a category reference. audit log definition comes first. Each option states what audit log definition commits a buyer to.

On audit log definition, this article uses audit log definition as the definition. It treats audit log definition as a working definition specific to this market and product, rather than a general one.

  • Set the parameters — use one vocabulary for audit log definition across the project
  • Record the alternatives — list the routes available for audit-log and what each is for
  • Record the compromise — record what you give up with each route in day one
  • This is the sequence audit log definition has to follow, anchored on audit log.

Day one: the appendix that arrived without a sentence

The appendix was four pages of feature shorthand, the kind that reads well in a meeting and badly in a claim. The lock list ran down one column, the access method down another, and then a short line: event log, retained, exportable. No definition came with it, and nobody expected one. In a single-market purchase that gap is survivable. In a cross-border programme it is not, because the gap gets filled by whoever writes the installation instructions last. For a buyer who needs that comparison in writing, use Smart Lock Glossary: Spindle Definition for B2B Buyers.

My own habit is simple, and it is the working definition this entry uses for the rest of the diary. Before a term enters an order, it gets three things: a plain sentence saying what it is, a named record that settles an argument, and the document that proves the record exists. Where the detailed shape of a term varies from platform to platform, and the audit log is one of those terms, my working definition stands for this programme and goes into the purchase order annex as ours. The supplier's silence gets recorded as a deviation rather than smoothed over with a pleasant adjective. That is how I read what an RFQ should contain: plain explanation: a term that arrives without a sentence arrives as an argument. The same question as audit log definition, read from a different angle, is covered in Smart Lock Glossary: Single Point Latch Definition for B2B Buyers. The same decision, read from a different angle, is covered in Smart Lock Glossary: Container Loading Plan Definition for B2B Buyers. The catalogue side of this is the smart door locks.

What the record is, in words a site manager can use

An audit log is the record a system writes when something happens, kept so it can be read back later: an event, a timestamp, and enough detail to identify what was involved. On a smart lock that starts with access events — a credential presented and granted, a credential presented and refused — and then covers the administrative events around them. A credential added. A schedule changed. A door held open past its configured time. A unit powered back up after its batteries were changed.

That plain meaning is the settled part of the phrase. The unsettled part is everything after it: which events the platform records, the field names it uses, how long records are kept, whether the record lives on the device or on a server, whether it can be altered, and who may read it. A specification that says a product provides an audit log and stops there describes a product category, not a product. Anything SKU-specific should be confirmed on the dated product page for the specific SKU rather than taken from a glossary or from memory, and making that confirmation a condition of the order is the importer's job.

Four records that all get called the log

Project correspondence uses one word for four different records, and the substitution happens silently. Sorting them out takes ten minutes at a desk and saves weeks on site.

RecordWhat it holdsWho creates itWhat it can settle
Event memoryThe most recent events held inside the deviceThe lock itself, continuouslyWhat happened at one door, until the buffer is overwritten
Audit logThe retained record of events, readable laterThe lock and its management softwareWhich credential was presented at which door, and when
Factory test recordProduction test results against a serial numberThe manufacturer during productionWhether a unit passed the line checks it was built to
Track and traceThe serial-level record of where a unit has beenThe supply chainWhich units are affected when something changes

The first two are the ones that swap places in a tender response. The third and the fourth are the ones an importer needs when the question arrives about the shipment rather than about the building.

What the term actually decides — audit log definition

Four things, each with a cost attached.

The first is dispute cost. If a client asks who opened a door at 03:12, the answer is either a record or an opinion, and only one of those survives a handover. Whether the record exists at all is decided in the quotation, not on site.

The second is credential traceability. A retained event record tells you a credential was presented. Turning that into a named holder depends on the credential lifecycle records held in the client's administration system and on the discipline of provisioning. How a lock credential lifecycle works: plain explanation covers the chain; the audit log is only the last link in it.

The third is the handover. Site acceptance criteria are usually signed as a set of statements about how the building behaved that day. If the record is part of what the client receives, the handover file says who holds the exports and how they are produced. If it is not, the client inherits a device with an unreadable history and a supplier who has moved on to the next order.

The fourth sits under the others: whether the records can be handed to the buyer's own client, and to that client's auditors, in a form they can filter. That is a file format question settled early, and it is why I ask for a sample export rather than a photograph of a screen.

The four confusions that cost real money

The buffer is not the log. Event memory is the small rolling store of recent events inside the device, and it overwrites. A buyer who accepts event memory in place of a retained record has bought an answer for this morning and nothing for the incident that happens in eleven months.

The credential is not the person. The event record identifies what was presented, not who held it. Every question that starts with who therefore has to be answered by joining two records from two systems, and the join is only as good as the provisioning discipline behind it.

The log is not automatically evidence. Whether a retained access record can be relied on in a dispute, an employment matter or a claim depends on the law of the market where the building stands, not on the phrase in the appendix. The test I would apply is plain: the record was produced by a system that was working, its clock was under control, and the chain from the device to the export is unbroken.

Nothing in the carton proves it exists. The record is created at installation and afterwards. It cannot be inspected in the carton, on the factory floor, or in a sample shipment.

The evidence I put in the request for quotation

This is the list I send before I ask for a price, so the answer arrives with the commercial response instead of after it. Every line has to be answerable in writing.

Evidence itemWhat it settlesIf the answer is missing
Sample event extract with raw field namesWhich events exist and how they are namedAssume the event you will ask about is not recorded
Retention period, and whether it is configurableHow far back a question can be answeredAssume the shortest period the supplier supports
Storage location for the recordWhether it survives a device swap or a unit replacementAssume the device buffer is the log
Export method and file formatWhether records can reach the client's own systemsAssume extraction is manual and unverifiable
Clock setting and time zone handlingWhether a timestamp can be trustedAssume every timestamp is local and correct
Behaviour when storage is fullWhether old records are overwritten or new ones droppedAssume the oldest records disappear
Coverage of administrative changesWhether credential and schedule changes are traceableAssume provisioning happens outside the record
Manual and export templateWhether your own team can read the file laterAssume the supplier's engineer is permanent

Every product-specific line in that table has to be confirmed on the dated product page for the specific SKU, because a platform family and a single SKU do not always behave the same way. When a line comes back blank, I write my own working assumption into the purchase order annex, mark it as an open deviation, and carry it through to site acceptance criteria. That way the gap stays visible to everyone who touches the order.

The factory record is a different animal

At the factory the records are production records. They say which serial number was built, which line checks it passed and what configuration it shipped with. That is exactly what an importer needs when the question is about the shipment, and it is exactly what a building owner is not asking about when they ask who opened a door.

The two records meet at the serial number and nowhere else. A smart lock audit log that exists only on the installed unit cannot tell a factory inspector what happened to the unit in the carton, and a factory test record cannot tell a site manager who used the door in March. Importers who treat the two as one record end up with either a missing history or a missing trace.

Two cross-border complications are worth naming. If the firmware that ships is later updated, event names and export formats can move with it, which makes the shipped firmware version part of the documented configuration rather than an installation detail. If a unit is replaced under warranty, the replacement inherits no history, so the link between the replaced unit and the new one has to live somewhere else. How a sample becomes a production standard: plain explanation covers the configuration side, and how a supplier is actually verified: plain explanation covers the factory side.

Pinning the definition down as it crosses the border

The definition has to survive three documents: the technical annex of the purchase order, the submittal documentation the installer works from, and the handover file the client signs. When the supplier's documentation is in one language and the local installation team reads in another, the translation gap is exactly where the meaning drifts. My rule is that the same sentence and the same evidence table appear in all three, and that the integrator's platform vocabulary is mapped onto the supplier's field names before the first door is handed over.

flowchart TD
  A[Term appears in a quotation appendix] --> B[Importer pins a written definition to the annex]
  B --> C[Installer works from the submittal]
  C --> D[Device generates events on live doors]
  D --> E[Records retained and exported]
  E --> F[Handover dispute settled with evidence]
  D --> G[Buffer overwritten before the question is asked]
  G --> H[Argument resolved from memory]

The branch on the right is the one that costs money. Importer due diligence packs ask for evidence that access to a site is recorded. The answer is often a screenshot taken on the day of the visit, which settles nothing a month later.

The event list I hand to the integrator

The artefact I actually want is the raw export file, not a picture of a screen. A screenshot cannot be filtered, sorted, reconciled against a credential list, or handed to an auditor as evidence. The export file can do all four.

erDiagram
  DEVICE ||--o{ ACCESS_EVENT : generates
  CREDENTIAL ||--o{ ACCESS_EVENT : presented_at
  HOLDER_RECORD }o--|| CREDENTIAL : maps
  ACCESS_EVENT {
    string event_type
    string credential_id
    datetime occurred_at
    string result
  }

The four fields on the event are the ones I insist on, because without each of them the record answers half a question. The event type says what happened, the credential identifier says what was presented, the timestamp says when, and the result says whether access was granted. The holder record is not part of the device record at all. It lives in the client's administration system and is joined by credential identifier, which is why that join has to be documented.

The access control event log vocabulary also decides how records are named once they cross into a platform, and two platforms rarely use the same word for the same event. That mapping belongs in the handover file. The last administrative question is who holds the administrator role on day one and who holds it after the installer leaves, because electronic access control records are only useful to the client if somebody can actually produce them. The recurring gaps in common misunderstandings in the credential lifecycle are mostly this shape.

Three moments when the record does its work

At handover. The record is empty when a lock is installed. If the client expects the log to show who used the building before handover, that expectation belongs to the system being replaced, and the baseline has to come from the site survey rather than from the new devices. Smart lock retrofit site survey and office smart lock site survey are where I would start that conversation, because a survey that never mentions the record will not produce it.

At the complaint. When someone disputes an event, four questions decide the outcome: is the clock trustworthy, was the record exported before the device was replaced or re-imaged, is the credential identifiable, and does the retained period even reach back that far. If the answer to any of them is no, the dispute stays an argument between two accounts.

At the change. A firmware update, a battery replacement, a credential expiry rule, a spare unit swapped into the frame, an office refit that adds doors. Ask whether the retained record survives each of them, and ask where the export key lives when the installing company closes. The failure patterns in why smart locks fail in the field: procurement version and the patterns in spare-parts request patterns: structure both end up here.

Which record settles which argument

The argument on siteThe record that settles itThe record that will notWhere it comes from
This badge opened the door at 03:12The retained event record with device identity and timestampA photograph of a live screenExport from the client's platform
That credential was never issued to themThe provisioning record that maps credential to holderThe device event log aloneClient access control administration
The unit in this door is the unit we orderedThe serial-level track and trace recordThe event logFactory and supplier records
The door was opened with a key, not a credentialAn event type that distinguishes the methodA generic access eventThe product event list
Nobody changed the schedule after handoverThe administrative change eventsThe access eventsExport from the platform
We can hand records to our client's auditorA documented export method and a named custodianA verbal assuranceSupplier documentation and the handover file
The record survived the battery changeA written answer plus a witnessed testThe feature list in the brochureSupplier confirmation and the commissioning test

The third column is the useful one. A dispute is often not caused by a missing record but by the wrong record being produced confidently.

Retention, privacy and the local question

Retention is one setting with two owners. The technical supplier sets what the platform can hold. The legal owner of the data decides what should be held. In one market the record of workplace access carries rules about how long it is kept, who may read it, and what an employee is entitled to be told. In another the same setting is treated as an ordinary operational record. A glossary cannot settle that, and neither can a supplier's brochure.

The buyer's question is precise: which authority in the destination market governs the record, what does that authority require it to contain, and what does it permit the importer or the client to do with a copy that leaves the building.

CONFIRM-WITH-LOCAL-LEGAL: Confirm with qualified counsel in the destination market which rules apply to retained workplace access records for this building type and workforce before a retention period is written into the purchase order, and confirm which party is treated as the holder of the data.

CONFIRM-WITH-CUSTOMS-BROKER: Confirm with the customs broker which document-retention obligations attach to the shipment paperwork and its digital records, because import documentation and access records are separate obligations and are often kept by different people.

If the records are hosted outside the destination country, or if the importer's own platform holds them on the client's behalf, the question changes shape again and the answer belongs with the same adviser. Importers who bundle these together usually receive an answer about the wrong one.

This entry is a procurement reference rather than legal advice, and the wording below is a starting point for a conversation with a qualified adviser in the market where the locks are installed.

The wording I put in the submittal

I keep one paragraph, and it goes into the technical annex and the handover file in the same form.

The installed units shall maintain a retained event record. Each entry shall carry the event type, the credential presented, the device identity and the time the event occurred, and shall remain readable without the unit being connected to a supplier-hosted platform. The retained period shall be stated in the product documentation for the specific SKU and shall be adjustable by the client's administrator. A sample export file shall be supplied with the handover file. Any element above that cannot be supplied shall be recorded as an open deviation at the point of order.

The wording is deliberately narrow. The alternative is a sentence about providing an audit log that tells nobody what happens when the client asks for the file, and that sentence becomes the subject of a variation negotiation six months later.

The build-up behind that decision is in smart lock factory testing what should be tested. That is the same question audit log definition has to answer here.

The questions I carry into the next quotation

  1. Which events does the unit record, in the supplier's own field names?
  2. Where is the retained record held, and what happens to it when the unit is replaced?
  3. How long is the retained period, and can the client's administrator change it?
  4. Can the records be exported in a documented format, and has anyone actually done it?
  5. How is the clock set, and what happens to it after a power interruption?
  6. Are credential additions, deletions and schedule changes recorded alongside access events?
  7. Who holds the administrator role on day one, and who holds it after the installer leaves?
  8. Which authority in the destination market governs the record, and what does it require?

I ask question four first, because it is the one that exposes the others. A supplier who has produced a real export file has usually already answered the rest.

If you would like the audit log definition written into your technical annex rather than left in a glossary, the quickest route is to send the door schedule and the evidence table from this entry with your request, and we will build the quotation and the submittal around the same wording. That is the lesson of this diary in one line: the term only costs money when it crosses the border undefined.

Ask for the offer against the same requirement: request a quote.

O seu carrinho
A sua experiência neste site será melhorada se permitir cookies Política de cookies
Chat on WhatsApp