Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,110 of 9,110 pages
About the help in other languages
All help pages

Red flags and pitfalls in CMS evaluations

The claims and bid patterns that should make an evaluation panel stop and ask for evidence when a bid is based on Exponential, and the mistakes panels make themselves - each with the documentation that shows the true…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/government/procurement/evaluation/red-flags-and-pitfalls.md

On this page

Red flags and pitfalls in CMS evaluations

This page is for every member of an evaluation panel. It lists bid statements about Exponential that go beyond what the product's documentation says, patterns that hide future costs or lock-in, and mistakes evaluation panels make. Each item links the page that shows the documented position, so you can ask the bidder a precise question.

Contents

  1. Claims that contradict the documentation
  2. Patterns that hide cost or lock-in
  3. Data and privacy warning signs
  4. Mistakes panels make
  5. How to respond to a red flag

Claims that contradict the documentation

Claim in a bidDocumented position
"Exponential is WCAG 2.2 AA compliant"admin4/admin4l "Partly complies"; public designs not audited (Accessibility standards)
"A VPAT / Accessibility Conformance Report is available for Exponential"none exists; Section 508 and EN 301 549 are "Unverified"
"Certified against OWASP ASVS"no ASVS assessment was made: "Unverified" (Security standards)
"Brute-force protection is built in and on"account lockout is off by default; brute force is detected by audit alert rules
"A strict Content Security Policy protects the site"report-only on administration, none on sites by default
"GDPR compliant out of the box"features provided; compliance is the organization's job, and there is no cookie banner (Privacy standards)
"Guaranteed response times from the Exponential project"the project publishes no SLA; only a first answer to private security reports within one business day (SLA options)
"Our version is the official long-term support release"SECURITY.md names the 6.0.x line as maintained; fixes come in the next 6.0.x release
"Built-in GIS / mapping"no GIS feature is documented; the ezgmaplocation extension adds a map location datatype that uses Google Maps, a third-party service

A bidder may still deliver what the claim promises through its own work. Ask it to restate the claim as a commitment for your site, with how it will be evidenced at acceptance.

Patterns that hide cost or lock-in

  • A private fork of the kernel that only the bidder maintains. Ask whether changes go back upstream (Contributing code back); a private fork makes every upgrade the bidder's monopoly.
  • Closed-source extensions delivered without source. Under the GPL, whoever receives an extension also receives its source (Licensing questions); require source delivery in the contract.
  • "License" or "subscription" fees for the core software. The software has no license fee. Fees for support, hosting or services are normal; make sure the bid says which is which.
  • Hosting tied to the supplier with no export. The data can be exported in open formats (Leaving Exponential); ask the bidder to demonstrate it.
  • Upgrades priced as new projects. Ask how the bidder keeps sites current (Keeping customers current) and what a 6.0.x update costs.
  • An old line. A bid on 5.x or older offers an unsupported version (SECURITY.md).

Data and privacy warning signs

  • A demo on a copy of a real site with real personal data.
  • Third-party analytics, captcha or social sign-in enabled without a consent plan: the Privacy standards page lists which shipped extensions send data to third parties when activated.
  • No answer to "who processes our personal data, where, and under which agreement?"
  • Credentials sent by e-mail during the tender.

Mistakes panels make

  • Scoring presentation quality instead of requirements.
  • Accepting "yes" in a compliance matrix without a source.
  • Writing a mandatory requirement nobody can meet (for example a product VPAT), and then waiving it unevenly.
  • Comparing license price only, ignoring hosting, staff, training and exit costs.
  • Forgetting the editors: no editor sits on the panel or tries the system.
  • Not testing the exit: export is checked only after the contract is signed.

How to respond to a red flag

  1. Write a clarification question that quotes the claim and the documentation page.
  2. Ask for evidence: a document, a test you can repeat, or a contractual commitment with an acceptance test.
  3. Score the answer, not the original claim.
  4. Record the exchange in the evaluation file.

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x