Crew vetting and site access requirements set who may enter a data center during a relocation, what screening they must pass, and how their temporary access is issued and revoked. Normal controls assume a few known, badged people. A move puts a dozen or more outside workers on the floor for several nights, often named only the day before.
The controls that governed access on an ordinary Tuesday do not describe what is happening. Something has to, and building it after the crew arrives at the gate is too late.
When Should Crew Vetting Requirements Be Set?
The vetting requirement should be defined at the point the work is scoped, not negotiated when personnel are proposed. Vendors staff from a pool, and a vendor who learns about a background check requirement two days before a move will either miss the date or send whoever is already cleared for something else.
The standard needs to be specific about what is checked and over what period. A criminal history check at county, state, and federal level covering seven years is a common baseline. Identity verification and right-to-work confirmation are separate items. Drug screening is required in some sectors and not others. Where the work touches regulated data, the applicable framework may specify its own requirements — a healthcare environment under HIPAA, a card processing environment under PCI DSS, a federal environment with its own clearance rules and the personnel screening controls in NIST SP 800-53.
It also needs to be specific about recency. A background check from four years ago is not evidence of anything current. Annual re-screening is a reasonable requirement and most established vendors already do it.
Subcontractors are where this quietly fails. The prime vendor is vetted, screened, and insured, and then supplements crew from a local labor broker for the night shift. The contract should require that every individual on site meets the same standard regardless of who employs them, and should require disclosure of subcontracting rather than prohibiting it — prohibition just moves it out of sight.
What Should a Site Access Roster Include?
A site access roster should name every person expected on site, submitted far enough ahead that it can be processed and checked.
The roster should carry full legal name matching government identification, the employer of record, the role, and the dates and hours of expected access. Photo identification is verified at the door against the roster, and the person checking is given the authority to turn people away.
Same-day additions will happen. Crews change, someone calls out, and the vendor sends a replacement. A defined exception path — a named approver, a documented justification, an expedited check where the standard permits one — is better than either a blanket refusal that stops the move or an informal wave-through that defeats the control.
Escort requirements should be set by area rather than applied uniformly. A crew moving equipment through a loading dock and a corridor is in a different risk position than a technician working inside a cage containing another tenant's hardware. Where escort is required, the escort has to be a real assignment with a real person, not a responsibility added to someone who is already running the move.
How Should Temporary Badges Be Issued and Revoked?
Temporary badges should expire with the work, open only the areas it needs, and be collected at the end. Their value depends entirely on that cycle.
Issue them with an expiration matched to the work, not to the calendar month. A badge valid for three nights is a badge that cannot be used in week four. Scope them to the areas the work requires. A mover who needs the dock, the corridor, and one row does not need the whole floor, and most access systems support this granularity even when organizations do not use it.
Collect them at the end. Uncollected temporary badges are the residue every relocation leaves behind, and the access review three months later finds twenty active credentials belonging to people nobody can identify. A deposit, a sign-in and sign-out log, and a reconciliation at the end of each shift handles this. Automatic expiration handles the ones that are never returned.
Log everything. Badge reads, sign-in sheets, and video covering the access points form the record that answers the question an incident investigation will ask, which is who was where and when. That record is worth substantially more than the controls that produced it if something turns up missing.
The Contract Carries the Obligations
Vetting requirements belong in the agreement, not in an email thread.
The contract should state the screening standard, require certification that each individual meets it, require the same of subcontractors, and preserve the right to audit the records. It should address what happens when someone does not clear — replacement at the vendor's cost, not a schedule extension.
Confidentiality obligations should bind the individuals doing the work, not only the corporate entity. Personnel-level nondisclosure agreements are ordinary in this context and vendors are accustomed to them.
Where a specific regulatory framework applies, the corresponding instrument goes alongside. A business associate agreement for healthcare environments, a data processing agreement where personal data is in scope, facility clearance requirements for classified work. These have their own negotiation timelines and they are not fast.
How Do You Verify a Vendor's Screening Claims?
Ask for documents rather than accepting an assertion. A vendor's statement that their people are screened is a starting point. The compliance file needs more than an assertion.
Ask for the screening policy, a sample redacted report, and the name of the screening provider. Ask how recently each individual on the roster was checked. For sustained engagements, audit a sample periodically rather than at onboarding only.
The organization that owns the facility owns the access decision. It cannot be delegated to a vendor, and after an incident, the question of who was allowed onto the floor will be answered by the badge log and the roster rather than by the contract that was supposed to govern them.