CivensaContact
Menu
Directory methodology

What is included, what is checked, and what is not.

A practical standard for keeping a changing procurement market useful without pretending that provider claims are product tests.

Ownership disclosure: Civensa is operated by BidSkim Limited, which develops BidSkim. BidSkim receives no preferential label, score or placement. The directory has no affiliate links or paid rankings.

Inclusion

We include an active product, service or official portal when it has a clear procurement use, a working official website and enough first-party information to describe its scope without relying on review sites. A listing is not an endorsement. We aim to cover meaningful choices, not every newly registered domain.

We exclude inactive services, lead-generation pages with no identifiable product, duplicate brands, unsupported comparison pages, review-only listings and providers for which we cannot establish a useful official source. We may also omit a provider while a material identity, ownership or product-status question is unresolved.

Evidence labels

Official source means the entry describes a government, public-body or intergovernmental portal using that body’s own guidance. Provider-stated means scope, coverage, features and prices come from the commercial provider’s own website or documents. Neither label means Civensa has validated delivery quality.

Every current listing is marked not independently tested. Best-for and not-for notes are editorial fit judgements based on the stated scope and limitation. They are not ratings, user reviews or performance findings.

Most products and services are shown alphabetically within each category or geographic group. The tender-alert shortlist builder can sort by a transparent public-evidence score, feature depth, headline value, price or name. The score is not a product review or performance rating.

Normalized feature and portal fields

Tender-alert products use the same feature definitions for AI or semantic matching, buyer and supplier profiles, renewals, similar contracts, buyer-document corpora, buyer requirements, requirements planning, award history and related workflow capabilities. A buyer-document corpus means searchable buyer-authored material such as plans, budgets, minutes, strategies or pipelines that can reveal upcoming work; tender attachments alone do not qualify. Yes requires clear first-party evidence that the complete capability is offered in at least one current plan. Higher-plan gating is shown separately and does not make a complete capability partial. Partial means the implementation is adjacent, incomplete, indirect, pilot-only or materially narrower. Not offered is the default when the reviewed public product pages do not establish the capability.

Buyer and supplier profiles receive Yes only where the provider establishes deliberately built cross-notice entities with canonicalisation, deduplication, entity resolution or comparable investment. Filters, names on notices, spend charts and flat directories are not enough. Requirements planning receives Yes only for a durable workflow that turns requirements into tracked gaps, evidence needs, owners, actions or readiness. Extraction, checklists and bid/no-bid explanations alone are partial.

Each tender-alert provider also has a deep audit page covering product maturity, target customers, data sourcing and freshness, matching method, identity investment, renewals, requirements planning, historical depth, integrations, security and onboarding, commercial structure, limitations, contradictory first-party statements and buyer diligence questions. Evidence strength describes the specificity of the reviewed sources, not product quality.

A portal appears in the coverage matrix only when a first-party provider page explicitly names it. Broad claims such as “all UK portals” are preserved separately and do not populate individual portal cells. The linked source beside a claim is evidence that the provider made it, not proof that Civensa independently confirmed feed completeness.

Product classes and shortlist score

The tender-alert comparison groups products into full intelligence, intelligence plus workflow, smart matchers and lite alerting. Classification is mechanical and types overlap: one product may be both full intelligence and workflow, for example. Full-intelligence products need at least five clearly evidenced intelligence capabilities plus a resolved buyer or supplier profile. Workflow products need at least two workflow capabilities alongside intelligence or requirements planning. Products with clear AI matching or moderate intelligence depth become smart matchers. Products that meet none of those tests are lite alerting.

The combined shortlist score is 68% feature depth and 32% headline value. The feature score uses all 14 normalized capabilities and totals 100 possible points. AI matching, buyer profiles and renewals each carry 12 points; supplier profiles, similar contracts, buyer requirements, requirements planning and award history each carry 8; buyer-document corpus carries 6; and frameworks and workflow features carry the balance. A partial capability receives 45% of its feature weight.

Headline value uses two affordability benchmarks: 45% of the affordability component comes from the entry plan that offers the relevant tender-alert or matching capability, and 55% from the highest listed package. A free search-only or limited plan is still shown in the pricing table but is not used as a free tracking benchmark. The total value calculation gives 55% to that blended affordability, 25% to whether numeric pricing is public, and 20% to whether billing is per seat, team or organisation. Annual monthly equivalents are used where published. Quote-only and unpublished prices receive a neutral-low affordability value rather than being treated as free. The entry plan may not contain every scored feature, the highest listed package may still require add-ons, currencies are not converted, and implementation quality is not tested. Buyers must compare the actual plans and order form before purchase.

Pricing and freshness

We separate each public plan into the price paid monthly, the published annual total and the annual plan's effective monthly cost. The effective monthly figure is annual price divided by 12, not a provider discount claim. An unpublished monthly or annual option stays unpublished; we do not multiply a monthly-only price by 12 and call it an annual plan. Billing basis, included users, tax, introductory pricing and material add-ons remain visible.

The normalized tender-alert fields were checked on ; other directory records retain their own displayed check date. Public pages can change at any time, so buyers should obtain a dated order form before purchase. Where a provider page contradicts itself, we say so rather than choosing the more convenient figure.

How to use the directory

Use it to form a shortlist and a question set. For software, run a real tender and inspect source traceability, permissions, exports and deletion terms. For consultancies, identify the people who will work on the bid, what the client must supply, the number of review rounds and who owns final submission. For portals, the live official notice and tender documents always control.

Corrections

Send the page, disputed statement and a direct official source to research@civensa.com. We will review factual corrections regardless of whether they come from a listed provider, competitor or reader. A request for more favourable wording is not, by itself, evidence.

Change-log standard

Material updates use one short line: date · entry · field changed · source or reason. We log price, plan, coverage, ownership, product-status and methodology corrections. Routine punctuation and layout edits are not logged.