How HR Teams Should Manage Employees with a Pending I-765

Managing employees with a pending I-765 is not simply a matter of asking for an update every few weeks. Form I-765 is used to request an Employment Authorization Document, commonly called an EAD, and the pending period can affect onboarding, reverification, staffing plans, and employee communications. HR needs a process that separates what the company must verify from what it should never investigate.

The first principle is simple: a pending application is not the same as an approved document. HR should rely on the employee’s current, acceptable documentation and the applicable Form I-9 rules, rather than treating a receipt notice alone as proof that the employee may begin or continue working. The official USCIS Form I-9 resources should be the starting point for the company’s verification procedure.

The second principle is consistency. Two employees in similar situations should receive the same request, deadline, escalation path, and privacy protections. A documented policy reduces the risk of ad hoc decisions, unnecessary questions about immigration history, or employment actions based on assumptions about a pending case.

For example, suppose an employee’s EAD expires in 45 days and the renewal application is still pending. HR should not wait for the employee to discover a problem during payroll processing. The team should already know which date triggers a reminder, which documents it may review, who evaluates a possible extension rule, and when immigration counsel should be consulted.

A good policy does not predict the USCIS decision or promise a processing time. It creates a controlled response to each reliable update while preserving the employee’s confidentiality and allowing qualified professionals to interpret unusual situations.

HR should verify only the information needed for a lawful employment process. That normally includes the employee’s identity and employment eligibility documentation for Form I-9, the relevant document expiration date, any required reverification date, and the company’s own follow-up deadline. The employee’s full immigration file, legal strategy, or personal explanation of the case is generally not needed for routine HR administration.

A receipt number can be useful for tracking a USCIS filing, but it is not automatically a replacement for an acceptable Form I-9 document. HR should not infer eligibility from a screenshot, an email, or a case status phrase without checking the applicable official rules and the document presented by the employee. For a plain-language explanation of receipt numbers, see how USCIS receipt numbers are structured and used .

The company should also avoid demanding a specific document when the employee is entitled to present a valid alternative under Form I-9 rules. The USCIS guidance on completing Form I-9 explains the general process, including the role of the employee and employer in completing the form.

Questions should be narrowly framed. “Please provide the documents needed for the Form I-9 review by this date” is safer and more neutral than “What is happening with your immigration case?” or “When will your status be fixed?” The latter questions may invite unnecessary disclosure and create inconsistent treatment.

If HR is uncertain whether a document or notice supports continued employment, it should not make a confident guess. Escalate to qualified immigration counsel, the company’s Form I-9 specialist, or the appropriate compliance function, depending on the issue.

The most effective approach is early planning, not last-minute pressure. Connect document dates to a workforce calendar so HR, payroll, managers, and scheduling teams know when a review may be needed. The calendar should show an internal action date and an employee communication date, not expose sensitive case details to every manager.

Payroll should not be instructed to stop payment merely because an I-765 case remains pending. Any employment decision must follow the company’s documented compliance process and the applicable rules. If a document issue could affect continued employment, HR should involve the right specialist before changing a schedule, placing a hold, or ending an assignment.

Managers need a carefully limited message. They may need to know that HR is reviewing a documentation deadline or that staffing coverage should be planned, but they usually do not need to know the employee’s receipt number, filing category, or personal immigration circumstances. This separation protects privacy and reduces workplace speculation.

A useful internal service-level framework might require HR to acknowledge an employee’s deadline question within one business day, verify the available records within three business days, and escalate unresolved questions before the internal action date. These are company response targets, not predictions about USCIS processing.

For multiple employees, use a dashboard with fields such as case owner, receipt date, form type, document expiration date, next review date, last observed status, and escalation flag. Do not use a single “approved or not approved” field because it can create misleading conclusions and may encourage unqualified legal interpretation.

Employers should also be alert to discrimination and document-abuse risks. The U.S. Department of Justice guidance for employers on Form I-9 and immigration-related employment practices is a useful reference for building a fair, consistent process.

After the policy and ownership model are established, a case-monitoring tool can remove repetitive manual checks. OPSControl tracks a USCIS case using its receipt number, maintains a history of observed status changes, and can send notifications through Telegram when the tracked case changes. It also supports monitoring for several common USCIS forms, including I-765, I-485, I-130, I-751, and N-400.

For an HR team, the practical value is visibility rather than interpretation. An HR owner can receive a notification, compare it with the employee’s documented deadline, and decide whether the next step is a routine reminder, a document review, a staffing conversation, or legal escalation. OPSControl is not a government service or law firm, and its alerts should not be treated as proof that an employee may work or that a case has been approved.

A simple workflow could send I-765 status notifications to the employee and assigned HR case owner through Telegram, then use Zapier to create a task in the company’s approved workflow system. A second rule can notify payroll or staffing only when the HR owner marks the item as requiring operational planning. This prevents every status change from becoming a company-wide alert.

HR departments managing several family or employee cases can organize each case separately and retain a chronological history for internal reference. OPSControl uses one-time billing per case rather than a recurring subscription, with the stated standard price of $9.99 per case and reduced pricing for additional cases beginning with the fifth case. The company should still evaluate its procurement, privacy, consent, and retention requirements before adopting any external tool.

Because no monitoring system should be treated as infallible, keep an official-source verification step in the policy. The USCIS case status online guidance can help HR define what a status check is designed to show, while guidance on silent USCIS updates explains why a visible message may not capture every meaningful internal event.