Attachment_0002_RFQ_Questions_Gov Responses.xlsx
XLSX spreadsheet 37 KB Posted
- Solicitation number
- 75D30127R95191
About this file
This file is a Government Questions and Answers document addressing 43 clarifications submitted by offerors regarding solicitation 75D30127R95191 for NCHS/Division of Vital Statistics Coding of the Vital Statistics Data. The document provides official government responses to technical, administrative, and pricing inquiries about the IDIQ contract.
The solicitation establishes a single-award, firm-fixed-price IDIQ contract set aside for 8(a) small business under NAICS code 561499 with a $21 million size standard. The contract requires manual coding of vital statistics records by nosologists/cause-of-death coders performing quality review and validation work. Key clarifications address: (1) similar experience evaluation criteria, accepting references from offerors, subcontractors, and joint ventures with detailed role descriptions; (2) staffing matrix composition and Key Personnel designation, left to offeror discretion per amendment 0001; (3) performance start requirements—work must begin within one week of contract award with phased personnel onboarding permitted as PIV cards and government-furnished equipment become available; (4) pricing based on accepted coded records with per-record rates varying by quantity increments (1-20,999 and 21,000-770,000 records), calculated by multiplying quantity by the awarded rate for each increment; (5) Service Contract Labor Standards wage determinations based on actual employee work locations rather than contractor headquarters, with offerors responsible for identifying applicable occupational classifications and wage rates; (6) quality assurance involving 2-3 monthly batches of 25 records per coder with error rates calculated during the current coding year, excluding carryover from prior contracts; (7) invoiceable CDC training and system downtime at 37 records per hour; and (8) minimum monthly production of 16,500 records per the updated Performance Matrix. Historical monthly volumes averaged approximately 40,000 manually coded records but are presented as planning information only, not guaranteed minimums. The current incumbent contractor is Strategic Innovative Solutions, Inc., and the Government will not share incumbent personnel information. Questions deadline: November 16, 2026, 1:00 PM ET; Proposal deadline: November 24, 2026, 10:00 AM ET.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFP_75D30127R95191_0001.pdf | ||
| RFP_75D30127R95191.pdf | ||
| Attachment_0001 - Artificial Intelligence (AI) Use Compliance and Risk Management Plan.docx | DOCX document | |
| Attachment_0002_RFQ_Questions_Form.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
Sheet1
| # | RFQ Page # | RFQ Section | Question | USG response |
| 1 | 117-118; 129-130 | L.7(4)(b) Technical Factor 2: Similar Experience; M.7.2; L.6(2) | L.7 asks for three (3) relevant contracts similar in scope, size, and complexity performed within the last three (3) years. (a) Will the Government consider the experience of proposed Key Personnel, or of a proposed subcontractor, under this factor, and if so what supporting documentation is required? (b) How will an offeror that submits fewer than three such contracts, or contracts that differ in scope, be evaluated? (c) Do contracts currently in performance qualify? (d) Please confirm that the dollar value of each reference contract required by L.7(4)(b)(c) may be stated in the Technical Proposal notwithstanding the L.6(2) instruction that the Technical Proposal contain no reference to cost. | a) The Government will consider relevant experience performed by the Offeror, proposed subcontractor, and Joint Ventures of which the Offeror was a member of. The Offeror shall identify the entity's role, the porition of the PWS it will perform or performed, and its availability and commitment to perform the work. For each joint venture reference, the Offeror shall also identify the Offeror's role and specific work performed under the joint venture contract. Key Personnel experience will not be considered under Technical Facotr 2, Similar Experience. |
b) The Offeror shall comply with the RFP. If the standards of the RFP are not met, the Government will evalaute what is provided but an omission may limit the Government's ability to assess relevant experience and may adversely affect the evaluation. Contracts differeing in size, scope, or complexity will be evaluated based on their degree of relevance.
c) Yes, contracts currently in performance may be submitted, if performance meets the requirements of the RFP.
d) Yes, the reference contract dollar value may be included in the Technical Volume.
| 2 | 118; 130 | L.7(4)(c)(a) Staffing Matrix; M.7.3(a) | The RFP requires resumes for proposed Key Personnel but does not designate which positions are Key Personnel. (a) Does the Government designate specific Key Personnel positions, or is the offeror to propose its own? (b) What evidence of availability is acceptable for proposed personnel who are not currently employed by the offeror? (c) Are individual coders/nosologists expected to be named in the Staffing Matrix, or may they be shown by position and number? | See amendment 0001. |
| 3 | 7-10; 14-15; 126-127 | B.9; B.10; B.11(b); PWS Section 4, Task 1(1) and Task 2; M.4; M.5 | PWS Tasks 1 and 2 require performance to begin no later than one week after contract award, while B.9 through B.11 state that work may begin only under a Task Order issued after a Notice of Intent given at least 30 calendar days before the Task Order start date. Sections M.4 and M.5 refer to issuing an 'order' or 'task order' under FAR Subpart 16.5. Please clarify (a) whether this solicitation awards a new single-award IDIQ contract, (b) whether the one-week period runs from award of the basic contract or from the start date of the first Task Order, (c) whether the first Task Order will be issued concurrently with contract award, and (d) the anticipated award date. | See amendment 0001. |
| 4 | 2; 15; 26-27; 42 | Section A item 7; PWS Section 4, Task 2; PWS Section 5; 1.18-1.20; Confidentiality (Designated Agent Agreement) | What lead times should offerors assume for (a) initiation and adjudication of background investigations and HHS PIV card issuance, (b) delivery of the Government-furnished laptop, (c) MedCoder (or successor system) access, and (d) execution of the Designated Agent Agreement? If the contractor employs personnel who currently perform this work, may their existing PIV cards, Government-furnished equipment, and system access remain active without interruption when their employer changes? | RFP Section 4 updated to replace MedCoder with NVSS access. |
| 5 | 14-15; 17 | PWS Section 4, Task 1(3) and Task 2; PWS Section 10 Minimum Vendor Qualifications | Task 2 refers to 'required NCHS training' and 'required Government-provided training'. For a coder new to this contract, what initial training or qualification does NCHS provide or require before the coder may code production records, how long does it take, how often is it offered, and is time spent in initial training invoiceable in the same manner as annual refresher training (37 records per hour)? Does NCHS require any specific credential or prior experience for coders, given that Section 10 states 'N/A'? | New coders must meet the requirements of the RFP, PWS Section 10 Minimum Vendor Qualifications, as incorporated in Amendment 0001. |
37 hours is for mandatory CDC training and refresher training.
6 14; 17 PWS Section 4, Task 1(1) and 1(4); PWS Section 8, Subsection A Performance Matrix Please describe how the per-coder error rate is determined: (a) the sample size or sampling rate per coder per month, (b) the period over which the 'average error rate < 2%' for quality-review and validation staff is calculated, (c) how the error rate of a newly assigned coder is established before and during the first months of performance, (d) whether Government error-rate results already on record for personnel who currently perform this work carry over to establish eligibility for quality-review and validation assignments at the start of the new contract, (e) the procedure for resolving coding disagreements, and (f) how the '98% of the time' Acceptable Quality Level is calculated for each performance objective (observation period and denominator). For planning purposes only, historical workload indicates that a coder is assigned 2-3 batches of 25 records per month. Records are adjudicated by federal staff. This information is not a performance requirement, minimum workload, guaranteed quantity, or staffing direction. Actual record quantities and workload requirements will be established by the applicable task order.
Period is the current coding year.
Newly assigned coder will be evalauted through the same monthly review proess once the coder begins performing work.
Error rates do not carryover from year to year, nor from current contract to new contract.
7 12; 14; 134 B.14 Pricing Terms; PWS Section 4, Task 1(1)-(4); M.8 Payment is per 'accepted record'. Please clarify (a) the acceptance criteria for a coded record and whether a record later found in the DACEB sample to contain an error remains an accepted record for payment, (b) whether quality-review, correction, and validation records are purchased and paid at the same per-record price as production records, and (c) how the 37-records-per-hour allowances for CDC downtime, refresher training, and interface orientation are documented, accepted, and invoiced, and at which increment's price. a) A coded record is considered accepted.
b) Same price per record for routine and quality review records.
C) Cannot be personal IT or powere issues; CDC or NCHS system downtime is chargable.
8 13; 14; 16-17 PWS Section 1 Background; PWS Section 4, Task 1(1); PWS Section 8 Deliverables; Subsection A Performance Matrix (a) PWS Task 1(1) and the Section 8 deliverables table set the monthly minimum at the total number of records purchased divided by the number of months, while the Performance Matrix states a minimum of 16,500 records per month in the base year or the total purchased divided by 12. Which calculation governs for a Task Order whose period of performance is not 12 months, what is the 'base year' for this IDIQ, and how is the minimum applied if the Government assigns fewer records in a month than the minimum? (b) To support pricing of the record-quantity increments, will the Government provide the number of records manually coded by contractor staff per month for the most recent 24 months, the current and projected automated-coding rate, the approximate share of quality-review and validation work, and the anticipated quantity and period of performance of the first Task Order? For information and planning purposes only, the average monthly volume of reords requiring manual coding over the last two years was approx. 40k records. This is historical information is not a guaranteed quantity, minimum quantity , or estimate of future Task Order volume. Offerors shall prepare and submit proposals in accordance with the requreiments of the RFP.
We cannot project the auto-coding rate.
Quality review may not been needed.
9 6; 122; 132-134 B.6 Service Contract Labor Standards; L.9(4) Detailed Pricing Information; M.8 (a) Which Service Contract Labor Standards occupational classification(s) does the Government consider applicable to nosologists/cause-of-death coders, or will a conformance be required? (b) For teleworking employees, will wage determinations be incorporated based on each employee's actual work location, and will the Government provide the wage determination(s) currently applied to this work? (c) How and when will FAR 52.222-43 adjustments be applied to the per-record prices for the 2028 through 2031 ordering periods, given that M.8 states the Government may consider whether pricing accounts for wage increases during those periods? (a) Applicable SCA Occupational Classification
The Government has not identified a final SCA occupational classification for nosologists/cause-of-death coders in the solicitation. Offerors shall review the duties and requirements in the PWS and propose the applicable SCA occupational classification(s) using the Department of Labor’s Service Contract Act Directory of Occupations.
The Government will review the proposed classification(s) for consistency with the actual duties required by the PWS. If an appropriate classification is not included in the applicable wage determination, the Government will pursue the applicable conformance process in accordance with the Service Contract Labor Standards requirements.
(b) Remote-Work Locations and Wage Determinations
For teleworking employees, the applicable wage determination will generally be based on the locality where the employee performs the contract work. The contractor’s headquarters or the Government’s facility will not automatically establish the applicable locality.
Offerors shall identify the anticipated places of performance for their proposed employees, including the applicable city, county, and state, and shall identify the wage determination(s) and occupational classification(s) used to develop their proposed pricing. The Government will review the proposed wage determinations and incorporate the applicable wage determination(s) into the resulting contract or applicable Task Order, as appropriate.
Because employee locations may not be known at the time of solicitation, FAR 52.222-49, Service Contract Labor Standards—Place of Performance Unknown, applies. The Government has not identified one wage determination that applies to all potential remote employees. Additional wage determinations may be requested and incorporated when the applicable places of performance become known.
(c) FAR 52.222-43 Adjustments is incorporated via amendment 0001.
Offerors shall propose firm-fixed prices for each calendar-year ordering period based on their proposed technical approach, staffing, labor categories, labor hours, applicable wage determinations, wages, fringe benefits, and other costs necessary to perform the PWS.
The proposed prices for 2028 through 2031 should reflect the Offeror’s reasonable pricing assumptions for the applicable calendar-year ordering periods, including known or reasonably anticipated differences in wages, fringe benefits, staffing, and other costs. However, the Offeror shall not include a contingency for wage or fringe-benefit increases for which a price adjustment is provided under FAR 52.222-43.
FAR 52.222-43 will be administered in accordance with its terms. A price adjustment will not be automatic merely because the calendar year changes or because the Contractor’s labor costs increase. Any adjustment must be supported by the Contractor’s actual increase or decrease in applicable wages and fringe benefits resulting from a qualifying wage determination, collective bargaining agreement, or other event identified in the clause. The adjustment will be limited to the allowable cost impact under the clause and will be documented through a written contract or Task Order modification.
The Government will not separately adjust the firm-fixed price per accepted record for general inflation, commercial wage growth, increased overhead, reduced productivity, or other costs not covered by FAR 52.222-43.
10 11-12; 123-124 B.13 Ordering List by Ordering Period; B.14(c)-(g); L.9(4) pricing schedule The pricing schedule in B.13 and L.9 lists both record-quantity increments for 2027 through 2030 but only the 1-20,999 increment for 01/01/2031-12/31/2031. Is the omission of a 21,000-770,000 row for 2031 intentional? In addition, the B.14(g) example refers to the '1-20,000 record range' whereas the schedule uses 1-20,999; please confirm the correct range and explain how increments are selected when a Task Order quantity can be divided in more than one way. See Amendment 0001.
The range is selected based on the quantity of records. The record-quantity increments are selected based on the total number of records required for the Task Order. The quantity will not be divided into alternative increments when the entire Task Order quantity falls within one pricing range. For example, a Task Order for 100,000 records will be priced as one 100,000-record increment using the 21,000–770,000 record rate. The Government will identify the applicable pricing increments in each Task Order, and the total Task Order price will be calculated by multiplying the quantity in each increment by the awarded firm-fixed price per accepted record for that increment.
11 4; 114; 120-121 Section B Contact Line Item Numbers; L.6(6); L.9(2)(3) L.9(2)(3) requires a 'Completed 2.0 Contact Line Item Numbers of the solicitation' and L.6(6) requires an Excel copy of the business proposal, but no Excel pricing template was posted. Please confirm (a) that '2.0' refers to Section B and the B.13/L.9 pricing schedule, and (b) whether the Government will provide an Excel template or the offeror should use its own format. a) See amendment 0001.
b) Offerors use their own excel template.
| 12 | 118; 130 | L.7(4)(c)(b) Staffing Recruitment and Replacement; M.7.3(b) | For the table of employee turnover rates for each of the previous two years, please identify the reporting years and the calculation method, including whether the table should cover all company employees or only comparable service personnel, and how a year with few or no employees in the applicable population should be reported. | See amendment 0001. |
| 13 | 2; 14-15; 42-43 | Section A item 7; PWS Section 4, Task 1(2); PWS Sections 5-6; Confidentiality - Remote Access (Teleworking) | Please confirm (a) that contractor coders may telework from any location in the 50 U.S. states and the District of Columbia subject to COR and NCHS Confidentiality Officer approval, (b) that all work involving NCHS data is performed exclusively on CDC-furnished equipment, so that no contractor-owned system requires NCHS CIPSEA approval, and (c) whether Government-furnished equipment will also be issued to contractor supervisory and program management staff who need access to CDC reports. | Yes |
Yes GFE may be issued to Contractor personnel who required CDC network access to perform authorized contract responsibilites, including coding personnel, and the Coding Supervisor. Equipment will not automatically be issued to program management staff, issuance will be based on the individuals need for access to CDC systems or reports and will be determined by the Government.
| 14 | 15; 16; 113; 118-119; 124 | PWS Section 4, Task 2; PWS Section 8 Deliverables; L.7(4)(c)(c); L.5(11); L.9(5)(a) | (a) PWS Task 2 states the Transition-In Plan is due no later than one week after contract award, while the PWS deliverables table and L.7 state five (5) calendar days after award. Which due date governs? (b) L.5(11) requires proposals to be valid for at least 180 days, while L.9(5)(a) requires a statement that the proposal is firm for at least 120 days. Which validity period governs? | See amendment 0001 |
| 15 | 1-2; 74; 113 | SF 1449; Section A items 2 and 8; Section I clause list (FAR 52.219-6); L.5(13) | (a) The SF 1449 and Section A item 8 state questions are due November 16, 2026, 1:00 PM ET, while L.5(13) states November 11, 2026, 2:00 PM ET, which precedes the solicitation issue date. Please confirm that questions received by November 16, 2026, 1:00 PM ET will be answered. (b) The clause list includes FAR 52.219-6, Notice of Total Small Business Set-Aside, although Section A item 2 states this is an 8(a) set-aside under FAR Subpart 19.8. Please confirm that competition is limited to eligible 8(a) participants. | See amendment 0001. |
Yes, the RFP is a total small business set aside for 8(a).
16 16, 17 C.8; C.8 Subsection A The deliverables table says 25,000 to 45,000 records per month are expected. The Performance Matrix sets a minimum of 16,500 records per month "in the base year." This contract has no base year. Which monthly figure should offerors use for staffing and pricing? Minimum is 16,500. See updated RFP Section 8.
17 12 B.14 For a task order of 300,000 records, does the 21,000-770,000 price apply to all 300,000 records? Please also confirm how a task order of 15,000 records and a later order of 15,000 records in the same year would be priced. See Amendment 0001.
The range is selected based on the quantity of records. The record-quantity increments are selected based on the total number of records required for the Task Order. The quantity will not be divided into alternative increments when the entire Task Order quantity falls within one pricing range. For example, a Task Order for 100,000 records will be priced as one 100,000-record increment using the 21,000–770,000 record rate. The Government will identify the applicable pricing increments in each Task Order, and the total Task Order price will be calculated by multiplying the quantity in each increment by the awarded firm-fixed price per accepted record for that increment.
| 18 | 118 | L.7(4)(c)(a); M.7.3(a) | The RFP asks for resumes of Key Personnel but does not name any key positions. Which positions are Key Personnel? Is a Project Manager required? Are resumes required for coders? | See amendment 0001. |
| 19 | 116, 117 | L.7(3); L.7(4)(a) | Please confirm that the Project Plan, the Staffing Matrix, resumes, and the cross-reference matrix do not count toward the 10-page limit, and state where each should be placed. | See amendment 0001. The information shall be contained in the applicable volume as identified in the RFP. |
| 20 | 6, 79 | B.6; I.6; L.9(4) | No wage determination is attached. Which Service Contract Labor Standards occupation code and title does the Government consider correct for the coders? Will the Government issue wage determinations by amendment before proposals are due? | The RFP includes clause 52.222-49 Service Contract Labor Standards-Place of Performance Unknown, and no wage determinations are included in the RFP. IAW L.9, "The Offeror shall identify each proposed place or area of performance, including the location where employees performing the contract work are expected to be located. For each proposed place or area of performance, the Offeror shall identify the applicable Service Contract Labor Standards wage determination and labor classification used to develop its proposed pricing, if known." |
| 21 | 78 | I.5 | How will a wage determination price adjustment under Section I.5 be applied to a firm-fixed price per accepted record? | FAR 52.222-43 Adjustments is incorporated via amendment 0001. |
FAR 52.222-43 will be administered in accordance with its terms. A price adjustment will not be automatic merely because the calendar year changes or because the Contractor’s labor costs increase. Any adjustment must be supported by the Contractor’s actual increase or decrease in applicable wages and fringe benefits resulting from a qualifying wage determination, collective bargaining agreement, or other event identified in the clause. The adjustment will be limited to the allowable cost impact under the clause and will be documented through a written contract or Task Order modification.
The Government will not separately adjust the firm-fixed price per accepted record for general inflation, commercial wage growth, increased overhead, reduced productivity, or other costs not covered by FAR 52.222-43.
| 22 | 118, 129 | L.7 Technical Factor 3 Staffing Plan (a); M.7.3 | The RFP requests resumes for proposed Key Personnel but does not designate Key Personnel positions. Which positions does the Government consider Key Personnel? Are resumes required for production coders? | See amendment 0001. |
| 23 | 17 | PWS Section 10 – Minimum Vendor Qualifications | Minimum qualifications are listed as N/A. Are there minimum experience or certification requirements for coders (e.g., prior NCHS ICD-10 mortality/underlying-cause coding experience)? Will NCHS provide initial training for new coders, and if so, what is its duration and is that time invoiceable at 37 records per hour? | See amendment 0001. |
| 24 | 14, 15 | PWS Task 1, Item 2; PWS Section 5 – Government Furnished Property | Task 1.2 states coding depends on Government-furnished computers, while Section 5 states GFP will be issued to "select contractor staff." Will every coder receive a CDC laptop and PIV card? Where and how is PIV issuance handled for remote staff, and what is the typical timeline from submission of onboarding paperwork to network/MedCoder access? | Every existing coder currently have a GOE and PIV card. For staff who do not currectly have the required tools, a grace period would be allowed provided the company is doing their due diligence to get it completed as quickly as possible. |
Must work with COR to have new staff sponsored who then will go the nearest CDC badge issuing facility when for new PIV cards. This applies to expired PIV cards as well.
RFP Section 8 updated to replace MedCoder with NVSS access.
| 25 | 7, 14, 15 | B.9/B.10; PWS Task 1, Item 1; PWS Task 2 | Performance is required to begin no later than one week after award, while the ordering period begins 01/01/2027 and the Government will provide a 30-day Notice of Intent before each Task Order. Is the one-week start tied to award of the IDIQ or to issuance of the first Task Order? Please confirm the anticipated award date and first Task Order start date. | See amendment 0001. |
| 26 | 15, 16, 119 | PWS Task 2; PWS Section 8 Deliverables; L.7 Staffing Plan (c) | PWS Task 2 states the Transition-In Plan is due no later than one week after award, while the Deliverables table and L.7 state five calendar days. Please confirm which applies. | See amendment 0001. |
| 27 | 13, 16 | PWS Section 1 – Background; PWS Section 8 Deliverables | Please provide historical contractor-coded volumes (records per month) for FY2025 and FY2026, the number of contractor coders currently performing, the average records per hour achieved, and the anticipated quantity for the first Task Order. | For information and planning purposes only, the average monthly volume of reords requiring manual coding over the last two years was approx. 40k records. This is historical information is not a guaranteed quantity, minimum quantity , or estimate of future Task Order volume. Offerors shall prepare and submit proposals in accordance with the requreiments of the RFP. |
| 28 | 15 | PWS Task 2 – Transition-In and Continuity of Performance | Is this a follow-on requirement? If so, please provide the current contract number and incumbent contractor, and confirm whether the Government will share incumbent personnel information referenced in PWS Task 2. | This is a follow-on contract, current provider is Strategic Innovative Solutions, Inc. The Government will not be sharming incumbent personnel information. |
| 29 | 6 | B.6 Service Contract Labor Standards | Since place of performance is unknown (FAR 52.222-49), which SCA occupational classification(s) does the Government consider applicable to this work, and should offerors price using the wage determination for each coder's residence location? | (a) Applicable SCA Occupational Classification |
The Government has not identified a final SCA occupational classification for nosologists/cause-of-death coders in the solicitation. Offerors shall review the duties and requirements in the PWS and propose the applicable SCA occupational classification(s) using the Department of Labor’s Service Contract Act Directory of Occupations.
The Government will review the proposed classification(s) for consistency with the actual duties required by the PWS. If an appropriate classification is not included in the applicable wage determination, the Government will pursue the applicable conformance process in accordance with the Service Contract Labor Standards requirements.
(b) Remote-Work Locations and Wage Determinations
For teleworking employees, the applicable wage determination will generally be based on the locality where the employee performs the contract work. The contractor’s headquarters or the Government’s facility will not automatically establish the applicable locality.
Offerors shall identify the anticipated places of performance for their proposed employees, including the applicable city, county, and state, and shall identify the wage determination(s) and occupational classification(s) used to develop their proposed pricing. The Government will review the proposed wage determinations and incorporate the applicable wage determination(s) into the resulting contract or applicable Task Order, as appropriate.
Because employee locations may not be known at the time of solicitation, FAR 52.222-49, Service Contract Labor Standards—Place of Performance Unknown, applies. The Government has not identified one wage determination that applies to all potential remote employees. Additional wage determinations may be requested and incorporated when the applicable places of performance become known.
30 11, 12, 14 B.13/B.14; PWS Task 1, Item 1 Please define an "accepted record." If a coder's sampled error rate exceeds 4%, are only the sampled records in error non-payable, or are additional records rejected? What sample size is used to compute per-coder error rates? A coded record is considered accepted.
For planning purposes only, historical workload indicates that a coder is assigned 2-3 batches of 25 records per month. Records are adjudicated by federal staff. This information is not a performance requirement, minimum workload, guaranteed quantity, or staffing direction. Actual record quantities and workload requirements will be established by the applicable task order.
| 31 | 117 | L.7 Technical Factor 2 – Similar Experience | May offerors cite contracts performed by a joint venture of which the offeror is a member, or by proposed subcontractors or Key Personnel? Will contracts providing qualified healthcare/health-information personnel to Federal health programs be considered similar in scope? | The Government will consider relevant experience performed by the Offeror, proposed subcontractor, and Joint Ventures of which the Offeror was a member of. The Offeror shall identify the entity's role, the porition of the PWS it will perform or performed, and its availability and commitment to perform the work. For each joint venture reference, the Offeror shall also identify the Offeror's role and specific work performed under the joint venture contract. Key Personnel experience will not be considered under Technical Facotr 2, Similar Experience. |
| 32 | 118 | L.7 Technical Factor 3 Staffing Plan (b) | Should the employee turnover table reflect company-wide turnover or turnover on similar contracts? | See amendment 0001. |
| 33 | 11, 114 | B.13 Ordering List by Ordering Period; L.6(6) | The 2031 ordering period shows only the 1–20,999 record range. Please confirm whether a 21,000–770,000 range applies for 2031. Will the Government provide an Excel pricing template for Volume II? | See amendment 0001. |
| 34 | 120 | L.8 CDCL.03; Attachment 0001 | Please confirm that an offeror who affirmatively states no AI will be used in contract performance is not required to submit Attachment 0001. | Confirmed. IAW L.8 CDCL.03, a plan is required using the provided tempalte if AI is planned or potential AI use is identified. |
| 35 | 2, 113 | Section A.8; L.5(13) | Section L.5(13) lists a questions due date of November 11, 2026, 2:00 PM ET, while Section A lists November 16, 2026, 1:00 PM ET. Please confirm the proposal due date remains November 24, 2026, 10:00 AM ET. | See amendment 0001. |
| 36 | Can CDC please provide an estimate of the timing and size (# of records) for the initial task order? | For information and planning purposes only, the average monthly volume of reords requiring manual coding over the last two years was approx. 40k records. This is historical information is not a guaranteed quantity, minimum quantity , or estimate of future Task Order volume. Offerors shall prepare and submit proposals in accordance with the requreiments of the RFP. | ||
| 37 | Can CDC please provide historical information on the number, frequency, and size (# of records) of prior task orders issued under the incumbent contract over the past 3 years? | For information and planning purposes only, the average monthly volume of reords requiring manual coding over the last two years was approx. 40k records. This is historical information is not a guaranteed quantity, minimum quantity , or estimate of future Task Order volume. Offerors shall prepare and submit proposals in accordance with the requreiments of the RFP. | ||
| 38 | 126 | M.3 CDCM.04 Evaluation of Artificial Intelligence Compliance and Risk Management Plan | Based on the inclusion of the AI Compliance and Risk Management Plan, can the government describe how human vs technology based solutions will be evaluated for this requirement, which is described throughout the PWS as ‘manual coding’? Since there is already a technology solution in place that is handling a majority of records per the PWS, it seems that the remaining records should only be handled by human coders and not additional technology. | No additional technology. Rejected records are handled by human coders only. |
| 39 | 2 | Section A: Solicitation / Contract Summary, Item # 8 | Would the government consider extending the deadline for proposal submission to the following Tuesday December 1 at 2pm, to allow offerors sufficient time to incorporate the government's responses to questions and finalize proposals? | The proposal due date remains 24 November 2026. |
| 40 | 14 | Section 4, Scope of Work; Tasks to be Performed - Task 1 | The PWS states the contractor shall begin coding no later than one week after contract award. Given that all staff must obtain HHS PIV cards and government-issued laptops before performing work, and since clearance /PIV credentialing can take several weeks, how should offerors reconcile this startup timeline requirement? Will CDC provide a grace period or phased start to phase staff in based on PIV card receipt. | The Contractor shall initiate the PIV and equipment process promplty and may phase personnel into performance as they obtain the required access and equipment. Personnel may not perform coding until the required access and equipment are available. |
| 41 | 5 | B.2, Ordering of Services | In order to ensure that staff is available for the IDIQ Tasks/RFTOPs, can the vendor either onboard additional surge staff upon award of the IDIQ or possibly when the 30 day notice is given for RFTOP release in order to meet the performance requirements? | RFTOPs will not be issued as detailed in the RFP. See amendment 0001 for additional information. |
| 42 | 14 | Section 4, Scope of Work; Tasks to be Performed - Task 1 | The RFP allows invoicing at a rate of 37 records per hour for downtime and for specific training. Also, The minimum number of records coded per month is determined by the total number purchased divided by the number of months? Can the govt confirm the required minimum productivity for normal coding activities is 25,000/month as per Section 8 (Deliverables/Reporting Schedule) Table Item #1 | Minimum is 16,500. See updated RFP Section 8. |
| 43 | 17 | SUBSECTION A – PERFORMANCE MATRIX | The Performance Matrix states the <4% error rate per coder must be achieved "98% of the time," with monthly monitoring. Please clarify how "98% of the time" is calculated. For example, does this mean a coder must be compliant in 11.76 out of 12 months in a year? | See amendment 0001. |
| 44 | 130 | M.7.3 Technical Factor 3: Staffing Plan | The RFP requires resumes for proposed Key Personnel but does not define which positions are designated as Key Personnel. Will CDC provide a list of Key Personnel positions for this contract, including the specific labor categories that require Government approval for substitution or is this up to the vendor to propose? | See amendment 0001. |
| 45 | 14 | Task 1: Coding of Causes of Death on Mortality and Fetal Death Records | What sample size/methodology is used to determine coder error rates? | For planning purposes only, historical workload indicates that a coder is assigned 2-3 batches of 25 records per month. Records are adjudicated by federal staff. This information is not a performance requirement, minimum workload, guaranteed quantity, or staffing direction. Actual record quantities and workload requirements will be established by the applicable task order. |
| 46 | 16 | SECTION 8 – DELIVERABLES/REPORTING SCHEDULE | Is there a cure period or remediation process if a coder exceeds the allowable error threshold? | The RFP does not establish a specific cure period or remediation process for a coder who exceeds the applicable error-rate threshold. The Contractor remains responsible for meeting the production and quality requirements stated in the PWS. |
| 47 | 113, 124 | L.5 (11) / L.9 (5)(a) | Section L.5(11) requires proposals to remain valid for at least 180 days, while Section L.9(5)(a) requires at least 120 days. Please confirm the required proposal validity period. | See amendment 0001. |
| 48 | 2, 109-111 | Section A.4 / L.2 / L.4 (7)(f) | Sections A.4 and L.2 describe a single-award IDIQ, but Section L.4(7)(f) reserves the right to make multiple awards. Please confirm whether the Government intends to make only one award? Under what circumstances would multiple awards be considered? | IAW the RFP, the intent is a single-award IDIQ; however, the Government reserves the right to make multiple awards as detailed in L.4. |
| 49 | 2, 109, 126-127 | Section A.2 / L.2 / M.4-M.5 | Sections A and L describe a standalone 8(a) set-aside IDIQ, whereas Sections M.4-M.5 refer to FAR Subpart 16.5 ordering procedures and awarding a task order. Please confirm that the contemplated award is a new 8(a) IDIQ contract, not a task order under GSA 8(a) STARS III, and clarify the eligible offeror pool. | The Government confirms that this solicitation will result in a new, standalone, single-award 8(a) Indefinite-Delivery, Indefinite-Quantity (IDIQ) contract. This solicitation is not for a Task Order under GSA 8(a) STARS III or any other Government-wide acquisition contract. |
FAR Subpart 16.5 applies to the establishment and administration of the resulting IDIQ contract and to the issuance of Task Orders under that contract.
The eligible offeror pool consists of eligible 8(a) Participants that meet the requirements of the solicitation, including the applicable NAICS code and size standard, SAM registration requirements, and all other responsibility and proposal submission requirements. Eligibility is not limited to contractors holding a GSA 8(a) STARS III contract.
See amendment 0001 for further information.
| 50 | 11, 123-124 | B.13 / L.9 (4) Pricing Schedule | The pricing tables list the 1-20,999-record tier for calendar year 2031 but omit the 21,000-770,000-record tier for 2031. Please provide the missing 2031 high-volume pricing row and confirm whether offerors are required to propose that rate. | See amendment 0001. |
| 51 | 11-12, 123-124 | B.13-B.14 (c), (g) / L.9 (4) | The pricing schedule defines the low-volume tier as 1-20,999 records, but the example in B.14(g) refers to 1-20,000 records. Please confirm that 20,999 is the correct upper limit and explain the rate applicable to an increment of 20,001-20,999 records. | See amendment 0001. |
| 52 | 12 | B.14 (b), (e)-(g) | For a task order exceeding 770,000 records, is the Government required to price a 770,000-record increment plus the remainder, as illustrated, or may it divide the order into multiple increments of 21,000-770,000 records? Please specify a consistent method for applying tier rates. | See Amendment 0001. |
The range is selected based on the quantity of records. The record-quantity increments are selected based on the total number of records required for the Task Order. The quantity will not be divided into alternative increments when the entire Task Order quantity falls within one pricing range. For example, a Task Order for 100,000 records will be priced as one 100,000-record increment using the 21,000–770,000 record rate. The Government will identify the applicable pricing increments in each Task Order, and the total Task Order price will be calculated by multiplying the quantity in each increment by the awarded firm-fixed price per accepted record for that increment.
53 11-12, 123-124 B.13-B.14 / L.9 (4) Are the pricing tiers determined by the quantity in each individual task order or by cumulative records ordered during the calendar year? For a task order whose performance crosses calendar years, which annual awarded rate will apply to accepted records? The pricing tier is determined by the total quantity of records included in each individual Task Order. Records from separate Task Orders will not be aggregated to determine the applicable pricing tier.
The Government intends, to the extent practicable, for Task Orders to be issued and performed within a single calendar-year POP identified in the Contract Price Schedule. If a Task Order’s period of performance crosses calendar years, the record-quantity increment will still be determined based on the total quantity included in that individual Task Order. Records accepted during each calendar year will be priced using the applicable awarded rate for that calendar-year POP. The applicable quantities, increments, and rates will be identified in the Task Order.
54 13, 16-17 Section C, Background / Section 8 Deliverables / Performance Matrix The PWS references a possible manual-coding need of 75,000-3,850,000 records, expected production of 25,000-45,000 records per month, and a performance-matrix minimum of 16,500 records per month in the base year. Please clarify which volume assumptions should be used for staffing and pricing. Minimum is 16,500. See updated RFP Section 8.
55 76, 11-12 I.3 FAR 52.216-19 / B.13-B.14 The Order Limitations clause establishes a 250-record minimum order, while the contract pricing schedule begins at one record. Will task orders for fewer than 250 records be issued, and if so, which requirements and pricing provisions would govern them? The 250-record minimum in the Order Limitations clause establishes the minimum quantity for an individual Task Order. The Government does not currently anticipate issuing a Task Order for fewer than 250 records.
The 1–20,999 record range in the Contract Price Schedule establishes the applicable pricing tier and does not override the 250-record minimum Task Order limitation. Accordingly, a Task Order for 250 through 20,999 records will be priced using the applicable firm-fixed price per accepted record for the 1–20,999 record range. The minimum guarantee and the Task Order minimum quantity are separate requirements.
| 56 | 5, 7-9, 14-15 | B.2 / B.9-B.11 / Section C, Tasks 1-2 | The PWS requires production within one week after contract award, but Sections B.9-B.11 describe a 30-day notice before each task order and prohibit performance before written task-order authorization. Please clarify whether the one-week readiness requirement begins at IDIQ award or issuance of the first task order and how these timelines are reconciled. | See amendment 0001. |
| 57 | 15-16, 119 | Section C, Task 2 / Section 8 Deliverables / L.7 (4)(c) | Task 2 requires the Transition-In Plan within one week after award; the deliverables table requires it within five days; and L.7 specifies five calendar days. Please confirm the controlling submission deadline, whether days are calendar days, and the timing of Government review/acceptance. | See amendment 0001. |
| 58 | 15, 119 | Section C, Task 2 / L.7 (4)(c) | Can the government clarify if the one-week start requirement is at the IDIQ level or the Task Order level? Performance must begin within one week of award, with onboarding, NCHS training, PIV issuance, government-furnished equipment, and MedCoder access. What turnaround times will CDC provide for these Government-controlled prerequisites, and how will delays outside contractor control affect the start date and performance standards? | The five-calendar day readiness requirement applies after award of the basic IDIQ and is subject to issuance of an authorized Task Order. Coding will not begin until required PIV credentials, GFE and system access are available. The Contractor shall promptly initiate all access and equipment requests and the the COR and CO of delays. |
| 59 | 14, 16 | Section C, Task 1 (2) / Section 6(B) | The PWS describes part-time coders at multiple locations but also requires eight consecutive hours of support Monday through Friday. Does the eight-hour coverage requirement apply to all coders or to designated management/administrative support, and what time zone and coverage window are required? What degree of flexibility is there regarding core business hours? | See amendment 0001. |
| 60 | 14, 17 | Section C, Task 1 (1), (4) / Performance Matrix | Please clarify how the less-than-4-percent production error rate, less-than-2-percent QC/validation error rate, and 98-percent acceptable-quality-level thresholds are calculated and assessed, including sampling frequency, review period, and treatment of corrected records. | See amendment 0001. |
| 61 | 14, 124, 134 | Section C, Task 1 (2)-(4) / L.9 (4) / M.8 | Task 1 permits invoicing for up to 37 records per hour for qualifying CDC system outages, annual refresher training, and new-interface orientation, while Sections L and M describe payment only for accepted records. Please explain how such noncoding hours will be documented, converted to payable record units, and invoiced under the IDIQ. | Cannot be personal IT or power issues; CDC or NCHS system downtime is chargable. |
| 62 | 6, 122-123 | B.6 Service Contract Labor Standards / L.9 (4) | For teleworking personnel in multiple states, should offerors base Service Contract Labor Standards wage determinations on each employee’s anticipated work location? If final locations or wage determinations are unknown at proposal time, what assumptions should offerors use for a comparable price evaluation? | Remote-Work Locations and Wage Determinations |
For teleworking employees, the applicable wage determination will generally be based on the locality where the employee performs the contract work. The contractor’s headquarters or the Government’s facility will not automatically establish the applicable locality.
Offerors shall identify the anticipated places of performance for their proposed employees, including the applicable city, county, and state, and shall identify the wage determination(s) and occupational classification(s) used to develop their proposed pricing. The Government will review the proposed wage determinations and incorporate the applicable wage determination(s) into the resulting contract or applicable Task Order, as appropriate.
Because employee locations may not be known at the time of solicitation, FAR 52.222-49, Service Contract Labor Standards—Place of Performance Unknown, applies. The Government has not identified one wage determination that applies to all potential remote employees. Additional wage determinations may be requested and incorporated when the applicable places of performance become known.
63 78-79, 122-124, 134 I.5-I.6 / L.9 (4) / M.8 The solicitation requires annual fixed record rates that account for labor-cost changes and includes Service Contract Labor Standards price-adjustment clauses. Should prices incorporate forecast wage/fringe increases, and how will post-award wage-determination adjustments be administered without duplicating amounts already priced? FAR 52.222-43 Adjustments is incorporated via amendment 0001.
FAR 52.222-43 will be administered in accordance with its terms. A price adjustment will not be automatic merely because the calendar year changes or because the Contractor’s labor costs increase. Any adjustment must be supported by the Contractor’s actual increase or decrease in applicable wages and fringe benefits resulting from a qualifying wage determination, collective bargaining agreement, or other event identified in the clause. The adjustment will be limited to the allowable cost impact under the clause and will be documented through a written contract or Task Order modification.
The Government will not separately adjust the firm-fixed price per accepted record for general inflation, commercial wage growth, increased overhead, reduced productivity, or other costs not covered by FAR 52.222-43.
| 64 | 114-117 | L.6 / L.7 (1)-(4) | The technical proposal limit is ten pages, excluding the cover, resumes, Staffing Matrix, and certain appendices; L.7 also allows the Project Plan as an appendix. Please confirm which appendices are excluded, whether the Project Plan outside the ten-page limit will be evaluated, and whether any additional appendix limits apply. | See amendment 0001. |
| 65 | 117-118 | L.7 (4)(b) Similar Experience | For the three relevant contracts performed within the last three years, may offerors use ongoing contracts awarded earlier but actively performed during that period? If two customer contacts are unavailable for a contract, will one contact plus a CPARS evaluation or other customer verification be acceptable? | Contracts currently in performance may be submitted, if performance meets the requirements of the RFP. Please provide at least Point of Contact for the reference. |
| 66 | 57-58, 120, 126 | H.6 / L.8 / M.3 / Attachment 0001 | For optional or potential future AI use that has not yet been selected or approved, what level of tool-specific detail is required at proposal time to obtain a Pass rating? Does contractor-only use of general productivity or drafting AI, with no Government data and no AI-supported contract deliverables, trigger an AI plan for contract performance? | For AI uses that have not yet been selected or approved, the Offeror shall identify the anticipated or potential use at the level of detail required by the CDCH.10 template, including the applicable task or function, proposed safeguards, data considerations, model or tool information to the extent known, and any other required information. The plan may identify the tool or configuration as preliminary or subject to future selection, but the Contractor may not use AI in contract performance until the Government reviews and approves the required plan. |
If the Offeror does not plan, expect, or anticipate using AI in performing the contract, it shall affirmatively state that no AI, including Generative AI, will be used in contract performance, and an AI Compliance and Risk Management Plan is not required at proposal submission. An Offeror’s unrelated internal use of AI that is not connected to contract performance does not, by itself, trigger the requirement.
| 67 | 121, 16 | L.9 (2)-(3) / Section C, Section 7 | Section L.9 requests a copy of the offeror’s current travel policy, while Section C states that travel is not applicable. Is submission of a travel policy nevertheless mandatory for responsiveness? | See amedment 0001. |
| 68 | 125-126, 132-134 | M.2 / M.8 Price Evaluation | How will the Government calculate an overall evaluated price and compare annual/tiered per-record rates when task-order quantities and volume distribution are not established in the solicitation? Will the Government provide a common estimated ordering scenario or weighting for price evaluation? | See amedment 0001. |
| 69 | 123–124, 132–134 | L.9; M.8 | Please provide the quantities and weighting or other calculation that will be used to derive the evaluated price across calendar years and the two quantity bands. If representative task orders will be used, please provide the common evaluation scenarios so that all offerors price on a consistent basis. | See amedment 0001. |
Sheet2
File details come from the government source that posted it. Updated .