Web Dev 4 2026-R-038 Questions and Responses.pdf

PDF 656 KB Posted

Attached to
U. S. Senate Web Dev 4
Solicitation number
2026-R-038
Issued by

About this file

This document is a Questions and Answers (Q&A) compilation for the U.S. Senate's Web Development IDIQ Contract (Solicitation 2026-R-038), addressing 215 inquiries from potential offerors.

The procurement establishes a multiple-award Indefinite Delivery/Indefinite Quantity (IDIQ) contract for web development and maintenance services for individual Senate Office websites, including Member, Committee, and other eligible offices. The contract employs a best-value tradeoff source selection methodology, with awards made to all offerors determined eligible. The contract ceiling is $5,637,600 per IDIQ with no guaranteed minimum; task orders are issued on an as-needed basis, typically providing 14 calendar days for proposal response. Procurement lead times for task order awards generally range from 3 to 5 weeks. The base period commences on or about January 1, 2027, with contract awards anticipated by end of calendar year 2026. The required Content Management System is WordPress only; alternative CMS platforms are not permitted. Development must occur exclusively on Senate-furnished equipment within the Senate network; code developed on non-Senate devices cannot be transferred to the Senate environment. All contractors must comply with WCAG 2.2 Level AA accessibility standards, OWASP Top 10 coding practices, and Attachment J-005 cybersecurity requirements. Pricing comprises five CLINs covering website design/development, content migration, website maintenance, and end-user support, submitted as fully burdened, all-inclusive rates. Offerors must submit a 50-page technical proposal (excluding resumes, references, and attachments), a Contractor Cybersecurity Plan, a staffing plan identifying Key Personnel with representative resumes for each, five past performance references via Attachment J-006 questionnaires and Attachment J-007 website information forms, and a pricing proposal. Remote performance is permitted with no on-site requirements; all contractor personnel require background investigations before network access. The SAA will not disclose incumbent contractor information or publish estimated labor quantities, TOPR volume projections, or anticipated award numbers.

View the file

Other files

Show all 11

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

Number Reference Question Answer

2026-R-038_(RFP)_Web_Dev_4, L.7.1.3, Qualifications and Resumes of Proposed Staff and M.5.1.4, Key Personnel - Pages 51 and 56

"The Offeror shall submit a representative resumes...for each individual to assigned to perform the work required under this Solicitation." (1) Please confirm that we should provide a resume for each labor category proposed for this requirement, whether Key or not Key. (2) In addition, can the Government clarify which positions should be considered Key?

Section L.7.1.3 requires Offerors to submit a staffing plan that identifies all proposed Key Personnel positions and includes a representative resume for each specifically named Key Personnel candidate proposed to perform under the contract. Offerors are responsible for proposing the key roles they consider necessary for successful contract performance, subject to evaluation under Section M.5.1.4. Resumes are required only for proposed Key Personnel.

2 2026-R-038 (RFP) Web Dev 4.pdf, I.13 (p. 39) Is there a requirement for websites to obtain an Authority to Operate (ATO)?

ATO is not required. However, all systems, applications, and cloud services proposed under this contract shall be subject to evaluation under the SAA CIO Cybersecurity Risk Assessment Process. The Offeror shall remediate vulnerabilities or deficiencies identified through such assessments as necessary to achieve and maintain a low or moderate risk rating, as determined by the Senate.

3 L.7.1.4 Section 4 – Past Performance

Could the government confirm Aretum meets relevant past performance requirements by submitting our Subsidiary(ies) past performance? Please note that Aretum LLC is a parent entity that intends to submit its response utilizing our fully-owned subsidiary Aretum Consulting Inc' or other subsidiaries past performance, utilizing a Meaningful Relationship between parent and subsidiaries. Aretum LLC followed the similar Meaningful Relationship Commitment Letter (MRCL) documentation to get the GSA OASIS+ Unrestricted Contract awarded under Aretum LLC (Parent Entity). Similarly, utilizing MRCL, Aretum LLC was also awarded the IDIQ Contract SeaPort NxG Contract.

Section L.7.1.4 allows references from the Offeror, including proposed subcontractors and wholly owned subsidiaries.

4 L.7.1.1.3 / M.5.1.1

Section L.7.1.1.3 states that the Offeror shall provide at least one qualifying Federal contract reference demonstrating relevant experience. Section M.5.1.3 states the Panel will review the Offeror's Subcontractors' similar experience. For the Go/No-Go Relevant Experience determination, may the qualifying Federal contract reference be held by a proposed Subcontractor, or must it be held by the Prime Offeror?

Section L.7.1.1.3 requires the Offeror to demonstrate its prior relevant Federal Government business experience as either a prime contractor or subcontractor.

5 L.7.1.4

Section L.7.1.4 requires five (5) Past Performance Questionnaires (Attachment J-006) and five (5) Past Performance Website Information forms (Attachment J-007). May the five references include a combination of Prime Contractor and Subcontractor contracts, or must all five references belong to the same entity?

Section L.7.1.4 applies to Offerors, including proposed subcontractors. The five references may include a mix of Offeror and proposed subcontractor contracts, provided the references otherwise meet the solicitation criteria and Attachment J-007 is completed for the same five references used for Attachment J-006.

G.5 Submission of Invoices and Payment Schedule AND G.5.4.2, 2nd paragraph

Please define "reasonable amount of time" in the statement "Payment is due within a reasonable amount of time". Does this contradict Net 60 in section G.5?

The Senate will pay within a reasonable time, defined as not later than sixty (60) calendar days after receipt of proper invoices approved by the Contracting Officer or their designee. The Senate will make reasonable efforts to process payment within thirty (30) calendar days, however, such efforts do not modify the contractual payment term of Net 60.

7 RFP Section M.5.1.4

