RFI Questions and Answers.pdf

RFI Questions & Answers – DOL Labor Market Transparency & Fraud Detection Tools

1. Does the Department of Labor (DOL) anticipate evaluating only end-to-end integrated platforms, or is the Department also interested in responses and demonstrations from component technology providers? Specifically, we are interested in whether capabilities designed for integration into a multi-vendor or prime/subcontractor architecture such as a downstream authorization and audit-evidence layer that consumes alerts and source context from another system will be evaluated.

Response: We are interested in both end-to-end platforms and component technology providers, and would like to see both types of software.

2. Is a new procurement or a follow-on/recompete of an existing contract. If there is an incumbent for this effort, could you please provide the incumbent contract ID and the Contractor's name?

Response: No, this is a new requirement.

3. The SAM response field says September 17 at 10 AM EDT, while sections 5 and 6 use EST.

Should both the September 15 question deadline and September 17 response deadline be understood as 10 AM local Eastern time (EDT)?

Response: Yes, both deadlines represent Eastern Standard Time (EST).

4. Is DOL interested in a component-focused response covering compliance-document workflows, source-linked exception review and audit reporting, where trusted identity proofing, work-authorization verification and portable credentials would require integration or new development?

We would clearly distinguish present capabilities from proposed work and would not claim a deployed end-to-end workforce identity product.

Response: We would be interested in seeing both sets of capabilities.

5. Is there a preferred capability-statement template, page limit, attachment format or response structure beyond sections A-D? For Industry Day, may a demonstration use synthetic data and clearly labeled prototypes, and what presentation length should vendors plan for?

Response: No, there is not a preferred capability statement template, page limit, or required response structure. Yes, a vendor may use synthetic data for a demonstration.

6. Are there required security authorizations, data residency constraints or identity/credential interoperability standards for participation or a demonstration, as distinct from requirements for a future production acquisition?

Response: No specific security authorization, data residency, or identity/credential interoperability standard is required to participate in Industry Day or provide a demonstration.

Vendors should describe any existing security authorizations, data hosting/residency practices, and interoperability standards supported by their solutions, including any limitations or dependencies. Any security, privacy, data residency, interoperability, or authorization requirements applicable to a future production environment would be established as part of a subsequent acquisition, if pursued.

9/26/2026

7. Would the Department consider granting an extension for the written RFI submission?

Response: No

8. In the event an extension is granted for the written submission, could you please clarify whether participation in the virtual Industry Day presentation/demo (tentatively scheduled for September 24–25, 2026) is mandatory for vendors submitting an RFI response?

Response: The demo is preferred, rather than mandatory.

9. May the firm include relevant federal work performed by its founder during prior employment, clearly identified as key-person experience?

Response: Yes

10. May the firm include internally developed software projects as examples of similar work, clearly identified as company product development?

11. Does DOL require completed contracts held by the responding firm or a minimum number of client references for this RFI or consideration for an Industry Day demonstration?

Please also identify any supporting documentation or reference contact information needed for these examples.

Response: Interested vendors should only identify similar contracts with their RFI response.

Neither information from your references or supporting documentation should be submitted.

12. Can DOL clarify the expected transaction/user volumes?

Response: DOL does not yet know.

13. What are the hosting/FedRAMP requirements?

Response: DOL has not established specific hosting or FedRAMP requirements at this stage.

Respondents should identify their current hosting environment, applicable security authorizations or certifications, and any FedRAMP status, if applicable. Requirements for a future production environment would be established as part of a subsequent acquisition, if pursued.

14. What required integrations are anticipated?

Response: DOL has not identified any required integrations at this stage. As part of its market research, DOL is interested in understanding respondents' existing integration capabilities, including supported APIs, data exchange standards, and experience integrating with Government or third-party systems. Any required integrations would be identified as part of a subsequent acquisition, if pursued.

15. What's the expected identity assurance level?

Response: DOL has not established a required identity assurance level at this stage

16. Section 7 references "RFO Part 10. Should this say "FAR Part 10, Market Research?""

