10-RFP 25-68 - HCM Platform and Implentation Svcs SOW (Final).pdf

Montgomery County, PA Office of Information Technology Solutions

Request for Proposal (RFP): 25-68 Human Capital Management (HCM) Platform & Implementation Services

RFP Title: HCM Platform & Implementation Services RFP Number: 25-68 Issue Date: February 6, 2026 Response Due Date: March 13, 2026 10:00 AM EST

1. Introduction & Background Montgomery County, Pennsylvania, is one of the Commonwealth’s largest and most dynamic counties, serving a diverse population across urban, suburban, and rural communities. As a government entity, Montgomery County is committed to delivering high-quality public services, fostering innovation, and maintaining operational excellence across all departments.

With a workforce of approximately 3,000 employees across a diverse set of functions including public safety, courts and criminal justice, health and human services, corrections, election services and assets and infrastructure, as well as many others, County operations are located across multiple locations throughout Montgomery County. The County’s workforce includes both unionized and non-union employees, governed by six collective bargaining agreements, reflecting the complexity and diversity of its human resources landscape.

Montgomery County’s Human Resources operations are currently supported by a mix of legacy systems, including NeoGov, TBX Employee Benefits, Microsoft Dynamics, SAP Concur, and ADP. These systems, while functional, present challenges in terms of data fragmentation, process inefficiencies, and limited analytics capabilities. The County’s IT environment leverages modern platforms such as Azure AD/Entra ID for identity management, single sign-on (SSO) via SAML/OIDC, Microsoft 365 for productivity, and Infor ERP/Finance for financial operations.

RFP for Human Capital Management Platform & Implementation Services

Recognizing the need for modernization, Montgomery County is seeking proposals for a comprehensive Human Capital Management (HCM) platform and implementation services.

The primary drivers for this initiative include:

• Consolidation of disparate HR systems into a unified platform

• Centralization and improvement of HR master data quality and reporting

• Automation of end-to-end HR processes, from hire to retire

• Enhanced compliance with payroll, tax, ACA, EEO-4, FLSA, FMLA, privacy, and accessibility regulations

• Delivery of robust analytics and self-service capabilities for employees and managers

• Implementation of a secure, scalable, and configurable SaaS solution with a proven track record

The County’s objectives for this project are to replace and consolidate legacy HR systems, centralize HR master data, automate HR processes, ensure regulatory compliance, provide advanced analytics and self-service tools. The selected HCM solution must support a wide range of HR functions, integrate seamlessly with existing IT infrastructure, and deliver a superior user experience for all stakeholders.

The target go-live date for the new HCM platform is Q1 2027 with a budget up to $4.46M over Fiscal Years 2026 and 2027 for software purchase and implementation. This initiative represents a strategic investment in the County’s future, aimed at optimizing costs, improving service delivery, and empowering the workforce through technology.

Montgomery County invites qualified vendors to submit proposals that address the County’s requirements, demonstrate relevant experience, and outline a clear and effective implementation approach. The County is committed to a transparent and collaborative selection process, ensuring the chosen solution aligns with its operational needs and long-term vision.

2. Scope of Work Montgomery County, Pennsylvania seeks a comprehensive Human Capital Management (HCM) solution that will modernize and streamline its HR operations. The selected platform must deliver robust functionality across a wide range of HR domains, supporting both current and future needs of the County’s workforce and administrative teams.

The scope of work for this RFP encompasses the following modules and capabilities, each of which is considered essential to the County’s HR transformation initiative:

2.1. In-Scope Modules

• Core HR: Management of employee master data, organizational structure, and position control.

• Payroll: Support for U.S. multi-state payroll processing and integration with global payroll connectors.

• Time & Attendance: Tools for scheduling, leave management, overtime rules, and integration with time clocks.

• Benefits Administration: Open enrollment, life event processing, EDI 834 transactions, and carrier connectivity.

