ssss.pdf

Control Number: USRAP-PG-RSC-03-v3.6 USRAP Processing Guide 03: Security Vetting Effective: May 31, 2024 Version: 3.6 Approver: Nicole Patel Summary: This Pr...

Control Number: USRAP-PG-RSC-03-v3.6 USRAP Processing Guide 03: Security Vetting Effective: May 31, 2024 Version: 3.6 Approver: Nicole Patel Summary: This Processing Guide provides standard operating procedures for U.S. Refugee Admissions Program (USRAP) refugee case processing using the START case management system, in compliance with Department of State Bureau of Population, Refugees, and Migration (PRM) and Refugee Processing Center (RPC) policies and requirements. USRAP Processing Guides are for Resettlement Support Center (RSC) use only and are not for further or public distribution. Any information sharing is governed by specific limitations and requirements in the cooperative agreements, the Memorandum of Understanding with the International Organization for Migration (IOM), and the USRAP Integrity & Compliance Guide. Direct requests to forward this Guide outside your organization, including to your subsidiaries, to the PRM Program Officer. Do not share this guidance outside your organization without written approval by PRM. Report suspected instances of fraud to the PRM/A Fraud Prevention and Integrity Team (FPIT), PRM Refugee Coordinator (RefCoord), and USCIS Desk Officer immediately. For further guidance, refer to the USRAP Integrity & Compliance Guide. Note: Red text indicates updated information. Text with dotted lines on the right-hand side indicate guidance specific to particular RSCs. Target Audience: START Users with the Caseworker User Role Topics: 1.0 Introduction 3 2.0 Initiating Security Checks 4 3.0 Consular Lookout and Support System (CLASS) Namecheck 4 3.1 CLASS Progress Statuses 5 3.2 CLASS Requests 6 3.3 Cancel CLASS Requests 8 3.4 CLASS Interim or Final Result Statuses 9 3.4.1 DHS Hit Review 10 3.4.2 Waivers for Not Clear CLASS Results 10 3.5 CLASS Conversion to CSC: Thailand Only 11 4.0 Inter-Agency Check (IAC) 12 4.1 IAC Applicant Task Statuses 12 4.2 IAC Requests 13 4.3 IAC Expedites 15 [Return to Top]  Control Number: USRAP-PG-RSC-03-v3.6 4.4 Cancel IAC Request 17 4.5 Update IAC Status for Applicants who do not require IAC 18 4.5.1 Applicants who are not in the required Age for IAC 19 4.6 IAC Result Statuses 20 4.7 Requirement to Monitor Recurrent Responses 21 5.0 Security Advisory Opinion (SAO) 21 6.0 Force Protection Review 21 7.0 Travel Fingerprints 22 7.1 Travel Fingerprint Statuses 23 7.2 Fingerprint Requests 24 7.2.1 Applicants Outside of TFP Age Requirements 28 7.2.2 Travel Fingerprints Collection Tab 29 7.2.3 Travel Fingerprints at the U.S. Embassy/Consulate 30 7.3 Travel Fingerprint Result Statuses 31 8.0 Not Clear Security Check Results: Moving Applicants, Applicant Statuses, & Case Groups 33 8.1 Resuming Case Processing for Cases with Not Clear Security Check Results 34 9.0 Bio-diffs and Re-Requesting Security Checks 35 10.0 Next Steps 38 Appendix A: Fingerprints at the U.S. Embassy Using Form FD-258 or Digital Scan 39 Appendix B: Fingerprint Exceptions (unclassifiable or medical fingerprint exception) 47 [Return to Top]  Control Number: USRAP-PG-RSC-03-v3.6 1.0 Introduction Refugee applicants in the USRAP complete security checks in part to determine their eligibility to resettle in the United States. Vetting partners must clear security checks before applicants can depart for the United States. USCIS officers will not approve the Form I-590 Registration for Classification until applicants receive a clear response for all security checks. The number of security checks applicants must receive depends on their age, nationality, and/or location. Policy Security clearances must be valid at the time of the refugee’s international departure. Security checks begin after initial data collection occurs (typically after the PreScreen Interview) and occur at different stages throughout refugee case processing. Security checks are conducted by U.S. government security vetting partners. Some security checks are recurrent throughout processing. RSCs initiate security checks (CLASS, IAC) and indicate Travel Fingerprint collection information in START, and track the progress and results. Note The START system will not automatically age out an applicant from security checks. To reach the Security Vetting Processing Stage Status of Completed Success, all applicants in the case need to have all security checks completed with statuses of Clear, Not Required, Excepted, Hit Clear or Deferred. If all security checks are complete for all applicants on the case, but one or more applicants have any security check Status of Not Clear, the Security Vetting Processing Stage Status will be Completed Failure. RSCs do not have responsibility to request or monitor security checks for applicants referred through the Special Immigrant Visa (SIV) or Follow-to-Join Refugee cases processed by U.S. embassies (FTJ-R, formerly Visa 93), with the exception of FTJ-R cases processed by RSC Africa and RSC MENA in Qatar. It is critical that all information received and captured for the first time from or about the Note applicant is entered in START by RSC staff before security checks are requested. This includes information in the applicant’s Alias Tab (passports, national IDs, UNHCR refugee certificates, birth certificates), addresses, family tree, contact information, and any biodata information according to the PreScreen Processing Guide or the Pre-Travel Data Collection. If information is provided by the applicant at a later stage, it is entered in START. New information may be collected at the time of USCIS interviews, Data Collection, during consultations, over the phone, or via email. The USRAP is transitioning to have USCIS assume responsibility for managing security checks. The aim is to provide a single, consolidated response to START for all security checks. The first security check to transition to this new system will be the Consular Lookout and Support System (CLASS) Namecheck. See the Section on Consular Lookout and Support System (CLASS) Namecheck section for more information about the transition. [Return to Top]  Control Number: USRAP-PG-RSC-03-v3.6 2.0 Initiating Security Checks RSCs must initiate security checks for each individual applicant or set the security check Status to Not Required pursuant to security check requirements as detailed below. Before requesting security checks, verify the following: 1. The case is in the correct Case Group(s). For more information about Case Groups, see the General Case Processing Guide and the Acceptance to Program Processing Guide. 2. All information collected during data collection is accurate and entered correctly into the system. 3. The PreScreen Validation Check Case Task Status is Completed Success. Please remember to Submit applicants (i.e., do not leave the applicant record in a Draft state) after moving applicants to other cases to prevent any disruption to the security vetting process. Note The system does not prevent security checks from being requested or from receiving security responses if a case has an Availability of Inactive. For information about security check statuses as prerequisites to the USCIS interview, refer to Note the USCIS Processing Guide. 3.0 Consular Lookout and Support System (CLASS) Namecheck The Consular Lookout and Support System (CLASS) Namecheck is a security check that runs applicant biographic information and aliases against a database owned by the U.S. Department of State Bureau of Consular Affairs. The Department of State Bureau of Consular Affairs owns the CLASS database the USRAP uses to submit an applicant’s biographic data and to receive information back on potential data matches for the applicant. START submits CLASS Name Check (CNC) requests to the CLASS database. The RPC reviews any potential “hits” to determine if they require further review by USCIS officers. START sends hits to USCIS for review on a ten minute cadence, and USCIS sends review results back to START. Possible CLASS Hit review results are Clear and Not Clear. If a waiver is available, it will be sent as a separate document. CLASS Hit information that has been adjudicated and cleared by USCIS officers does not expire. Starting in June 2024, PRM/A and USCIS will transition various locations whereby CLASS transitions to a Consolidated Security Check (CSC) run through USCIS systems. The transition will occur country by country. The CSC conversion for CLASS does not apply to SIV, FTJ-R processed by RPC, and Amerasians as these case types do not use USCIS systems to process security checks. FTJ-R cases processed by RSCs will continue to use CLASS. See the Section on CLASS conversion to CSC for more information. [Return to Top]  Control Number: USRAP-PG-RSC-03-v3.6 USCIS systems For potential reviews the matches, USCIS information. If there staff will conduct RSCs enter is a potential match, review. After applicant data into USCIS conducts analysis, USCIS START. START further review. If will either send a sends information there is no potential response to to USCIS systems. match in the START or collect information, USCIS more information will send a response during an to START. interview/re- interview. Applicants must have a Clear CLASS result to depart. Policy Once CLASS has been requested, certain changes to the biodata information for an applicant will require the RSC to re-request CLASS. For more information on re-requesting CLASS due to changes in biodata information, refer to the section on Bio-diffs and Re-Requesting Security Checks. SIV and FTJ-R cases processed by U.S. embassies receive CLASS checks through external Note processes. FTJ-R cases processed by RSCs Africa, MENA are requested in START. A CLASS result expires 15 months from the time the CLASS Status becomes Clear in START. If an applicant does not depart before the clearance expires, the RSC must manually re-request CLASS for the applicant. If RSC cancels CLASS after the previous Status was Expired, CLASS Status will remain Expired. Best practice is for RSCs to re-request CLASS two weeks before expiration. Track security Note checks by expiration date by using the filter feature in START. Staff will review the filter to determine if RSC will re-request CLASS. 3.1 CLASS Progress Statuses The CLASS security check progress appears in the Status box on the applicant-level CLASS task screen. This field automatically updates. The CLASS task progress Statuses include: Not Started Default Status. CLASS has not yet been requested. Requested CLASS has been requested. A START user can cancel CLASS when the CLASS status is Requested. Pending The CLASS Namecheck has been processed by the Bureau of Consular Affairs of the U.S. Review Department of State and is pending review by the RPC Namecheck Team to determine if the CLASS result requires further review by USCIS officers or additional security checks. CLASS results are [Return to Top]  Control Number: USRAP-PG-RSC-03-v3.6 typically returned in 10 business days, but some applicants will see immediate results. A START user can cancel CLASS when the CLASS status is Requested or Pending Review. Scheduled CLASS is under review by the RPC Namecheck Team. A START user cannot cancel CLASS when the CLASS status is Scheduled. 3.2 CLASS Requests CLASS can be requested for all active applicants on a case at one time from the Case Level or individually from the Applicant Level. To request CLASS from the Case Level: 1. Locate the CLASS Case Task. 2. Click the “Request CLASS Namecheck” button either from the top or bottom of the screen. 3. Click “OK” on the Confirmation prompt. [Return to Top]  Control Number: USRAP-PG-RSC-03-v3.6 4. Once submitted, the user will see a blue information banner on the top of the CLASS Case task with the following verbiage: "Successfully requested CLASS for: (Applicants’ Names). In order to request CLASS for all applicants on the case, the following must be true: Case Availability must be Active, Hold, or Inactive for the Request CLASS button to display on the CLASS Case Task. Note The CLASS applicant level task status must be Not Started or Expired. This functionality does not facilitate re-requests. If RSC needs to cancel the CLASS request, the cancellation must be done at the applicant level. To request CLASS from the Applicant Level: 1. Access the CLASS task directly from the applicant-level screen or from the My Workload module if the task is assigned to an Assignment Group or an individual. 2. On the applicant-level screen, select the “Tasks” tab. Click the underlined task number (beginning with “ATSK”) aligned with CLASS. You will be redirected to the CLASS Applicant Task record. [Return to Top]  Control Number: USRAP-PG-RSC-03-v3.6 3. On the CLASS applicant task record, click “Request CLASS Namecheck” in the top right corner. The page will automatically reload. Please reference the Bio-diffs and Re-Requesting Security Checks section for information on Note when to re-request CLASS due to new or updated biographic or contact information and how to use the ‘Active Bio-Diffs’ module. 3.3 Cancel CLASS Requests If RSC staff mistakenly requested CLASS, RSC can cancel a CLASS Namecheck Request if the CLASS Task Status is Requested or Pending Review. [Return to Top]  Control Number: USRAP-PG-RSC-03-v3.6 Canceling a CLASS request will update the CLASS Status to Not Started. If CLASS is canceled when the previous Status was Expired or Clear, the CLASS Status will remain as is. RSC will then request CLASS. When the CLASS task status is Scheduled, the request has been sent out to external partners Note and cannot be canceled. However, if a bio-diff occurs when a CLASS Status is at Scheduled, users can re-request the CLASS Namecheck. Please reference the Bio-diffs and Re-Requesting Security Checks section for additional information on the statuses where users can re-request a security check if that check has a bio-diff. To cancel CLASS Namecheck when CLASS Task Status is Requested or Pending Review, on the CLASS task record, click the “Cancel CLASS Namecheck” button in the top right corner. When CLASS task status is at DHS Envelope required, CLASS cannot be canceled. If DHS Note Envelope required needs to be canc 3.4 CLASS Interim or Final Result Statuses Complete the following actions for each respective CLASS result Status: Clear CLASS has been completed and the applicant has been cleared. Continue case processing as usual. Not Clear CLASS has been completed and the applicant has not been cleared. Schedule and process the case for USCIS Interview. A Not Clear CLASS result is not in and of itself grounds to administratively close a case. USCIS will determine whether the case can continue processing or should be closed (see the USCIS Processing Guide for the USCIS case closure process). Only RSC staff with the CAS Case Processor role can re-request CLASS when the CLASS status is Not Clear. Expired A CLASS result has expired after 15 months. Re-request CLASS if the case Availability is Active or Hold and the case is not waiting to be closed (i.e. waiting to distribute a decision letter). If CLASS [Return to Top]  Control Number: USRAP-PG-RSC-03-v3.6 has expired, RSC will see an on-screen notification of expiration will appear when RSC opens the case. Best practice is for RSC to maintain a saved search or filter to regularly review a list of all expired or soon-to-be expired CLASS checks. DHS Envelope CLASS has been completed and requires USCIS to review a DHS hit review. USCIS will resolve the Required DHS hit review Status and will send the result to START when the hit has been resolved. No RSC action required. 3.4.1 DHS Hit Review DHS Hit Review is conducted by the U.S. Department of Homeland Security’s (DHS) U.S. Citizenship and Immigration Services (USCIS). Results from the CLASS Namecheck that produce matches, or “hits,” against existing Consular records require DHS Review. An applicant who requires a DHS Hit Review has a CLASS result Status of DHS envelope required. As of October 2023, RSC staff no longer handle the DHS Hit Review form. The form will be maintained in Global and results sent to START. Applicants who require a review of a DHS Hit must clear this review before the RSC can Policy request travel for the case. START sends possible matches on biodata and alias information to USCIS/IRAD’s case management system, Global, for review. Global sends the results of the review back to START. When a CLASS memo is required for an applicant, USCIS would, in the past, send a generic email to RSC saying that a CLASS memo existed for the case. In START, USCIS will no Note longer send RSCs this message and, even if by accident they do, RSC will no longer add that message to the file since USCIS officers can see this information in Global. If USCIS/IRAD cannot make a determination in advance of the interview, an officer will review the information from the memo with the applicant at the time of USCIS interview. Infield adjudications will be sent from Global to START. Officers will upload DHS Hit Review forms to internal documents in Global. 3.4.2 Waivers for Not Clear CLASS Results If CLASS is Not Clear, USCIS may determine that a waiver is available. If the USCIS officer makes a determination of Not Clear Waiver Available for the CLASS Hit, USCIS officers can adjudicate the waiver concurrently without filing an I-602 waiver. If the USCIS officer decides not to concurrently adjudicate the I-602 waiver, RSCs can assist the applicant in applying for an I-602 Inadmissibility Waiver. If the USCIS officer makes a determination of Not Clear Waiver Not Available, the applicant cannot apply for an I-602 waiver. After USCIS reviews and adjudicates the I-602 waiver, if USCIS sends the waiver to RSC, scan and upload the waiver (Document Type: “I-602 Inadmissibility Waiver”) in START. forms USCIS is transitioning to store CLASS waiver information in Global and transmit the Note information to START; this will result in no physical forms for CLASS waivers. [Return to Top] [ 10 ]  Control Number: USRAP-PG-RSC-03-v3.6 3.5 CLASS Conversion to CSC: Thailand Only All newly created cases and applicants will have a new CSC Case and Applicant Task with status of Not Started. All existing cases and applicants in Thailand will have the CSC Task added. For existing cases that have a CLASS task, when a CSC result is received in START from USCIS, CLASS task will automatically update to Converted to CSC regardless of the CSC result. If the CLASS applicant task contains an expiration, START will clear the expiration when CLASS has a status of Converted to CSC. When START updates the CLASS status to Converted to CSC, the CLASS applicant task becomes read-only; RSC staff will not be able to change the CLASS status. START will no longer identify CLASS Bio-diffs for cases participating in the pilot locations. RSCs will not initiate the CSC check. START will send information to Global, and Global will use START case information in order to initiate the CSC check. Currently, the criteria from which Global will initiate the CSC check is one of: Data Collection Applicant Task is Completed, or Afghan Pre-Travel Data Collection Action Item is Completed Success, or Lautenberg Specter Pre-Travel Vetting Action Item is Completed Success. CSC Case and Applicant Statuses CSC Case CSC Applicant Task Additional Information Task Status Status Not Started Not Started Default status In Progress Pending CSC result is in-progress. Completed Not Clear Applicant has not cleared the security check. Case cannot continue Failure processing. In the initial phases of the transition to use CSC, USRAP partners do not expect to return a Not Clear result. Completed Clear Applicant has cleared the security check. The case can continue Success processing. In the initial phase, RSC can expect all results to come back as Clear. However, RSCs should note that cases that need further review from USCIS will come back with a Clear status and an Adjudicative Hold. No action from RSCs is needed. CSC expiration will populate in the expiration tab and will expire after 180 days. USCIS will manage the expiration of CSC. No action from RSC is needed. [Return to Top] [ 11 ]  Control Number: USRAP-PG-RSC-03-v3.6 In the event that RSCs would like to request expedited CSC processing or flag the need for a CSC re- request (if case is close to travel), RSCs should work with USCIS desk officers by providing a clear justification. 4.0 Inter-Agency Check (IAC) The Inter-Agency Check (IAC) is a security check coordinated by several U.S. government vetting agencies. The IAC is a recurring security check, meaning the security vetting partners continuously run the applicant’s data against their security holdings. USCIS sends all IAC clearances to START. IAC results are valid for 3 years (36 months) from the date the IAC was adjudicated by vetting partners. As of March 2022 the IAC security check is also known as the "National Vetting Center (NVC) check.” USRAP partners are likely to use the term “NVC check.” Applicants must have a Clear, Hit Clear or Not Required result to depart. Once RSC has Policy requested IAC, certain changes to the biodata information for an applicant will require the RSC to re-request the IAC. For more information on re-requesting IAC, refer to the section on Bio-diffs and Re-Requesting Security Checks. SIV, FTJ-Rs processed by U.S. embassies, and cases with the case Category Parolee receive IAC Note checks through external processes. FTJ-R cases processed by an RSC are requested in START. 4.1 IAC Applicant Task Statuses The IAC security check progress appears in the Status box on the applicant-level IAC task screen. The IAC progress Statuses include: IAC Applicant Definition RSC can RSC can RSC can cancel Task Status request update to Not IAC request/ IAC IAC/ Required expedite request Expedite IAC Not Started All applicants will have a default IAC Yes Yes No Status of Not Started. Yes – IAC Expedite Not Required RSC selects this Status if the applicant is Yes No No below the age of 14 or above age 80 at the time of processing. Yes – IAC Expedite [Return to Top] [ 12 ]  Control Number: USRAP-PG-RSC-03-v3.6 Requested RSC has requested IAC. No No Yes Expedite RSC has requested Expedited IAC. See No No Yes Requested IAC Expedites section. Expedite Expedite Request was approved. See No No Yes Approved IAC Expedites section. Expedite Expedite Request was denied. See IAC No No Yes Denied Expedites section. The IAC returns to Requested status and will process as a regular IAC request. Scheduled Applicant data has been transmitted to No No Yes RPC to send to vetting agencies. Expired IAC result expired after 3 years. RSC Yes Yes No must manually re-request IAC with the exceptions below: Yes – IAC Expedite 4.2 IAC Requests Access the IAC task directly from a case’s applicant-level screen or from the My Workload module if the task is assigned to an Assignment Group or an individual. Request IAC for each applicant whose biographic or alias tab dates of birth indicates that the applicant is between the ages (and including the ages) of 14 through 79, regardless of nationality or gender. Also request IAC for applicants who will likely be 14 at the time of travel to avoid processing delays (recommended age of 13 years). Please reference the Bio-diffs and Re-Requesting Security Checks section for information on Note when to re-request IAC due to new or updated biographic or contact information and how to use the ‘Active Bio-Diffs’ module. If any information in the Alias tab indicates the applicant's age is between the ages of 14 and Note 79, request IAC for the applicant. If RSC updates the IAC Applicant Task to Not Required, START will automatically change the status back to Not Started. RSC can request IAC for all Active (i.e., this does not apply to applicants with an applicant status of Deceased, Withdrawn, Abandoned, No Special Humanitarian Concern - Access) and submitted applicants on a case at one time from the Case Level Task or individually from the Applicant Level Task. Requesting IAC expedite is only available from the Applicant Level Task. [Return to Top] [ 13 ]  Control Number: USRAP-PG-RSC-03-v3.6 To request IAC from the Case Level: 1. Locate the IAC Case Task. 2. Click the “Request IAC” button either from the top or bottom of the screen. 3. Click “OK” on the Confirmation prompt. 4. Once submitted, the user will see a blue information banner on the top of the IAC Case task with the following verbiage: "Successfully requested IAC for: (Applicants’ Names).” START will only process the requests for Active applicants (i.e., applicants who do not have an Applicant Status of Deceased, Withdrawn, Abandoned, No Special Humanitarian Concern - Access) whose records are submitted in START. [Return to Top] [ 14 ]  Control Number: USRAP-PG-RSC-03-v3.6 Case Availability must be Active, Hold, or Inactive for the Request IAC button to display at the IAC Case Task (CTSK). Note The IAC applicant level task status must be Not Started. The Case Task request functionality does not facilitate IAC re-requests. If RSC needs to cancel the IAC request, the cancellation must be done at the applicant-level. To request IAC from the Applicant Level: 1. On the IAC Applicant Task, click the “Request IAC” button. 2. The page will reload and the Status field will display Requested. 4.3 IAC Expedites The majority of cases receive an IAC response within two weeks. However, if a case meets any of the criteria below, RSC can request an expedited IAC response if an IAC result is needed before 30 days: [Return to Top] [ 15 ]  Control Number: USRAP-PG-RSC-03-v3.6 Acute medical conditions where care outside the host country is required, OR Security/protection concerns, including individuals facing deportation, OR Minors at risk of aging in, OR Involvement in litigation in a U.S. court regarding their case, OR A case would otherwise be Ready for Departure (RFD), OR Pending expiration of travel documents where renewing travel documents would create undue hardship and delay. Follow the steps below to request an IAC expedite: 1. Click the “IAC Expedite” button from the IAC Applicant Task. Users are able to see the “IAC Expedite” button when the IAC Applicant Task Status is Not Note Started, Not Required, Expired, Hit Clear or Clear. Users are not able to see the “IAC Expedite” button if the case Availability is Closed. 2. Once expedited, the Applicant Task will display an Expedite Requested status. 3. Users with the IAC Expedite Approver role (IAC Expedite reviewers) can navigate to the “My Approvals” module to review the request. 4. After review, users can select the case(s) they would like to take action on and click on the “Action on Selected Rows” dropdown to either “Approve” or “Reject” the request. IAC Expedite Approver users are only able to see IAC approval requests in the “My Approvals” Note module and receive IAC approval email notifications relevant to their respective RSCs. [Return to Top] [ 16 ]  Control Number: USRAP-PG-RSC-03-v3.6 5. IAC Expedite checkbox will be checked once the IAC expedited is approved. 4.4 Cancel IAC Request If RSC has mistakenly requested IAC, RSC can manually cancel an IAC request from the IAC Applicant Task only. Canceling an IAC check will automatically update the IAC Status to Not Started. If IAC is canceled when the previous Status was Expired, IAC Status will remain as Expired. RSC will Request IAC or set it as Not Required as appropriate. Note If a bio-diff occurs when an IAC status is Canceled, users can re-request the IAC security check. Please reference the Bio-diffs and Re-Requesting Security Checks section for additional information on the statuses where users can re-request a security check if that check has a bio-diff. To cancel an IAC request: [Return to Top] [ 17 ]  Control Number: USRAP-PG-RSC-03-v3.6 1. On the IAC applicant task record, click the “Cancel IAC” button in the top right corner. A pop-up will appear requesting confirmation. 2. Click “OK.” 4.5 Update IAC Status for Applicants who do not require IAC For applicants with biographical and alias information that indicates the applicant is aged 13 or below, or 80 and above, do not request an IAC check. Instead, change the IAC Status from the default Status of Not Started to Not Required. If RSC changes the IAC Status to Not Required, but the applicant still requires IAC due to Note biographical, alias tab, or other instances of the applicant’s (e.g., the family tree record of that person) date of birth information, START will automatically change the Status to Not Started. To change the IAC Status to Not Required: 1. On the applicant-level screen, select the “Tasks” tab. Click the underlined task number (beginning with “ATSK”) aligned with “IAC.” You will be redirected to the IAC Applicant Task record. [Return to Top] [ 18 ]  Control Number: USRAP-PG-RSC-03-v3.6 2. On the IAC task record, click the “Not Required” button in the top right corner. 3. The page will reload and the Status field will read Not Required. 4.5.1 Applicants who are not in the required Age for IAC If an applicant reaches age 80 (“ages out”) when IAC check Status is Requested, the initial IAC check will continue to run recurrently. If an applicant who is otherwise not in the IAC age range (under age 14) previously received an IAC response (clear, not clear, Hit Clear, Approved by USCIS), that individual will continue to require an IAC security check. 1. Click the ‘Cancel IAC’ button on the IAC applicant task. [Return to Top] [ 19 ]  Control Number: USRAP-PG-RSC-03-v3.6 2. Select ‘OK’ on the confirmation window 3. Next, select ‘Not required’ on the IAC applicant task 4. The IAC applicant task is now Not Required. Due to recurrent vetting, an applicant who ages out might still receive an IAC result after aging out. If the result is Clear, no action is required, but if the Clear result changes to Expired and Note the applicant is 80 or older, the Status must be updated to Not Required. The START application does not allow a RSC user to request travel for an applicant that has a IAC Status of Expired, even if the applicant has aged out. If an applicant ages out when the IAC check is Clear, the Status will remain Clear. For applicants who do not require IAC based on their age (i.e. have aged-out, or are under age 14), but who previously have received an IAC result (Clear, Hit Clear, or Not Clear), if new biodata is captured which triggers a bio-diff, request IAC to get the updated result (after bio- Note diff). Then, For applicants who have aged out, wait for the IAC check to transition to Expired and set the IAC task to Not Required. 4.6 IAC Result Statuses IAC checks are recurring. Result Statuses represent the most current result of either Clear or Not Clear. Complete the following actions for each respective IAC Status: Clear The IAC check has been completed and the result is Clear. Hit Clear USCIS authorized approval over Not Clear check results. [Return to Top] [ 20 ]  Control Number: USRAP-PG-RSC-03-v3.6 Not Clear The IAC check has been completed and the result is Not Clear. 1. Other applicants on the case with the Not Clear result will receive individual results as they are evaluated separately. For example, they could receive Clear or Not Clear. 4.7 Requirement to Monitor Recurrent Responses Because the IAC is a continuous security check, an individual’s IAC Status can change at any time, from Clear to Not Clear and vice versa, until departure. Therefore, RSC must monitor for the IAC Task Status change. This is a filter that identifies when the system updates an IAC check to Not Clear. For a report that identifies a transition from Clear to Not Clear, please consult with RSC Data/Report staff. See USCIS Force Protection Review for guidance on when an IAC check flips to Not Clear for a case that is already scheduled for USCIS review in the current or subsequent quarter. 5.0 Security Advisory Opinion (SAO) A Security Advisory Opinion (SAO) is a security check facilitated by the U.S. Department of State. RSCs no longer need to request SAO. However, the SAO applicant task will remain until SAO is removed from the system completely. RSCs need to change the SAO task to Not Required. If SAO and IAC are in a Not started state, do not mark SAO as Not required until it is time to perform security checks. If SAO is in a Not started state and IAC is Clear, click Not required for SAO. If SAO is in a Not started state and IAC is Not clear, do not click Not required for SAO. The RPC and its vetting partners are addressing applicants with Not clear statuses for IAC and/or SAO separately. If SAO is Not Clear and IAC is any status, RSC staff should wait for SAO transition to see the outcomes of SAO being transitioned to IAC. 6.0 Force Protection Review The process for conducting Force Protection Review is as follows: 1. USCIS runs a review of pre-USCIS cases with an IAC Not Clear result to determine which cases USCIS will be able to interview. 2. USCIS will send a list of cases to RPC. This list will include whether a case is allowed to go for a USCIS interview, or not allowed to go for a USCIS interview. In the future, USCIS will submit this information via Global to START. 3. The RPC adds the Pre-Interview Check - USCIS Review Action Item to each applicant in the case, with the status of either: a. Not Started - USCIS has not completed their review b. Completed by USCIS - Interviewable (equivalent to completed success) c. Completed by USCIS - Not Interviewable (equivalent to completed failure) [Return to Top] [ 21 ]  Control Number: USRAP-PG-RSC-03-v3.6 4. The RSC can include cases with a Completed by USCIS - Interviewable status on a future USCIS Circuit Ride, in accordance with PRM guidance. 5. USCIS is responsible for communicating any future action for the cases with a Completed by USCIS - Not Interviewable status. 6. If a case has a mixture of Completed by USCIS - Interviewable and Completed by USCIS - Not Interviewable, RSC should not schedule this case for interview. All members of the case must have the Completed by USCIS - Interviewable status for the case to be scheduled. a. If an applicant with a “Completed by USCIS - Interviewable ” is moved from a case that had an applicant with a “Completed by USCIS - Not Interviewable,” the “interviewable” applicant can proceed to USCIS as long as all members on the case are “interviewable.” RSC staff will not have the ability to update the Action Item. Note RSCs should not take action on post-USCIS interview cases that USCIS added the Completed by USCIS - Not Interviewable status to; RSC-action is only required for cases that are pre-USCIS interview. At this time, and until further notice, RSC may only schedule cases with an “interviewable” status for Level 1, Level 2 urgency cases, and certain priority caseloads (as communicated by PRM), and cases that were previously removed from interview appointments due to a last minute IAC security check result of Not Note Clear. The Pre-Interview Check - USCIS Review Action Item Action Item does not take precedence of the Iraqi P2 Suspension Action Item. For a case that has been scheduled for the USCIS interview and has an IAC status flip from Clear to Pending or Not Clear, and therefore the case does not yet have the Pre-Interview Check – USCIS Review Action Item, the case must be removed from the USCIS Interview schedule if it is scheduled within the next two weeks, no matter the case’s urgency level. USCIS will run their review of pre-USCIS cases with an IAC Not Clear every two weeks. During the force protection review, NVC will review information for all case members, not just one particular applicant within the case. All requests for and questions about force protection review should be sent to Hannah Brown ([email protected]). Do not send your questions about Force Protection Review to USCIS or RPC. Only the IAC check is involved in Force Protection reviews. Therefore, the Pre-Interview Check-USCIS Review-Not Interviewable Action Item will only be applied based on whether applicants have an IAC Not Note Clear. 7.0 Travel Fingerprints Travel Fingerprints security check is a review of applicant fingerprints managed by USCIS and run against various U.S. government records. USCIS officers generally take fingerprints (FP) at the time of the adjudication interview, or at the PreScreen Interview in certain locations. This task involves scheduling a [Return to Top] [ 22 ]  Control Number: USRAP-PG-RSC-03-v3.6 fingerprint appointment with USCIS for the applicants on a case and recording Travel Fingerprint collection information. Travel Fingerprints expire 15 months after the result Status updates to Clear. Applicants require non- expired Travel Fingerprints to be ready for departure. An applicant may travel with a Travel Fingerprint Status of Clear, Not Required, Deferred, or Excepted. Travel Fingerprints expiration are provided by USCIS. Travel Fingerprints do not expire for the status Excepted. Policy Required applicants must have a Clear, Deferred, Excepted, or Not Required result to depart. SIV and FTJ-R cases processed by U.S. embassies receive Travel Fingerprint checks through Note external processes. When USCIS collects Travel Fingerprints for FTJ-R cases processed by RSC Africa, the collection information is recorded in START. 7.1 Travel Fingerprint Statuses The TFP progress appears in the Status box on the applicant-level TFP task screen. The TFP Statuses are: Not Started Default Status. Travel fingerprints have not yet been requested. Travel fingerprints returns to this Status after Travel fingerprints have been canceled. The Travel Fingerprint “Request” button will display in the top right-hand corner of the screen when an applicant is between the ages of 14 and 80. Not Required The applicant is outside of the required age range (14-79) and is not required to complete fingerprinting. If the RSC updates the TFP Applicant Task Status to Not Required, but the applicant meets the TFP requirement criteria, START will automatically change the Task Status back to Not Started. Requested The RSC has requested Travel Fingerprints. If not already done, a fingerprinting appointment should be scheduled. If an applicant’s fingerprints have been taken but are unusable, USCIS determines that the TFP must be retaken, which displays in START as Requested. Taken USCIS has scanned the Travel Fingerprint form and a USCIS officer has taken the applicant’s fingerprints. Await results from USCIS. The TFP status will only update to Taken when received from USCIS. While RSC does not update the TFP task status to Taken, RSC staff enter information on the date that USCIS collects Travel Fingerprints. USCIS may send a Taken status even if the Travel Fingerprint Status was previously Expired, Clear, etc. This means that the fingerprints require a new adjudication and USCIS will send an updated status once the re-adjudication is complete. No RSC action is required. If TFP status is at Taken when closing a case, there is no need to adjust the status.The case could be closed with the Taken status. [Return to Top] [ 23 ]  Control Number: USRAP-PG-RSC-03-v3.6 If a Travel Fingerprint Task Status is updated immediately from Not Started to Clear, do Note not reset the Travel Fingerprint Task Status to Requested. 7.2 Fingerprint Requests Request a Travel Fingerprint (TFP) security check by opening the Travel Fingerprints task screen or from the “My Workload” module if the task is assigned to an Assignment Group or an individual. If an applicant ages into Travel Fingerprints or is added to the case after the USCIS interview, follow the procedure below to request Travel Fingerprints. Note If the applicant is added to a case after the USCIS interview, but does not require Travel Fingerprints, update the Travel Fingerprint Task Status to Not Required. Travel Fingerprints can be requested for all Active (i.e., this does not apply to applicants with an applicant status of Deceased, Withdrawn, Abandoned, No Special Humanitarian Concern - Access) and submitted applicants on a case at one time from the Case Level or individually from the Applicant Level. Case Availability must be Active, Hold, or Inactive for the Request TFP button to display. The TFP applicant-level Task Status must be Not Started. This functionality does not facilitate re- requests. Note If RSC needs to cancel the TFP request, the cancellation must be done at the applicant-level. To request Travel Fingerprints from the Case Level: 1. Locate the Travel Fingerprints Case Task. 2. Click the “Request TFP” button either from the top or bottom of the screen. [Return to Top] [ 24 ]  Control Number: USRAP-PG-RSC-03-v3.6 3. Click “OK” on the confirmation prompt. 4. Once submitted, the user will see a blue information banner on the top of the Travel Fingerprint Case task with the following notice: "Successfully requested TFP for: (Applicants’ Names).” [Return to Top] [ 25 ]  Control Number: USRAP-PG-RSC-03-v3.6 To request Travel Fingerprints from the Applicant Level: Click the “Request TFP” button in the upper right-hand corner or bottom of the screen. The Task Status will change from Not Started to Requested. If necessary, cancel the TFP request by choosing the “Cancel” button in the top Note right-hand corner of the task screen. The TFP request will be canceled and the Task Status will change from Requested to Not Started. Once the Travel Fingerprints Task Status is Requested, work with USCIS to organize the fingerprint collection schedule, whether applicants are already appearing for USCIS Interview or are going to be scheduled to be fingerprinted by USCIS at another time. If applicants are being fingerprinted on the same day or in coordination with a USCIS Interview schedule, RSC does not need to create a separate Fingerprints schedule. If applicants are not being fingerprinted on the same day as USCIS Interview, schedule a USCIS Travel Fingerprints appointment for the applicants in START. Choose a day when [Return to Top] [ 26 ]  Control Number: USRAP-PG-RSC-03-v3.6 all applicants that need fingerprinting on a case can attend. Use the scheduling feature to create a Fingerprints schedule and add each case to the schedule. See the Scheduling Processing Guide for more information. To prepare for the Fingerprint appointment, generate and print the Travel Fingerprint Form for applicants who are 14 years old and older and younger than 79.5 years. USCIS will use this form and collect the applicant’s fingerprints and photograph on the day of the scheduled appointment. To generate the Travel Fingerprinting Form: 1. Select “Generate Forms” and select the applicants who required the form 2. Select Travel Fingerprint as the form in the Generate Forms page. 3. Click “Submit.” 4. Click “OK” in the generated Barcode. If USCIS is unable to scan the Barcode from the Travel Fingerprint Form, try scanning the Barcode directly from START. Note START will delete the Barcode from the Travel Fingerprint Applicant Task. 5. Click “Submit” one more time to generate the Travel Fingerprint Form. [Return to Top] [ 27 ]  Control Number: USRAP-PG-RSC-03-v3.6 For detailed information on the Generate Forms functionality, see the General Case Processing Guide. The Travel Fingerprint Form is not required when Travel Fingerprints are taken at a U.S. Embassy or Consulate. Note If USCIS does not write on or mark the form or even if officers initialize and date-stamp the TFP form, RSC can shred the form once the fingerprinting process is completed. The TFP generated form is not required to remain in START as part of the applicant’s A-file. Once complete, RSC may delete the form from START. Notify USCIS in-person at the time of fingerprint collection when an applicant has a physical impediment or missing/partial fingertips. USCIS can request a medical waiver for review for potential return of Travel Fingerprints Task Status of Excepted. After USCIS collects fingerprints, create a record in the Travel Fingerprint Collections tab. If the RSC used a separate Fingerprint Schedule, update the applicant attendance status for each applicant to the appropriate status regarding whether the applicant attended and completed fingerprint collection. See the Scheduling Processing Guide for more information on recording applicant attendance. USCIS will transmit Travel Fingerprint results and expiration date from Global to START through the interface The Travel Fingerprint results and expiration date will populate in the Travel Fingerprints Task record. Travel Fingerprint results received from Global are read-only in START. Run a filter list (this list looks at Travel Fingerprint Task updates in the past 15 days) to determine when Global has updated information on the Travel Fingerprints results. 7.2.1 Applicants Outside of TFP Age Requirements If an applicant does not require TFP, click the “Not Required” button and the Travel Fingerprints Task Status will change from Not Started to Not Required. Only update an applicant’s Travel Fingerprint Task Status to Not Required if the applicant is under the age of 14 and under or aged 80 and above. [Return to Top] [ 28 ]  Control Number: USRAP-PG-RSC-03-v3.6 RSCs should only put forth minor applicants for TFP if they are 14 years of age or older at the time of the USCIS interview. Leave the travel fingerprint status at Not Required for the individual who has not yet turned 14. If an applicant below 14 years of age has completed TFP collection, when they turn 14, the TFP status will switch from Not Required to Not Started and then to Clear within a short period of time. Individuals who have Travel Fingerprints collected are not eligible to have a Travel Fingerprint status of Deferred. If the Travel Fingerprints are collected, they must be reviewed. The RSC can use some discretion in determining what the best course of action is for an applicant that may age out of the deferred TFP status prior to travel. Consider the following when making a decision: Note If the case is unlikely to depart prior to the applicant turning 17, RSC may proactively reschedule applicant fingerprinting that aligns with an upcoming circuit ride, etc. If the case is likely to depart prior to the applicant turning 17, there is no need to reschedule applicant fingerprinting. 7.2.2 Travel Fingerprints Collection Tab When RSCs schedule an applicant for TFP collection and can confirm their prints have been collected, RSCs will record the date of collection and affirm prints have been collected in the Travel Fingerprint Collection tab located in the Applicant Task. This record provides RSCs the ability to indicate the TFPs have been collected while maintaining the Not Required status for individuals under the age requirement. RSC will update the Travel Fingerprint Collection date for all applicants who have Travel Fingerprints collected (i.e., not just individuals who have TFPs taken while not yet meeting the age requirement). Note The RSC role in TFP collection will be complete when the TFPs have been collected and entered in START. To create a record in the Travel Fingerprint Collection tab: 1. Click “New.” [Return to Top] [ 29 ]  Control Number: USRAP-PG-RSC-03-v3.6 2. Click the calendar icon and select the “Date Collected.” Note The Collected field will default to “Yes”. 2. Click the “Submit” button either at the top or bottom of the screen. 7.2.3 Travel Fingerprints at the U.S. Embassy/Consulate With USCIS approval, an applicant may have fingerprints taken at a local U.S. government office. For example, RefCoords who will be fingerprinting USRAP applicants are encouraged to liaise with Consular Affairs and their local Regional Security Officer (RSO) at post on fingerprint technical advice, as needed, or may contact their USCIS Regional Operations Desk Officer for questions related to taking refugee applicant prints in particular. Fingerprints must be captured by a U.S. citizen employee of the U.S. government or by a non- Policy U.S. citizen employee of the U.S. government under the supervision of a U.S. citizen employee of the U.S. government. RSC staff are not approved to collect fingerprints. [Return to Top] [ 30 ]  Control Number: USRAP-PG-RSC-03-v3.6 Note Only the FD-258 FP Card form should be used. Do not use the SF-87 form. Refer to the Appendix for guidance on manually capturing Travel Fingerprints and mailing the FD-258 FP card. For tracking and coordination purposes, RefCoords and RSCs should inform the relevant USCIS Regional Operations Desk Officer when fingerprint cards are mailed. RefCoords are requested to fingerprint applicants as soon as possible, prioritizing those cases where fingerprints are the only remaining processing step before the case could travel this fiscal year. 7.3 Travel Fingerprint Result Statuses After processing the travel fingerprints, USCIS’s system, Global, will transmit results to the START as Task Status of Clear, Not Clear, No Decision, or Excepted. Travel Fingerprint Task Status in START can be changed by USCIS Global Note (uscis.travelfingerprint.user) to any status, including, but not limited to, Clear, Not Clear, Excepted, and No Decision at any time, even if Travel Fingerprint Task Status was never changed to requested by RSC. Depending on the result of the TFP check, the RSC may need to take action. RSCs should complete the following actions for each respective TFP result Status: Clear TFP has been completed and the applicant has been cleared. TFP with the status of Clear will have an expiration date. Not Clear TFP has been completed and the applicant has not been cleared. TFP with the status of Not Clear will not have an expiration date. Please note that new case members can be added when there is TFP result of Note Not Clear for one or more case members. If the case has a TFP result of Not Clear prior to the USCIS Interview, USCIS will internally prepare a memo for the adjudicating officer. This memo is not available to RSCs. Schedule and process the case for USCIS Interview. A Not Clear Travel Fingerprint result is not in and of itself grounds to administratively close a case. USCIS will determine whether the case can continue processing or should be closed (see the USCIS Processing Guide for the USCIS case closure process). [Return to Top] [ 31 ]  Control Number: USRAP-PG-RSC-03-v3.6 If the case has a TFP result of Not Clear after the USCIS Interview, USCIS will see the updated security result in Global and have a list of cases to review to determine if an updated decision needs to be issued. USCIS will prioritize review of the cases based on their capacity. No Decision USCIS is still reviewing the TFP result, and no final determination has been made. The TFP does not need to be re-requested. If an applicant re-takes fingerprints twice with unclassifiable results (No Decision), then USCIS will request internal approvals for an exception, and will transmit the new Status of Excepted to START. TFP with the status of No Decision will have an expiration date. When one or more case members have a TFP status of No Decision, members can be split to another case. Additionally, new derivatives can be added to the Note case when there is a TFP No Decision result. Please note that START will not allow a case with a TFP status of No Decision to transition to Ready for Departure (RFD). Excepted The applicant is not required to receive a Clear TFP result to continue. USCIS has either granted a medical waiver to the applicant or the applicant’s TFP check has resulted in No Decision two or more times and USCIS has decided to grant an exception. TFP with the status of Excepted will not have an expiration date. Please reference the Appendix on Fingerprint Exceptions (unclassifiable fingerprints or medical related fingerprint exception). Expired Fifteen months have passed since the result of Clear was returned. No RSC action required. USCIS will re-review TFP. The status will remain Expired until USCIS reviews and updates the FP status in Global, which transmits to START, and turns Expired to Clear. TFP with the status of Expired will not have an expiration date. RSCs do not have to monitor expired Travel Fingerprints. USCIS has the ability to identify cases that have a Travel Fingerprint status of Expired in Global and will Note take action when needed. USCIS prioritizes review of Expired TFP based on urgency (expedite) and Must Travel by Date (MTBD). Deferred The applicant is not required to receive a Clear TFP result to continue. USCIS has deferred the decision on the applicant's TFP as the applicant is between the ages of 14-16 after the applicant's case completed a USCIS Interview. TFP with the status of Deferred will not have an expiration date. [Return to Top] [ 32 ]  Control Number: USRAP-PG-RSC-03-v3.6 With respect to children aged 14-16 whose applications were approved prior to turning 14 and now require fingerprint collection, USCIS has indicated that U.S. Customs and Border Protection (CBP) will fingerprint these minors at the port of entry in the U.S. rather than delaying travel where age-in fingerprints are the Policy only remaining processing step. This policy applies to child refugee applicants who aged into the fingerprint requirement subsequent to USCIS Interview but prior to approval of Form I- 590. START will now ingest both No Decision and Excepted Travel Fingerprint results through the Note START-Global interface, and populate them directly in the Status field on the Travel Fingerprint Applicant Task. Travel Fingerprints (TFPs) may flip from clear to taken due to a routine TFP refresh in the Global system targeted at preventing expired TFPs. This is expected system behavior from Global and START; it is not a glitch and should not be emailed to the [email protected] for action. The RIO biometrics team (RAIO-RIO-Biometrics) identify these cases using filters Note and will take the appropriate action when necessary. However, in special cases, like medicals, applicant scheduled for travel, etc., reach out to the RIO biometrics team (RAIO-RIO- Biometrics [email protected]), copying the appropriate IRAD desk officer and their PRM program officer. 8.0 Not Clear Security Check Results: Moving Applicants, Applicant Statuses, & Case Groups As of February 10, 2022, a Not Clear security check result is not grounds in and of itself to prevent a case from processing. If a pre-USCIS interview case receives a Not Clear result, refer to the section on Force Protection Review. USCIS will ultimately determine whether a case is permitted to proceed with processing regardless of the Not Clear security check result, or should be closed. This guidance applies to all cases that have an IAC Not Clear security check result and have not been presented to USCIS, regardless of when the Not Clear security check result was received. RSCs cannot move (split) applicants with a Not Clear security check result (except for Travel Fingerprints) to another case unless the applicant with a Not Clear result is being moved due to withdrawal, death, or abandonment. RSCs can add applicants to a case where one or more applicants on the target case has a Not Clear security check result. RSCs may continue to update Applicant Statuses to Deceased, Withdrawn, Abandoned, or No Special Humanitarian Concern - Access, as applicable, even if the applicant has a Not Clear security check result. After counseling the applicants, the RSC may move (split) members from a case with a Travel Fingerprint Not Clear result. Do not remove the case with the Not Clear Travel Fingerprint result from the Requested by USCIS Case Group. [Return to Top] [ 33 ]  Control Number: USRAP-PG-RSC-03-v3.6 RSCs should submit an ITSM ticket prior to splitting cases containing an applicant with a Not Note Clear security check result. RSCs, after consulting with the applicants, may remove cases from Resettlement: Same Household and/or Travel Case Groups to allow the clear case(s) to continue processing without the Not Clear case. The cases must remain in the Requested by USCIS Case Group for USCIS to track the connection between cases. If the applicant(s) indicates that they do not wish for the case with the Not Clear to be removed from the Resettlement: Same Household and/or Travel Case Group, then add the Case Group Hold Action Item with the status of Adverse Security Results. 8.1 Resuming Case Processing for Cases with Not Clear Security Check Results For Afghan P-1 and P-2 cases and Litigation cases ONLY: RSCs should create and monitor a filter to identify cases with a Not Clear security check where a bio-diff exists and re-request the affected security check. Only RSC staff with the CAS Case Processor role or the RSC Rerequest NCL role can re-request IAC when the status is Not Clear. For all cases: If no bio-diff exists and USCIS determines a Not Clear result will stand, but the applicant is approvable for travel: 1. Vetting partners will transmit the Hit Clear status to START. 2. RSC can continue processing. If a bio-diff occurs after ‘Hit Clear” status appears in START, the RSC will need to request expedited IAC and re-requests. RSCs will need to submit an ITSM ticket to request the Note expedited IAC because currently the IAC Expedite button does not display in START when a bio-diff occurs. If USCIS requests that IAC be re-requested for a case with a Not Clear result: 1. USCIS will assign the Biographic Data and Alternate Identities Action Item to the case to instruct RSCs to re-request IAC. 2. The RSC will request expedites for IAC and re-requests. a. To re-request IAC, follow the guidance in IAC Requests. 3. Once START receives the updated IAC result, USCIS will review the results. 4. If the new security check results come back Clear, RSC can continue processing the case through to travel. 5. If the new security check results come back Not Clear, USCIS will review the case again and determine if the case can continue processing. No action is needed by RSC. The case with the Not Clear result will appear in USCIS’ queue for Note review. 6. If the case is permitted to proceed with processing, the status will update to Hit Clear. [Return to Top] [ 34 ]  Control Number: USRAP-PG-RSC-03-v3.6 7. RSC can continue processing. At RSC discretion, if RSC wants to hold cases with a Not Clear security check from further processing, use the Denial/Closure Action Item with the Adverse Security Result status. This is optional and based on RSC local decisions regarding post-USCIS processing for Medicals and Cultural Orientation. Note If RSC is holding the case, and also needs to put the cases in the case group on hold, those cases will have an Availability of Hold with the Action Item Case Group Hold = Adverse Security Results. This should only apply to cases Travel and Resettlement Same Household Case Group. If the cases in the Case Group have Not Clear security check results, it is sufficient to use Denial/Closure Action Item with the status Adverse Security Result. If USCIS does not allow the Not Clear case to continue processing, follow case closure procedures as outlined in the USCIS Processing Guide. 9.0 Bio-diffs and Re-Requesting Security Checks Changing a bio-diffable field does not always trigger a bio-diff. Changing a bio-diffable field causes START to look at the change and determine if the information is an actual or significant change to a field that could result in the need to re-request CLASS or IAC. If there is a need to re-request the security checks, the Bio-diff notification will be a red banner displayed across the top of the Applicant-level screen. If the RSC updates applicant data, do not re-request a security check unless the banner notification displays indicating that a Bio-diff has occurred. Bio-diff errors do not clear until the security check is re- requested; if the banner appears erroneously or does not disappear after re-requesting, submit a ticket through the ITSM portal. START will not trigger a CLASS or IAC bio-diff for applicants with status = Abandoned, Note Deceased, Withdrawn, or No Special Humanitarian Concern - Access, even if the change would normally do so. [Return to Top] [ 35 ]  Control Number: USRAP-PG-RSC-03-v3.6 After a Bio-diff notification displays, RSCs can re-request the security checks at the following statuses: CLASS: Not Started, Scheduled, DHS Envelope Required, Cleared, Pending Review, or Expired CLASS: Not Clear (if the staff member has the CAS Case Processor) IAC: Not Required, Not Started, Scheduled, Clear, or Expired Note IAC: Not Clear (if the staff member has the CAS Case Processor or RSC Rerequest NCL role) Any case with a Bio-diff will not be able to transition to Ready for Departure Case Status until the triggered security checks are re-run. After re-requesting a CLASS security check, the bio-diff notification will disappear from the screen. However, after re-requesting an IAC security check, the notification will disappear once the IAC status updates to Scheduled. If a case with Availability of Inactive has a bio-diff, do not re-request the check unless otherwise instructed by PRM and USCIS. Note If there is a processing need to request CLASS or IAC due to bio-diff or expiration while the Case Availability is Inactive, re-request the check. Locate a list of applicants with a Bio-diff for CLASS or IAC by navigating to the “Active Bio-Diffs” module, or consult your RSC Data Team for a report: 1. Locate the “Active bio-diffs” module on the Filter Navigator under the Security Vetting Module. 2. Use the search fields to locate your case(s). 3. Notice that three columns indicate if a Bio-diff has been triggered for CLASS or IAC. [Return to Top] [ 36 ]  Control Number: USRAP-PG-RSC-03-v3.6 Note Access to the “Active bio-diffs” module will depend on users’ security permissions. Bio-diffs will not automatically force a re-request of Security Checks. RSCs will need to manually re- request triggered Security Checks. Updates to the following fields in a record that has already been “Saved and Submitted” will trigger a Bio- diff. After an update is made to a “bio-diff” (IAC or CLASS) field value, there is a brief (less than a minute) period of time, referred to as the “recalculation period”, in which START checks if the value is the same as the most recent value sent for the security check. If, during that recalculation period, START determines that the value is different, then it creates the bio-diff as usual. However, if the user immediately (within the 1 minute recalculation period) changed Note the value back to the previous value, then START recognizes that the value was already sent for the security check and does not create a Bio-diff. There are no re-request exceptions in START. However, there are some guidelines for Travel Documents meeting the criteria outlined in the Travel Processing Guide. Applicant First name, Middle name, Surname, Second surname, Maiden name, Sex, Biographical fields Birth country, Birth date, Nationality CLASS Alias Fields First name, Middle name, Surname, Second surname, Sex, Country of birth, Date of birth, Nationality, Place of issuance, Number Submission of a new Alias record Applicant Fields First name, Middle name, Surname, Second surname, Maiden name, Birth country, Birth state/province, Birth city, Birth date Alias Fields First name, Middle name, Surname, Second surname, Country of birth, Date of birth, Place of issuance, Number Submission of a new Alias record Employment Fields Employer, Street Address, City, State/Province, Country Submission of new Employment record [Return to Top] [ 37 ]  Control Number: USRAP-PG-RSC-03-v3.6 Address Fields Address (Street), City, State/Province, Country, Postal Code IAC Submission of new Address record Contact (Applicant) Phone Number, Contact Value (depending on Phone vs. Email Type) Fields Submission of new Contact record associated with an Applicant Family Tree Member First Name, Middle Name, Surname, Second Surname, Maiden Name, Fields (Current) Street Address, City, State/Province, Country, Postal Code, Nationality Submission of new Family Tree applicant record associated with an Applicant Family Tree Member Phone Number, Contact Value (depending on Phone vs. Email Type) Contact Fields Submission of new Contact record associated with a Family Tree member Addition of a new Family Tree member Update to any of the fields above for a Family Tree member Updating any of the fields above for a Family Tree member will cause an IAC bio-diff. Please note that if the Principal Applicant provides updated contact information later during the process, it will be necessary to update the Contact tab. This is to ensure that the security vetting partners receive the most up-to-date contact information. Removing an entire biodata record (for example, an address record or an employment record) does not cause an IAC Bio-diff and does not require an IAC re-request; however, deleting only part of a biodata record will cause an IAC Bio-diff and does require and IAC. Creating a new record and clicking “Save as Draft” will not trigger Bio-diff. Clicking “Submit,” “Save,” or “Save and Return” for a new record if it contains any of the above information will Note trigger a Bio-diff. Capitalization updates will not trigger an IAC bio-diff when an update is made on the Applicant, non-Applicant (Family Tree), Alias, Address, Employment, Contact, or Non-Applicant (Family Tree) Contact records. If left blank on the Applicant tab, START will not include “City” and “State/Province '' when checking for a bio-diff. This also applies to “Document Number” and “Issuing Country” on the Alias tab for documents that are not a passport or national ID. If staff updates or submits “Country of Birth'' on the Alias tab (for documents that are not passport or national ID), START will not include "City" and "State/Province'' fields when checking for a bio-diff. 10.0 Next Steps Security checks continue throughout the USRAP process, until the case is updated to an Availability of Closed, or all required security checks have been completed and all security check statuses are either [Return to Top] [ 38 ]  Control Number: USRAP-PG-RSC-03-v3.6 Clear, Not Required, Deferred, Hit Clear or Excepted. Continue processing with the USCIS Processing Guide. Once all required security checks have been completed and all security check statuses are either Clear, Not Required, Hit Clear or Excepted, continue processing with the USCIS Processing Guide. [Return to Top] [ 39 ]  Control Number: USRAP-PG-RSC-03-v3.6 Appendix A: Fingerprints at the U.S. Embassy Using Form FD-258 or Digital Scan In urgent cases, for instances when there is no Circuit Ride in the region, and it is not planned in the foreseeable future, RSC may request assistance from the U.S. Embassy in the processing location for fully rolled fingerprints to be taken of cases that are otherwise ready for departure (RFD); slapped prints are not sufficient. Such cases may include applicants whose fingerprints need to be re-taken for various reasons (e.g. bad quality of initial fingerprints). Initial coordination with the U.S. Embassy is done in coordination with PRM, copy in the email: RefCoord; PRM Program Officer; with relevant RSC staff and managers. RSC requests U.S. Embassy confirmation on their availability to assist with fingerprinting. Once confirmation is received, a designated RSC staff member informs the U.S. Embassy focal point on the number of applicants to be fingerprinted, inquire suitable dates, timeslots, and information needed using encrypted information. The information may include but not limited to: 1. Full name of the applicant 2. A-Number 3. Date of birth 4. Country of birth 5. Sex (Applicant-affirmed gender identity) 6. Current citizenship 7. Race 8. Biometrics Height Weight Hair color Eye color 9. Alias (all known names used by the applicant) 10. Current residence address 11. Reason for fingerprinting (I-590 for Refugee cases) Spreadsheet sample Ink Fingerprinting Appointment, Sep 15th Time Slot 9:30 10:00 Applicant Full Name Applicant 1: Full name Applicant 2: Full name A-number A XXX XXX XXX A XXX XXX XXX Date of Birth DDMMYYYY DDMMYYYY Place of Birth Sex Male Female [Return to Top] [ 40 ]  Control Number: USRAP-PG-RSC-03-v3.6 Citizenship Race White (includes Hispanic) White (includes Hispanic) Reason fingerprinted I-590 I-590 Biometrics Height 5 feet 1 inches 5 feet 3 inches Weight 105 pounds 129 pounds Eye color Hazel Green Hair color Brown Sandy Alias Current residence address [Return to Top] [ 41 ]  Control Number: USRAP-PG-RSC-03-v3.5 It is recommended to organize the information in an Excel Spreadsheet per example above. An encrypted file must be sent to the U.S. Embassy Focal Point. No START-generated reports are to be shared with the U.S. Embassy without prior PRM authorization. As soon as dates and time slots are confirmed, RSC must contact the applicants and schedule them for fingerprinting appointments at the U.S. Embassy in their processing location. Applicants shall be instructed to bring a copy of the USCIS Approval Letter (Notice of Eligibility) or USCIS Deferral Letter confirming their status and an ID document (e.g., passport). Only an applicant who needs to be fingerprinted shall be invited to the U.S. Embassy. Minors must be accompanied by the Principal Applicant in a case. Depending on the type of available equipment at the U.S. Embassy, fingerprints may either be taken using an ink-free, digital scan or using an ink and completing the FD-258 form. RSC staff member must inform the U.S. Embassy focal point on the procedures after fingerprints were taken. Fingerprints should be taken manually only when electronic fingerprinting equipment is not available, and the subject must be printed immediately. After receiving the appropriate training, U.S. Embassy staff should follow the instructions on Form FD- 258 for manually rolling fingerprints and completing the biographic information fields on Form FD-258. See sample below: Return to Top [ 42 ]  Control Number: USRAP-PG-RSC-03-v3.5 Return to Top [ 43 ]  Control Number: USRAP-PG-RSC-03-v3.5 Filling in the Masthead of Form FD-258: 1. The officer must type or clearly print all masthead information in BLACK ink. 2. Name Block: Clearly print the applicant’s last name, first name, and middle name in that order in this block. The middle name is to be spelled out. 3. Also Known As (AKA) Block: Clearly print any other names the applicant has used, especially birth names or any previous names (e.g., maiden name, religious name, etc.). If the applicant’s legal name is different from the name on the applicant’s ID document, be sure to place the name from the ID document in the AKA block. 4. Originating Agency Identified (ORI) Number Block: This should be completed with the name of the office holding the application or petition and that will receive the results of the FBI fingerprint check. Complete with the nine-digit ORI code of your office. Return to Top [ 44 ]  Control Number: USRAP-PG-RSC-03-v3.5 5. Applicant’s Signature Block: The applicant may not sign the Form FD-258, Fingerprint Card, prior to being fingerprinted. If he or she has already signed, it is permissible to white out the signature. The signature may then be re-executed in the presence of an officer after the fingerprints have been taken, as required by step 26. 6. Applicant’s Address Block: Clearly print the applicant’s complete, permanent U.S. address in this block. Some applicants may enter foreign address if they do not maintain a U.S. address. Care should be taken to ensure that the address is correct and matches the address provided on the application form. 7. Date of Birth (DOB) Block: The applicant’s date of birth must be clearly printed in this block. 8. Citizenship (CTZ) Block: The name of the country of which the applicant is a citizen should be printed in this block. 9. Sex (SEX) Block: Print F for female and M for male. 10. Race (RACE) Block: Print one of the following corresponding alphabetic codes in this block. Write the code with which the applicant most closely identifies: i) (1) A Asian or Pacific Islander; ii) (2) B Black; iii) (3) I American Indian or Alaskan native; iv) (4) U Unknown; or v) (5) W White. 11. Height (HGT) Block: Print the applicant’s height, in feet and inches, in this block. 12. Weight (WGT) Block: Clearly print the applicant’s weight, in pounds, in this block. 13. Eye Color (Eyes) Block: Print one of the following three-letter codes to show the applicant’s eye color in this block: vi) (1) BLK Black Eyes; vii) (2) BLU Blue Eyes; viii) (3) BRO Brown Eyes; ix) (4) GRY Gray Eyes; x) (5) GRN Green Eyes; xi) (6) HAZ Hazel Eyes; xii) (7) MAR Maroon Eyes; or xiii) (8) PNK Pink Eyes. 14. Hair Color (Hair) Block: Print one of the following 3-letter codes to show the applicant’s hair color in this block: xiv) (1) BAL Bald; xv) (2) BLK Black Hair; Return to Top [ 45 ]  Control Number: USRAP-PG-RSC-03-v3.5 xvi) (3) BLN Blonde Hair; xvii) (4) BRO Brown Hair; xviii) (5) GRY Gray Hair; xix) (6) RED Red Hair; xx) (7) SDY Sandy Hair; or xxi) (8) WHI White Hair. 15. Place of Birth (POB) Block: Print the name of the country where the applicant was born in this block. 16. Originating Agency Case Number (OCA) Block: This block should be left blank. 17. FBI Number (FBI) Block: Enter this information if known. Otherwise, leave this block blank. 18. U.S. Armed Forces Number (MNU) Block: If the applicant has been assigned a U.S. Armed Forces number, clearly print it in this block. Otherwise, this block should be left blank. 19. U.S. Social Security Number (SOC) Block: If the applicant has been assigned a U.S. Social Security number, print it in this block. Otherwise, leave this block blank. 20. Miscellaneous Number (MNU) Block: If the applicant has been assigned an alien registration number (A number), it should be printed in this block. 21. Date Fingerprint Block: Clearly print the date. 22. Signature of Person Taking Fingerprints: Sign at the time of taking the fingerprints. 23. Employer and Address Block: The name and address of the agency taking the fingerprints should be clearly printed in this box. 24. Reason Fingerprinted Block: The form number of the associated DHS application (I-590) should be printed in this block. 25. Applicant’s signature: As indicated in step 6, once the FD 258 is completed, and the fingerprints have been taken, the applicant must sign his or her name in this block in the presence of the person taking the prints. The signature must match the name printed in the Name Block. 26. Upon completion of the Form FD-258, Fingerprint Card, place the fingerprint card in an envelope and proceed to seal. The officer must sign his or her name across the sealed envelope flap. Submit the fingerprint cards to the appropriate office. As soon as fingerprints of the scheduled applicants are taken, the U.S. Embassy focal point must inform RSC staff. When the individual’s fingerprints are collected manually, on Form FD-258, Fingerprint Card, the FD-258 will not be returned to the applicant/petitioner nor the RSC. The staff who collected the fingerprints will forward the FD-258 to the Nebraska Service Center (NSC) to have the FD-258 scanned and electronically sent to the FBI for processing. All manually collected fingerprints taken on form FD- 258 must be transmitted in a secure manner. This means that the U.S. Embassy staff should place the fingerprint card in an envelope and seal the envelope, then place the envelope inside a second Return to Top [ 46 ]  Control Number: USRAP-PG-RSC-03-v3.5 envelope, and mark this envelope with the complete address of the sender and recipient. Fingerprints must be sent either through diplomatic pouches or the U.S. Postal Service. Staff should not use the host country’s postal system to transmit fingerprints. RSC staff must ensure and confirm with the U.S. Embassy focal point that completed FD-258 fingerprinted cards are not returned to the applicant or the RSC. They should be sent directly to the NSC per instructions above. If available, RSC focal point requests tracking numbers of the envelopes for follow-up purposes. Note Follow up on data and dates with USCIS is required. After the cards are shipped RSC notifies USCIS (copied: PRM Ref. Coord., PO) with the submission of the cards date, airway bill # if available, and the list of case details. Follow up periodically to check the status of the FPs. In case of any delay, contact USCIS Regional Desk Officer. The U.S. Embassy is not copied. All fingerprints collected manually on FD-258 should be mailed to the NSC at the following address: USCIS Nebraska Service Center Fingerprint Clearance Coordination Center Attn: Carisa Bergen, Supervisor Immigration Service Analyst P.O. Box 87251 Lincoln, NE 68501-2521 The following address should be used for cases where a courier/express delivery is used: USCIS Nebraska Service Center Fingerprint Clearance Coordination Center Attn: Carisa Bergen, Supervisor Immigration Service Analyst 850 S Street Lincoln, NE 68508 Return to Top