TOEIC Link — Visitor Check-In and Facility Badge Access Vocabulary Cluster

Getting into a building is a controlled, time-bound process, which makes the front desk and the security notice natural TOEIC Link settings. A visitor email, a badge-access memo, or a lobby sign rarely tests whether you know a door was opened; it tests whether you can read three things at once — who is permitted where, for how long that permission lasts, and whether the person needs someone with them. Those three facts decide what a passage's questions are really asking, and a reader who fixes them first has the notice anchored before the options appear.

This guide walks the visit from pre-registration to sign-out as a connected sequence, isolates the badge and authorization vocabulary the test leans on, and closes with a drill protocol. It builds on general office and facilities terminology and pairs with the IT helpdesk ticket and access request vocabulary cluster, since a digital access request and a physical one share the same approval logic, and with the orientation in what TOEIC Link measures.

The visit as a check-in-to-sign-out sequence

The organizing fact is that a visit has a beginning and an end that must match, and the passage reasons about whether they do. A visitor who checks in but never signs out is a specific, testable problem, so a reader who tracks the sequence reads the notice the way security wrote it.

A well-run visit begins before arrival with pre-registration — a host registers (or pre-books) a guest in advance so the front desk expects them. On the day, the visitor checks in at reception (the front desk or lobby), presents photo ID, and is issued a visitor badge (or visitor pass). A passage may hinge on whether the guest was pre-registered: a pre-registered visitor is cleared quickly, while a walk-in (an unannounced visitor) must be verified with the host before entry, which the memo may say causes a delay. The badge is usually temporary and often time-limited — valid only for the day and only for certain floors — and the visit ends when the guest signs out and returns the badge at reception.

The distinction between the two badge types organizes much of the vocabulary. An access badge (or key card, proximity card) belongs to an employee and opens doors by their access level; a visitor badge is a limited, expiring version of the same idea. A passage may present a visitor badge that "does not open the third-floor lab" and expect the reader to infer that the guest's access was deliberately restricted, not malfunctioning.

The badge and access-level vocabulary — where permission is defined

The heart of a facility-access passage is the small set of terms describing what a badge can and cannot open, and the test concentrates its inference questions there. The central idea is the access level (or access privilege).

An access level is the set of doors and floors a badge is authorized to open, assigned by role — a warehouse badge opens the loading dock but not the executive floor. To change what a badge can reach, an administrator grants or revokes access, and a passage may turn on a badge that still opened a door after the employee changed roles, expecting the reader to infer that access was never revoked — the same failure to update a record that breaks a licence or a subscription elsewhere. A restricted area (server room, lab, executive suite) requires a higher access level than general office space, and a secure area may need two-factor entry — a badge plus a PIN — so a passage stating that "the badge alone did not open the door" is testing whether the reader knows a second factor was required, not that the badge failed.

Timing vocabulary sits alongside permission. A badge may be active or deactivated; a lost badge is deactivated immediately and a replacement issued, and a passage may hinge on a found badge that no longer works because it was deactivated when reported lost. An expired visitor badge stops working at end of day, and the test likes a returning visitor who assumes yesterday's badge still opens the door. After-hours access (entry outside normal building hours) is often a separate privilege, so an employee whose badge works at 10 a.m. but not 10 p.m. is inside the rules, not locked out by error.

The escort and authorization vocabulary — where the harder passages live

When a visitor's own badge is not enough, the vocabulary shifts to who must accompany or approve them, and this is where the harder passages live. The central term is the escort.

Many buildings require a visitor to be escorted — accompanied at all times by an employee, the host or a designated escort. An escort-required badge cannot be used alone; the guest may enter the lobby but not move through the building without the host, and a passage may present a visitor who "waited in reception until the host arrived" and expect the reader to infer that the escort rule, not a scheduling mix-up, kept them there. A sponsor (the employee responsible for the visitor) vouches for the guest and is accountable for their conduct, which is why an unescorted visitor is treated as a security breach and reported.

The authorization vocabulary follows the same approval logic as any access request. A visit to a restricted area may need prior approval from an area owner or security, submitted as an access request and granted before the day. A contractor may need a background check or a signed non-disclosure agreement (NDA) before a badge is issued, and a passage may hinge on a contractor turned away because the NDA was not yet on file — the visit was approved in principle but not cleared in practice. This gap between "approved" and "cleared" is the same distinction the test probes in the vendor onboarding and approval vocabulary cluster: permission granted on paper is not the same as permission active in the system.

Incident, tailgating, and audit vocabulary

Once access is in force, the surrounding vocabulary records who went where and flags what went wrong, and passages test it. The most common failure is tailgating (or piggybacking) — following an authorized person through a door without badging in — and a passage may present a lobby notice asking each person to badge in individually, expecting the reader to see it as a tailgating countermeasure. An access log (or entry log) records every badge swipe, and a passage may hinge on a log showing an entry but no matching exit, echoing the check-in-without-sign-out problem the visit opened with.

Audit and review vocabulary closes the cluster. A periodic access review (or access audit) checks that each person's access level still matches their role and revokes what is no longer needed; stale access (privileges outliving the reason for them) is exactly what such a review is designed to catch. A passage may describe a former employee whose badge still worked weeks after departure, expecting the reader to infer that the offboarding step of deactivating access was skipped — a lapse the access review exists to prevent.

Drill protocol — reading access passages under time pressure

Practice this cluster with a fixed routine so the permission logic becomes reflex rather than recall.

First, on any access passage, answer the three questions before reading the options: who is this person (employee, visitor, contractor), where are they allowed (which floors or areas), and for how long (today only, after-hours, expired). Those three facts predict most questions more reliably than rereading the notice.

Second, watch for the "badge did not work" line and decide why. Almost always the passage is testing one of three causes — the badge expired, the access was revoked, or a second factor or escort was required — and distinguishing which is the whole point of the question.

Third, match the beginning to the end. A visit that checks in must sign out; a door that opens must log an exit; an employee who leaves must be offboarded. When a passage names one half of a pair and not the other, the missing half is usually where the question lives.

Drilled this way, visitor and badge passages resolve into a matter of who, where, and how long, and the vocabulary stops being a list of security terms and becomes a map of exactly what the notice is testing.