Voter Registration Q and A responses.pdf

Q&A ID # Solicitation Reference Question and Answer Q: Requirement D-3, states the contractor shall deliver the data file in a single fixed-length ASCII format or shapefile/GeoJSON format. Section F.8 states deliverables shall be submitted in CSV or Parquet files delivered via AWS, Azure, or Census MFT. Please confirm the required file format(s) for the data deliverables.

A: The required file formats are ASCII format or shapefile/GeoJSON. Section F.8 has been updated accordingly in Amendment A001.

Q: Question 0007 in Section L.1.3.1 requires sample data to be delivered in accordance with Attachment J.3, MFT User Guide. The MFT account request form requires an Agency Agreement Number. Please confirm what agreement number or identifier Quoters should reference when requesting MFT accounts for sample data submission, and whether sample data may be uploaded through an MFT account held by a Quoter's teaming partner or data provider on the Quoter's behalf.

A: Quoters should use the RFQ number in the Agency Agreement Number field. Yes, sample data may be uploaded through an MFT account held by a Quoter's teaming partner or data profiver on the Quoter's behalf.

Q: Requirement DE-2 requires the date of most recent record access/file pull from the municipality, the date of most recent update, and the date of first observation at the current registration address. Please confirm whether items (a) and (b) are required at the individual record level for each unique voter ID, or at the source-file level (e.g., the date each state or jurisdiction file was most recently pulled or updated).

A: To clarify, DE-2 (File Update Information) states that the USCB requires:

a. Date of most recent record access/file pull from municipality for a unique voter ID. For this, it requires the date each municipality was accessed at the source-file level.

b. Date of most recent update (e.g., change) to the record of a unique voter ID. For this, it requires this data at the individual record level (the most recent update per address).

Q: Section B.4.1 describes CLIN 0001 only. Please confirm the intended scope of CLIN 0002A, Historical Voter Registration Data (2024-current).

Is this a one-time delivery of historical file vintages, and should it include all vintages held by the vendor from 2024 to present?

A: Yes; this is one delivery. The historical files should be one file per year for 2024 and 2025. The current year file is for 2026.

Q: Data elements DE-11 and DE-12 reference general election indicators and performance metrics by year. Please confirm the required historical depth of general election vote history (for example, the number of general election cycles) for the base delivery and for CLIN 0002A.

A: The historical files should be one file per year for 2024 and 2025, including general election vote history. The current year file is for 2026.

Q: Section F.5 identifies a single base-year delivery of voter registration data due September 25, 2026. Does the Bureau anticipate refreshed or updated data deliveries during the period of performance, and if so, what delivery frequency should Quoters assume for pricing purposes?

A: This is one delivery. The historical files should be one file per year for 2024 and 2025. The current year file is for 2026.

6 F.5

5 C.3.3

3 C.3.3

4 B.4.1

Question & Answer (Q&A) For Commercial Voter Registration Data 1333-26-0883

1 C.3.2 & F.8

2 L.1.3.1

Q: Is there any incumbent/recompete or this is a brand-new project? If yes, could you please provide us with their award number or even if the customer bought similar services in the past?

A: This data was previously acquired by contract # 1333LB24C00000022 from Data-Clear.

7 N/A