In “Section 3 - Qualifications and Resumes of Proposed Staff,” the Senate requires representative resumes, but as written the Section M - Evaluation Criteria describes scoring based on the availability and commitment of Key Personnel. Could the Senate clarify the requirement?

Section L.7.1.3 requires Offerors to submit a staffing plan that identifies all proposed Key Personnel positions and includes a representative resume for each specifically named Key Personnel candidate proposed to perform under the contract. Offerors are responsible for proposing the key roles they consider necessary for successful contract performance, subject to evaluation under Section M.5.1.4. Resumes are required only for proposed Key Personnel.

2026-R-038_(RFP)_Web_Dev_4, C.3.4.1 Development Requirements - Page 9

Since all development must occur within the Senate network, will sandbox, staging, and CI/CD tools be provided, or must contractors adapt to existing Senate tooling?

The SAA will provision and maintain the production CMS platform. Staging and development environments shall be governed by SAA standards and made available to awarded contractors through the Senate network.

Attachment J-001-A - Senate Web Development Guide Section User Data Collection AND Attachment J- 001-B - Senate Web Design Guide Section User Data Collection

Please confirm whether the Contractor or SAA will be responsible for the Captcha license. It is stated in the IDIQ that the SAA will provide Adobe Analytics/Java licenses.

The SAA will be responsible for procuring required CAPTCHA licenses. The contractor shall be responsible for implementing the licensed solution as part of contract performance.

10 N/A Is this activity considered a new requirement or a follow-on to an existing contract?

Yes. This requirement is a follow-on procurement and represents the fourth iteration of a multi-award IDIQ contract vehicle.

11 N/A If there is an incumbent, would you be able to share the vendor’s name, the contract number, value, award date and expiration date?

The SAA does not disclose information regarding incumbent contractors.

12 N/A How are success metrics defined (traffic, engagement, task completion, accessibility)?

Website success shall be determined by the receiving Office’s written acceptance of the completed project and the results of post-launch monitoring. Attachments J-001-A and J-001-B set forth applicable technical requirements, including Section 508 accessibility and security compliance. Notwithstanding those requirements, the primary performance criteria are timely, within-budget, launch-ready delivery and the Office’s written acceptance.

13 N/A Do priorities differ across Senate Offices? If so, how?

Yes. Each Senate Office functions as an independent customer and may have unique content, branding, legislative priorities, constituent service needs, and functional requirements. Member, Committee, and caucus offices may therefore require materially different website solutions. Offerors may review publicly available senate.gov websites for general comparative research regarding feature sets and presentation.

14 C. 1 IDIQ

What are typical timelines for Task Orders to be issued to making award decisions?

Task Order Proposal Requests (TOPRs) are issued on an as-needed basis under the IDIQ contract. Approved contractors will generally be provided 14 calendar days to submit a proposal in response to a TOPR. Typical procurement lead times range from approximately 3 to 5 weeks from TOPR issuance to the Office’s final award decision; however, actual timelines may vary depending on the scope and complexity of the requirement. No minimum or maximum award timeframe is guaranteed.

15 J-001-A; "Approved Plugins" What is the process for requesting new functionality or plugins?

Requests to add a new plugin to the approved list identified in Attachment J-001- A shall be submitted to the SAA for review and approval. The SAA’s review process includes, at a minimum, assessments of security, accessibility, and compatibility. The review and approval process may take up to six months.

16 J-001-A; "Approved Plugins"

The document mentions that requests for additional plugins may require an addiitonal 6 months for review and approval. Is the contractor liable for timelines going out of initial scope if this occurring during a build?

Because approval of a proposed plugin cannot be assured, contractors are expected to scope and price their proposals based on the currently approved plugin list set forth in Attachment J-001-A. Contractors shall not propose, rely upon, or otherwise include unapproved plugins in response to TOPRs. This approval process applies to plugins not currently on the approved list that a contractor may wish to use in connection with future task orders. Unless and until a plugin has been formally approved by the SAA and added to the approved list, contractors shall not reference such plugin as available for use within the proposed scope of work.

17 2026-R-038 Web Dev RFP; Pricing et al

The RFP mentions that pricing for end-user support is included in the scope of this engagement. Can you please clarify if "end-user" in this context is internal team members or audience members that are visting the senate.gov sites?

For purposes of this RFP, “end-user support” means support provided to Senate Office personnel who use the SAA-provided CMS to create, update, and maintain content for their Office’s website

18 J-001-B; "Future updates" How frequently are the design guides updated? Do all sites share a common theme or components?

There is no established or fixed schedule for updates to these documents.

Updates are issued infrequently, however, contractors are responsible for reviewing all current solicitation materials, including any revisions to these documents, prior to submitting a proposal in response to each TOPR. Offerors should refer to Attachments J-001-A and J-001-B for information regarding components and requirements that are generally common to newly established Office websites.

19 J-001-B; "Design and Functionality" Do the offices share the same color palette, typography, fonts, etc.?

No. Each Senate Office independently determines its branding and visual design preferences, including but not limited to color palette, typography, font selection, layout, and other design elements.

20 J-003; Content Migration Can the SAA provide guidance on the typical scale and complexity of content migration (e.g., number of pages, document types, integrations)?

The scope, scale, and complexity of website migrations may vary substantially depending on multiple factors, including the type of Office involved (for example, Member, Committee, or caucus), the age and maturity of the Office’s existing web presence, and, in the case of a redesign, the content management system currently supporting the existing website.

21 J-001 A/B Are there standardized content models, taxonomies, or governance practices that contractors should follow across Senate Office websites?

