Identify the work that would actually remain in the United States and why it requires the claimed knowledge. Do not keep an obsolete deployment schedule in the account.
Reassess the assignment after a project delay
There may be relevant preparation or validation work, but describe it accurately rather than assuming its existence. Have material changes and authorization reviewed before the employee starts a revised assignment.
Identify which sessions, responsibilities or locations changed and what remains the same. A customer launch date does not guarantee an authorization decision or excuse inconsistencies in the submitted account. Preserve the original assignment plan alongside the revised one rather than overwriting it, so a reviewer can compare what was proposed with what is now expected. Document the postponement itself through internal approval memos, an updated statement of work, or a revised sequencing plan that shows the delay reflects a genuine operational decision rather than a gap in eligibility. Confirm with counsel whether the existing filing still describes the position accurately or whether an amendment better reflects the current plan, since relying on an outdated description carries its own risk. Notify the relevant adviser as soon as the postponement becomes likely rather than waiting until a decision is imminent, because early review leaves more options for correcting the record. Keep the person responsible for the U.S. operation involved throughout, since that person can confirm which parts of the original plan still hold.