The vendor is required to provide online community engagement platform to ensure that engagement is inclusive, transparent and meaningful, the city implemented a branded 24/7 engagement platform called be heard boulder (BHB).
- Needs they identified included, but are not limited to:
• Automated and reliable analysis of both quantitative and qualitative data
• Robust reporting options, including ability to disaggregate data and conduct meaningful cross-tabulation within and across BHB projects
• Multi-language and digital accessibility
• More flexible integration options with other city-owned digital systems
• More mobile-friendly access
• Ability to consolidate and evaluate data collected during companion in-person engagement offerings; and
• Flexible options to display visuals and videos that will enhance the responding community members’ understanding of the issue.
- Non-negotiable functionalities
1. Digital accessibility
• If the services described herein include information technology or digital content that must be made “accessible,” the successful proposer must agree, if requested by the city, to undertake such reasonable efforts that may be needed of the successful proposer to adapt and convert work product to ensure it is accessible within the meaning of §§ 24-85-101, et seq., C.R.S., and its implementing regulations.
• For contracts for which the provision of information technology comprises a primary or material component of the service (such as software and web services) the city anticipates requiring that the successful proposer agree to ensure legal compliance, subject to limited exceptions
2. Single sign-on and two-factor authentication:
• The proposed solution must support integration with microsoft Entra id (formerly azure active directory) to enable secure and seamless user authentication and access management.
• The solution must support single sign-on (SSO) using industry-standard protocols such as SAML 2.0, OpenID connect, or Oauth 2.0.
• It must also allow enforcement of multi-factor authentication (MFA) through microsoft Entra conditional access policies.
• Support for automated user provisioning and deprovisioning via SCIM or equivalent standards is preferred.
• The solution must provide role-based access control (RBAC) capabilities that align with microsoft Entra group membership or claims-based access.
• The system must support federated identity and comply with the organization’s conditional access policies as defined in microsoft Entra.
• Vendors are required to describe the supported authentication protocols, the architecture of their Entra integration, and any limitations, prerequisites, or licensing requirements related to enabling SSO, MFA, and user provisioning.
3. Mobile-friendly design and access:
• Both city staff and community members using the system must be able to access the information and participate in all tools using a variety of devices, including cell phones.
4. City ownership of all data:
• The city of boulder reserves all rights of ownership, title and control to data produced or amended during its use of the software under common law, federal copyright law or other law relating to confidential and trade secret information.
5. City branding:
• The city must have the ability to brand the platform consistent with its preferences, including desired colors, fonts and logos.
- Questions/Inquires Deadline: February 10, 2026