Senate Offices are not required to adhere to a uniform or standardized content model, taxonomy, navigation structure, or information architecture. Mandatory cross-site requirements are generally limited to applicable accessibility standards, including Section 508, ADA Title II, and the latest applicable WCAG requirements pursuant to C.3.4.9; security requirements, including Attachment J- 005 Cybersecurity SOPs and C.3.4.1; privacy and user data handling requirements, including those set forth in Attachments J-001-A and J-001-B; use of approved plugins and approved social media platforms as identified in the applicable attachments; and the SAA-provided WordPress base build. Subject to those requirements, each Office retains discretion over its content structure, taxonomy, navigation approach, and editorial governance.

22 J-001-A; CMS Base builds Are development, staging, and production environments provisioned by the SAA, and what are the deployment expectations?

In accordance with Attachment J-001-A, the SAA shall provision the CMS platform and the supporting infrastructure.

23 N/A Is remote work permitted for this engagement, or are there any on-site requirements for contractors?

Remote performance is permitted and anticipated under this requirement. There are no on-site performance requirements.

24 N/A Is there any preference or evaluation advantage for SDVOSB or other small business categories under this contract?

No. As set forth in Section M of the Solicitation, award will be made using a best-value tradeoff source selection methodology.

25 M.5.1.1 / L.7.1.1.3

The Go/No-Go Relevant Experience factor (M.5.1.1) requires the Offeror to demonstrate relevant business with the federal government, and Section L.7.1.1.3 requires at least one qualifying Federal contract reference. (a) Does experience as a subcontractor on a Federal prime contract satisfy this requirement? (b) May an Offeror reference Federal contract experience gained by its key personnel while employed at a prior firm? (c) Does state or local government contract experience qualify under this factor?

(a) Yes. Relevant work performed by the Offeror entity as a subcontractor under a Federal prime contract may be submitted to satisfy the requirements of M.5.1.1.

(b) No. The Go/No-Go Relevant Experience factor evaluates the Offeror entity’s organizational contract experience, not the experience of individual personnel.

(c) No. Section M.5.1.1 expressly requires relevant business performed with the Federal Government. State and local government experience does not satisfy this requirement, but may be submitted for consideration under Factor 2, Past Performance.

26 C.3.11.2 / Attachment J-001-A

What Content Management System(s) does the SAA currently provide to Senate Offices as its standard base build? For example, is Drupal the primary CMS, and if so, which version(s) are in active use? This will help offerors accurately represent their CMS expertise in their technical proposals.

The SAA provides a WordPress base build for all newly elected Senators. The base build will utilize the version of WordPress that is current at the time the base build is created.

27 C.1.3

Section C.1.3 states contractors must use SAA-provided resources and Senate-supplied equipment when connecting to Senate systems. Is all development work required to be performed exclusively on Senate-provided hardware, or may contractors use their own equipment (e.g., personal or company-owned laptops with VPN access) for development and testing prior to deploying to the Senate network?

All development activities shall be performed using Senate-furnished equipment on the Senate network. Development work performed on non-Senate devices may not be transferred, ported, or otherwise migrated into the Senate environment.

28 General / H (Security)

Does performance of this contract require personnel to hold any security clearance or pass a Senate background investigation? If so, what level of investigation is required, and is there a timeline by which clearances must be obtained after contract award?

Any contractor personnel requiring access to the Senate network must successfully complete the applicable background investigation process before VPN credentials will be issued. In accordance with Section H.4.3.2, personnel security processing requires a minimum lead time of two weeks.

29 General / C.3

Is remote work authorized for day-to-day contract performance (e.g., website design, development, and maintenance tasks), or is regular on-site presence at Senate facilities in Washington, DC required? If both, please clarify which tasks require on-site presence.

Remote performance is permitted and anticipated under this requirement. There are no on-site performance requirements.

30 L.7.1.4 / Attachment J-006

For the five (5) Past Performance Questionnaires (Attachment J- 006): must completed questionnaires be received at acquisitions@saa.senate.gov by the May 4, 2026 proposal deadline, or may they be submitted by references directly to the SAA either before or shortly after the proposal deadline?

Past Performance Questionnaires (Attachment J-006) must be submitted directly by the reference point of contact to acquisitions@saa.senate.gov no later than the proposal due date.

31 C.3.1.8.d / L.7.1.1.3

Section C.3.1.8.d requires 'references and examples of the Contractor's website graphic design work previously completed and available to view in a web browser.' Are commercial or private-sector website portfolio examples acceptable, or must all referenced work involve federal, state, or local government websites?

Commercial and private-sector website portfolio examples are acceptable, provided that each example is publicly accessible via a web browser and demonstrates capabilities relevant to the graphic design requirements of this solicitation.

32 L.7.2.2.1.d / Section K

Will the SAA provide a fillable Section K (Representations and Certifications) template as part of this solicitation, or should offerors submit their current SAM.gov representations and certifications (online reps and certs) to satisfy this requirement?

The Offeror shall complete the fillable Section K for the prime contractor and for each proposed subcontractor, if any, and shall include the completed forms within the model contract submission.

33 L.7.2.2.1.a / Section A

For the completed Section A (solicitation/contract form, page 1, subsections 9–14) required in Volume II: is an electronic or digital signature (e.g., DocuSign, PDF signature) acceptable, or is a handwritten wet signature required prior to scanning and submission?

Electronic or digital signatures, including DocuSign and PDF-applied signatures, are acceptable for Section A and all other signature blocks included in the proposal, provided that the signature clearly identifies the authorized representative by name and title and is affixed by an individual authorized to bind the Offeror.

34 L.3

For proposals requiring multiple email transmissions due to the 6MB size limit, what subject line convention should be used? For example: '2026-R-038 Skilak Consulting — Transmission 1 of 3' and '2026-R-038 Skilak Consulting — Final Transmission (3 of 3)'? Please confirm the preferred format.

The SAA does not prescribe a required subject-line format for proposals submitted in multiple transmissions pursuant to Section L.3. Any clear and consistently applied subject-line convention is acceptable.

