Verification of Existing Staff and Why It Is Usually Barred

The electronic verification system is built around a hiring event. A case is created for a new hire, within a defined period after the hire date, using information already recorded on the form. Nothing in that design contemplates an employer returning to a worker who has been on the payroll for years and running the check again. The rules say so directly, and the prohibition is one of the more consistently misunderstood features of the system.

The default rule and its rationale

A participating employer verifies new hires and does not verify existing employees. The rule is absolute in its default form, and the reason is structural. The statutory verification duty attaches when a person is hired; it is not a recurring obligation revisited at intervals. A system that mirrors that duty naturally attaches to the same moment.

The second reason is about discretion. If an employer could re-run any current worker, it would have to choose which ones, and the choice would rest on something. In practice the something tends to be an accent, a name, a document that looked unfamiliar at the time, or a rumor. Each of those is the kind of basis the anti-discrimination provision exists to prohibit, and the flat rule removes the occasion for it.

The federal contractor exception

The principal lawful route to running an existing worker belongs to federal contractors. Where the acquisition clause applies, the contractor verifies employees assigned to the covered contract, whether or not those employees were hired before the contract existed. The obligation is created by the clause, not by any general employer power, and it is bounded by the clause's own terms and its calendar, which is treated in the federal contractor verification clause.

Verification of assigned employees is initiated within 90 calendar days after enrollment or within 30 calendar days of the employee's assignment to the contract, whichever falls later. That timing rule accommodates both the contractor who enrolls at award and the employee who joins the contract months afterward. Each assignment restarts the shorter of the two clocks for that person.

What counts as assignment is not defined with precision, and contractors resolve it differently. Some treat any charged hour as assignment; others require a formal designation in the staffing record. The safer construction is the broader one, because the cost of an unnecessary case is administrative while the cost of a missed one is a clause breach. Whichever construction is adopted, it should be written down and applied uniformly, since an inconsistent practice looks like selection.

The whole-workforce election

A contractor may instead elect to verify all existing employees working in the United States rather than tracking assignment. The election is expressly permitted, and it is often the more practical course for an employer whose staff rotate across contracts or whose assignment records are imprecise. It converts a continuous tracking problem into a single defined exercise followed by a simple ongoing rule.

Two exclusions survive the election. Employees holding an active clearance at the confidential, secret or top secret level are outside the requirement, as are employees for whom a background investigation has been completed and credentials issued under the applicable directive. Those exclusions exist because the underlying vetting has already occurred through a more demanding process.

The election also has a practical consequence for the paper file. Verifying a long-serving employee frequently surfaces a form that was completed years earlier under a different version, by a manager no longer with the business, and with omissions that were never noticed. Those defects are separate from the verification result and are corrected under the ordinary correction rules. An employer that plans the election without budgeting for the paperwork it uncovers tends to run out of time on the second half of the exercise.

What misuse looks like from the outside

The account record shows which cases were created, for whom, and when. A case created for someone with a long tenure and no contract assignment stands out, and a pattern of such cases is visible without any investigation into the employer's reasoning. Where the pattern correlates with national origin or with a particular document type, an investigator has both the misuse and the disparate treatment in a single dataset.

The right response to a genuine doubt about an existing employee is to separate the paperwork question from the status question. A defective form is corrected under the annotation rules, described in annotating a form completed late, and a systematic review is run as an internal audit rather than through the verification system. Where the doubt concerns status rather than paperwork, the employer is in knowledge territory, and a workforce verification counsel is better placed to assess the position than a supervisor acting on an impression.

Rehires, acquisitions and the boundary cases

Two situations sit close to the line. A person rehired after a genuine break in employment is a new hire, and a case is created in the ordinary way. A person whose employment continues without interruption is not a new hire, whatever internal transfer or job change has occurred, and no case is created. Whether a break was genuine is a factual question that turns on whether the employment relationship actually ended, not on how the payroll system recorded it.

The other boundary is an acquisition. Where an employer takes on a workforce from another entity, whether those workers are new hires depends on how the transaction is structured and on what the acquiring employer elects to do with the inherited records. The election available in that setting is a records question rather than a verification question, and it interacts with the retention obligations described in retaining and destroying records. What is not available is running selected inherited workers through the system while leaving the rest alone.