• Talent Acquisition / ATS: End-to-end recruiting, job posting, and enhanced candidate experience.

• Onboarding & Offboarding: Compliance with I-9 and E-Verify, and automated provisioning workflows.

• Performance Management: Goal setting, performance reviews, and 360-degree feedback.

• Compensation: Merit, bonus, and equity management, including compensation planning.

• Learning: Learning management system (LMS) capabilities or integration with existing LMS platforms.

• Talent/Succession & Workforce Planning: Strategic workforce planning and succession management.

• Employee & Manager Self-Service: Mobile-first self-service tools for employees and managers.

• HR Case & Knowledge Management: Centralized case tracking and knowledge base functionality.

• Reporting, Dashboards & Advanced Analytics: Comprehensive reporting and analytics for HR data.

• Compliance & Audit: Support for regulatory requirements including EEO-4, ACA 1095-C, W-2/941, and COBRA.

• Identity/Access: Single sign-on (SSO), role-based access controls, and SCIM provisioning.

• Integrations: Seamless integration with ERP/Finance systems, AD/Entra ID, background check providers, tax filing, and benefits carriers.

• Data Migration: Migration of HR master data, historical payroll records, and accrual balances.

• Change Management & Training: Structured change management and training programs for stakeholders.

• Post-go-live Hypercare & Support: Dedicated support following implementation to ensure a smooth transition.

2.2. Minimum Qualifications

To be considered for award, vendors must meet the following minimum qualifications:

• Demonstrated experience implementing HCM solutions for organizations of a similar scope and size as Montgomery County, PA, preferably in the public sector.

• Proven track record of successful HCM deployments including core HR, payroll, time and attendance, benefits, and talent management modules.

• Ability to provide references from at least three (3) similar clients.

• Financial stability and organizational capacity to support a project of this scale.

• Certified implementation team with experience in government or regulated environments.

• Compliance with relevant security, privacy, and accessibility standards (e.g., SOC 2

Type II, ISO 27001, WCAG 2.2 ).

• Demonstrated ability to meet the County’s timeline and resource commitments.

3. Vendor Instructions To facilitate a fair and thorough evaluation process, vendors are required to adhere to the following instructions and timelines:

3.1. Key Dates

• RFP Release: February 6, 2026

• Vendor Q&A Deadline: February 20, 2026

• Answers Published: February 27, 2026

• Proposal Submission Deadline: March 13, 2026 10:00 AM EST

• Finalists Notified: March 27, 2026

• Demos & Deep Dives: March 30, 2026 – April 3, 2026

• Selection & Notice of Award: April 9, 2026

3.2. Submission Requirements

• Proposals must be submitted via the County’s Bonfire (Euna) system at:

Montgomery County PA

• Each submission should include a single PDF document, along with native Excel files for pricing and requirements matrices.

• Proposals must remain valid for a minimum of 180 days from the submission deadline.

https://montcopa.bonfirehub.com/portal/?tab=openOpportunities

• Vendors should clearly mark any proprietary content and refrain from including third-party confidential information without explicit permission.

3.3. References

Vendors must provide references from at least three (3) organization of similar size and complexity, preferably public sector or government entities, where the proposed HCM solution has been successfully implemented within the past five years. References may be contacted as part of the evaluation process. Each reference should include:

o Organization Name o Contact Person (name, title, email, phone) o Project scope and modules implemented o Go-live date

3.4. Cost Proposal

Vendors must submit a comprehensive cost proposal using Appendix B – Pricing Workbook that clearly details all anticipated costs associated with the proposed HCM solution and its implementation. The cost proposal must be structured as follows:

1. Summary Table

• Provide a summary table outlined total costs by major category (e.g., software licensing, implementation services, training, on-going support and maintenance, etc.)

2. Detailed Breakdown

• Software Licensing o Per Employee Per Month (PEPM) or tiered pricing o Separate pricing for regular and contingent workers o Any volume discounts or tiering rules o Additional modules (e.g., time-keeping, payroll) priced separately.

