Accreditation cloud based software

University of Houston-Clear Lake is requesting proposals for accreditation cloud-based software under RFP 26-007, with proposals due March 12, 2026 at 2:00 p.m. Central Time. A Historically Underutilized Business (HUB) Subcontracting Plan is required for proposals exceeding $100,000, with statewide HUB participation goals ranging from 11.2% to 32.9% depending on contract category; for professional services, the goal is 23.7%.

The scope is a secure, cloud-based platform enabling preparation, management, and submission of compliance and accreditation reports with multi-user collaboration, version control, task assignment, real-time progress tracking, document storage, template use, and workflow automation. The system must provide role-based access controls, single sign-on compatibility, multi-factor authentication, encryption of data in transit and at rest, Texas RAMP compliance, and support for CSV, XML, and JSON data exchange formats. Respondents must submit detailed pricing including setup fees, annual licensing costs, user tiers, support costs, and optional modules, along with at least three references from higher education clients currently using the proposed software for accreditation or compliance reporting.

The contract term is three years with options to renew for two additional one-year terms, for a maximum of five years. The contractor must guarantee a minimum 99.9% system uptime and hold Commercial General Liability Insurance of at least $1 million per occurrence and $2 million aggregate, plus Professional Liability or Errors & Omissions Insurance of at least $5 million per occurrence.

Evaluation criteria are weighted equally at 20 points each: past projects with similar scale and scope, software functionality/support/training/ease of use, access/security/integration, customization and scalability, and competitive rates. Questions are due March 2, 2026. Proposals are valid for a minimum of 120 days from submission. Addendum 1, posted March 3, 2026, corrected a reference error in Section 1.2 and must be signed and returned with proposals.