35 H.3 / M.5.1.4

Section M.5.1.4 references Key Personnel requirements defined in Section H.3. Please confirm the specific Key Personnel position titles and minimum qualifications required, as this information is critical to the staffing plan in our technical proposal.

The solicitation does not identify specific Key Personnel labor categories, position titles, or minimum qualification requirements. Offerors are responsible for identifying proposed Key Personnel and demonstrating that such personnel possess qualifications appropriate to the requirements of the statement of work.

Key Personnel will be evaluated in accordance with the criteria set forth in Section M.5.1.4.

36 C.3.4.1.4 / Attachment J-005

Section C.3.4.1.4 requires contractors to follow OWASP Top 10 coding practices. Should offerors reference the most current version of the OWASP Top 10 (2021), or is a specific version mandated? Additionally, does the Senate have a preferred vulnerability scanning or SAST tool for OWASP compliance verification?

Offerors shall align with the most current version of the OWASP Top 10 in effect as of the proposal due date. The SAA does not require the use of any specific vulnerability scanning tool or static application security testing (SAST) tool for purposes of demonstrating OWASP compliance.

37 B.7.1 / L.7.2.1

For the pricing proposal, should labor rates in Section B.7.1 reflect fully burdened all-inclusive rates (inclusive of overhead, G&A, fringe, and profit), or should cost elements be broken out separately? Please confirm the preferred format for the pricing narrative/rationale.

Rates proposed in Section B.7.1 shall be fully burdened and all-inclusive. The CLIN table shall include one rate per CLIN for each applicable period: hourly rates for labor-hour CLINs and monthly rates for firm-fixed-price support CLINs. If subcontractors are proposed, the rates entered in the CLIN table shall reflect composite prices or rates. The supporting pricing narrative shall describe the services included, applicable assumptions, exceptions or dependencies, and the basis for the proposed pricing. Offerors may provide additional labor category detail in the narrative to support price reasonableness.

2026-R-038_(RFP)_Web_Dev_4, C.3.1 C.3 Statement of Work - Page 6

Can the Government provide a list of Senate Offices that may participate in this IDIQ?

All Member offices, Committee offices, and other eligible Senate offices, including non-Member offices, may obtain public-facing websites under this contract.

Attachment J-001-A Senate Web Development Guide, CMS Base Builds - Page 4

Can the Government clarify whether the SAA-provided WordPress environment is implemented as a multisite architecture, and if so, how governance is managed across sites (e.g., shared themes, plugin controls, deployment processes, and site-level customization boundaries)?

A multisite architecture will not be implemented under this contract.

2026-R-038_(RFP)_Web_Dev_4, B.8 Contract Ceiling and Guaranteed Minimum - Page 5

Given that there is no guaranteed minimum and multiple IDIQ awards are anticipated, can the Government provide an estimated number of Task Orders per year or historical ordering patterns to help vendors plan staffing and pricing strategies?

The volume of task orders may fluctuate significantly based on election outcomes. Task Order Proposal Requests (TOPRs) are issued for all newly sworn-in Senators and for any Senate office, including Member, Committee, caucus, and other eligible offices, that requests a redesign or redevelopment of its existing website.

2026-R-038_(RFP)_Web_Dev_4, C.3.1 Pre-Award Procedures - Page 6

Will Task Order evaluations be based solely on Office preference, or will the SAA apply standardized evaluation criteria across TOPRs (e.g., technical, past performance, price)?

Task order awards are made based on the preferences and requirements of the requesting Office. However, the SAA reserves the right to exclude from consideration any proposal that does not conform to contract requirements.

2026-R-038_(RFP)_Web_Dev_4, C.3.1.7 Task Order Proposal Requirements - Page 7

Is the 20-page limit for TOPR responses inclusive of resumes, past performance, and visuals, or are any sections excluded from the page count?

In accordance with Section L.6, resumes, references, past performance information, certifications, and attachments shall not count toward the Technical Proposal page limitation.

2026-R-038_(RFP)_Web_Dev_4, B.3 Contract Type -

For Labor-Hour Task Orders, will the Government provide estimated level-of-effort ranges in TOPRs, or is scoping entirely the responsibility of the Contractor?

Project scoping is the responsibility of the contractor and shall be based on the Office requirements identified in the applicable TOPR.

44 2026-R-038_(RFP)_Web_Dev_4, B.4 Pricing - Page 2 Are there expectations or guidance regarding the proportion of work anticipated under Firm-Fixed-Price vs. Labor-Hour Task Orders?

The SAA is unable to provide such figures, as requirements vary considerably by Office and may fluctuate substantially based on election outcomes and other operational factors.

Attachment J-001-A Senate Web Development Guide, CMS Base Builds - Page 4

Given that WordPress is the provided CMS base build, are contractors permitted to propose alternative CMS platforms under any circumstances or is WordPress strictly required?

The Senate is not considering alternative CMS platforms under this solicitation.

Attachment J-001-A Senate Web Development Guide, Custom Code - Page 5

What is the typical approval timeline for custom code requests, and how should contractors account for this in project schedules?

Use of custom code is uncommon, and approval timelines vary depending on the business need, scope, security considerations, and staff availability. Accordingly, Offerors should scope TOPR responses based on the approved plugin list and the SAA-provided WordPress base build and should not propose schedules that are dependent upon pending approval of custom code.

Attachment J-001-A Senate Web Development Guide, Plugins - Page 4–5

Can the Government clarify the process and expected timeline for approving new plugins, especially for functionality not currently supported by the approved list?

In accordance with Attachment J-001-A, proposed plugins are subject to SAA review for security, accessibility, and compatibility. The review and approval process may require up to six (6) months.

