SSN QA_FOIA-eDiscovery BPA.xlsx
XLSX spreadsheet 32 KB Posted
- Attached to
- Freedom of Information Act (FOIA)/eDiscovery FedRAMP-authorized cloud-based platform for Treasury
- Solicitation number
- 2032L226N00002
- Issued by
- Not on record
About this file
This is a Sources Sought Notice Excel workbook for a Department of Treasury FOIA/eDiscovery enterprise platform procurement. The document seeks industry input on capabilities for a department-wide Blanket Purchase Agreement (BPA) targeting a unified, FedRAMP-authorized cloud-based platform to manage electronically stored information (ESI) across Treasury's 50+ bureaus, including IRS, Fiscal Service, and others. The comprehensive questionnaire covers vendor capabilities in areas such as platform features, AI/ML technologies, multimedia processing, compliance controls, case management, data ingestion, enterprise scalability, and potential teaming arrangements.
Key technical requirements include supporting high-volume ESI workloads (terabytes of data, 200+ concurrent users), comprehensive FOIA and eDiscovery lifecycle management, advanced features like predictive coding and intelligent redaction, multimedia processing, and robust compliance with federal standards including FISMA, NIST, Privacy Act, and Section 508. The sources sought notice aims to gather market intelligence to shape the acquisition strategy, with vendors invited to respond via an Excel template detailing their technical capabilities, enterprise implementation experience, and recommended approaches for a consolidated FOIA/eDiscovery solution across Treasury's complex organizational landscape.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| SSN QA_FOIA-eDiscovery BPA_12.18.25.xlsx | XLSX spreadsheet | |
| SSN QA_FOIA-eDiscovery BPA_12.15.25.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Instructions
| Instructions |
| 1. Purpose |
| This Excel workbook is designed to gather standardized sources sought responses from industry regarding turnkey workforce development, training, and hire-train solutions. |
| 2. How to Complete |
| - Complete all fields in the 'Company Information' and 'SSN Questions' tabs. |
| - Use the dropdown menus provided in the 'Response Options' column where applicable. |
| - For open-text items, enter your response directly into respective cell in Column C. |
| 3. Dropdown Responses |
| Cells marked as 'Dropdown' include pre-configured selectable options. |
| If an option labeled 'Other' is selected, please provide brief clarification in "Response Details" column. |
| 4. Multi-Select Questions |
| Some dropdowns include items that may require more than one applicable response. |
| Since Excel dropdowns allow single selection only, please use one of the following methods: |
| a. Select the most relevant single response; AND |
| b. Provide details in the "Response Details" column. |
| 5. Open Text Fields |
| For narrative responses, please keep entries concise (3–6 lines preferred). |
| 6. Do Not Modify |
| Please do NOT modify: |
| Column Headers |
| Dropdown Option List |
| Structure of Worksheet |
| 7. Saving and Submitting |
| After completing the form, save a copy using the following naming format: |
| <CompanyName>_SourcesSought_Response.xlsx |
Submit the completed workbook according to the instructions in the SAM.gov notice.
| 8. Questions |
| Information or questions submitted in response to this Sources Sought Notice should be sent via email to Angela Gallo at Angela.C.Gallo@irs.gov with a subject of “(insert company name) FOIA/eDiscovery BPA Sources Sought Response”. Any questions related to this notice can be sent to the above email address prior to response deadline. |
Company Information
| Company Information |
| Company Name |
| Address |
| Cage Code |
| Unique Entity Identifier (UEI) |
| Size Classification |
| Socio Economic category |
| Primary POC 1, name, email, phone number |
| Primary POC 2, name, email, phone number |
SSN Questions_FOIA-eDiscovery
| Question Number | Questions | Response Options | Response Details |
| General | |||
| 1 | Does your company have experience providing large-scale FOIA, eDiscovery, or records-management SaaS solutions for federal or commercial clients? | ||
| 1a | If so, please provide a brief list of relevant engagements, including client, scope, and solution components. | ||
| 2 | Does your company currently offer a unified FOIA + eDiscovery platform? | ||
| 2a | If no, do you provide these capabilities through integrated partner products, modules, or teaming arrangements? | ||
| 2b | If yes, please list the integrated components of your platform (e.g., case management, processing engine, review module, redaction suite, reporting engine, foia.gov, pay.gov, login.gov and id.me via enterprise authentication tools). | ||
| 3 | Does your company hold an active FedRAMP Authorization for any FOIA/eDiscovery solution? | ||
| 3a | If yes, specify the FedRAMP level (Moderate or High), sponsoring agency, and authorization boundary. | ||
| Vision | |||
| 4 | Has your company delivered enterprise SaaS platforms capable of supporting the full lifecycle of FOIA and litigation discovery (preservation through production)? | ||
| 5 | Has your platform supported high-volume ESI workloads, including terabytes of data, hundreds of workspaces, various level of organizational structure, and 200+ concurrent users? | ||
| 5a | If yes, describe relevant capacity benchmarks. | ||
| 6 | Does your platform incorporate AI or ML-based capabilities (e.g., predictive coding/CAL, entity extraction, intelligent redaction, privilege detection)? | ||
| 6a | If yes, please list available AI/ML features. | ||
| 6b | If additional AI features are in development, briefly describe expected enhancements. | ||
| 7 | Does your solution support multimedia processing (audio transcription, video redaction, image recognition)? | ||
| 7a | If yes, specify which formats and capabilities. | ||
| 8 | Please identify which core FOIA/eDiscovery functions your system currently supports, select all that apply: ingestion; processing; deduplication; email threading; clustering; predictive coding; review hosting; FOIA case management; PII/privilege detection; automated redaction; audit logging; scheduled and ad-hoc reporting; API integrations | ||
| 9 | Describe any prior experience supporting federal FOIA processes, DOJ reporting requirements, litigation discovery workflows, or compliance-driven document production. | ||
| 10 | Describe your organization’s capacity to support enterprise-scale implementations, including maximum hosted data volume, number of concurrent cases, and maximum annual throughput of processed ESI. | ||
| Acquisition | |||
| 11 | Does your organization have recommended best practices for structuring a department-wide BPA that consolidates FOIA and eDiscovery services under a unified enterprise contract vehicle? | ||
| 11a | If yes, briefly list recommended practices (e.g., modular CLIN structure, scalable consumption tiers, shared services model). | ||
| 12 | Does your organization have preferred acquisition models for large FOIA/eDiscovery SaaS platforms (e.g., tiered licensing, per-GB models, enterprise unlimited, workspace-based)? | ||
| 12a | If yes, briefly list recommended models and reasons for applicability. | ||
| 13 | Does your organization have recommended performance metrics or SLAs for FOIA processing, eDiscovery throughput, system availability, AI accuracy, or user support responsiveness? | ||
| 13a | If yes, briefly describe them (e.g., ingestion rates, redaction error rate, uptime, response time). | ||
| Governance | |||
| 14 | Does your organization have established approaches for managing enterprise deployments across multiple bureaus or federated components, including shared governance, configuration control, and bureau-specific workflows? | ||
| 15 | Does your organization have experience identifying risks or challenges associated with department-wide FOIA/eDiscovery transformation (e.g., migration risks, legacy systems interoperability, user adoption, data integrity)? | ||
| 16 | Does your organization have a defined approach for ensuring compliance with federal privacy, cybersecurity, and accessibility requirements (e.g., FISMA, NIST SP 800-53, Privacy Act, NARA ERM, Section 508, IPv6)? | ||
| 16a | If yes, briefly list core compliance controls embedded in your solution. | ||
| Solution Capabilities (FOIA & eDiscovery) | |||
| 17 | What standard practices does your organization use to ensure accurate, defensible ESI processing and review (e.g., hashing, audit logs, chain-of-custody, metadata preservation)? | ||
| 17a | What factors typically drive the cost of these services (e.g., storage, processing volume, AI features, case complexity)? | ||
| 18 | Does your platform provide FOIA case management capabilities (intake, classification, workflows, routing, correspondence, fee management, disposition tracking)? | ||
| 18a | If yes, describe key features (e.g., tracking due dates, multi-office workflows, requester portal, DOJ reporting). | ||
| 19 | How does your platform support automation or efficiency improvements for FOIA operations, including proactive disclosure, duplicate request identification, or automated exemption suggestions? | ||
| 20 | How does your solution support the ingestion, processing, and review of the following categories, select all that apply: Structured data, unstructured text, email, mobile device data, short messages, cloud repositories, audio, video, social media, forensic images. | ||
| Market Expectations for FOIAeDiscovery Services | |||
| 21 | What challenges or risks does industry typically account for when pricing large FOIA/eDiscovery SaaS implementations (e.g., data migration complexity, storage growth, concurrency, bureau variation)? | ||
| 21a | What types of Government-provided information help industry price these solutions more accurately (e.g., data volumes, formats, number of users, active case load, flow rates)? | ||
| 22 | What metrics or methods does your organization use to measure successful FOIA processing outcomes or litigation review performance (e.g., cycle time reduction, reviewer efficiency, AI accuracy, backlog reduction)? | ||
| Team Arrangements | |||
| 23 | Does your company anticipate forming teaming arrangements to meet the full suite of Treasury FOIA/eDiscovery requirements? | ||
| 23a | If yes, identify the anticipated roles and capabilities of each team member. | ||
| 23b | If no, describe how your single solution meets all PWS requirements. | ||
| Optional | |||
| 24 | Please provide any additional feedback, innovations, or solution approaches Treasury should consider in shaping the acquisition strategy for a unified FOIA/eDiscovery enterprise platform. |
Sheet1
| 14 | 14a | 15 | 15a | 16 | 17 | 17a | 18 | ||
| Yes | Candidate sourcing and recruiting pipelines | Sourcing and recruiting complexity | Completion or milestone incentives | Increased program duration | Integrated sourcing, training, placement, and retention | Competition for technical talent | Expected hiring volumes or cohort sizes | Training completion rates | <100 learners/year |
| No | Candidate screening and technical assessments | Training duration and curriculum depth | Retention bonuses | Higher staffing levels (coaches, mentors, coordinators) | Single point of accountability | Fluctuating hiring volumes | Estimated timelines or surge intervals | Assessment or certification pass rates | 100–500 learners/year |
| Immersive cohort-based training or bootcamp delivery | Instructor expertise and availability | Performance-based incentives tied to hiring or retention | Increased up-front investment in candidates | Cohort-based delivery aligned with hiring cycles | Variability in participant readiness | Target job roles and technical skill areas | Placement rate into federal roles | 500–1,000 learners/year | |
| Pre-employment upskilling or remedial training | Cohort size and delivery modality | Extended onboarding or transition support | Additional post-placement monitoring requirements | Shared data systems for end-to-end participant tracking | Security clearance or suitability delays | Expected retention benchmarks | Time-to-readiness or time-to-placement | 1,000+ learners/year | |
| Certification preparation or technical skill assessments | Assessment or certification costs | Structured mentoring or apprenticeship models | Greater financial or performance risk assumed by the vendor | Outcome-based performance metrics | Surge capacity requirements | Assessment or certification requirements | Onboarding success indicators | ||
| Job-readiness or professional skills development | Placement and onboarding support | Continuing-education or upskilling benefits | Other (specify) | Continuous feedback loops across the full lifecycle | Evolving technical skill requirements | Participant baseline skill levels | Retention rates at defined intervals (e.g., 3/6/12 months) | ||
| Structured placement support into federal roles | Post-placement retention services | Guaranteed talent pipelines | Ability to rapidly scale delivery | Retention challenges in federal roles | Onboarding or placement-support expectations | Participant satisfaction measures | |||
| Post-placement mentoring or performance monitoring | Technology platforms or LMS usage | Risk-sharing or shared-cost models | Ability to support both new-hire pipelines and employee upskilling | Limited planning data | Required LMS or technology platforms | Employer or hiring-manager satisfaction | |||
| Retention support programs | Clearance or suitability process requirements | Retention guarantees or service warranties | Services delivered separately (not turnkey) | Other (specify) | Other (specify) | Post-placement performance data | |||
| Alumni or community-of-practice support | Other (specify) | Post-hire performance monitoring | Other (specify) | Long-term career progression tracking | |||||
| Scalable or hybrid training delivery models | Other (specify) | Other (specify) | |||||||
| Data and analytics for participant tracking | |||||||||
| Other (specify) |
File details come from the government source that posted it. Updated .