Response: No, in accordance with Executive Order 14275, Restoring Common Sense to Federal Procurement, and OMB Memo M-25-26, Overhauling the Federal Acquisition Regulation, the Federal Acquisition Regulation (FAR) was replaced by the Revolutionary FAR Overhaul (RFO).

17. Would DOL consider responses from vendors proposing a modular solution or teaming arrangement in which specialized capabilities—such as digital identity, credential management, cybersecurity, and advanced fraud analytics—are provided through an integrated architecture, or is DOL primarily seeking a single commercially available end-to-end platform from one vendor?

Response: We would like to see both types of software.

18. For Industry Day, will DOL consider demonstrations of prototype or proof-of-concept capabilities using synthetic data when clearly identified as such, particularly for advanced analytics, anomaly detection, risk scoring, explainability, and investigative workflows, or should all demonstrated functionality currently be commercially deployed?

Response: Yes. DOL will consider demonstrations of commercially available capabilities as well as prototypes or proof-of-concept capabilities using synthetic data, provided respondents clearly identify which capabilities are currently commercially available, which are configurable, and which would require customization or new development

19. Would DOL consider specialized vendors whose primary contribution is fraud detection, anomaly detection, risk scoring, data reconciliation, explainable analytics, and investigative decision support, while identity verification and digital credential issuance are provided by other components or teaming partners?

Response: Yes. DOL will consider specialized vendors whose capabilities may be integrated with other components or provided through teaming arrangements

20. For planning purposes, does DOL anticipate providing Government-furnished data or access to authoritative Federal data sources for employment, wage, work authorization, compliance, or related records? If so, can DOL identify the general categories of data sources expected to be available to the selected solution?

Response: DOL has not determined at this stage whether Government-furnished data or access to authoritative Federal data sources would be provided for a future solution. As part of its market research, DOL is interested in understanding the types of data and data sources respondents' solutions would require or could utilize, including any assumptions regarding Government-furnished data or access to external data sources.

21. Has DOL identified anticipated cybersecurity, hosting, cloud authorization, or compliance requirements for the contemplated solution, such as FedRAMP authorization level, FISMA categorization, NIST controls, or other Department-specific security requirements? If these requirements have not yet been determined, should respondents identify their proposed security architecture and assumptions?

Response: DOL has not established specific cybersecurity, hosting, cloud authorization, or compliance requirements for a future production environment at this stage. Respondents should identify their proposed security and hosting architecture, existing security authorizations or certifications, and any relevant assumptions, limitations, or dependencies.

22. To support a meaningful Rough Order of Magnitude (ROM), can DOL provide planning assumptions regarding anticipated scale, such as approximate number of workers, employers, Government users, transactions/events, data sources, or expected analytical workload? If these assumptions are not currently available, may respondents provide scenario-based ROM estimates with clearly stated volume and deployment assumptions?

Response: DOL has not established specific planning assumptions regarding anticipated user, transaction, data, or analytical volumes at this stage. Respondents may provide scenario-based ROM estimates using reasonable assumptions regarding scale and deployment, provided those assumptions are clearly identified.

23. For the Industry Day demonstration, does DOL expect live integration with authoritative external systems, or may vendors demonstrate representative integration workflows using APIs, simulated interfaces, and synthetic data where production access to Government systems is not available?

Response: DOL does not require live integration with authoritative external systems for the Industry Day demonstration. Vendors may demonstrate integration capabilities using live integrations, APIs, simulated interfaces, synthetic data, or other representative methods available within the Industry Day timeframe. Vendors should clearly identify which capabilities are currently operational, simulated, configurable, or would require additional development or access to external systems.

24. Can DOL provide the anticipated presentation and demonstration duration for each participating vendor, including any expected allocation between company overview, technical demonstration, and Government Q&A? Additionally, will vendors be permitted to use presentation slides, prerecorded backup demonstrations, or supporting technical materials in addition to a live demonstration?

Response: We are still developing the industry day and demo session schedule as vendors continue to register. Once the RFI closes, specific details will be provided with the registered vendors.

25. What tools does Department of Labor use for these functions today? What are challenges with the current solution that DOL is seeking to overcome?