Attachment J-002 Website Testing and QA Requirements - Page 3–5

Are there standardized templates or reporting formats required for defect tracking, readiness reviews, and testing documentation?

The Solicitation does not prescribe standard report formats. However, all reports delivered under the contract shall comply with all applicable contractual requirements.

2026-R-038_(RFP)_Web_Dev_4, C.3.5 QA Requirements - Page 10

Will the Government provide access to automated testing tools or environments, or are contractors expected to supply their own testing frameworks within Senate constraints?

The SAA provides an accessibility testing tool, as referenced in Attachment J-002, as well as the staging and production deployment pipeline.

2026-R-038_(RFP)_Web_Dev_4, C.3.4.7 Search Requirements - Page 10

Is there an existing enterprise search solution (e.g., indexing service) that contractors must integrate with, or are search implementations expected to be handled within the CMS?

Search functionality is expected to be implemented through the CMS. In addition, certain approved plugins may be used to provide enhanced search capabilities, as identified in Attachment J-001-A, Approved Plugins.

2026-R-038_(RFP)_Web_Dev_4, C.3.4.8 CDN Compatibility - Page 10

Can the Government specify the current Content Delivery Network (CDN) and any performance or caching requirements contractors must design against?

The Senate utilizes Akamai as its content delivery network (CDN). Specific security-related requirements and constraints associated with Akamai are set forth in Attachment J-001-A, User Data Collection.

2026-R-038_(RFP)_Web_Dev_4, C.3.6 Website Maintenance - Page 11

Are there defined SLAs for issue resolution beyond the 15-minute acknowledgement requirement, such as response and resolution time tiers?

The contract does not establish specific service-level agreements (SLAs) for issue resolution. Nevertheless, Offerors should recognize that Senate Offices expect timely resolution and proactive status communication commensurate with the severity and urgency of the service request.

2026-R-038_(RFP)_Web_Dev_4, C.3.8 Defect Remediation - Page 12

Can the Government clarify expectations for “no-cost” defect remediation over time (e.g., duration, scope boundaries, and distinction from new feature requests)?

For purposes of contract performance, defects are issues involving features, functionality, or content that have already been developed and implemented on an Office website but are subsequently found not to function as intended. By contrast, new feature requests involve the development or addition of new functionality, features, or content not previously implemented.

54 Attachment J-003 Sample TOPR - Page 1–2 Will all TOPRs follow a similar structure and level of detail as the sample, or should contractors expect significant variability in requirements and documentation?

TOPRs will generally follow a structure similar to the sample provided; however, the specific requirements, as well as the level of detail and supporting documentation, may vary by Office and by individual TOPR.

Attachment J-003 Sample TOPR, Content Migration -

For non-WordPress sites requiring migration, will the Government provide inventories, data schemas, or migration tools, or is full discovery expected from the Contractor?

For migrations from non-WordPress websites, the Senate will provide available content databases and will make available any approved plugins that facilitate migration to WordPress. The awarded contractor is expected to derive as much schema-related knowledge as reasonably possible from initial migrations and to retain and apply that knowledge in support of future migration efforts.

Attachment J-004 Senate Supported Software List -

Are there any restrictions on development tools (e.g., IDEs, build tools, version control systems) beyond the supported software list that contractors should plan for?

Contractors shall use only tools identified on the Senate Supported Software List set forth in Attachment J-004 for any activity involving Senate systems.

2026-R-038_(RFP)_Web_Dev_4, Section M Evaluation Factors - Page 53–57

Can the Government clarify the relative weighting of technical approach, past performance, and price for base IDIQ awards?

As provided in Section M, the Technical Approach factor is more important than Past Performance, and when combined, all technical evaluation factors are more important than Price. Offerors should refer to Section M of the Solicitation for the complete relative weighting of all evaluation factors.

2026-R-038_(RFP)_Web_Dev_4, C.3.1.8 Non-TOPR Documentation - Page 7

Will the non-TOPR documentation (e.g., design approach, staffing, past work) be evaluated as part of the base IDIQ award, or only used during TOPR competitions?

Any and all information submitted by Offerors as part of their contract proposals may be used by the SAA for purposes of proposal evaluation in accordance with the terms of the Solicitation.

2026-R-038_(RFP)_Web_Dev_4, C.3.3 Task Order Administration - Page 8

Can the Government clarify the expected level of direct interaction between contractors and Senate Office staff versus coordination through the COR?

Routine day-to-day coordination with Senate Office staff is expected and is a normal aspect of contract performance. Coordination with the Contracting Officer’s Representative (COR) is required for contract administration matters, including, but not limited to, invoicing, contract modifications, task order issuance, and acceptance.

2026-R-038_(RFP)_Web_Dev_4, C.3.4 Accessibility Requirements - Page 10

Which WCAG version will be enforced at delivery (e.g., 2.1 AA vs.

2.2), and will this vary over the life of the contract?

In accordance with Section C.3.4.9, the required accessibility delivery standard is WCAG 2.2 Level AA.

Attachment J-001-A Senate Web Development Guide, CMS Base Builds - Page 7

Can the Government specify if there are any customizations to the Adobe Analytics implementation that should be maintained?

No specific customizations are required to be maintained unless such requirement is expressly identified in the applicable TOPR.

2026-R-038_(RFP)_Web_Dev_4, L.7.1.1.3, Offeror Relevant Experience - Page 50

The offeror is instructed to provide at least one qualifying contract reference of a recently awarded, relevant project that has been awarded within the past 3 years AND were designed using the targeted CMS. Will the Government please define "targeted CMS?"

The target content management system under this Solicitation is WordPress.

63 General Are there incumbent vendors currently providing these services to SSA? If yes, please provide vendor names and contract numbers.