• Implementation Services o Project Management o Configuration and setup o Data migration (including mock conversions and reconciliation) o Integration with existing systems o Testing (unit, SIT, UAT) o Change Management and training o Go-Lieve and hypercare support

• Annual Maintenance & Support o Standard support o Premium support options o Named technical account manager (if applicable)

• Other Costs o Travel (the County anticipates that periodic travel by the selected vendor may be necessary; however, we expect that most of the engagement can be done virtually) o Additional storage o Optional modules or services o Termination assistance (data export, transition services)

• Cost Proposal Variants o Vendors must provide two cost proposals:

1. Including time-keeping and payroll modules

2. Excluding time-keeping and payroll modules

3. Payment Schedule o Outline proposed payment milestones (e.g., % on contract signing, configuration completion, go-live, post-go-live support).

4. Assumptions & Exclusions

• Clearly state any assumptions, exclusions, or dependencies that may impact pricing.

3.5. Questions

• All vendor questions must be submitted through the Bonfire (Euna) portal at:

Montgomery County PA by February 20, 2026.

4. Proposal Format To ensure consistency and facilitate a fair evaluation, all proposals must follow the format below. Each section should be clearly labeled and adhere to the specified page limits.

1. Executive Summary (2 pages max)

• Provide a concise overview of the proposed solution, highlighting key features, benefits, and alignment with Montgomery County’s objectives.

2. Company Overview

• Include company history, ownership structure, size, financial stability (recent financial statement or summary), and notable partnerships relevant to public sector HCM projects.

3. Solution Overview

• Describe the proposed HCM platform, including system architecture, data model, supported environments (production, test, etc.), and mobile capabilities.

4. Functional Capabilities Matrix

• Complete Appendix A, indicating how each requirement will be met (out-of-box, configuration, extension, third-party, or not available).

https://montcopa.bonfirehub.com/portal/?tab=openOpportunities

5. Technical & Integration Approach

• Detail integration strategy with County’s existing systems (ERP, AD/Entra ID, etc.), including APIs, middleware, SSO, and SCIM support.

6. Security, Privacy & Compliance

• Complete Appendix C and provide a summary of security controls, certifications (SOC 2, ISO 27001, etc.), privacy practices, and accessibility compliance.

7. Implementation & Project Plan

• Outline the proposed implementation methodology, project governance, roles and responsibilities, timeline, milestones, and risk management approach.

8. Change Management & Training

• Describe the approach to stakeholder engagement, communications, training programs, and strategies for user adoption.

9. Support & SLA

• Explain the support model, hours of coverage, escalation process, and service level commitments post-implementation.

10. Accessibility (WCAG 2.2) & UX

• Summarize accessibility features, compliance with WCAG 2.2, and user experience design principles.

11. References

• See Section 3.3 for more information.

12. Pricing

• Complete Appendix B – Pricing Workbook

13. Contractual Terms & Exceptions

• Identify any exceptions or redlines to the County’s standard contract template, with rationale for each.

14. Demo Readiness

• Complete Appendix D scenarios

5. Functional Requirements (Summary) Vendors must complete the Appendix A - Functional Requirements Matrix indicating Availability and Approach:

• OOB (Out-of-Box)

• Config (configuration only)

• Ext (extension/customization)

• 3rd (third-party)

• N/A (not available)

Priority: Must / Should / Nice-to-Have Comments: Limits, dependencies, roadmap (with ETA), or assumptions.

ID Area Requirement Priority

HR-01 Core HR Position management with budgeting and FTE control Must

HR-12 Self-Service Mobile ESS/MSS for profile, pay, leave, approvals Manager side with delegation capability

Must

PAY-

Payroll

Multi-state taxes, garnishments, year-end (W2/941)-;

