Site Access Logs: Recording Who Did What on a Job
When a technician leaves a site, the most useful record is often the one nobody wrote down. Small businesses frequently discover this after a cabinet is found unlocked, a cable is traced to the wrong patch panel, or a vendor insists a device was never touched. A simple access and activity log, kept consistently, turns those disputes into quick lookups. This article focuses on a narrower question than general documentation: how to record who entered a space, what they handled, and what changed, in a form you can actually review later. The approach below is general guidance for any business with on-site equipment, and it does not depend on any particular provider's tools or processes.
Why access records matter more than most owners expect
Most small offices rely on memory and goodwill. The bookkeeper knows the electrician came on Tuesday, and the owner remembers someone was in the server closet last month. That works until two people remember differently, or until the person who knew has left. Access records give you a neutral source of truth that does not depend on anyone's recall.
The records also serve practical purposes beyond disputes. When something stops working, a list of recent visits narrows the search quickly. When you plan a change, knowing what has already been touched prevents duplicate work. When an insurer or landlord asks who had keys or badges during a given window, you can answer without a scramble.
What to capture at each visit
A useful entry answers five questions: who came, when they arrived and left, where they worked, what they did, and what was different afterward. Names should be full names with the organization they represent, since first names alone cause confusion when two contractors share a crew. Times should include the date and be written in the same format every time so entries sort correctly.
For the location, name the specific room, rack, or device rather than the building. For the work performed, describe actions rather than intentions. 'Replaced failed drive in array B, slot 3' is useful. 'Looked at storage' is not. For changes, record the before and after state where practical, such as a firmware version, a port assignment, or a password reset noted by the date rather than the password itself.
Setting up a log that people will actually use
The best log is the one that takes two minutes to fill out. Keep a single sheet or shared document near the entry point, or attach a short form to the work ticket. Avoid systems that require creating accounts or navigating several screens, because people skip them under pressure. If visitors sign in at the front desk, make the log there and reference it in the technical notes.
Decide in advance who is responsible for recording entries. It is usually the person who escorts or hands off the visitor, or the internal contact who scheduled the work. Assigning the task to a named role, rather than hoping everyone remembers, is what keeps the habit alive after the first month.
Questions to ask any field provider before work begins
Before a technician arrives, ask how they document their visit. Find out whether they produce a written summary, what that summary typically includes, and how quickly you receive it. Ask whether they will note any equipment they open, reconfigure, or remove, and whether they will flag anything they could not complete. These are reasonable questions for any vendor, and the answers tell you more than a sales description does.
Also ask how access is controlled on their side. Will they carry badges or keys, and who keeps records of those? If subcontractors are involved, ask whether the same documentation standard applies to them. You should not assume an answer; confirm it in writing when the stakes are meaningful.
A short checklist for every site visit
Before the visit: confirm the scope in writing, note any restricted areas or hours, and assign an escort or contact. Record the visitor's full name, organization, and purpose in the access log at arrival. Photograph or note the current state of any equipment that will be touched, including cable labels and device status lights.
During the visit: keep the access log current, note significant changes as they happen rather than at the end, and record any unexpected findings. After the visit: collect the written summary, compare it against your own log, file both together, and follow up on any open items. A mismatch between your log and the vendor's summary is worth resolving the same day, while people still remember the details.