This procurement is being conducted under a multi-award IDIQ contract structure in which multiple incumbent contractors compete for TOPRs. The SAA does not disclose incumbent contractor names, contract numbers, or contract values.

2026-R-038_(RFP)_Web_Dev_4, L.7.1.1.3 and M.5.1.3 Conflict - Page 55

Section L.7.1.1.3 refers to project examples AWARDED within the past 3 years whereas M.5.1.3 refers to project that are CURRENTLY ONGOING or COMPLETED within the past 3 years. Please clarify the time window for projects suitable to use as references.

The two time-based requirements apply independently. Section L.7.1.1.3 governs eligibility for the Offeror Relevant Experience requirement and requires that the referenced work have been awarded within the past three (3) years.

Section M.5.1.3 governs the relevance standard for Past Performance evaluation and requires that the referenced work be ongoing or completed within the past three (3) years. References submitted by the Offeror must satisfy the applicable timeframe requirement for the evaluation factor under which they are provided.

2026-R-038_(RFP)_Web_Dev_4, L.7.1.4, Past Performance - Page 52

The Offeror is instructed to send a Past Performance Questionnaire (PPQ) to 5 relevant references. If the contract being used as a reference has a CPARs, can we use that in lieu of a PPQ?

CPARS information may be cited within the technical proposal as supplemental past performance information, however, CPARS does not replace the Past Performance Questionnaire (Attachment J-006) required by Section L.7.1.4.

2026-R-038_(RFP)_Web_Dev_4, L.7.1.4, Past Performance - Page 52

Please confirm that if we are proposing use of a Subcontractor, we can use their past performance as 1 or 2 of the 5 to be submitted.

Confirmed.

2026-R-038_(RFP)_Web_Dev_4, L.7.2.1, Price Section Instructions - Page 53

Please confirm that we should use the table format presented in B.7.1 to prepare our price proposal.

Confirmed.

2026-R-038_(RFP)_Web_Dev_4, L.7.2.1, Price Section Instructions - Page 53

The offeror is instructed to "provide the firm-fixed-rates for all the services, material, and deliverables inclusive of approved fully burdened direct labor rates, travel, per diem, and other direct costs."

We understand the labor rate guidance but without specifics of travel, per diem, and ODCs, how are we to approach firm-fixed-rates for non-labor costs?

Offerors should propose fully burdened labor rates in Section B.7.1 that, to the extent practicable, include all anticipated travel costs, per diem, and other direct costs (ODCs).

Attachment_J-003_- _Sample_Task_Order_Proposal_Request_(TOPR)

Please confirm that the Sample TOPR is provided for informational purposes only and does not require a proposal response with our May 4 submission.

Confirmed.

2026-R-038 (RFP) Web Dev 4.pdf, C.3.1.7.1 (p. 7); L.6- L.7 (pp. 49-53)

Please confirm that the twenty (20) page limit in Section C.3.1.7.1 applies only to post-award Task Order Proposal Requests (TOPRs), and that the current IDIQ proposal should follow the page limits and volume structure in Section L.

Confirmed.

71 2026-R-038 (RFP) Web Dev 4.pdf, B.1 (p. 2) Is the scope of this contract a single site or website for all of the US Senate office?

This IDIQ contract is intended to support the development and maintenance of individual public-facing websites for Senate Offices, including Member, Committee, and other eligible Offices. It does not contemplate a single, unified enterprise platform. Each task order will pertain to the website requirements of a single Office.

72 2026-R-038 (RFP) Web Dev 4.pdf, B.7.1 (pp, 3-4) What is estimated level of effort by CLIN per year?

No. Task order volume may vary based on election outcomes, and the level of effort for each task order will depend on the specific requirements of the requesting Office.

73 2026-R-038 (RFP) Web Dev 4.pdf, C.3.4.1.1 (p. 9) Are there different environments on the Senate network, e.g., Dev, Test, Prod?

Yes. The SAA shall provision the applicable environments, and detailed information regarding those environments will be provided to awarded contractors.

74 2026-R-038 (RFP) Web Dev 4.pdf, C.3.4.2 (p, 9) Does the sample TOPR need to be addressed in the proposal? No.

75 2026-R-038 (RFP) Web Dev 4.pdf, H.3 (p. 24) What roles are key?

The Solicitation does not prescribe specific Key Personnel labor categories or position titles. Offerors are responsible for identifying and designating proposed Key Personnel, which will be evaluated in accordance with Section M.5.1.4.

76 General Comment Is there an incumbent contractor?

Yes. This requirement is being procured under a multi-award IDIQ contract structure, with multiple incumbent contractors eligible to compete for TOPRs.

77 General Comment How many awards does SAA expect to make?

Awards will be made to all Offerors determined to be eligible for award under the best-value tradeoff methodology set forth in Section M of the Solicitation.

78 General Comment Where are the web sites currently hosted?

The SAA shall provide the production hosting environment for Senate Office websites within the SAA-managed Senate environment. Detailed technical information regarding that environment will be provided to awarded contractors.

Attachment J-005 - U.S. Sergeant at Arms Standard Operating Procedures (SOPS) for Cybersecurity.pdf, §14.2-14.3 (pp. 30-32); 2026-R-038 (RFP) Web Dev 4.pdf, L.7.1 (pp. 49-53)

Attachment J-005 states that the Contractor will provide a comprehensive Contractor Cybersecurity Plan (CSP) in its proposal.

Please confirm whether a standalone CSP is required in the current IDIQ proposal submission, and if so, identify the required volume/section and whether it counts toward the Technical Volume page limit.

Confirmed.

Attachment J-001-A - Senate Web Development Guide.pdf, 'Compliance and Future Updates' (p. 3);

Attachment J-001-B - Senate Web Design Guide.pdf, 'Future Updates' (p. 3); 2026-R-038 (RFP) Web Dev 4.pdf, C.3.4.5 (p. 10)