ability to display PTO Accruals and balances on biweekly paystubs; Dual PTO tracking- both in payroll and TLM system

Must

TNA-

Time

Complex overtime & shift differentials; meal penalties;

ability to generate a year end payroll register;

Effectively handle 24/7 scheduling and time management on a rotation basis.

Must

BEN-

Benefits EDI 834 to carriers; life event automation Must

TA-05 Recruiting Structured requisitions, approvals, assessments Must

ONB-

Onboarding I-9 Section 1/2, E-Verify integration Must

PER-

Performance Cascading goals; calibration; 9-box Must

CMP-

Compensation Merit/bonus planning with budget guardrails Must

RPT-

Reporting Prebuilt & ad-hoc reports; scheduler; data export Must

CMP-

Compliance EEO-1, VETS-4212, ACA 1095-C generation Must

INT-

Integrations REST APIs; webhooks; flat-file SFTP; SCIM Must

SEC-

Security RBAC, attribute-based access; SSO (SAML/OIDC) Must

ACC-

Accessibility WCAG 2.2 compliance and VPAT Must

6. Technical, Hosting & Integrations

6.1. Vendor Validation and Disclosure Requirements

Vendors must attest that all technical, hosting, integration, and data migration capabilities described in this section are available as proposed at the time of submission. Any dependencies on third‑party solutions, configuration assumptions, or limitations must be clearly disclosed in the proposal and in Appendix A – Functional Capabilities Matrix.

The County reserves the right to validate these capabilities through written proposals, scripted demonstrations, deep‑dive workshops, reference checks, and implementation planning activities. Failure to accurately represent technical or integration capabilities may result in disqualification or removal from further consideration.

6.2. Architecture & Environments

• SaaS: environments for Prod and Test

• Uptime SLA: ≥ 99.9% monthly

• RTO/RPO targets: RTO 8 hours / RPO 1 hour

• Data residency options: US Host only

6.3. Identity & Access

• SSO: SAML 2.0 / OIDC

• Provisioning/Deprovisioning: SCIM 2.0

• Fine-grained RBAC/ABAC; audit trails

6.4. Integrations (typical)

• Identity: Azure AD/Entra ID / Active Directory

• Finance/ERP: Microsoft Dynamics /INFOR/SAP

• Time Clocks: Minimum of 5 with possibility of expanding. Biometric preferred.

• Benefits: EDI 834 (medical, dental, vision, life), COBRA, HSA/FSA

• Tax Filing & Payments (U.S. federal, state, local)

• Background Check: [Sterling, Checkr, First Advantage]

• LMS / Content Providers: [Cornerstone, LinkedIn Learning, etc.]

• Document Management: DocuSign, Adobe Sign, M365

• Analytics: OData/ODBC, data warehouse export (daily incremental + full)

6.5. Data Migration

• In-scope datasets: employees, dependents, jobs/positions, orgs, accrual balances, pay history (13+ years ), performance history, benefits elections

• Vendor to provide data mapping templates, validation rules, mock conversion cycles (≥2), and reconciliation reports

7. Security, Privacy & Compliance

7.1. Vendor Attestation and Evidence Requirements

Vendors must formally attest that the proposed solution complies with all security, privacy, data protection, audit, and accessibility requirements described in this section. Compliance must be demonstrated through completion of Appendix C – Security & Compliance Questionnaire, including submission of all required supporting documentation (e.g., SOC reports, policy summaries, and VPATs).

Failure to attest to or substantiate any requirement in this section may result in disqualification or reduced evaluation scores at the County’s discretion. The County reserves the right to request additional clarification or documentation during evaluation, demonstrations, or contract negotiations.

7.2. Certifications & Controls

• SOC 2 Type II (last 12 months) & SOC 1 Type II for payroll-impacting controls

• ISO/IEC 27001 (preferred)

• Regular third-party penetration testing; summarized remediation reports

• Vulnerability management (SLAs by severity)

