Comparing corporate communications supply routes on identical evidence fields

The named-supplier set is empty because no exact UK edition has both a complete dossier and a common controlled test. A useful comparison is still possible at route level. Cedar Vale Engineering Ltd, a fictional England manufacturer, needs to control one approved source statement, restrict publication, issue a correction and export its evidence.

No route has a score, price or winner. The evidence date is 6 September 2026.

Common comparison unit

The unit is one authorised source-copy version moving through approval, non-live staging, correction and archive. Compare each route on: exact operator, functional boundary, contract unit, data role, access control, accessibility, audit record, support, change notice, correction, export, deletion and exit. Unknown stays unknown.

Route	What the buyer controls	Evidence needed before use	Main exit question
Buyer-owned manual baseline	source file, sign-off record and existing route	permissions, version log, accessible output, backup and correction drill	can another owner recover the record?
Single-function subscribed service	one bounded publishing, approval or monitoring job	exact entity and edition, UK terms, configured test and support scope	can the function and history be exported?
Multi-function suite	linked workflow across several modules	evidence for each module and every connection, with outcomes kept separate	can one module be removed without losing the source record?
Managed communication service	supplier performs defined work for the buyer	authority, personnel access, subcontractors, acceptance, correction and continuity	can work, assets and evidence return to the buyer?

This table does not compare named products. It prevents a broad suite claim from receiving credit for untested functions.

Create one worksheet per route. State the legal operator, exact service boundary, evidence date, region, contract, charging unit and minimum term. Then mark every other field pass, fail or unresolved. The buyer should not translate "per user", "per message" and "per managed month" into one price without real quantities, VAT treatment, implementation work and exit costs.

Apply identical privacy fields

Each route gets a purpose-by-purpose data map. The ICO's controller and processor contract guidance explains Article 28 arrangements and is under review following DUAA. Contract wording must be checked against who actually determines purposes and essential means.

International access needs its own record. The ICO's transfer guide, updated 15 January 2026, frames restricted transfers around the applicable processing, the initiating organisation and the separate receiving entity. Do not infer the answer from a data-centre region alone.

Keep access evidence comparable

Every route must serve the same approved content and correction task. GOV.UK's accessible communication formats guidance, updated 17 June 2026, discusses planning formats and supplier work in government communication. It does not prove a private service is accessible. Record the configured test and an alternative route for Cedar Vale's eligible user.

Test security and recoverability

The same synthetic fixture checks role access, approval order, obsolete-version blocking, correction, log export, account recovery and deletion. NCSC cloud Principle 13 describes buyer access to audit information and alerts. A provider claim is not an observed Cedar Vale result.

Costs stay blank until the exact service supplies currency, VAT status, unit, period, term, implementation, support and exit charges. Accessibility, privacy, security, legal, contract and exit are hard gates rather than weighted preferences. If no route passes, retain the manual baseline, narrow the job or stop. Reopen the evidence after a service, contract or buyer requirement changes. The comparison authorises neither procurement nor publication.