Response: DOL currently performs labor compliance, program integrity, and enforcement functions through a variety of existing administrative, investigative, and data systems and processes. This RFI is not intended to replace a single existing solution. Rather, DOL is conducting market research to understand whether commercially available technologies can provide additional capabilities to improve labor market transparency, connect relevant compliance information, identify potential fraud or noncompliance earlier, and support more efficient compliance and investigative workflows.

DOL is particularly interested in capabilities that can associate and reconcile relevant information across workers, employers, contractors, worksites, employment or program requirements, wage and payment records, work assignments, housing and transportation records, training or credential records, and other relevant compliance information. DOL is also interested in understanding how commercially available solutions can identify inconsistencies or anomalous patterns across such records and provide source-linked information for appropriate human review.

Respondents are encouraged to demonstrate capabilities and use cases that could improve preventative compliance, program integrity, fraud detection, investigative targeting, and audit readiness, while maintaining appropriate privacy, security, legal, and data-access safeguards.

Such capabilities are intended to support DOL's existing compliance, oversight, and enforcement functions and not to replace or delegate governmental decision-making or enforcement authority.

26. What are Department of Labor's architecture objectives with these functions? Are you seeking a single platform solution or is best of breed per function acceptable?

Response: DOL has not established a preferred solution architecture at this stage. As part of this market research, DOL is interested in understanding both integrated end-to-end platform approaches and modular or best-of-breed approaches in which specialized capabilities can interoperate.

27. Do your architecture objectives limit solutions in any way (number of platforms, types of platforms, specific technology stack, etc.)?

Response: No—not at this stage.

28. What forms and formats are the digital certifications and training credentials shared in? Would OCR type verification alone meet the requirement? If not, what other methods are expected and required?

Response: DOL has not established required forms, formats, or verification methods for digital certifications or training credentials at this stage.

29. What data sources for worker identity, digital credentials, and compliance does DOL currently collect and possess and what data sources need to be collected by this solution?

Response: DOL has not identified a specific set of Government data sources that would be provided to, or a specific set of new data sources that would be required to be collected by, a solution at this stage.

30. Who will be the primary users and stakeholders of the solution?

Response: For an initial agricultural use case, anticipated users and stakeholders may include agricultural employers and their authorized representatives, agricultural workers, and authorized DOL personnel responsible for program administration, compliance, oversight, or enforcement.

Depending on the use case, other relevant participants may include farm labor contractors, recruiters, housing or transportation providers, and other entities involved in the employment relationship.

31. Are there specific worker populations, labor programs, or compliance programs that DOL anticipates prioritizing during initial implementation?

Response: DOL anticipates that agricultural employers and agricultural worker populations may be a priority area for initial implementation and demonstration. DOL is particularly interested in capabilities that can support compliance involving worker and employer identity, employment authorization, wages and payments, worksite assignments, housing, transportation, and other applicable labor requirements.

32. Can DOL confirm it would consider a prime/subcontractor teaming model combining specialized integrators and vendors (e.g., identity verification + credentialing + compliance tracking)?

33. Which DOL program(s) or worker populations is this initially targeting (e.g., H-2A/H-2B visa workers, apprenticeship programs, OSHA-regulated industries)? This affects which compliance data types are in scope.

Response: DOL anticipates that agricultural employers and agricultural worker populations may be a priority area for initial implementation and demonstration. Relevant programs and compliance areas may include the H-2A temporary agricultural worker program; the Migrant and Seasonal Agricultural Worker Protection Act (MSPA), including requirements applicable to farm labor contractors, housing, and transportation; Fair Labor Standards Act (FLSA) requirements applicable to agricultural employment, including minimum wage, recordkeeping, and agricultural child labor requirements; and applicable Occupational Safety and Health Act requirements and agricultural safety standards.

DOL is interested in understanding how respondents' solutions could support compliance across the agricultural employment lifecycle, including recruitment and worker onboarding, worker and employer identity, employment authorization, employment relationships and farm labor contracting, wages and payments, hours and work records, worksite and job assignments, housing, transportation, training and safety, and other applicable employment requirements.

Respondents may also identify capabilities that can associate and reconcile information across workers, employers, farm labor contractors and other intermediaries, worksites, housing locations, transportation providers, and related compliance records to identify potential inconsistencies or indicators of noncompliance.