7.3. Privacy & Legal

• Data Processing Addendum (DPA) with subprocessor listing & change controls

• Breach notification ≤ 12 hours after discovery

• Support for GDPR/CCPA data rights (access, correction, deletion) where applicable

• PII handling & Data ownership: Data Sharing Agreement

• Data ownership: customer retains ownership; vendor provides complete export at termination (no fee beyond reasonable services)

7.4. Accessibility

• WCAG 2.2 conformance; provide current VPAT

7.5. Audit & Logging

• Immutable audit logs for admin actions and sensitive updates

• Export capability for audit and eDiscovery

8. Implementation & Change Management

8.1. Approach & Deliverables

Vendors must provide a comprehensive implementation plan that demonstrates a proven methodology for deploying the HCM, Payroll, and Time Labor management solution in a government environment. The plan should address the following key deliverables and activities:

• Project Governance:

o Outline the project management structure, including PMO cadence, reporting intervals, and escalation procedures.

o Define roles and responsibilities using a RACI (Responsible, Accountable, Consulted, Informed) matrix to ensure clarity and accountability throughout the project lifecycle.

• Requirements & Design Workshops:

o Conduct collaborative workshops with County stakeholders to validate requirements, gather input, and finalize system design.

o Develop configuration workbooks to document business processes, data mappings, and system settings.

• Iterative Builds & Conference Room Pilots (CRP):

o Employ an iterative approach to system configuration, allowing for regular feedback and adjustments.

o Facilitate Conference Room Pilots to demonstrate system functionality, validate workflows, and ensure alignment with County needs.

• Testing:

o Execute a comprehensive testing strategy, including unit testing, system integration testing (SIT), and user acceptance testing (UAT).

o Provide test scripts and scenarios to guide County participants and ensure thorough validation of all modules.

• Cutover Planning:

o Develop a detailed cutover plan outlining key activities, timelines, and go/no-go criteria for system launch.

o Address data migration, user provisioning, and contingency procedures to minimize risk during transition.

• Hypercare Support:

o Deliver post-go-live support for a minimum of 60–90 days, including rapid issue resolution, system monitoring, and user assistance.

o Define exit criteria for hypercare and transition to steady-state support.

• Knowledge Transfer & Role-Based Training:

o Provide comprehensive training programs tailored to HR, Payroll, Managers, and Employees.

o Ensure knowledge transfer to County staff, including system administration, troubleshooting, and ongoing maintenance.

• Change Management Plan:

o Present a robust change management strategy, including stakeholder engagement, communications planning, training materials, and a change impact matrix.

o Address strategies for user adoption, resistance management, and ongoing support.

8.2. Timeline

• Vendors must submit a detailed project timeline using MS Project or Gantt chart format, highlighting critical path activities and major milestones.

• Clearly state all assumptions, including required County resource commitments and decision timelines.

8.3. Risk & Issues Management

• Selected vendor must maintain a RAID (Risks, Assumptions, Issues, Dependencies) log throughout the project.

• Vendor must submit with their proposal the top five project risks and provide mitigation strategies for each.

9. Support & Service Levels Vendors must describe their support model and service level commitments for the HCM solution, both during implementation and post-go-live. The support plan must include:

• Support Hours:

o Specify standard support hours (e.g., 8×5 local time) and availability of 24×7 support for Priority 1 and Priority 2 issues with response/resolution targets by severity in accordance with County requirements.

• Response & Resolution SLAs:

o Define response and resolution timeframes by severity level (P1–P4), including escalation procedures and communication protocols. County will require an uptime SLA of ≥ 99.9% monthly with service credits provided upon miss.

• Release Cadence:

o Outline the schedule for major and minor system releases, including advance notice to the County and access to a sandbox or preview environment for testing new features. The County shall require advance notice of such releases along with preview and sandbox access.

• Named Customer Success Manager (CSM) / Technical Account Manager(TAM):

