Badges [ 13 ] [-]
Memberships [ 3 ] [+]
Activity Stream [+]
Ideas Contributed [ 118 ] [+]
Today, the Staging and the Production systems may not have identical code running because new code is tested on Staging. This means that testing, training, and debugging must be done on the Production system where a valid SSN and document numbers must be used. I suggest adding a Test system that is identical to Production except that is uses an E-Verify Simulator. This would allow it to be used 24/7 and would not require ...more »
The E-Verify user manual and most others have not been updated for the modernization updates. The manuals must be consistent with the product to be useful. No updates to E-Verify should be released without updated documentation being published at the same time.
The E-Verify GUI requires the user to upload scanned copies (front and back) of the employee's document before even creating a case. The only time E-Verify even needs the documents is if a) an initial status of DHS TNC is returned, AND b) the employee decides to contest the case results. This approach assumes that the person entering the information into E-Verify has a scanner and knows how to use it. It also increases ...more »
The new E-Verify public site does not include a page for manuals. This makes it very difficult to find them and not all of them are posted on the E-Verify GUI.
Please post the manuals, like they used to be, on the public site with their own page.
The dropdown at the end of the client enrollment process shows E-verify instead of E-Verify.
The E-Verify Modernization project only updated the headers and footers of the E-Verify GUI on the pages that were changed. Pages not changed still have the old headers and footers, which provide different menu options and footer links. When updating the UI of a website, the headers and footers for all pages should be the same. Why have only some pages with the new design and others with the old design. Not a good approach. ...more »
E-Verify should not prompt the user to indicate that no photo displayed when a Photo Match document is used on Form I-9. E-Verify should already know that no photo exists and not prompt the user at all. Asking users to indicate that no photo displayed will result in users responding incorrectly saying that no photo was displayed when one was.
E-Verify should be hardened to minimize user errors.
Regarding the What's New item: All E-Verify Cases Must Reach A Final Case Result and Be Closed 1. E-Verify will transfer all case data to a new interface later this month. Q: E-Verify should tell customers (users and agents) what is happening, when it is happening, and why it is happening 2. Open cases that have not been accessed for more than 365 days will be closed by E-Verify, but will remain accessible to employers ...more »
E-Verify should provide more detail as to the enhancements listed in newsletters. For example, the high-level information provided regarding E-Verify Modernization Coming in Spring 2018 is very general and does not give users (especially employer agents and Web Services users) any specifics on what the improvements are or how they will or won't impact users. E-Verify should provide customers (i.e., users) more detail ...more »
When the FAQ page is updated on the E-Verify public website the date of the update is listed at the bottom right of the page. However, the updates are not noted. When an update is made mark it somehow (bold, red asterisk, date updated in title, etc.) so users know what information/guidance is new since the last update. This way users can easily find the updates without drilling down into every question.
When the Q&A page is updated in I-9 Central the date of the update is listed at the bottom right of the page. However, the updates are not noted. When an update is made mark it somehow (bold, red asterisk, date updated in title, etc.) so users know what information/guidance is new since the last update. This way users can easily find the updates without drilling down into every question.
Add a field to the Web Services API for the hiring location to be passed. What's the purpose of adding hiring locations to E-Verify if the API doesn't allow the location to be passed to E-Verify?