34. For "trusted work authorization status," does DOL expect real-time integration with existing federal systems (e.g., E-Verify, DHS SAVE), or a new independent verification capability?

Response: DOL has not determined at this stage whether trusted work authorization status would be supported through integration with existing Federal systems, an independent verification capability, or another approach.

35. Does DOL have a preferred or required digital credential standard (e.g., W3C Verifiable Credentials, mobile driver's license/mDL standards) for portability across employers and regulators?

Response: DOL has not established a preferred or required digital credential standard at this stage; respondents should identify the standards supported by their solutions and any associated interoperability considerations or dependencies.

36. Does DOL currently use existing systems for worker identity, credential issuance, or compliance record-keeping that a new solution would need to integrate with, replace, or coexist alongside? If yes, can the Government provide a detailed description of each system?

Response: No specific existing DOL systems have been identified at this stage that a proposed solution would be required to integrate with, replace, or coexist alongside. Any such requirements applicable to a future production environment would be identified as part of a subsequent acquisition, if pursued.

37. Does DOL expect the identity-verification component to also assess behavioral or device-level risk signals (e.g., detecting automated/bot activity, spoofed devices, synthetic identities), or is document/biometric verification alone sufficient?

Response: DOL has not established a specific identity-verification methodology at this stage and is open to capabilities, including behavioral or device-level risk signals, that may enhance identity integrity, fraud detection, or compliance

38. Will DOL favor solutions that integrate with existing identity-verification infrastructure already used across federal agencies, versus a fully new/standalone identity system?

Response: DOL has not established a preference for either approach at this stage and is open to both solutions that integrate with existing identity-verification infrastructure and new or standalone approaches. Respondents should describe the capabilities, benefits, and limitations of their proposed approach.

39. Who is expected to own worker-submitted data and issued credentials; DOL, the worker, the employer, or the vendor?

Response: DOL has not established final data ownership requirements at this stage. Consistent with the worker-centric approach contemplated by this RFI, DOL anticipates that workers should retain appropriate control over worker-submitted data and portable credentials, including the ability to access and share their credentials as appropriate. Respondents should describe their proposed data and credential ownership model, including the respective rights of workers, employers, the vendor, and Government users to access, use, share, correct, retain, and export such information.

40. What data retention requirements or limits does DOL anticipate for personal/biometric data collected under this program?

Response: DOL has not established specific data-retention periods or limits for personal or biometric data at this stage. DOL anticipates that any collection and retention of such information would be appropriately limited to what is necessary for the applicable purpose and subject to applicable privacy, security, consent, records management, and other legal requirements.

Respondents should describe their current data-retention and deletion practices, including how retention periods can be configured and how personal or biometric information is deleted or otherwise disposed of when no longer required.

41. Which specific contract vehicles is DOL expecting to use (GSA MAS, a GWAC, etc.)?

Response: A determination has not been made at this time since we are currently performing market research.

42. How will DOL weigh "commercially available and proven at scale today" versus "requires new development" when evaluating responses - is a mature, widely-deployed capability preferred over a custom-built one even if the custom option covers more of the stated scope?

43. Is DOL more interested in solutions with a demonstrated track record identifying fraud patterns across organizations/employers (network-level intelligence), or is a single-employer/single-agency view sufficient?

44. Should fraud detection be capable of surfacing anomalies in real time as data is submitted, or is periodic/batch review (e.g., quarterly) sufficient for DOL's purposes?

Response: DOL has not established a required frequency for fraud or anomaly detection at this stage. DOL is interested in capabilities that can identify potential fraud, anomalies, or compliance issues in real time or near real time where appropriate. Respondents should describe the detection frequencies supported by their solutions, including any differences in capabilities, data requirements, or costs associated with real-time versus periodic analysis.

45. What level of false-positive tolerance is acceptable, and does DOL expect vendors to show quantitative precision/recall performance data as part of their response?

Response: DOL has not established a specific false-positive tolerance or quantitative performance threshold at this stage. DOL is interested in understanding how respondents evaluate and validate the accuracy of fraud, anomaly, and risk-detection capabilities, including false positives and false negatives

46. What is the anticipated Period of Performance (POP)?

Response: An anticipated PoP is not known at this time, we are still conducting market research.

47. Is DOL envisioning a pilot, phased implementation, or enterprise-wide deployment?

48. What contract structure is being contemplated (e.g., base plus option years, subscription model, BPA, or another acquisition vehicle)?

49. Does DOL anticipate contractor staffing support (FTEs) as part of the future requirement? If so, what functional areas are expected (e.g., implementation, training, data analysis, investigations support, help desk, program management)?

50. Can DOL provide any guidance regarding the anticipated funding profile, budget range, or acquisition strategy being considered to help industry propose appropriately scaled solutions?

Response: No, not at this time since we are currently performing market research.

51. Is DOL envisioning a software purchase, a SaaS subscription, or a managed service?

52. Does DOL anticipate a single-award or multi-award acquisition approach?

53. Is DOL considering a small business set-aside, socioeconomic set-aside, or unrestricted procurement strategy?

54. Would DOL consider a modular acquisition approach that allows capabilities to be deployed incrementally (e.g., identity verification, credential management, compliance monitoring, fraud analytics)?

Response: Yes. DOL would consider a modular approach that allows capabilities to be deployed incrementally. DOL has not established a preferred acquisition or deployment approach at this stage.

55. Which DOL agencies, offices, or programs are expected to be primary users of the solution?

Response: DOL anticipates that the Wage and Hour Division (WHD) would be a primary user and stakeholder for the initial agricultural use cases. DOL does not intend, however, to foreclose potential use by or participation from other DOL agencies, offices, or programs with relevant equities in agricultural labor, worker protection, program administration, compliance, enforcement, safety, or related matters.

56. Is DOL's primary objective worker identity verification, labor compliance, fraud detection, benefits eligibility verification, foreign labor program oversight, workforce credentialing, or a combination of these objectives?

Response: DOL's primary objectives are to strengthen program integrity and workforce protection. DOL is interested in understanding how capabilities such as worker identity and employment authorization verification, labor compliance monitoring, fraud and anomaly detection, workforce credentialing, and related tools can support those objectives. DOL is particularly interested in capabilities that improve transparency, help employers and workers comply with applicable labor requirements, identify potential fraud or noncompliance, and provide reliable information to support appropriate Government oversight and human review.

DOL has not established a preference for any single capability at this stage.

57. What worker populations are envisioned as initial users of the platform? For example, H-2A workers, H-2B workers, apprentices, construction workers, federally funded workforce program participants, or broader labor-market populations.

Response: DOL anticipates that agricultural workers, including H-2A workers, would be among the initial worker populations contemplated for the platform. DOL is also interested in understanding how respondents' solutions could support other agricultural worker populations and related agricultural labor compliance use cases.

58. Approximately how many workers, employers, and government users are expected to be supported by the platform – initially, growth, and ultimately?

Response: The Department is unable to answer that question at this time.

59. Is DOL seeking labor market intelligence at the individual worker level, employer level, market/industry level, or across all three?

Response: DOL's primary interest is in capabilities that provide relevant information and insights at the individual worker and employer levels. DOL is also interested in understanding how appropriately aggregated or analyzed worker- and employer-level data can provide useful market-or industry-level insights, including patterns or trends relevant to program integrity, workforce protection, compliance, and fraud detection.

60. What authoritative data sources does DOL anticipate making available or requiring integration with? Examples may include:

• E-Verify

• USCIS

• State licensing systems

• OSHA records

• Wage records

• DOL enforcement databases

Response: DOL has not identified specific authoritative data sources that it anticipates making available or requiring integration with at this stage. As part of this market research, respondents should identify the authoritative data sources their solutions currently use, could integrate with, or would require to support the proposed capabilities, including any associated assumptions, dependencies, or limitations. Any Government-furnished data sources or required integrations for a future production environment would be identified as part of a subsequent acquisition, if pursued.

61. Are real-time integrations expected, or would periodic batch processing be sufficient for certain use cases?

Response: DOL anticipates that real-time integrations will be expected where appropriate to support timely verification, compliance monitoring, fraud detection, and program integrity. DOL also recognizes that periodic or batch processing may be appropriate for certain data sources or use cases. Respondents should describe the real-time and batch integration capabilities supported by their solutions, including any dependencies or limitations.

62. What interoperability standards are preferred or anticipated? Examples may include:

• OpenID Connect

• OAuth

• W3C Verifiable Credentials

• Digital Wallet standards

• NIST Digital Identity guidelines

Response: DOL has not established preferred or required interoperability standards at this stage.

63. Does DOL envision workers retaining ownership and portability of their credentials across employers, programs, and jurisdictions?

Response: Yes. DOL envisions a worker-centric approach in which workers retain appropriate control over and portability of their credentials, including the ability to access and share credentials across employers, programs, and jurisdictions, as appropriate. Respondents should describe how their solutions support worker-controlled access, portability, interoperability, consent, and appropriate privacy and security safeguards.

64. How important is portable digital identity relative to fraud detection and compliance monitoring within the overall solution? What fraud elements is DOL targeting? For example, unemployment insurance, validity of visa applications, workers compensation, etc.

Response: DOL views portable digital identity as an important enabling capability within the broader objectives of strengthening program integrity and workforce protection. DOL is interested in understanding how portable, worker-controlled identity and credentials can work together with compliance monitoring, fraud and anomaly detection, and audit-ready records to improve transparency and support appropriate Government oversight.

With respect to fraud and compliance, DOL is particularly interested in capabilities that can identify or help prevent inconsistencies involving worker or employer identity, employment authorization, recruitment and employment relationships, wages and payments, hours and work records, worksite or job assignments, housing, transportation, credentials and training, and other applicable labor or program requirements. DOL is also interested in capabilities that can associate and reconcile information across workers, employers, farm labor contractors and other intermediaries, worksites, and related compliance records to identify potential fraud, noncompliance, or other anomalous patterns.

DOL has not limited its interest to a specific category of fraud at this stage. Respondents are encouraged to identify additional fraud, program-integrity, and workforce-protection use cases that their solutions can support, including the underlying data necessary to identify such risks.

65. How important is workforce credential verification, certification management, and skills transparency within the overall solution?

Response: DOL views workforce credential verification, certification management, and skills transparency as important capabilities that can support the broader objectives of program integrity, workforce protection, and labor market transparency. DOL is interested in solutions that enable workers to securely maintain and share portable, verifiable credentials, including relevant training, certifications, licenses, and qualifications, while allowing authorized employers and Government users to validate the authenticity and status of those credentials.

66. Is DOL seeking predictive analytics, anomaly detection, risk scoring, generative AI capabilities, case summarization, or a combination of these capabilities?

Response: DOL is interested in understanding a range of analytical and AI-enabled capabilities, including predictive analytics, anomaly detection, risk scoring, case or record summarization, and other capabilities that may support program integrity, workforce protection, compliance monitoring, fraud detection, and investigative or audit workflows.

67. What explainability, transparency, and human-review requirements would apply to AI-generated alerts, recommendations, or risk scores?

Response: DOL has not established specific explainability, transparency, or human-review requirements at this stage.

68. Is SOC2 certification acceptable or does DOL anticipate that any future solution will require FedRAMP authorization and, if so, at what impact level?

Response: DOL has not established specific FedRAMP authorization or impact-level requirements for a future production environment at this stage. Respondents should identify their current security certifications and authorizations, including SOC 2 and any applicable FedRAMP status, and describe their proposed security and hosting architecture. Any specific security, cloud authorization, or FedRAMP requirements applicable to a future acquisition would be established as part of a subsequent acquisition, if pursued.

69. What security categorization is anticipated for the solution (e.g., FISMA Moderate or High)?

Response: DOL has not established an anticipated security categorization for a future production solution at this stage. Respondents should identify the security categorization and control environment currently supported by their solutions, as applicable, and any assumptions or dependencies associated with supporting different Federal security requirements.

70. Will the solution need to support mobile devices, field operations, and offline data collection scenarios?

Response: Yes. DOL is interested in solutions that support mobile devices and field operations, particularly for agricultural use cases involving workers, employers, farm labor contractors, worksites, housing, transportation, and other compliance activities. Respondents should describe their mobile and field capabilities, including the ability to collect and securely maintain relevant information in locations with limited or intermittent connectivity and to synchronize such information when connectivity becomes available.

71. Is DOL anticipating a pilot program prior to enterprise-wide deployment? Is DOL open to a roll-out strategy in terms of functionality to ease employer transition?

Response: Yes. DOL is open to a pilot program prior to broader deployment and to a phased rollout strategy that allows capabilities to be implemented incrementally. DOL is interested in understanding how respondents would structure a pilot and subsequent deployment to validate capabilities, support employer and worker adoption, minimize transition burdens, and evaluate program-integrity, workforce-protection, compliance, and fraud-detection outcomes before potential scaling.

72. Are there priority use cases involving foreign labor programs, visa holders, labor trafficking prevention, worker exploitation detection, or related labor-risk monitoring activities?

Response: Yes. DOL is particularly interested in use cases involving agricultural workers and foreign labor programs, including H-2A workers, that advance program integrity and workforce protection.

73. Would DOL value supply chain transparency and labor-risk monitoring capabilities associated with workforce identity, worker protections, and employment compliance?

Response: Yes. DOL would value supply-chain transparency and labor-risk monitoring capabilities where they support the Department's broader objectives of program integrity, workforce protection, and employment compliance. DOL is interested in understanding how respondents' solutions can associate workforce identity and employment information with employers, farm labor contractors and other intermediaries, worksites, transportation activities, and other relevant entities or records to improve transparency and identify potential labor-risk, fraud, exploitation, or compliance indicators.

74. Do you see DOL investigators having direct access to review and verify credential data as part of audit reviews?

Response: DOL is interested in capabilities that would allow appropriately authorized DOL personnel, including investigators where applicable, to review and verify relevant credential and supporting compliance information for authorized audit, oversight, or investigative purposes. The specific scope and method of access have not been established at this stage and would be subject to applicable privacy, security, consent, data-access, and other legal requirements.

75. Does DOL foresee any potential conflicts with state regulatory limitations?

Response: DOL recognizes that applicable state laws, regulations, privacy requirements, data-sharing restrictions, licensing requirements, and other state-specific requirements may vary by jurisdiction and could affect particular use cases or implementation approaches. DOL has not identified specific state regulatory conflicts at this stage. Respondents should identify any known state-specific requirements, limitations, or potential conflicts relevant to their proposed solutions and describe how their solutions can accommodate differing state requirements.

76. Would DOL value monitoring of employee activity from a terrorism compliance standpoint to potentially include sanction list inclusion, indications of radicalization, etc.

Response: DOL would be interested in understanding capabilities that can support applicable terrorism-related, sanctions, or other legally required compliance screening where relevant to DOL's programs and authorities

77. How are vendors integrated data sources and technology vendors vetted by DOL?

Response: DOL has not established a specific vetting process for integrated data sources or third-party technology providers at this stage.

78. Is DOL looking for vendor to perform investigations/audits?

Response: No. DOL is not seeking a vendor to perform Government investigations or audits. As described in response to Question #25, DOL is interested in technologies that can support compliance, oversight, and investigative workflows by identifying potential fraud or noncompliance, reconciling relevant information, surfacing anomalies or risk indicators, and providing source-linked, audit-ready information for appropriate review by authorized DOL personnel. Any investigative, audit, compliance, or enforcement determinations would remain with the appropriate Government officials.

79. What retention period does DOL consider appropriate for non-employee certification/training/licensing data?

Response: DOL has not established a specific retention period for certification, training, licensing, or other credential data at this stage.

80. What existing information and reporting tools is DOL looking to replace?

Response: DOL has not identified specific existing information or reporting tools that it is seeking to replace at this stage.

81. Does DOL anticipate any travel or other direct costs (ODCs) for this effort?

Response: DOL has not identified any anticipated travel requirements or other direct costs (ODCs) at this stage. If travel or other ODCs are required as part of a future acquisition, those requirements would be identified in the applicable solicitation or acquisition documentation.