o Assign a dedicated CSM or Technical Account Manager to serve as the primary point of contact for the County, ensuring proactive support and issue resolution. The County shall require a named CSM or TAM as part of the contract.

• Case Portal & Knowledge Base:

o Provide access to an online case management portal for submitting, tracking, and managing support requests.

o Include a searchable knowledge base with documentation, FAQs, and troubleshooting guides.

10. Evaluation Criteria & Scoring

10.1. Overview

All proposals received by the specified date shall be subject to evaluation by a review committee. This is a "Best Value" solicitation. Montgomery County may award a contract or multiple contracts to those responsible offerors who can accomplish the requirements set forth in the RFP in a manner most advantageous to the County considering price and all non-price factors described herein. Montgomery County will select the offer(s) that represent the best value to the County based on a comparative analysis and an integrated assessment of proposals against all source selection criteria in this solicitation. If deemed necessary by a department or departments, in writing with clear justification for the need, Montgomery County may award a contract or multiple contracts to a proposal other than the highest technically rated proposal or a proposal other than the lowest priced proposal in keeping with the below scoring method.

The County will use a muti-phase down-selection process to identify the proposal representing best overall value. Participation in later phases requires selection to advance.

10.2. Selection Criteria

Category Weight

Functional Fit 30%

Implementation Approach & References 20%

Total Cost of Ownership 20%

Security, Privacy, Compliance 15%

Integration & Technical Fit 10%

UX/Accessibility & Mobile 5%

10.3. Cost Normalization (TCO)

Cost will be evaluated using Appendix B to calculate a 5-year total cost of ownership (TCO).

To enable apples-to-apples comparison, the County will:

• Use a baseline of 3,000 active employees for PEPM calculations unless otherwise stated.

• Evaluate two scenarios request in the RFP: (a) including Time & Payroll; (b) excluding Time & Payroll.

• Apply the vendor-proposed annual escalator, subject to County caps in Commercial Terms.

• Include required implementation, support, options the County deems “in scope”, and any one-time fees.

10.4. Down-Selection Phases

Vendors may be down-selected after each phase, and only those selected will proceed to the next phase. Advancement is at the sole discretion of the evaluation committee.

1. Written proposal review

2. Scripted demonstrations and deep-dive workshops

3. Reference checks

4. Best and Final Offer (BAFO)

11. Demonstrations & Workshops

11.1. Scripted Demos

Vendors must execute County-provided scenarios in Appendix D using County test data. Ephasis end-to-end flows, usability (clicks-to-complete), auditability, exception handling, and accessibility.

11.2. Environment & Data

Vendors provide a cloud demo environment with SSO configured (mock SAML/OIDC acceptable) and pre-loaded test data. No production data may be used.

11.3. Evaluation Rubric

Evaluators will use the scoring rubric included in Appendix D.

12. Commercial Terms (Summary)

12.1. Price Protections

• Price hold: ≥ 36 months from effective date.

• Annual increases: Lesser of 3% or CPI-U.

• Unit of measure: PEPM and/or tiered; separate rate class for contingent workers where applicable.

• Implementation: Fixed-fee by milestone; T&M only for approved change requests.

• Travel: Pre-approved, at cost, remote-first expected.

• Termination assistance: Complete data export (full schema + documentation) and optional transition services at standard rates.

• IP & customizations: County owns artifacts paid for; vendor retains platform

IP.

• Insurance: General Liability, Tech E&O/Professional Liability, Cyber Liability

(minimum limits in Appendix C for attestation).

12.2. Service Levels & Credits (applicable post go-live)

Support services, SLAs, uptime commitments, and service credits are defined in Section 9 – Support & Service Levels.

13. Acceptance Criteria The acceptance criteria outlined below are intended to govern the County’s acceptance of implementation deliverables, system readiness, and transition to steady‑state operations. These criteria as well as an other negotiated between the County and the selected vendor and incorporated into the executed contract, will be used to validate successful delivery prior to milestone payments and final acceptance.

