Real Estate Luxury

Powered by StealthAgents

Luxury Brokerages

Set up a vendor access log for estate service visits

A vendor access log that records the visit before the gate opens, names the scope, and reconciles keys and codes after the work is done.

Victoria Harmon
Set up a vendor access log for estate service visits
Table of contents

A staffed estate can receive a dozen service visits in a week, and each one is a small access decision. A vendor access log turns those decisions into a record that the house manager, the owner, and the security team can trust. The log should be short enough to complete at the gate and specific enough to answer a question later. A one-page form with seven fields is usually enough for a normal service visit.

Key takeaways

  • Open the log entry before the vendor reaches the gate.
  • Record the room, the scope, and the expected duration.
  • Track every key, code, or badge issued and returned.
  • Reconcile the day's visits against the schedule each evening.

Record the visit before the gate opens

The log entry should exist before the vendor arrives, not after the work is finished. A pre-entry forces the team to confirm the appointment, the company, and the person who will attend. It also gives the gate a name to check against. A log filled in at the end of the day is a memory exercise, not a control.

Include the vendor's company, the technician's name, the arrival window, and the staff member who authorized the visit. If the vendor sends a substitute, record the change and the reason. A substitute who is not on the schedule should wait while the house manager confirms. The gate should never accept a name that is not on the log.

Confirm the appointment with the vendor the day before, not only at the gate. A confirmation reduces the chance that a technician arrives on the wrong day or with the wrong equipment. Record the confirmation and the name of the person who gave it. The gate should know what was promised before the van appears.

Name the room and the scope

A visit record needs the room or system the vendor will touch, such as the pool equipment room, the wine cellar, or the security panel. The scope tells the next person what was expected and what should be checked afterward. A general note that says maintenance is not enough to protect the property. Name the system or the room in the same words the property file uses.

If the scope changes during the visit, add a short note and tell the house manager. A plumber who came for a leak may also need to open a wall, which changes the risk and the cleanup. The log should show the change before the work expands. A quick message is better than a surprise invoice.

Mark the rooms that are off limits during the visit, such as a private study or a guest suite. The vendor may need a nearby utility closet but not the room itself. A clear boundary prevents a technician from opening a door out of curiosity. The house manager should walk the route if the property is unfamiliar.

Capture the time in and time out

Record the time the vendor enters and the time the vendor leaves. The gap is useful for reconciling the invoice, the security footage, and the staff schedule. A visit that runs much longer than expected may need a follow-up question. The times should come from the gate record, not from an estimate at the end of the week.

If the vendor leaves and returns with parts, record each entry and exit. A single visit line hides the second entry and weakens the record. The gate should treat each crossing as a separate event. A clean time trail is easier to review than a note that says returned later.

Use the same clock for the gate, the staff schedule, and the invoice review. A log that mixes phone time and gate time will produce gaps that look like missing minutes. State the time zone at the top of the log. A consistent clock makes the review faster and the questions more precise.

Log the key or code used

Every key, code, or badge should be linked to the visit that used it. Record what was issued, who received it, and when it was returned. If a vendor uses a temporary code, note the code identifier and the time it was disabled. A key that is issued without a return line will eventually go missing.

Review the key log at the end of each day and confirm that every item is back. If an item is missing, tell the house manager before the vendor leaves the property. A missing key is easier to resolve while the technician is still on site. The log should make the return as visible as the issue.

Keep a separate line for a key that is held overnight or across several visits. A multi-day key needs an owner, a return date, and a check when it comes back. A temporary issue that quietly becomes permanent is the most common key problem. Review the open key list at the end of each week.

Review the log weekly

At the end of the week, compare the log against the service schedule and the invoices. Look for visits that were not scheduled, keys that were not returned, and rooms that were entered without a scope note. A short weekly review catches small gaps before they become habits. Invite the gate lead to the review so the fixes reflect what is possible at the window.

Ask the house manager and the security lead to review the same log together. One person may notice a pattern in the times, while the other notices a pattern in the vendors. Record one change for the next week, such as a stricter arrival window or a new key process. A log that never changes is probably not being read.

Compare the week's visits with the invoices before approving payment. A visit that has no log entry should be questioned, and an invoice for a visit that never happened should be held. The comparison does not need to be adversarial. It is a simple check that the record and the bill describe the same work.

Keep exploring