Key takeaways
- Define a compliant visit by a fixed field list, not by a signed log.
- Compare the register with the badge system and the host calendars.
- Report after-hours and restricted-material visits separately.
- Measure the time from arrival to host notification, not only the entry.
Question and scope
This audit asks whether the executive office visitor log records enough to show who entered, who hosted, and when the visit ended. The unit is one visit tied to one host and one entry in the register. The review follows the invitation, the lobby check, the escort, and the departure. It does not judge the guest's purpose.
Set the scope to one office, one building, and a fixed period. Record the reception process, the badge system, and the after-hours rule. If the process changed during the period, separate the visits. A new badge system can change the record without changing behavior.
Include scheduled meetings, unscheduled arrivals, deliveries, and after-hours visits. Include at least one visit that involved restricted material. Record the category and the access level. A sample of only scheduled meetings will miss the cases the protocol is meant to control.
Include a visit that was cancelled after the guest arrived. A cancelled visit still produces a lobby record and sometimes a badge. Record the cancellation and the departure. The register should show the whole visit, not only the meeting.
What the sources establish
NIST SP 800-53 describes physical access controls and audit logging as part of a security program, which supports a record-based review without prescribing a visitor register format. CISA physical security guidance supports planning for access control and visitor management. BLS occupational data describes the assistant role but not a front-desk standard. The same guidance does not define which guests require an escort.
The sources do not establish a retention period for visitor logs or a required badge design. They also do not say whether every guest must be escorted. The audit therefore measures the office's own rule and the record it produces. The report should keep that local scope visible.
The sources support separating a missing entry from an inaccurate one. A register can list every visitor and still name the wrong host. The audit should test both presence and accuracy. A complete-looking log is not evidence of compliance.
Definitions and measures
Define a compliant visit as one with a host, a purpose, an arrival time, an identification check, a badge, an escort decision, and a departure time. Define the compliance rate as the share of visits with every required field. Keep the field list fixed across the sample. A visit with a missing field is counted as incomplete even when the meeting went well.
Measure the time from arrival to host notification and from host collection to the meeting start. A guest who waits alone in the lobby for twenty minutes is a control gap even with a complete log. Report both intervals. The register alone does not show the experience.
Record whether the badge was returned and whether the departure time was entered by the desk or estimated later. An estimated departure is weaker evidence than a recorded one. Report the source of the timestamp. The audit should distinguish a live record from a reconstruction.
Record whether the guest saw restricted material and whether the host signed the access note. A visit can be compliant at the desk and still be a disclosure risk. Report the access level separately. The audit should not treat every visit the same.
Sampling and collection
Sample visits from the lobby register, the badge system, and the hosts' calendars. Include a board meeting, a vendor visit, a delivery, and an after-hours entry. Record the category and the host. A calendar-based sample may miss the visits the register is meant to catch.
Collect the invitation, the register entry, the badge record, the escort note, and the departure time. Mask personal details that are not needed. If a visit was recorded only on paper, copy the page and note the location. A paper record can be complete and still be hard to audit.
Include a visit with a name that does not match the invitation. A nickname or a plus-one can create a record that looks wrong but is not a breach. Record the discrepancy and the explanation. The audit should distinguish a data error from a control failure.
Verification pathway
Check the register against the badge system and the hosts' calendars. A visitor who appears in one and not the other is an unresolved entry. Record the direction of the mismatch. The audit should test both missing and duplicate entries.
Confirm that the host named in the register was actually in the building and expected the guest. A host who is travelling cannot have collected the visitor. Record the host and the confirmation. The name alone is not evidence of the handoff.
Review the after-hours entries for a named approver and a departure time. An after-hours visit without an approver is the highest-risk case in the sample. Record the approver and the time. The audit should report those visits separately.
Check whether the guest signed the confidentiality acknowledgment when the visit involved restricted material. A missing signature is a different finding from a missing badge. Record the document and the gap. The audit should keep the two controls separate.
Analysis and reporting
Report the number of visits, the field completeness rate, the escort rate, and the badge return rate. Break the results down by visit type, time of day, and host. Report the after-hours visits separately. A single compliance rate can hide a serious gap.
Inspect the failures for patterns. A cluster of missing departure times may point to a shift handoff, while a cluster of missing hosts may point to a booking process. Choose one change, such as a departure check or a host confirmation. Do not rank reception staff by completeness when their visitor mix differs.
Report the time from arrival to host notification as a separate measure. A complete log can still describe a guest who waited unaccompanied. Show the median and the longest case. The measure is closer to the control than the field count.
Limits and next action
The audit cannot prove that a guest with a complete record had no access to restricted material or that every visitor was honestly identified. It also cannot capture a visit that was never entered. The report should state those limits and avoid treating the register as proof of security. Record the sample date so the next review knows what was not covered.
Set a repeat audit date and keep the field list stable. Assign the correction to the office manager and give the front desk a short arrival checklist. The next audit should test whether the same field or the same after-hours step fails again. A useful result is a register that can be trusted at the end of the day.
Keep the audit record with the visitor policy and the badge inventory so a later review can compare the rule with the practice. Set the next sample date and name the owner. A protocol that is never checked will drift with each shift change. The office should be able to show what it fixed.
Sources
- Secretaries and Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Outlook Handbook.
- Executive Secretaries and Executive Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics.
- Executive Secretaries and Executive Administrative Assistants, O*NET OnLine.
- Business Formation Statistics, U.S. Census Bureau.
- Nonfarm Business Sector: Labor Productivity, Federal Reserve Economic Data.
- Productivity Statistics, OECD Data Explorer.
- World Development Indicators, World Bank DataBank.
- ILOSTAT Labour Statistics, International Labour Organization.
- 2024 Work Trend Index Annual Report, Microsoft and LinkedIn.
- The economic potential of generative AI, McKinsey Global Institute.
- Creating helpful, reliable, people first content, Google Search Central.
- Search Engine Optimization Starter Guide, Google Search Central.
- Dear Manager, You Are Holding Too Many Meetings, Harvard Business Review.
- NIST SP 800-53 Rev. 5, Security and Privacy Controls.
- CISA, Physical Security.
- BLS, Secretaries and Administrative Assistants.
Related research
Apply the research
Use the finding to frame one question for your own team: which support work is currently invisible, and who should own the next step? A scoped consultation can turn that question into a practical role. Write the question down before the meeting. Name the person who owns the next step.
Turn the finding into a support scope.
Bring the workflow that feels hardest to see. We will help define the role, the evidence it should maintain, and the decisions that stay with leadership.
Talk through the role