• All Must requirements delivered OOB/Config unless otherwise approved.

• Integrations validated; data reconciled within thresholds.

• Parallel payroll accuracy ≥ 99.5% (if in scope).

• Accessibility conformance (VPAT).

• Security/privacy artifacts delivered; DPA executed.

• Training and knowledge transfer complete; hypercare exit achieved.

14. Appendices

14.1. Appendix A: Functional Capabilities Matrix

14.2. Appendix B: Pricing Workbook

14.3. Appendix C: Security & Compliance Questionnaire

14.4. Appendix D: Scripted Demo Scenarios

14.5. Appendix E: Statements and Certifications Forms

15. Submission Checklist (Vendor) Vendors are responsible for ensuring that all required materials are submitted by the proposal deadline. Failure to submit required items may result in disqualification or reduced evaluation scores. All submissions must be made through the County’s Bonfire (Euna) portal as described in Section 3.

☐ Executive Summary Concise overview of the proposed solution and alignment with County objectives.

☐ Company Overview Company background, ownership, size, financial stability, and relevant public-sector experience.

☐ Solution Overview Description of the proposed HCM platform, modules, architecture, environments, and mobile capabilities.

☐ Completed Appendix A – Functional Capabilities Matrix (Excel) All requirements completed using the required response options (OOB / Config / Ext / 3rd / N/A), with comments where applicable.

☐ Technical & Integration Approach Integration strategy with County systems (e.g., ERP/Finance, AD/Entra ID), APIs, SSO, and data exchange methods.

☐ Security, Privacy & Accessibility Response Completed Appendix C – Security & Compliance Questionnaire (Excel), including all required attestations and supporting artifacts (e.g., SOC reports, VPAT).

☐ Implementation & Project Plan Implementation methodology, governance, roles, timeline, milestones, risk management, and assumptions.

☐ Change Management & Training Approach Stakeholder engagement, communications, training strategy, and user adoption approach.

☐ Support Model & Service Levels Post-go-live support structure, hours, escalation, SLAs, and release management.

☐ Accessibility (WCAG 2.2) & User Experience Summary Description of accessibility features and user experience principles (with VPAT provided in Appendix C).

☐ References (Minimum of Three) References meeting the requirements outlined in the RFP, preferably public-sector implementations of similar size and scope.

☐ Completed Appendix B – Pricing Workbook (Excel) All pricing tabs completed, including required cost scenarios, assumptions, and payment milestones.

☐ Scripted Demo Readiness (Appendix D) Acknowledgement of ability to support the scripted demo scenarios using County-provided test data.

☐ Contractual Terms & Exceptions Identification of any exceptions or redlines to the County’s standard contract terms, with rationale.

☐ Assumptions, Dependencies & Exclusions Clearly stated assumptions or dependencies that may impact scope, timeline, or pricing (if not already included in Appendix B).

☐ Completed Appendix E Public Disclosure Statements, Certification and Representation of Offerors, and Local, Small, and Diverse Business Concern Certification

Submission Format Confirmation

☐ Proposal submitted as one searchable PDF (excluding Excel appendices) ☐ Appendix A submitted as Excel (.xlsx) ☐ Appendix B submitted as Excel (.xlsx) ☐ Appendix C submitted as Excel (.xlsx) with attachments ☐ Appendix E: Public Disclosure Statements, Certification and Representation of Offerors, and Local, Small, and Diverse Business Concern Certification as PDF ☐ Proposal valid for at least 180 days from submission deadline ☐ All proprietary or confidential content clearly marked

Optional / If Applicable

☐ Additional supporting documentation (e.g., product roadmaps, sample reports) ☐ Optional modules or services clearly identified and priced separately ☐ Premium support or TAM offerings (if applicable)

15. Submission Checklist (Vendor)