Attachment J - Section F Deliverables Schedules and Performance Requirements Summary Table_20260513.docx
DOCX document 51 KB Posted
- Attached to
- Legal Services for Unaccompanied Alien Children (UAC) Federal contract opportunity
- Solicitation number
- 75P00126R00003
- Issued by
- Not on record
About this file
This document is a Deliverables Schedule and Performance Requirements Summary Table that outlines all contractual deliverables, reporting requirements, and performance metrics for the Legal Services for Unaccompanied Alien Children (UAC) contract.
The table specifies eight primary tasks with detailed delivery requirements: Task I involves transition-in activities with full staffing within 120 calendar days of award; Task II requires development and delivery of legal orientation materials within 30 calendar days and conducting orientations for 100% of UAC within 10 business days; Task III mandates confidential legal consultations for all UAC within 10 business days of notification; Task IV encompasses direct legal representation services including court attendance, T visa applications, U visa applications, VAWA services, adjustment of status, temporary protected status, employment authorization, certificates of citizenship, special immigrant juvenile status, asylum applications, voluntary departure, and change of venue filings, with evidence of completion submitted via API and monthly reporting; Task V requires establishment and management of a nationwide legal service provider network with roster maintenance; Task VI involves annual data collection and transfer system interfaces with API connectivity; Task VII focuses on pro bono maximization with performance tracking; and Task VIII addresses transition-out planning and execution. All deliverables must be submitted via specified formats (API, MS Word, MS Excel, PDF) to the Contracting Officer (CO) and Contracting Officer's Representative (COR). Key reporting frequencies include weekly submissions during transition-in and transition-out periods, monthly project progress and staffing reports, and concurrent data entry to ORR systems for most services, with acceptable quality levels (AQL) of 95% for most service delivery metrics. The COR is designated as the primary recipient for most deliverables, with data also flowing to ORR via API connections where applicable.
View the file
Other files for this federal contract opportunity
Show all 50
Legal Services for Unaccompanied Alien Children (UAC) has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Deliverables Schedule and Performance Requirements Summary Table
| Task # |
| Description |
| Format |
| Frequency |
Due Date
| Recipient |
| AQL |
Task I: Transition-In
C.4.2.1 Task I Transition-In Plan submitted with the proposal. The plan shall, at a minimum, describe the Contractor’s ability to meet the requirements set forth in Section C.4.2.1. The plan shall include a description of how the Contractor will ensure minimum disruption to vital Government business and how they will achieve all proposed objectives within 120 calendar days after contract award, fully staff to meet this timeframe to achieve full performance, and ensure that there will be no service degradation during transition.
Initial: With proposal in accordance with proposal instructions in Section L
Microsoft (MS)Word for narrative information; MS Excel for quantitative information. MS PowerPoint at kick-off meeting.
Initial: with proposal in accordance with the submission deadline in Section L;
Presented in detail at the kick-off meeting
| CO, COR |
| N/A |
C.4.2.1 Task I Progress reporting regarding Transition-In performed IAW the requirements of C.4.2.1. Disruption minimized during transition-in.
See C.5.4.1 and C.5.4.2 for project progress and staffing status reporting.
Weekly project progress reporting during transition-in
COR,
ORR
N/A
C.4.2.1 Task I At completion of transition in, the Contractor shall be fully staffed and fully performing the requirements of the contract. Upon completion of the transition in, the Contractor shall notify the COR that transition in has been completed. The notice shall be in writing and include the listing of all cases by A Number and type and status of legal representation service.
Notification via e-mail at completion. For attachments:
MS Word for narrative information; MS Excel for quantitative information. API for case status information Within 120 calendar days after contract award
| COR |
| N/A |
Task II: Conduct Legal Orientations
C.4.2.2 Task II
| Develop and provide for approval audiovisual tools (e.g., recorded videos, online content) for use, as needed, in providing legal orientations to UAC provide legal orientations to UAC |
| In the format intended for delivery to UAC |
| Initial: 30 calendar days after award |
Changes: No less than 10 business days before first target use date
| COR |
| Initial only:+ 10 calendar |
day variance to the COR (i.e., 40 calendar days after award)
C.4.2.2.1 Task II The Contractor shall conduct legal orientations for 100% of UAC in ORR custody in accordance with 45 C.F.R. 410.1309(a)(2) and Section C.4.2.2 of the contract. These orientations shall inform UAC of their legal rights and responsibilities within the U.S. immigration system and shall be delivered by an independent legal service provider that has appropriate qualifications and experience.
| In-person or remote |
| Within 10 business days of notification except or the timeline approved by the COR for extenuating circumstances |
Every six (6) months for unrepresented UAC who remain in ORR custody.
As soon as practicable, but not later than 10 business days, for UAC released before receiving an orientation in custody.
| UAC |
| N/A |
C.4.2.2 Task II
| Provide legal orientation data specified in the “Legal Orientation Metrics” section of C.4.2.6 |
| API, MS Word |
for narrative information; MS Excel for quantitative information For API reporting, data entry concurrent with services provided (to the maximum extent practicable);
Monthly as part of the requirements of C.5.4.
COR,
API to ORR 95%
Task III: Conduct Legal Consultations
C.4.2.3 Task III The Contractor shall provide confidential legal consultations to 100% UAC in ORR custody to assess potential forms of relief from removal and other case disposition options in accordance with 45 C.F.R. 410.1309(a)(2).
Delivered per C.4.2.3 The contractor shall provide legal consultations to UAC within ten
(10) business days of notification by UAC care providers or ORR or the timeline approved by the COR for extenuating circumstances.
| UAC |
| N/A |
| C.4.2.3.1(4) Task III |
| Transfer Referral: Contractor shall provide documentation showing legal referral for unrepresented UAC |
in ORR custody upon a UAC's transfer between ORR facilities.
| API, MS Word for narrative information, and MS Excel for quantitative information |
| Monthly |
| COR |
| N/A |
C.4.2.3 Task III
| Provide data specified in the “Legal Consultation Metrics” section of C.4.2.6 |
| API, MS Word for narrative information; MS Excel for quantitative information |
| For API reporting, data entry concurrent with services provided (to the maximum extent practicable); |
Monthly as part of the requirements of C.5.4.
| COR, API to ORR |
| 95% |
Task IV: Direct Legal Representation Services
| C.4.2.4.1 Task IV |
| General Requirements Proof of Representation: |
Ensure all personnel, defined in C.4.1, timely enter notice of appearance with EOIR, the Department of Homeland Security (DHS), and with any other tribunal or administrative agency requiring notice of representation
Provide timely notice of representation to ORR in the designated system of record designated by the COR and care provider staff, i Listing and copies of all L-3A, G-28, and EOIR-28 forms and/or documentation of new representation.
API, pdf, MS Word for narrative information, and MS Excel for quantitative information including tracking by A Number For API reporting, data entry concurrent with services provided (to the maximum extent practicable);
Monthly as part of the requirements of C.5.4.
COR,
ORR (via API), applicable forum, care provider staff N/A
| C.4.2.4.1 Task IV |
| Representation In-Court/Proceedings Attendance: |
The Contractor shall provide direct legal representation to all UAC in or released from ORR care for all immigration court and/or any other DHS proceedings. Subject to availability of funding, the contractor can either invoice ORR for services identified as Items 3-13 listed on the pricing worksheet or provide the representation pro bono.
The Contractor shall ensure that a qualified legal representative is present and has entered an appearance at all scheduled immigration court proceedings and any other DHS-related proceedings for each UAC Per the requirements of this section and the PWS.
Contractor shall document, justify, and report within 24 hours of any instance of a UAC appearing without a qualified legal representative
| Report any instances of any appearances of a UAC without a qualified legal representative via email |
| Report any instances of any appearances of a UAC without a qualified legal representative within 24 hours |
| COR |
| N/A |
Task IV: T Visa Application Services (Item 3)
| C.4.2.4.2 Task IV |
| T Visa Application Services: |
The Contractor shall provide evidence of service completion as described in this section.
IAW C.4.2.6,
Task VI: APIs, Data shall be made available in a structured, searchable database format (Parquet, JSON, XML, or CSV as appropriate for system integration)
IAW C.5.4.1
Project Progress Reports: MS Word for narrative information, MS Excel for quantitative information.
IAW G.3.2.2 pdf copy of evidence of completion documents shall be sent to the COR for review prior to submission of the monthly invoice in IPP.
IAW C.4.2.6,
Task VI: Data entry into the system shall be concurrent with services provided (to the maximum extent practicable);
Per the schedule identified under C.5.4.1 Project Progress Reports
| COR;ORR (via API) |
| N/A |
Task IV: U Vias Application Services (Item 4)
C.4.2.4.2 Task IV
| U Vias Application Services: The Contractor shall provide evidence of service completion as described in this section |
| IAW C.4.2.6, |
Task VI: APIs, Data shall be made available in a structured, searchable database format (Parquet, JSON, XML, or CSV as appropriate for system integration)
IAW C.5.4.1
Project Progress Reports: MS Word for narrative information, MS Excel for quantitative information.
IAW G.3.2.2 pdf copy of evidence of completion documents shall be sent to the COR for review prior to submission of the monthly invoice in IPP
IAW C.4.2.6,
Task VI: Data entry into the system shall be concurrent with services provided (to the maximum extent practicable);
Per the schedule identified under C.5.4.1 Project Progress Reports
| COR; ORR (via API) |
| N/A |
Task IV: Violence Against Women Act (VAWA) Services (Item 5)
| C.4.2.4.2 Task IV |
| VAWA: Contractor shall provide evidence of service completion as described in this section. |
| IAW C.4.2.6, |
Task VI: APIs, Data shall be made available in a structured, searchable database format (Parquet, JSON, XML, or CSV as appropriate for system integration)
IAW C.5.4.1
Project Progress Reports: MS Word for narrative information, MS Excel for quantitative information.
IAW G.3.2.2 pdf copy of evidence of completion documents shall be sent to the COR for review prior to submission of the monthly invoice in IPP
IAW C.4.2.6,
Task VI: Data entry into the system shall be concurrent with services provided (to the maximum extent practicable);
Per the schedule identified under C.5.4.1 Project Progress Reports
| COR; ORR (via API) |
| N/A |
Task IV: Adjustment of Status (AOS) Services (Item 6)
C.4.2.4.2 Task IV
| Adjustment of Status (AOS) Services: Contractor shall provide evidence of service completion as described in this section |
| IAW C.4.2.6, |
Task VI: APIs, Data shall be made available in a structured, searchable database format (Parquet, JSON, XML, or CSV as appropriate for system integration)
IAW C.5.4.
Project Progress Reports: MS Word for narrative information, MS Excel for quantitative information.
IAW G.3.2.2 pdf copy of evidence of completion documents shall be sent to the COR for review prior to submission of the monthly invoice in IPP.
IAW C.4.2.6,
Task VI: Data entry into the system shall be concurrent with services provided (to the maximum extent practicable);
Per the schedule identified under C.5.4. Project Progress Reports
| COR; ORR (via API) |
| N/A |
Temporary Protected Status Services (Item 7)
| C.4.2.4.2 Task IV |
| Temporary Protected Status Services: Contractor shall provide evidence of service completion as described in this section |
| IAW C.4.2.6, |
Task VI: APIs, Data shall be made available in a structured, searchable database format (Parquet, JSON, XML, or CSV as appropriate for system integration)
IAW G.3.2.2
Pdf copy of evidence of completion documents shall be sent to the COR for review prior to submission of the monthly invoice in IPP
IAW C.4.2.6,
Task VI: Data entry into the system shall be concurrent with services provided (to the maximum extent practicable);
Monthly as part of the requirements of C.5.4.
| COR; ORR (via API) |
| N/A |
Employment Authorization (Item 8)
| C.4.2.4.2 Task IV |
| Employment Authorization: Contractor shall provide evidence of service completion as described in this section |
| IAW C.4.2.6, |
Task VI: APIs, Data shall be made available in a structured, searchable database format (Parquet, JSON, XML, or CSV as appropriate for system integration)
IAW C.5.4.
Project Progress Reports: MS Word for narrative information, MS Excel for quantitative information.
IAW G.3.2.2 pdf copy of evidence of completion documents shall be sent to the COR for review prior to submission of the monthly invoice in IPP
IAW C.4.2.6,
Task VI: Data entry into the system shall be concurrent with services provided (to the maximum extent practicable);
Per the schedule identified under C.5.4. Project Progress Reports
| COR; API to ORR |
| N/A |
Task IV: Application for Certificate of Citizenship (Item 9)
| C.4.2.4.2 Task IV |
| Application for Certificate of Citizenship: Contractor shall provide evidence of service completion as described in this section |
| IAW C.4.2.6, Task VI: APIs, Data shall be made available in a structured, searchable database format (Parquet, JSON, XML, or CSV as appropriate for system integration) |
IAW C.5.4.
Project Progress Reports: MS Word for narrative information, MS Excel for quantitative information.
IAW G.3.2.2 pdf copy of evidence of completion documents shall be sent to the COR for review prior to submission of the monthly invoice in IPP.
IAW C.4.2.6,
Task VI: Data entry into the system shall be concurrent with services provided (to the maximum extent practicable);
Per the schedule identified under C.5.4. Project Progress Reports
| COR; ORR (via API) |
| N/A |
Task IV: Special Immigrant Juvenile Status Services (Item 10)
| C.4.2.4.2 Task IV |
| Special Immigrant Juvenile Status Services: Contractor shall provide evidence of service completion as described in this section |
| IAW C.4.2.6, |
Task VI: APIs, Data shall be made available in a structured, searchable database format (Parquet, JSON, XML, or CSV as appropriate for system integration)
IAW C.5.4.
Project Progress Reports: MS Word for narrative information, MS Excel for quantitative information.
IAW G.3.2.2 pdf copy of evidence of completion documents shall be sent to the COR for review prior to submission of the monthly invoice in IPP
IAW C.4.2.6,
Task VI: Data entry into the system shall be concurrent with services provided (to the maximum extent practicable);
Per the schedule identified under C.5.4.1 Project Progress Reports
| COR; ORR (via API) |
| N/A |
Task IV: Affirmative and Defensive Asylum Application Services (Item 11)
| C.4.2.4.2 Task IV |
| Affirmative and Defensive Asylum Application Services: Contractor shall provide evidence of service completion as described in this section |
| IAW C.4.2.6, |
Task VI: APIs, Data shall be made available in a structured, searchable database format (Parquet, JSON, XML, or CSV as appropriate for system integration)
IAW C.5.4.
Project Progress Reports: MS Word for narrative information, MS Excel for quantitative information.
IAW G.3.2.2 pdf copy of evidence of completion documents shall be sent to the COR for review prior to submission of the monthly invoice in IPP
IAW C.4.2.6,
Task VI: Data entry into the system shall be concurrent with services provided (to the maximum extent practicable);
Per the schedule identified under C.5.4. Project Progress Reports
| COR; API to ORR |
| N/A |
Task IV: Voluntary Departure (Item 12)
| C.4.2.4.2 Task IV |
| Voluntary Departure: Contractor shall provide evidence of service completion as described in this section |
| IAW C.4.2.6, |
Task VI: APIs, Data shall be made available in a structured, searchable database format (Parquet, JSON, XML, or CSV as appropriate for system integration)
IAW C.5.4.
Project Progress Reports: MS Word for narrative information, MS Excel for quantitative information.
IAW G.3.2.2 pdf copy of evidence of completion documents shall be sent to the COR for review prior to submission of the monthly invoice in IPP
IAW C.4.2.6,
Task VI: Data entry into the system shall be concurrent with services provided (to the maximum extent practicable);
Per the schedule identified under C.5.4.Project Progress Reports
| COR; ORR (via API) |
| N/A |
Task IV: Change of Venue / Address Filings (Item 13)
| C.4.2.4.2 Task IV |
| Contractor shall provide evidence of service completion as described in this section |
| IAW C.4.2.6, |
Task VI: APIs, Data shall be made available in a structured, searchable database format (Parquet, JSON, XML, or CSV as appropriate for system integration)
IAW C.5.4.
Project Progress Reports: MS Word for narrative information, MS Excel for quantitative information.
IAW G.3.2.2 pdf copy of evidence of completion documents shall be sent to the COR for review prior to submission of the monthly invoice in IPP
IAW C.4.2.6,
Task VI: Data entry into the system shall be concurrent with services provided (to the maximum extent practicable);
Per the schedule identified under C.5.4. Project Progress Reports
| COR; ORR (via API) |
| N/A |
Task V: Annual Legal Service Provider (LSP) Network Management
C.4.2.5 Task V Annual LSP Network Management: The Contractor shall stablish and manage a robust nationwide network of qualified LSPs delivering timely and consistent legal services to UAC.
Reporting content IAW C.4.2.6.9.
| API; If required by COR: MS Word for narrative information; MS Excel for quantitative information |
| API. Data entry into the system shall be concurrent with network status. If requested by COR, within 2 business days |
Monthly IAW C.4.2.6.9
| COR; API to ORR |
| +72 hour variance for data update |
C.4.2.5 Task V Annual LSP Network Management: The Contractor shall build and maintain a roster of attorney and non-attorney volunteers who can provide legal services under the Contractor's supervision, as required, for any UAC or cases suitable for pro bono involvement.
| API; If required by COR: MS Word for narrative information; MS Excel for quantitative information |
| API. Data entry into the system shall be concurrent with roster status. If requested by COR, within 2 business days |
| COR; API to ORR |
| +72 hour variance for data update |
C.4.2.5 Task V Reporting Requirements:
Provide data detailing the delivery of all services under this Task per C.4.2.6
| API, MS Word for narrative information; MS Excel for quantitative information |
| API: Concurrent with services (to the maximum extent practicable); ; Monthly as part of the requirements of C.5.4. |
| COR; API to ORR |
| 95% |
Task VI: Annual Data Collection and Transfer System / Interface
C.4.2.6 Task VI Annual Data Collection and Transfer System / Interface: Provide all data required under C.4.2.6.
All data reported under this contract shall be made available through dashboards and direct connection to existing ORR platforms and tools (APIs).
APIs, Data shall be made available in a structured, searchable database format (Parquet, JSON, XML, or CSV as appropriate for system integration).
API: Concurrent with services provided (to the maximum extent practicable);
Monthly as part of the requirements of C.5.4.
| COR; API to ORR |
| +72 hour variance for data entry after services provided |
Task VII: Pro Bono Maximization
C.4.2.7 and C.5.2.3 Task VII
Pro Bono Maximization: Achieve at least the pro bono percentage proposed for the base period and each option period. IAW C.4.2.7 and C.5.2.3.
Provide data specified in the “Pro Bono Data Metrics and Reports” section of C.4.2.6
| API, MS Word for narrative information, and MS Excel for quantitative information |
| Percentage of total direct legal representation hours included in proposal; reporting per C.4.2.6; |
Monthly as part of the requirements of C.5.4.
| CO, COR |
| N/A |
Task VIII: Transition Out
C.4.2.8 Task VIII Transition-Out Plan:
The transition–out plan shall detail the contractor’s plan to facilitate the accomplishment of a seamless transition from the incumbent to the incoming contractor/government personnel at the expiration of the contract. The Contractor must work cooperatively with the incoming contractor/service provider and the Government in support of a seamless transition and continuity of all legal services.
| MS Word |
| Draft transition-out plan: No later than 30 calendar days after the completion of transitioning in. |
Final transition-out plan: No later than 120 calendar days prior to the end of each period of performance..
| COR |
| + 7 business day variance |
Task VIII: Transition Out
C.4.2.8 Task VIII
| Transition-out: Contractor shall complete the requirements of C.4.2.8 starting 120 calendar days prior to the end of the contract (or as directed by the CO) without service disruption |
| See C.5.4.2 and |
C.5.4.3 for project progress and staffing reporting
| Weekly project progress reporting during transition-out execution; transition-out completed in 120-calendar days. |
| COR; API to ORR |
| N/A |
Other Annual Requirements
| C.5.1.1.2(C) |
| Meeting Agendas: The Contractor shall support the Government’s establishment of meeting agendas as directed by the COR. |
| Word, PowerPoint, or Excel (as appropriate) |
| Not less than 3 business days prior to meeting occurrence at the direction of the COR |
| COR |
| + 1 |
business day variance
| C.5.1.1.2(C) |
| Meeting Minutes: When meeting with the ORR personnel, the Contractor shall record meeting minutes in writing and submit the minutes to the COR for contract documentation |
| Word document |
| Within 2 business days after meeting |
| COR |
| + 1 business day |
| C.5.1.2 |
| Contract Status Meetings: |
The Contractor shall participate in conference calls with ORR/COR.
| Video conference or in-person |
| Monthly unless directed |
| COR |
| NA |
| C.5.1.3 |
| Contract Performance Review Meetings: The Contractor shall prepare for and participate in contract performance review meetings to be scheduled every other month (unless directed otherwise by the COR) with the COR and other Government personnel as appropriate to review the Contractor's performance. |
| Meetings: video conference or in-person |
Contractor Performance self-assessment: template and in the format as directed by the COR Performance Review meeting: Every other month unless directed otherwise by the COR
Written Contractor Performance self-assessment no less than two (2) business days prior to the meeting.
| COR |
| N/A |
| C.5.1.4 |
| Kick Off Meeting: |
Within 10 business days of contract award, or as directed by the COR, the Government will conduct a kick-off meeting with the Contractor in accordance with the PWS.
| Video conference or in-person |
| Within 10 business days of contract award, or as directed by the COR |
| CO, COR |
| N/A |
| C.5.2 |
| Project Management Plan (PMP): The Contractor shall provide a Contractor PMP in accordance with the contract that fully documents its management approach for the recruitment, delivery, and execution of contracted services. The PMP shall consist of a Contract Management Plan, Quality Management Plan, and Pro Bono Services Plan. |
| Initial: With proposal in accordance with proposal instructions in Section L |
Annual: API, MS Word for narrative information; MS Excel for quantitative information Initial: With proposal in accordance with submission deadline in Section L
Revisions: The first revision, if necessary, is due within five (5) business days after the kick-off meeting. If returned with comment or rejected in part or whole by the Government, the Contractor shall then have seven
(7) business days to submit a revision that addresses the Government's comments or reason for rejection. The PMP or any of its components shall be updated by the Contractor and submitted to the COR as necessary but no less than annually (to the COR no less than 120 calendar days prior to the commencement of the following option period).
| CO, COR |
| First revision: + five (5) business days variance; |
Annual: + (10) business days variance
| C.5.4.1 |
| Project Progress Report: The Contractor shall provide progress reports in accordance with the contract |
| Utilizing the Government templates and via the modality required by the Government including through dashboards and direct API connection to existing ORR applications; to COR: via email (MS Word for narrative information; MS Excel for quantitative information). |
Email of large file files utilizing API: concurrent with services provided (to the maximum extent practicable).
To COR, weekly during transition-in and transition-out; otherwise monthly unless directed otherwise by the COR.
| COR; API to ORR |
| N/A |
C.5.4.2
| Contractor/Subcontractor Staffing Reports: The Contractor shall submit staffing reports (to include “status of required uninitiated and in-process background investigation and suitability determinations” in accordance with the contract. |
| Utilizing the Government templates and via the modality required by the Government including through dashboards and direct API connection to existing ORR applications.; to |
COR via email (MS Word for narrative information; MS Excel for quantitative information) To COR, weekly during transition-in and transition-out; otherwise monthly unless directed otherwise by the COR.
API reporting in accordance with reporting frequency to the COR.
| COR; API to ORR |
| N/A |
| C.6.3 |
| Travel Plan: The Contractor must submit a Travel Plan for review and approval for travel greater than 50 miles in accordance with the contract |
| Template provided by COR Plan submitted via email or other method cooperatively developed and agreed-to between COR and the |
Contractor during performance Travel plans must be submitted to the COR for review and approval at least five (5) business days in advance of planned travel.
| COR |
| +1 business day variance |
| H.7 |
| Adherence to Statutes, Regulations and Policies In the performance of all work under this contract, the contractor shall comply with and be guided by the authorities identified in this Section. |
Where the contractor determines it is unable, or potentially unable, to meet a performance requirement due to an apparent or actual conflict among applicable authorities, including ethics rules governing attorneys, the Contractor shall promptly notify the COR in writing, identify the conflict, and seek ORR guidance to resolve the conflict in a manner consistent with ORR’s statutory mandates.
| Email; Microsoft Word or pdf for any attachments |
| Within 24 hours of the identification of a conflict in authorities |
| COR |
| N/A |
| H.9 |
| Status of all Background Investigation and Suitability Determinations: Prior to allowing any contractor, subcontractor, or other personnel to perform services under this contract, the contractor shall ensure background investigations and suitability determination investigations are completed per the requirements of this section. |
| Utilizing the Government templates and via the modality required by the Government including through dashboards and direct API connection to existing ORR applications; to COR: via email (MS Word for narrative information; MS Excel for quantitative information) |
| To COR, |
weekly during transition-in and transition-out; otherwise monthly unless directed otherwise by the COR.
API reporting concurrent with reporting frequency to the COR monthly unless otherwise as directed by the COR
| COR; API to ORR |
| N/A |
| H.9 |
| Notification of Inability to Complete: Contractors must notify the COR in writing if they are unable to complete all the required background investigation components. Submitted as part of the C.5.4.2 |
Contractor/Subcontractor Staffing Reports and, Separate Email and included in C.5.4.2 Contractor / Subcontractor Staffing Reports
| Weekly and IAW C.5.4.2 Contractor / Subcontractor Staffing Reports |
| COR; API to ORR |
| N/A |
| H.12 |
| Security Requirements: As stated in the contract |
| As required |
| As required by the contract or directed by the COR, as applicable |
| COR, ORR |
| N/A |
| H.13 |
| Security Training: |
The Contractor (and/or any subcontractor) shall submit a roster by name, position, e-mail address, phone number and responsibility of all staff working under this contract where the Contractor shall develop, can access, or host and/or maintain a government information system(s).
| Email; MS Word/pdf or MS Excel for any attachments |
| Within seven |
(7) business days of the effective date of this contract and updated as staff are onboarded.
| COR |
| +2 business day variance |
| H.13 |
| Rules of Behavior (RoB). |
Signed RoB shall be provided
| Initially annually thereafter, which may be done as part of annual ACF Information Security |
Awareness Training
| COR |
| N/A |
File details come from the government source that posted it. Updated .