Website_and_Digital_Asset_Compliance_(Addendum_#3_Revision).pdf

County of San Mateo

Request for Proposals (RFP) for Website and Digital Asset

Compliance

Human Resources Department

RFP No. 2025-RFP-00532

RFP Contact: Brae Hunter bhunter@smcgov.org

1. Introduction and Schedule

The County of San Mateo (the “County” or “SMC”) covers most of the San Francisco Peninsula. The region covers 744 mi and is home to nearly 800,000 residents and 20 incorporated cities. The County provides for the health and welfare of all people within its borders and serves as the local government for the unincorporated areas. Innovation thrives here in industries including bioscience, computer software, green technology, hospitality, financial management, health care, education and transportation. The

County prides itself on how that prosperity fosters its commitment to protecting and enhancing the health, safety, welfare and natural resources of the community.

1.1. Summary

The County is seeking a qualified vendor to help achieve full Americans with Disabilities Act (ADA) and

Web Content Accessibility Guidelines (WCAG) 2.1 Level AA compliance across our public-facing digital assets, including websites, mobile apps, and eligible documents, to ensure accessibility for all residents, including those with disabilities. The project involves conducting comprehensive audits, remediating accessibility barriers, and establishing sustainable processes for ongoing compliance. This initiative is critical to promoting user friendly digital spaces while meeting federal accessibility requirements.

1.2. Background

As a county committed to bridging the digital divide, this initiative aligns with broader efforts like the

Digital Inclusion Initiative, which has already addressed connectivity gaps for underserved communities.

The challenges include remediating extensive digital assets (websites, apps, and documents), navigating complex federal and state regulations, and fostering a culture of accessibility across all departments. A vendor that can deliver not just compliance but also innovative, user-centered solutions—such as seamless assistive technology integration and proactive accessibility monitoring—will set a new benchmark for public sector accessibility in California.

Five percent (5%) of the total evaluation points awardable will be added to the proposal score for each

Local Business or Local Non-Profit score for evaluation purposes. An additional three percent (3%) preference shall be given to a Local Business or Local Non-profit (for a total of eight percent (8%) of total points awardable) if the proposer is a Small Business or Small Non-Profit, or an additional 5 percent preference (for a total of ten percent (10%) of total points awardable) if the proposer is a Micro Business or Micro Non-Profit.

1.3. Contact Information

Brae Hunter Safety and Ergonomics Manager/ ADA Title II Coordinator Email: bhunter@smcgov.org Phone: (650) 647-9930

Department:

Human Resources Department mailto:bhunter@smcgov.org tel:(650)647-9930

Page 3 of 18 Release date of June 2, 2025

Department Head:

Rocio Kiryczun Director

1.4. Timeline

RFP Released June 2, 2025

Pre-Proposal Meeting (Mandatory) June 12, 2025, 2:00pm

Meeting ID: 273 335 789 823 2

Passcode: mE2ra24F

Deadline for Questions, Comments and

Contract Exceptions

June 18, 2025, 12:00pm

Proposal Due Date and Time July 8, 2025, 5:00pm

Interview July 14, 2025

Teams link TBD

Anticipated Contract Award Date July 21, 2025

2. Scope of Work

2.1. Compliance Audit & Gap Analysis

A. Conduct automated scans of the County’s approximately 50+ websites with 18,000+ webpages, 26,000+ publicly available PDFs, and various mobile applications

B. Manually test with screen readers like JAWS (Job Access with Speech) /NVDA (NonVisual

Desktop Access)

C. Document inventory with priority classification:

1. P1 - critical barriers (e.g. form access)

2. P2 - structural issues (navigation/ headers)

3. P3 - cosmetic fixes (color contrast/ alt text)

Page 4 of 18 Release date of June 2, 2025

D. Create conformance report using World Wide Web Consortium’s template based on WCAG

(Web Content Accessibility Guidelines) 2.1, Level AA principles (Perceivable, Operable, Understandable, Robust), including remediation recommendations

2.2. Document Remediation

A. Determine eligible records for remediation:

1. Forms/ documents actively used to apply for, access, or participate in services, programs, or activities

2. Public-facing websites & web applications

3. Mobile apps for government services

B. Conduct comprehensive remediation of eligible assets with the following output standards:

1. Machine-readable text and tagged headings

2. Alternative text for images and logical reading order

3. Validation reports confirming compliance

4. If Artificial Intelligence is proposed to be used, human validation of the output is required

2.3. Website & App Modifications

A. Technical implementation:

1. Implement Accessible Rich Internet Applications (ARIA) landmarks for screen readers

2. Resolve accessibility violations on all webpages

3. Captioning for publicly available videos

4. Enhancement of form error identification and reporting

a. Clear, descriptive error messages

b. Text-based error identification

c. Inline/ real-time validation

d. ARIA attributes for error indication

e. Multiple cues for errors

f. Error summaries and navigation

g. Error reporting

5. Mobile app touch target adjustments (minimum 44 px)

B. Code Repository Updates:

Page 5 of 18 Release date of June 2, 2025

1. Version-controlled accessibility fixes including:

a. Clear, single purpose commits with descriptive messages

b. Code review and branching

c. Security and access control

2.4. Public Participation & Testing

A. Conduct three (3) community feedback sessions

B. Establish ongoing accessibility feedback mechanism

C. User testing with 15+ participants, prioritizing persons with experience navigating public websites with disabilities, including but not limited to::

1. Visual impairments

2. Motor disabilities

3. Cognitive disabilities

D. User Testing Documentation

1. Screen reader/ assistive tech compatibility logs

2. Task success rates for participants

E. Compile data into feedback report, highlighting recurring usability issues

2.5. Employee Training

A. Provide live and/ or on-demand training for County employees to be able to independently create and maintain accessible digital assets that meet WCAG 2.1, Level AA requirements, with the objectives that County employees will be able to:

1. Understand the legal obligation of County to provide digital accessibility, including WCAG

2.1, Level AA standards

2. Identify common barriers to digital access for people with disabilities

3. Apply WCAG 2.1, Level AA principles (Perceivable, Operable, Understandable, Robust)

4. Develop practical skills using common and County-specific tools (i.e. Microsoft Word, Adobe, Drupal)

5. Use accessibility checkers (common and County-specific)

6. Participate in a culture of ongoing accessibility awareness and continuous improvement

B. Coordinate with the County’s Information Services Department to ensure training is relevant and covers County-specific technology, processes, and tools.

Page 6 of 18 Release date of June 2, 2025

2.6. Project Management

A. Timeline:

1. Phase 1 - Audit (1-3 months)

2. Phase 2 - Remediation (4-6 months)

3. Phase 3 - Validation (1-3 months)

B. Governance:

1. Twice a month emailed status reports briefly explaining tasks completed/ in process/ to do

2. Quarterly ADA Coordinator Committee reviews

3. ADA Coordinator oversight

2.7. Deliverables

A. Compliance Audit & Gap Analysis:

1. Conformance Report (using W3C template) with remediation recommendations

2. Prioritized Asset Inventory

B. Document Remediation:

1. Accessible PDF Library

a. Machine-readable text and tagged headings

b. Alt-text for images and logical reading order

c. Validation reports confirming compliance

C. Website & App Modifications

1. Technical Implementation Deliverables:

a. ARIA landmark integration for screen readers

b. Resolved accessibility violations

c. Captioned/ audio-described videos

d. Enhanced form error identification

e. Mobile app touch targets ≥44px

2. Code Repository Updates:

a. Version-controlled accessibility fixes including:

i. Clear, single purpose commits with descriptive messages

Page 7 of 18 Release date of June 2, 2025

ii. Code review and branching

iii. Security and access control

D. Public Participation & Testing

1. Community Feedback Report: summaries from 3 sessions, highlighting recurring usability issues

2. User Testing Documentation

a. Screen reader/ assistive tech compatibility logs

b. Task success rates for participants

1. Ongoing feedback mechanism: integrated system (e.g. form, email) or reporting accessibility issues

B. Employee Training

1. Training materials

3. Submission Requirements

3.1. Submission Deadline

Proposals must be electronically received by 5:00 pm, on Tuesday, July 8, 2025 via eProcurement system.

Allow sufficient time for the upload to complete by the Due Date and Time. Partial uploads will automatically terminate, and proposals will be rejected. The eProcurement system submission time will be the official submission time. The County will not be responsible for and may not accept proposals that are late due to slow internet connections or for any other failure of the eProcurement system.

NOTE: The County does not maintain the eProcurement system and is not liable for site failures or technical problems. To resolve technical issues, contact OpenGov Technical Support by using the real time chat located in the lower right hand corner of the screen, or via email at procurement-support@opengov.com https://procurement.opengov.com/portal/smcgov

3.2. Pre-submission Registration

Organizations or individuals interested in responding to this solicitation must register online with the

County of San Mateo at:

• https://procurement.opengov.com/portal/smcgov

It is recommended that organizations complete this registration as soon as possible. The County will not be responsible for and may not accept proposals that are late due to a failure to register in the eProcurement system.

mailto:procurement-support@opengov.com mailto:procurement-support@opengov.com https://procurement.opengov.com/portal/smcgov https://procurement.opengov.com/portal/smcgov

Page 8 of 18 Release date of June 2, 2025

3.3. Submission via eProcurement Portal

Required Documents

Please refer to the Technical Proposal section for submittal documents and requirements.

Electronic Submissions

Include the proposer name and the RFP title and number in each filename. Submit proposals via the eProcurement website, allowing sufficient time for the upload to complete by the Due Date and Time. As noted above, the eProcurement portal submission time will be the official submission time, and partial uploads will automatically terminate, and proposals will be rejected. Contact eProcurement Portal with technical questions regarding this site.

Conflicts between Certain Requirements

Prior to the submission deadlines and solely relating to a determination of the timeliness of questions, comments, and proposal submissions, information displayed on the eProcurement portal site will take precedence in the event of a discrepancy between that information and the information within the solicitation documents. For all other discrepancies, the information in the solicitation documents will take precedence.

Format

Documents should be created in the following format:

• Text should be Times New Roman (12-point minimum font size) and unjustified (i.e., with a ragged-right margin)

• Pages should have margins of at least one inch on all sides (excluding headers and footers)

• If the proposal is lengthy, a Table of Contents should be included.

• PDF format is preferred.

Errors in Proposals

The County will not be liable for any errors in proposals. Proposals may be rejected as unresponsive if they are late, incomplete, missing pages or information, or cannot be opened for any reason. The County may waive minor irregularities, but such waiver will not modify any remaining RFP requirements.

4. Minimum Qualifications and Technical Proposal

4.1. Minimum Qualifications

4.1.1. Has Proposer provided similar services for at least a year within the last three years?*

☐ Yes

☐ No

*Response required

4.1.2. Proposer has a minimum of two (2) years of experience within the last five (5) years in providing comparable services for at least one public agency within California?* https://procurement.opengov.com/portal/smcgov/projects/160009/document?section=1456390

Page 9 of 18 Release date of June 2, 2025

☐ Yes

☐ No

*Response required

4.1.3. Please confirm your firm is registered with System for Award Management (SAM)*

SAM.gov

☐ Please confirm

*Response required

4.1.4. What is the registered Business Name and Unique Entity ID (UEI) No.?*

• UEI number can be obtained by registering your business through SAM.GOV

• Should you be in the process of obtaining your UEI number, please enter the digits ‘123’ temporarily for your response below in order to proceed with proposal. This temporary number should be replaced with the correct registration number for submission of the proposal.

*Response required

4.2. Technical Proposal

Proposals should be no more than 30 pages in total.

4.2.1. Introduction and Executive Summary *

Submit a letter of introduction and executive summary of the proposal. The letter must contain:

• Name, title and contact information (email, phone, and address) for representative of proposer that is responsible for communication related to this RFP.

• Name, title, contact information, and signature of person authorized to obligate firm to perform the commitment contained in the proposal.

Submission of the letter will constitute a representation by proposer that it is willing and able to perform the commitments contained in the proposal and has not violated the terms of this RFP.

*Response required

4.2.2. Statement of Minimum Qualifications *

Describe how the proposer meets the minimum qualifications as set forth in Minimum Qualifications of this RFP.

Submission of the Minimum Qualifications checklist is not a substitute for providing a detailed written response.

*Response required

4.2.3. Project Approach *

This section should correlate to the Scope of Work. Proposer should give a short summary describing how it will perform the relevant work https://sam.gov/content/home

Page 10 of 18 Release date of June 2, 2025

*Response required

4.2.4. Scope of Work tasks/milestones *

Describe your proposed approach to specific tasks/milestones

*Response required

4.2.5. Proposed schedule *

Attach proposed schedule referencing ability to complete the project within the County's required time frame

*Response required

4.2.6. Performance Measures

Provide a plan for achieving 95+% compliance with a clear plan for 100% compliance.

4.2.7. Innovations*

Refence any notable innovations or improvements that you expect to provide (with respect to, for example, efficiency, technology, sustainability)

*Response required

4.2.8. Firm Qualifications *

Attach information regarding background and qualifications, including the following:

• A brief description of the proposer.

• A description of not more than three (3) projects similar in size and scope conducted by the proposer, including the client, reference and telephone numbers, primary staff members involved, budget, schedule, and project summary. Descriptions should be limited to one (1) page for each project.

• If subcontractors are anticipated, identify them (if known) and provide information on how they will be used.

*Response required

4.2.9. Team Qualifications *

Provide a chart identifying:

▪ Project team and reporting structure

▪ Lead project manager

▪ Role each person will play in the project

Provide a brief description of the experience and qualifications of the project team members, including short resumes if desired.

Written assurance that the key individuals listed and identified will be performing the work and will not be substituted or reassigned without the County’s prior approval

Page 11 of 18 Release date of June 2, 2025

*Response required

4.2.10. References*

Provide two references, including the name, address, and telephone number of recent clients (preferably other public agencies):

*Response required

4.2.11. Price proposal

If your pricing structure is incompatible with the pricing table provided, please upload pricing information here.

5. Pricing Proposal

Line Item Description Unit of Measure Unit Cost

1 Compliance audit/ gap analysis Per site/ app

2 Document remediation Per document or page

3 Website and app modifications Per site/ app

4 User testing and feedback Per community feedback session

5 Training Per session

6. Evaluation and Selection Criteria

The proposals will be evaluated by a selection committee with relevant expertise. The County intends to evaluate the proposals generally in accordance with the criteria itemized below. Proposers with the highest scoring proposals may be interviewed by the committee to make the final selection.

6.1. Phase 1

No. Evaluation Criteria Scoring Method Weight (Points)

1. Firm Qualifications

Relevant certifications, experience of entire firm (e.g. previous Accessibility Conformance

Reports, training policies and practices, references)

Points Based 20 (20% of Total)

Page 12 of 18 Release date of June 2, 2025

2. Team Qualifications

Individual certifications (e.g. International

Association of Accessibility Professionals

(IAAP) Accessible Document Specialist, IAAP

Web Accessibility Specialist, IAAP Certified

Professional in Web Accessibility), previous project experience, Points Based 15 (15% of Total)

3. Project Approach/ Scope Tasks &

Milestones Points Based 20

(20% of Total)

4. Proposed Schedule

How quickly can the firm bring the County into compliance?

Points Based 15 (15% of Total)

5. Innovations Points Based 10 (10% of Total)

6. Price Points Based 20 (20% of Total)

6.2. Phase 2

No. Evaluation Criteria Scoring Method Weight (Points)

1. Local Business

Five percent (5%) of the total evaluation points awardable will be added to the proposal score for each Local Business or Local Non-Profit score for evaluation purposes. An additional three percent (3%) preference shall be given to a Local Business or Local Non-profit (for a total of eight percent (8%) of total points awardable) if the proposer is a Small Business or Small Non-Profit, or an additional 5 percent preference (for a total of ten percent (10%) of total points awardable) if the proposer is a

Micro Business or Micro Non-Profit.

Points Based 10 (100% of Total)

6.3. Phase 3

No. Evaluation Criteria Scoring Method Weight (Points)

1. Interview Points Based 10 (100% of Total)

7. Instructions to Proposers

Page 13 of 18 Release date of June 2, 2025

7.1. Instructions

Proposers are encouraged to attend a pre-proposal conference on Thursday, June 12, 2025, at 2:00 pm, to be held at Meeting ID: 273 335 789 823 2 Passcode: mE2ra24F. All questions will be addressed at this conference and any available new information will be provided at that time. If you have further questions regarding the RFP, please post them on the eProcurement portal.

7.2. Communications

A. As of the issuance date of this RFP and continuing until it is canceled or an award is made, no proposer or person acting on behalf of a prospective proposer may discuss any matter relating to the RFP with any officer, agent, or employee of the County, other than through eProcurement portal, to the Authorized Contact Person, or as outlined in the evaluation or protest procedures.

B. Proposers (including any agent, owner, employee, board members, or other such affiliates) shall not offer any gift, favor, or other personal benefit to any County officer or employee during the procurement process for this agreement, including during the solicitation period and contract negotiations.

Violation of the foregoing prohibitions may result in a proposer being found non-responsible and barred from participating in this or future procurements.

7.3. Contract Award

A. Award Procedure

Contract negotiations are neither an offer nor guarantee that a contract will be executed. A contract award, if any is made, will be to the responsive, responsible proposer offering the overall best value to the County for the services and goods described in this solicitation, or as applicable, for a specific portion of the services and goods described. Any agreement reached will be memorialized in a formal agreement using the attached template, executed by the appropriate authority.

B. Notice of Intent to Award

If a decision is made to take steps to enter into an agreement with one or more proposers, the

County will post a Notice of Intent to Award or otherwise notify proposers the remaining proposers of their non-selection. Notice may instead be provided by including approval of the agreement as an item on an agenda for a meeting of the Board of Supervisors.

C. Commencement of Performance

After all parties have signed the agreement, the County will notify the contractor and performance may proceed. Prior to execution of the agreement by the County, no County employee may authorize work under the agreement. Any work performed prior to the full execution of the Agreement may not be compensated.

7.4. Term

Human Resources Departmentis issuing Request for Proposal (RFP) No. 2025-RFP-00532 for Website and Digital Asset Compliance.

Page 14 of 18 Release date of June 2, 2025

The agreement shall have a term of two (2) years. In addition, the County shall have one (1) option to extend the term for an additional period not to exceed two years, which the County may exercise in its sole, absolute discretion. To exercise this option, the County shall provide written notice to the Contractor at least thirty days before the end of the agreement’s term.

The County’s standard contract template has been included with this solicitation. The awarded contractor will be expected to sign an agreement prepared by the County using this template. Please ensure that your firm has completed legal review of these contract terms. If your firm wishes to request exceptions to these standard terms, submit a Contract Exceptions Request by the Deadline for Questions, Comments and

Contract Exceptions listed in the Solicitation Schedule below. The County will consider Contract

Exceptions Requests but reserves the right to reject requested modifications to its standard terms.

8. Terms and Conditions for Receipt of Proposals

8.1. Errors, Omissions and Inquiries regarding the RFP

Proposers are responsible for reviewing all portions of this RFP. Proposers are to notify the department, in eProcurement portal, if the proposer discovers any ambiguity, discrepancy, omission, or apparent error in the RFP. Such notification should be made promptly after discovery, but in no event later than five business days prior to the deadline for receipt of proposals. Modifications and clarifications will be made by addenda as provided below.

Inquiries regarding the RFP should be lodged in eProcurement portal.

8.2. Objections to RFP Terms

Should a proposer object on any ground to any provision or legal requirement set forth in this RFP, the proposer must, not more than ten calendar days after the RFP is issued, provide written notice to the department, via eProcurement portal, setting forth with specific grounds for the objection.

8.3. Addenda

The County may cancel, revise, or reissue this RFP, in whole or in part, for any reason. Revisions will be posted as Addenda on eProcurement portal. No other revision of this RFP is valid. Proposers shall be responsible for ensuring that their proposals reflects any and all Addenda issued by the County prior to the proposal due date regardless of when a proposal is submitted. Therefore, the County recommends that proposers consult eProcurement portal frequently, including shortly before the proposal due date, to confirm that all Addenda have been downloaded.

8.4. Term of Proposal

Submission of a proposal signifies that the proposed services and prices are valid for the duration of the proposed agreement term and that the quoted prices are genuine and not the result of collusion or any other anti-competitive activity.

8.5. Revision or Withdrawal of Proposal

A proposer may revise a proposal on the proposer’s own initiative at any time before the deadline for submission of proposals. The proposer must submit the revised proposal in the same manner as the original on or before the proposal due date.

Page 15 of 18 Release date of June 2, 2025

A proposer may withdraw a proposal at any time before the deadline for submission of proposals. After that time, whether or not a new RFP is issued for the same subject matter, withdrawal of a proposal may preclude the proposer from participating in the procurement as a proposer or subcontractor, except that an original equipment manufacturer may participate indirectly through a reseller.

8.6. Errors and Omissions in Proposal

The County will not be liable for any errors in proposals. Proposals may be rejected as unresponsive if they are incomplete, are missing pages or information, or cannot be opened for any reason. The County may waive minor irregularities, but such waiver will not modify any of the remaining RFP requirements.

8.7. No Commitment

Neither submission of a proposal nor the County’s receipt of proposal materials confers any right to the proposer nor any obligation on the County. This RFP does not commit the County to award a contract.

8.8. Financial Responsibility

The County shall have no financial responsibility for any costs incurred by a firm in responding to this

RFP or participating in any presentations or negotiations.

8.9. Estimated Quantity

If the RFP results in an indefinite quantity or a requirements agreement, the goods and services actually requested by the County may be less than the maximum value of the agreement and there is no guarantee, either expressed or implied, as to the actual quantity of goods and services that will be authorized under the agreement.

8.10. Public Record

A. General

1. All proposals, protests, and information submitted in response to this solicitation will become the property of the County and will be considered public records. As such, they may be subject to public review.

2. Any contract arising from this RFP will be a public record.

3. The County is not seeking proprietary information and will not assert any privileges that may exist on behalf of the proposer.

4. Submission of any materials in response to this RFP constitutes:

▪ Consent to the County’s release of such materials under the Public Records Act without notice to the person or entity submitting the materials; and

▪ Waiver of all claims against the County and/or its officers, agents, or employees that the

County has violated a proposer's right to privacy, disclosed trade secrets, or caused any damage by allowing the proposal or materials to be inspected; and

▪ Agreement to indemnify and hold harmless the County for release of such information under the Public Records Act; and

Page 16 of 18 Release date of June 2, 2025

▪ Acknowledgement that the County will not assert any privileges that may exist on behalf of the person or entity submitting the materials.

8.11. Confidential Information

A. Proposers are responsible for asserting any applicable privileges or reasons why a document should not be produced in response to a public record request.

B. If submitting information protected from disclosure as a trade secret or any other basis, identify each page of such material subject to protection as “CONFIDENTIAL.” If requested material has been designated as confidential, the County will attempt to inform the proposer of the public records request in a timely manner to permit assertion of any applicable privileges.

C. Failure to seek a court order protecting information from disclosure within ten days of the

County’s notice of a request to the proposer will be deemed agreement to disclosure of the information and the proposer agrees to indemnify and hold the County harmless for release of such information.

D. Requests to treat an entire proposal as confidential will be rejected and deemed agreement to

County disclosure of the entire proposal and the proposer agrees to indemnify and hold the

County harmless for release of any information requested.

E. Trade secrets will only be considered confidential if claimed to be a trade secret when submitted to the County, marked as confidential, and compliant with Government Code Section 6254.7.

8.12. Reservations of Rights by the County

The issuance of this RFP does not constitute an agreement by the County that any contract will actually be entered into by the County. The County expressly reserves the right at any time to:

• Waive or correct any defect or informality in any response, proposal, or proposal procedure;

• Reject any or all proposals;

• Reissue an RFP;

• Prior to submission deadline for proposals, modify all or any portion of the selection procedures, including deadlines for accepting responses, the specifications or requirements for any materials, equipment or services to be provided under this RFP, or the requirements for contents or format of the proposals;

• Procure any materials, equipment or services specified in this RFP by any other means; or

• Determine that no project will be pursued.

8.13. No Waiver

No waiver by the County of any provision of this RFP shall be implied from any failure by the County to recognize or take action on account of any failure by a proposer to observe any provision of this RFP.

Page 17 of 18 Release date of June 2, 2025

8.14. Cooperative Agreement (Piggyback)

This competitive solicitation is being conducted as a Cooperative Procurement. The services, terms and conditions of any agreement resulting from this solicitation may be used by other organizations as a

Cooperative Agreement.

This provision in no way commits any affiliate to procure services from any awarded contractor, nor does it guarantee that any additional orders will result. At their discretion, and subject to their own procurement policies, interested organizations may make use of this competitive procurement and contract directly from the awarded contractor.

9. Protest Procedures

9.1. Protest of Non-Responsiveness Determination

Within five (5) working days of the County's issuance of a notice of non-responsiveness, any firm that has submitted a proposal and believes that the County has incorrectly determined that its proposal is non-responsive may submit a written notice of protest. Such notice of protest must be received by the County on or before the fifth working day following the County's issuance of the notice of non-responsiveness. The notice of protest must include a written statement specifying in detail each and every one of the grounds asserted for the protest. The protest must be signed by an individual authorized to represent the proposer, and must cite the law, rule, local ordinance, procedure or RFP provision on which the protest is based. In addition, the protestor must specify facts and evidence sufficient for the County to determine the validity of the protest.

9.2. Protest of Contract Award

Within five (5) working days of the County's issuance of a notice of intent to award the contract, any firm that has submitted a responsive proposal and believes that the County has incorrectly selected another proposer for award may submit a written notice of protest. Such notice of protest must be received by the

County on or before the fifth working day after the County's issuance of the notice of intent to award.

The notice of protest must include a written statement specifying in detail each and every one of the grounds asserted for the protest. The protest must be signed by an individual authorized to represent the proposer, and must cite the law, rule, local ordinance, procedure or RFP provision on which the protest is based. In addition, the protestor must specify facts and evidence sufficient for the County to determine the validity of the protest.

9.3. Delivery of Protests

All protests must be received by the due date. If a protest is mailed, the protestor bears the risk of non-delivery within the deadlines specified herein. Protests should be transmitted by a means that will objectively establish the date the County received the protest. Protests or notice of protests made orally

(e.g., by telephone) will not be considered. Protests must be delivered to:

Protests@smcgov.org

Subject: Website and Digital Asset Compliance, 2025-RFP-00532

Page 18 of 18 Release date of June 2, 2025