The guides state that requirements may be revised and that awarded contractors must rely on an internal SAA site. For purposes of this solicitation, please confirm that offerors will be evaluated only against the versions of the attachments issued with the solicitation (plus any formal amendments), and not against unpublished or future internal guidance.

Confirmed.

2026-R-038 (RFP) Web Dev 4.pdf, C.3.11.2 (p. 14);

Attachment J-001-A - Senate Web Development Guide.pdf, 'Content Management System Base Builds'

(p. 4); Attachment J-001-B - Senate Web Design Guide.pdf, 'General Guidelines' (p. 4); Attachment J- 003 - Sample Task Order Proposal Request (TOPR).pdf, 'Content Migration' (p. 2)

Please confirm whether WordPress is the only approved CMS for performance under this IDIQ, and whether references in the sample TOPR to a contractor's 'proposed CMS' should be understood as WordPress within the SAA-provided environment rather than an offeror-selected alternative CMS.

Confirmed.

Attachment J-001-A - Senate Web Development Guide.pdf, 'Approved CMS Plugins' and 'Custom Code'

(pp. 4-5); Attachment J-001-B - Senate Web Design Guide.pdf, 'Approved CMS Plugins and Design Functionality' (p. 4)

If a required feature cannot be provided through the current approved plugin set and requires either a new plugin review or approved custom code, should offerors assume that such functionality may be proposed conditionally, or should it be excluded from scope until SAA approval is obtained?

In responding to Task Order Proposal Requests (TOPRs), contractors should identify any instances in which the current list of approved plugins does not satisfy the functional requirements of the effort. In such cases, the contractor should specify what additional plugin, if any, would need to be added to the approved plugin list and/or, in the limited circumstances where necessary, indicate that custom code would be required to meet the stated requirement.

Attachment J-003 - Sample Task Order Proposal Request (TOPR).pdf, 'Approved social media feeds' and 'share website content on social media' (pp. 3-4);

Attachment J-001-A - Senate Web Development Guide.pdf, 'Social Media Integration / Privacy Concerns' (pp. 7-8); Attachment J-001-B - Senate Web Design Guide.pdf, 'Privacy Concerns' (pp. 6-7)

Please clarify the compliant implementation methods for 'approved social media feeds' and social sharing functionality, given the prohibition on embedding third-party code, widgets, JavaScript, API calls, and external iFrames. For example, are simple outbound links or static/manual content displays the intended approach?

This prohibition applies to unapproved third-party integrations. Third-party integrations that have been expressly approved by the Senate, including approved social media platforms, are permitted.

Attachment J-001-A - Senate Web Development Guide.pdf, 'Approved social media platforms' (pp. 7- 8); Attachment J-001-B - Senate Web Design Guide.pdf, 'Approved social media platforms' (pp. 6- 7)

Please confirm whether the approved social media platform list in Attachments J-001-A and J-001-B is the complete list for proposal and performance purposes unless the SAA issues a written exception, and whether any changes to the list prior to award will be issued by formal amendment.

Confirmed.

2026-R-038 (RFP) Web Dev 4.pdf, C.3.4.9 (p. 10);

Attachment J-001-B - Senate Web Design Guide.pdf, 'Accessibility' (p. 8); Attachment J-003 - Sample Task Order Proposal Request (TOPR).pdf, 'Accessibility' (p.

2)

Section C.3.4.9 references Section 508, ADA Title II, and 'the latest WCAG standard applicable at delivery.' Please identify the specific WCAG version and conformance level that offerors should propose against (e.g., WCAG 2.1 AA, WCAG 2.2 AA, or other).

In accordance with Section C.3.4.9, the required accessibility delivery standard is WCAG 2.2 Level AA.

2026-R-038 (RFP) Web Dev 4.pdf, C.3.5 (p. 10);

Attachment J-002 - Website Testing and Quality Assurance Requirements.pdf, pp. 3-7

Attachment J-002 references a Senate-provided accessibility test tool and an internal SAA knowledgebase site for additional testing guidance. Will the SAA identify the specific required tools and any mandatory internal procedures for offerors during the solicitation period, or are those details only provided after award?

Information regarding Senate-provided accessibility testing tools and applicable internal knowledgebase procedures will be communicated to awarded contractors after contract award.

2026-R-038 (RFP) Web Dev 4.pdf, C.1.3 (p. 5); F.2.2- F.3 (pp. 19-20); Attachment J-005 - U.S. Sergeant at Arms Standard Operating Procedures (SOPS) for Cybersecurity.pdf, §14.2-14.3 (pp. 30-32)

Please clarify whether any contractor-owned systems may ever directly connect to Senate systems, networks, or VPNs under this contract, or whether all such access must occur exclusively through Senate-provided equipment. If contractor corporate IT assets are never permitted to connect directly, please confirm that references to those assets in the CSP requirements are limited to the contractor's internal development/support environment.

Pursuant to Sections F.2.2 and F.3, all access to the Senate network must occur through Senate-Furnished Equipment (SFE). Accordingly, references in Attachment J-005 to contractor corporate IT assets pertain to the contractor’s internal development and support environment, rather than to direct access to Senate systems.

Attachment J-005 - U.S. Sergeant at Arms Standard Operating Procedures (SOPS) for Cybersecurity.pdf, §14.3.8 and §15 (pp. 35, 50); 2026-R-038 (RFP) Web Dev 4.pdf, C.3.6 (pp. 11-12)

Please clarify the authorization model for remote support. Is written authorization required only for CPS/CSS server access, while oral or ticket-based approval is sufficient for other office systems on an as-needed basis, or is written authorization required for all categories of remote access?

Remote access to Office websites and/or associated data shall be granted only upon issuance of a task order, receipt of a specific service request from an Office or the SAA, or as otherwise expressly authorized by the SAA.

2026-R-038 (RFP) Web Dev 4.pdf, H.4.3 (pp. 25-27);

L.7.1 (pp. 49-53)

Please confirm whether background checks, non-disclosure forms, and related personnel security documents are post-award onboarding requirements only, or whether any of these materials must be submitted with the current proposal for proposed key personnel or other staff.

Background investigations, non-disclosure agreements, and related personnel security documentation are post-award requirements only.

2026-R-038 (RFP) Web Dev 4.pdf, H.4.3.1-H.4.3.3 (pp.

26-27); F.2-F.3 (pp. 19-20)

Please confirm whether the U.S. citizenship/eligibility and background check requirements apply only to personnel who require Senate building access, Senate-issued devices, or Senate network/system access, or whether they apply to all contractor and subcontractor personnel supporting the contract, including personnel performing offsite work with no direct Senate access.

U.S. citizenship or other applicable work eligibility requirements, as well as background investigation requirements, apply to all contractor personnel who will perform work under this contract.

91 2026-R-038 (RFP) Web Dev 4.pdf, F.2-F.2.1 (p. 19)

Section F.2.1 states that contractor sites, including home offices, may be audited. Please clarify whether this requirement applies to any home office used for any level of contract support, including proposal support, project management, and content-only support, or only to locations that access Senate systems/data.

Confirmed. This requirement applies to any and all contractor facilities or sites involved in performance under the contract.

92 2026-R-038 (RFP) Web Dev 4.pdf, C.3.6.3 (p. 11)

Please clarify the scope of the requirement for a human acknowledgement of any service request within fifteen (15) minutes during normal business hours. Does this apply to all request channels (email, phone, ticketing portal), and is it measured from initial receipt by the contractor or from routing to the responsible support team?

This requirement applies to all communication channels and shall be measured from the contractor’s initial receipt of a communication from an Office.

2026-R-038 (RFP) Web Dev 4.pdf, C.3.8 and E.1.4 (pp.

12, 17-18); Attachment J-002 - Website Testing and Quality Assurance Requirements.pdf, 'Website Exception Period' (p. 7)

Please clarify whether the obligation to repair defects at no additional cost 'regardless of when identified' is limited to contractor-caused defects as defined in Section E.1.4, and does not extend to failures caused solely by SAA-managed platform changes, SAA plugin/core updates, approved third-party service changes, or office content changes.

Confirmed.

2026-R-038 (RFP) Web Dev 4.pdf, E.1.7 and H.16 (pp.

17, 31-32); Attachment J-003 - Sample Task Order Proposal Request (TOPR).pdf, 'Statement of Work' (p.

1)

Please clarify the distinction between the eight (8) hours of Post- Launch Emergency Support referenced in the sample TOPR and the separate emergency support provisions in Section H.16. Are Senate-declared emergency/crisis support requirements outside the included eight hours separately compensable under H.16?

Neither Senate declared nor Office declared emergencies are excluded from the scope of this provision. All work performed under this contract, including end-user support, requires an explicit task order. This provision is intended to ensure that Offices that elect not to include end-user support in their initial task order for website design and development may nevertheless obtain a limited amount of urgent support, up to a maximum of eight (8) hours, from the contractor that developed the site, without requiring the Office to wait for issuance of a separate task order for ongoing support beyond that initial period.

Attachment J-003 - Sample Task Order Proposal Request (TOPR).pdf, 'Content Migration' (p. 2); 2026- R-038 (RFP) Web Dev 4.pdf, B.7.1 and C.3 (pp. 3, 6)

The sample TOPR states that content migration is not required for websites currently in WordPress, while the IDIQ includes a separate Content Migration CLIN. Please confirm whether offerors should assume that WordPress-to-WordPress rebuilds generally exclude content migration unless a TOPR expressly requires it.

Confirmed.

2026-R-038 (RFP) Web Dev 4.pdf, C.3.6.5 (p. 11);

Attachment J-001-A - Senate Web Development Guide.pdf, 'Website Analytics' and 'Social Media Integration' (pp. 7-8)

Please identify the Senate-provided tools, if any, that contractors are expected to use for search engine optimization, analytics support, and accessibility support during ongoing Website Maintenance and End-user Support, or confirm that this information will be provided only after award.

Attachment J-001-A identifies the Adobe Analytics baseline and the approved plugin set, including approved SEO support plugins. Attachment J-002 references the Senate provided accessibility testing tool. Additional implementation details will be provided to the awarded contractor after award.

2026-R-038 (RFP) Web Dev 4.pdf, C.3 (p. 6);

Attachment J-001-A - Senate Web Development Guide.pdf, 'User Data Collection' and 'Capture of External IP Addresses' (pp. 5-6); Attachment J-001-B - Senate Web Design Guide.pdf, 'User Data Collection'

(p. 6)

Please clarify whether any temporary server-side processing, queuing, anti-spam filtering, or transient logging of form submissions is permitted so long as the data is transmitted only to the approved office recipient or CSS and is not stored for user-facing retrieval. If so, please describe any permissible constraints.

Temporary server-side processing, anti-spam filtering, and transient logging of non-PII data are permissible provided that:

(a) the data is transmitted only to the approved Office recipient or CSS;

(b) no user-facing capability is provided to retrieve stored data; and

(c) all such processing complies with Attachment J-005.

Attachment J-001-A - Senate Web Development Guide.pdf, 'Capture of External IP Addresses' (p. 5);

2026-R-038 (RFP) Web Dev 4.pdf, C.3.4.1.2 (p. 9)

Because Attachment J-001-A states that SAA will add the Akamai True-Client IP code to the base WordPress templates, please confirm whether contractors are nevertheless responsible for validating external IP capture on every form and every…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .