Frameworks Level: Advanced
Tools and interoperability
How catalogue, data quality, lineage, master data and governance tools can work together, which open standards connect them, and how to buy them without lock-in.
In brief
- 9 kinds of tool, mapped to DAMA knowledge areas, with the open standards that connect them.
- 9 common pairings rated for how mature their open routes are.
- 23 questions for a request for information or tender, as CSV.
Most organisations run several tools for data asset management, often from different suppliers, and many are offered a bundled suite. This page sets out the kinds of tool involved, the open standards and patterns that let them work together, where bundles and contracts create lock-in, and questions to ask in a request for information (RFI) or tender, framed by what the DAM Policy needs. It names no products and endorses none; for named products and a fuller question builder, see the related links at the end of this page.
Five principles
- Your metadata, glossary, quality rules, lineage and results are your data. Make sure you can get all of them out, in open formats, at any time and at no extra charge.
- Prefer open standards at the boundaries between tools, even when the tools come from one supplier. That keeps the option to replace one part without replacing the rest.
- Buy capabilities, not bundles. Price, evaluate and be able to exit each capability separately.
- Prove interoperability before you sign. A round-trip test with your own data is worth more than a list of connectors.
- Plan the exit at the start: cost it, time it and write it into the contract and business case.
This portal's synthesisO: This playbook's own synthesis of published guidance of Open Standards principlesV: Verified against the primary source on 2026-11-05, Technology Code of Practice point 11: define your purchasing strategyV: Verified against the primary source on 2026-11-05 and Managing technical lock-in in the cloudV: Verified against the primary source on 2026-11-05.
Kinds of tool
Each kind of tool supports one or more DAMA knowledge areas. Products often cover several kinds; judge each kind separately.
TL-CAT
Data catalogue and metadata management
Records what data assets exist, what they mean, who owns them and how they can be used; harvests technical metadata from data platforms.O: This playbook's own synthesis of published guidance
DAMA area: Metadata management
Open standards: Data Catalog Vocabulary (DCAT) version 3V: Verified against the primary source on 2026-11-05; Metadata standards for sharing and publishing dataV: Verified against the primary source on 2026-11-05; SKOS: Simple Knowledge Organization System referenceV: Verified against the primary source on 2026-11-05; Egeria open metadata and governanceV: Verified against the primary source on 2026-11-05
Integration patterns: Scan and harvest Documented API Open file exchange Events and webhooks
Ask: Can every catalogue record, including custom fields, owners and classifications, be exported as DCAT and imported into another catalogue without loss?
TL-GLOS
Business glossary and vocabularies
Holds agreed business terms, definitions, synonyms and hierarchies, and links them to data assets.O: This playbook's own synthesis of published guidance
DAMA area: Metadata management Data governance
Open standards: SKOS: Simple Knowledge Organization System referenceV: Verified against the primary source on 2026-11-05
Integration patterns: Open file exchange Documented API
Ask: Can the glossary be exported and imported as SKOS, keeping broader and narrower terms and links to assets?
TL-DQ
Data quality profiling, rules and monitoring
Profiles data, runs quality rules, scores dimensions, raises issues and tracks remediation.O: This playbook's own synthesis of published guidance
DAMA area: Data quality
Open standards: Data on the Web Best Practices: Data Quality VocabularyV: Verified against the primary source on 2026-11-05; Open Data Contract Standard (ODCS)V: Verified against the primary source on 2026-11-05; CSV on the Web (CSVW) primerV: Verified against the primary source on 2026-11-05
Integration patterns: Documented API Contract-driven checks Events and webhooks Embedded views
Ask: Are rules held in a readable, exportable form, and can results be published as DQV or through an open API for a catalogue to show?
TL-LIN
Lineage and data observability
Shows where data comes from, how it moves and changes, and whether pipelines ran as expected.O: This playbook's own synthesis of published guidance
DAMA area: Metadata management Data integration and interoperability
Open standards: OpenLineageV: Verified against the primary source on 2026-11-05; PROV-O: the PROV ontologyV: Verified against the primary source on 2026-11-05
Integration patterns: Events and webhooks Scan and harvest
Ask: Does the tool emit and accept OpenLineage events, including from pipelines and platforms the supplier does not own?
TL-MDM
Reference and master data management
Holds the golden record for entities such as organisations, people, places and products, and the reference lists that other systems share.O: This playbook's own synthesis of published guidance
DAMA area: Reference and master data
Open standards: SKOS: Simple Knowledge Organization System referenceV: Verified against the primary source on 2026-11-05; Identifying property and street information (UPRN and USRN)V: Verified against the primary source on 2026-11-05; API technical and data standardsV: Verified against the primary source on 2026-11-05
Integration patterns: Documented API Events and webhooks Open file exchange
Ask: Can master and reference data, with match and survivorship rules and history, be extracted in an open format and served through a documented API?
TL-POL
Governance workflow, policy and access
Manages stewardship tasks, approvals, data sharing requests, classification and access policies.O: This playbook's own synthesis of published guidance
DAMA area: Data governance Data security
Open standards: OpenAPI SpecificationV: Verified against the primary source on 2026-11-05; Government Security ClassificationsV: Verified against the primary source on 2026-11-05; Data Sharing Governance FrameworkV: Verified against the primary source on 2026-11-05
Integration patterns: Documented API Shared identity and access Events and webhooks
Ask: Can classifications and access policies be read by other tools through an API, and does the tool use your identity provider rather than its own user store?
TL-CONTRACT
Data contracts and data products
Describes what a data producer promises consumers, such as schema, quality thresholds, owners and service levels.O: This playbook's own synthesis of published guidance
DAMA area: Data integration and interoperability Data architecture
Open standards: Open Data Contract Standard (ODCS)V: Verified against the primary source on 2026-11-05; Open Data Product Standard (ODPS)V: Verified against the primary source on 2026-11-05
Integration patterns: Contract-driven checks Open file exchange
Ask: Are contracts stored as ODCS files you can keep in your own repository, and can more than one tool enforce them?
TL-REC
Records and content management
Manages documents and records, retention and disposal, and transfer to an archive.O: This playbook's own synthesis of published guidance
DAMA area: Document and content management
Open standards: ISO 15489-1:2016 Records management: concepts and principlesS: Found by web search; the site blocked automated checking, so open it before relying on it; ISO 23081-1:2017 Metadata for records: principlesS: Found by web search; the site blocked automated checking, so open it before relying on it; Digital records transferV: Verified against the primary source on 2026-11-05
Integration patterns: Documented API Open file exchange
Ask: Can retention and disposal decisions and record metadata be shared with the data catalogue, so a data asset and its records follow one schedule?
TL-AI
AI assistants and search over metadata
Lets people ask questions of the catalogue, glossary and quality results in plain language.O: This playbook's own synthesis of published guidance
DAMA area: Metadata management
Open standards: Model Context ProtocolV: Verified against the primary source on 2026-11-05; OpenAPI SpecificationV: Verified against the primary source on 2026-11-05
Integration patterns: AI access through an open protocol Documented API
Ask: Can an assistant your organisation already approves read the catalogue through an open protocol or documented API, respecting the same access rules?
Open standards at the boundaries
Standards that let tools exchange catalogue records, vocabularies, quality results, lineage, contracts and API descriptions. For data shared within government and published data, also follow Metadata standards for sharing and publishing dataV: Verified against the primary source on 2026-11-05 and the UK Cross-Government Metadata Exchange Model (xGov MEM)V: Verified against the primary source on 2026-11-05.
| Standard | Maintained by | Used between |
|---|---|---|
| Data Catalog Vocabulary (DCAT) version 3V: Verified against the primary source on 2026-11-05 | W3C | Data catalogue and metadata management |
| Metadata standards for sharing and publishing dataV: Verified against the primary source on 2026-11-05 | Data Standards Authority | Data catalogue and metadata management |
| SKOS: Simple Knowledge Organization System referenceV: Verified against the primary source on 2026-11-05 | W3C | Data catalogue and metadata management, Business glossary and vocabularies, Reference and master data management |
| Egeria open metadata and governanceV: Verified against the primary source on 2026-11-05 | LF AI & Data Foundation | Data catalogue and metadata management |
| Data on the Web Best Practices: Data Quality VocabularyV: Verified against the primary source on 2026-11-05 | W3C | Data quality profiling, rules and monitoring |
| Open Data Contract Standard (ODCS)V: Verified against the primary source on 2026-11-05 | Bitol (LF AI & Data Foundation) | Data quality profiling, rules and monitoring, Data contracts and data products |
| CSV on the Web (CSVW) primerV: Verified against the primary source on 2026-11-05 | W3C | Data quality profiling, rules and monitoring |
| OpenLineageV: Verified against the primary source on 2026-11-05 | LF AI & Data Foundation | Lineage and data observability |
| PROV-O: the PROV ontologyV: Verified against the primary source on 2026-11-05 | W3C | Lineage and data observability |
| Identifying property and street information (UPRN and USRN)V: Verified against the primary source on 2026-11-05 | GDS | Reference and master data management |
| API technical and data standardsV: Verified against the primary source on 2026-11-05 | Government Digital Service | Reference and master data management |
| OpenAPI SpecificationV: Verified against the primary source on 2026-11-05 | OpenAPI Initiative | Governance workflow, policy and access, AI assistants and search over metadata |
| Government Security ClassificationsV: Verified against the primary source on 2026-11-05 | Cabinet Office | Governance workflow, policy and access |
| Data Sharing Governance FrameworkV: Verified against the primary source on 2026-11-05 | Central Digital and Data Office | Governance workflow, policy and access |
| Open Data Product Standard (ODPS)V: Verified against the primary source on 2026-11-05 | Bitol (LF AI & Data Foundation) | Data contracts and data products |
| ISO 15489-1:2016 Records management: concepts and principlesS: Found by web search; the site blocked automated checking, so open it before relying on it | International Organization for Standardization | Records and content management |
| ISO 23081-1:2017 Metadata for records: principlesS: Found by web search; the site blocked automated checking, so open it before relying on it | International Organization for Standardization | Records and content management |
| Digital records transferV: Verified against the primary source on 2026-11-05 | The National Archives | Records and content management |
| Model Context ProtocolV: Verified against the primary source on 2026-11-05 | Model Context Protocol project | AI assistants and search over metadata |
Integration patterns
How tools connect, and the lock-in risk each pattern carriesO: This playbook's own synthesis of published guidance.
| Pattern | How it works | Use it for | Lock-in risk | Watch out for |
|---|---|---|---|---|
| Scan and harvest | The catalogue or lineage tool connects to a database, warehouse, file store or business intelligence tool and reads its technical metadata on a schedule. | Building and refreshing the inventory of technical assets. | Medium | Connectors are often licensed separately, priced per source, or maintained only for the supplier's own platform. Ask who maintains each one and how quickly it follows new versions. |
| Documented API | One tool reads or writes another's records through a published API, described in OpenAPI, with the same access controls as the user interface. | Showing quality scores in the catalogue, creating issues, syncing owners or terms. | Low | Check rate limits, whether every object is available through the API (not only some), and whether API calls are charged. |
| Events and webhooks | A tool publishes an event when something changes, such as a rule failing, a pipeline running or an asset being classified, and others subscribe. | Near real-time alerts, lineage capture and keeping several tools in step. | Low | Prefer open event formats such as OpenLineage over supplier-specific payloads. |
| Open file exchange | Export and import in open formats such as DCAT (JSON-LD or Turtle), SKOS, CSV with CSVW, or ODCS YAML. | Migration, exit, bulk loading, publishing and sharing with other organisations. | Low | Exports that drop custom fields, history or links are a form of lock-in. Test a full round trip. |
| Contract-driven checks | Producers publish a data contract; quality and pipeline tools read the same file to check data, and the catalogue shows it. | Agreeing what consumers can rely on, and checking it automatically. | Low | Contract formats are still maturing; keep contracts in your own repository, not only inside a tool. |
| Embedded views | One tool shows another's information in place, for example quality results on a catalogue page. | Giving users one place to look without copying data. | Medium | Embedding through a supplier's private integration can hide a dependency that breaks when either tool changes. |
| Shared identity and access | All tools sign users in through your identity provider and take roles and groups from it. | Always. It keeps ownership and stewardship roles consistent across tools. | Low | Some products charge more for single sign-on or automated user provisioning; ask early. |
| AI access through an open protocol | An assistant reads the catalogue, glossary and quality results through a documented API or a Model Context Protocol server. | Plain-language questions over metadata, with answers that cite their source. | Medium | Make sure the assistant respects access rules and that prompts and answers stay in your approved environment. |
Which tools need to work together
The common pairings, what flows between them, the open route if there is one, and what to do where there is notO: This playbook's own synthesis of published guidance. Of 9 pairings, 4 have established open standards, 3 have emerging ones and 2 depend on each product.
| Between | What flows | Open route | Maturity | If there is no open route | Watch out for |
|---|---|---|---|---|---|
| Catalogue and data quality | Quality scores, rule results and open issues shown against each asset; asset owners and definitions used by quality rules. | DQV for results, ODCS for rules and thresholds, documented APIs. | Emerging | Scheduled export of results as CSV, matched on a shared asset identifier. | Without a shared, persistent asset identifier the two tools drift apart. |
| Catalogue and lineage | Where data comes from, where it goes and which jobs change it. | OpenLineage events, PROV-O. | Established | Harvest lineage from the platform's own logs. | Lineage limited to one supplier's platform hides the rest of the journey. |
| Catalogue and glossary | Business terms linked to assets and columns. | SKOS for the vocabulary; DCAT themes and keywords for links. | Established | CSV term lists with stable identifiers. | Terms stored as free text cannot be reused elsewhere. |
| Catalogue and master data | Which assets hold the golden record and which are copies; reference lists used in metadata. | Documented APIs; SKOS for reference lists. | Vendor-specific | Record the authoritative source as catalogue metadata. | Bundled master data and catalogue modules often share a private model that is hard to separate. |
| Catalogue and records management | Retention, disposal and record metadata for data assets that are also records. | Documented APIs; records metadata standards. | Vendor-specific | A shared retention schedule identifier recorded in both tools. | Two retention schedules for the same information leads to unlawful keeping or early disposal. |
| Data quality and pipelines | Rules run as data moves; failed checks stop or flag a load. | ODCS contracts; OpenLineage run events. | Emerging | Rules called from the pipeline through a documented API. | Rules written in a proprietary language cannot move with you. |
| Governance workflow and identity and access | Owners, stewards, approvals and access decisions. | Your identity provider's standard protocols; documented APIs. | Established | Scheduled sync of roles from the human resources or identity system. | Local user stores create orphaned owners when people leave. |
| Catalogue and other organisations | Published and shared dataset descriptions, harvested by national catalogues. | DCAT, schema.org Dataset and the Metadata Exchange Model. | Established | Publish a CSV catalogue with documented columns. | Private catalogue formats block harvesting by data.gov.uk and the National Data Library. |
| Catalogue and AI assistants | Questions answered from catalogue, glossary and quality information, with links back. | Documented APIs; Model Context Protocol. | Emerging | Publish a text export for an approved assistant to index. | An assistant that bypasses catalogue access rules can disclose restricted metadata. |
- Established Open standards exist and are widely implemented
- Emerging Open standards exist but support varies between products
- Vendor-specific No common open standard; each product does it its own way
Whether two named products interoperate changes with each release. Ask suppliers to show it with your data, and ask other organisations what they found.
One supplier or several
A bundled suite from one supplier and a set of tools from several suppliers can both work. What matters is whether you can change one part without changing the restO: This playbook's own synthesis of published guidance.
What a bundle can offer
- One contract, one support route and one user interface.
- Integrations between modules usually work on day one.
- Can be quicker to start for a small team.
Where a bundle can lock you in
- Modules share a private metadata model, so replacing one part means replacing all of it.
- Weaker modules are carried by stronger ones, and evaluated less carefully.
- Pricing across modules is hard to compare with separate tools.
- Connectors to other suppliers' tools are fewer, slower or charged extra.
- The exit cost grows with every module adopted.
Three tests for any bundle
- Could you replace the data quality module next year and keep the catalogue? What would it cost?
- Are the module prices shown separately, and can you drop a module at renewal without penalty?
- Do the modules use the same open standards between themselves that they offer to other tools?
Commercial barriers and how to avoid them
Barriers that arise with catalogue, data quality and bundled toolsO: This playbook's own synthesis of published guidance. The Competition and Markets Authority's Cloud services market investigationV: Verified against the primary source on 2026-11-05 found that data egress fees and barriers to interoperability restrict switching and multi-cloud, and raised concerns about software licensing in cloud; see the CMA announces package of actions on business software and cloud servicesV: Verified against the primary source on 2026-11-05.
| Barrier | What happens | How to avoid it |
|---|---|---|
| Pricing metric that punishes growth | Charges per asset, per scanned table, per rule run or per user can make cataloguing everything, or running quality checks often, unaffordable. The DAM Policy expects broad coverage. | Model cost at three and five times today's volume; prefer prices tied to things you control; cap annual increases. |
| Shared credits or consumption pools | Credits spread across modules make it hard to see what each capability costs and easy to overspend. | Ask for a price per capability and a monthly usage report you can export. |
| Connectors and APIs charged extra | Some connectors, API access, single sign-on or automated user provisioning sit in higher tiers. | List every integration you need in the requirement and require them in the evaluated price. |
| Export and exit charges | Fees or effort to get data and metadata out, including cloud egress charges, make exit costly. The CMA found egress fees and interoperability barriers restrict switching in public cloud. | Require complete export in open formats at any time at no extra charge, and an exit plan with supplier support in the contract. |
| Ownership of rules, terms and lineage | Contracts can leave quality rules, glossary content, classifications or derived lineage as the supplier's property or in a form only their tool can read. | State that all content you or the tool create about your data is yours, and must be exportable. |
| Platform and marketplace commitments | Buying through a cloud marketplace against a spend commitment can tie a catalogue or quality tool to one cloud platform. | Check the tool runs and is supported on other platforms, and that the commitment does not lengthen the term. |
| Licence terms that limit where software runs | Licensing that costs more on a rival cloud reduces choice. The CMA has raised concerns about business software licensing in cloud. | Ask for licence terms that are the same wherever the software runs. |
| Long terms, auto-renewal and price uplift | Multi-year terms, automatic renewal and uncapped increases reduce your bargaining power at exactly the point you might switch. | Use break points, notice periods you can meet, and capped increases; diarise renewal decisions a year ahead. |
For services supplied into the European Union, the EU Data Act (Regulation (EU) 2023/2854)S: Found by web search; the site blocked automated checking, so open it before relying on it phases out switching charges, including egress charges for a switch. It is not UK law, but suppliers may offer the same terms to UK buyers: ask.
Six steps to buy without lock-in
- Map what you have. List the tools in use or planned for each capability, who owns them, contract end dates and how they connect today.
- Set the boundaries. Decide which open standard sits at each boundary between capabilities, using the pairs on this page, and record it as an architecture decision.
- Run an RFI. Use the questions on this page. Search Find a Tender and G-Cloud for how other bodies specified similar tools.
- Test before you buy. In the proof of concept, run a round trip of export and import, show quality results in the catalogue through an open route, and capture lineage from a pipeline you own.
- Write it into the contract. Include export in open formats, content ownership, separate capability prices, capped increases and a costed exit plan.
- Keep checking. Repeat the export test each year before renewal, and record the result in your assurance evidence.
These steps support Technology Code of Practice point 11: define your purchasing strategyV: Verified against the primary source on 2026-11-05 and Technology Code of Practice point 4: make use of open standardsV: Verified against the primary source on 2026-11-05, and the delivery and change practices on building DAM into contracts, designing out lock-in and buying routes and contract terms.
Questions for a request for information or tender
23 questions, grouped. Use them as written or adapt themO: This playbook's own synthesis of published guidance. Download them as CSV to load into your own RFI template. They focus on what the DAM Policy needs from a tool; for product-level questions, a lock-in checker and a test script, see Related elsewhere at the end of this page.
Standards and export
- RFI-01 Which open standards does the product read and write for catalogue records, glossaries, quality results, lineage and data contracts? Give versions.
- RFI-02 Can we export everything, including custom fields, history, owners, classifications, comments and links, at any time, in open formats, without supplier help or extra charge?
- RFI-03 Describe a round trip, exporting our catalogue as DCAT and re-importing it into another product. What is lost?
- RFI-04 Does the product support the government Metadata Exchange Model for critical data assets?
APIs, connectors and plugins
- RFI-05 Is every object and action in the user interface available through a documented API? Provide the OpenAPI description.
- RFI-06 List each connector, who builds and maintains it, its licence and price, and how quickly it follows new versions of the connected system.
- RFI-07 Which connectors exist for other suppliers' catalogues, quality tools, lineage tools and records systems?
- RFI-08 Does the product emit and accept OpenLineage events? Can it read ODCS data contracts?
- RFI-09 What rate limits, call charges or tier limits apply to APIs and events?
Content ownership and portability
- RFI-10 Confirm that metadata, glossary terms, quality rules, scores, lineage and any content the product derives from our data belong to us.
- RFI-11 In what form are quality rules held? Can they be read and run outside the product?
- RFI-12 Can we keep data contracts and rules in our own code repository and have the product read them from there?
Commercial terms and exit
- RFI-13 Give separate prices for each capability, and confirm we can stop any one at renewal without penalty.
- RFI-14 Model the price at today's volumes and at three and five times them.
- RFI-15 Which features, connectors, single sign-on or provisioning sit in higher tiers?
- RFI-16 What does exit involve, how long does it take, what support is included, and what does it cost, including any cloud egress?
- RFI-17 Are licence prices the same on any cloud or on our own infrastructure?
Security, identity and AI
- RFI-18 Does the product use our identity provider for sign-in and automated user provisioning, at no extra charge?
- RFI-19 Can classification and access policies be read by other tools?
- RFI-20 If the product includes AI features, where are prompts and answers processed and stored, are they used to train models, and can they be switched off?
- RFI-21 Can an assistant we already approve query the product through an open protocol, respecting the same access rules?
Evidence
- RFI-22 Name customers who use the product with another supplier's catalogue, quality or lineage tool, and how they connect them.
- RFI-23 Will you take part in a short proof of concept using our data and an interoperability test we define?
Ready-made requirements and templates
Ready-made requirements to adapt when you buy or build a tool that supports data asset management. Pick the kinds of tool you need, keep the requirements that fit, change the priority to suit, and use them in a request for information (RFI), a tender or an internal build. Each requirement says which DAM Policy requirement and capability it serves, and how a supplier can prove it.O: This playbook's own synthesis of published guidance
This is not commercial or legal advice. Your commercial team chooses the route to market and the evaluation method, and the Procurement Act 2023 and its guidance govern the process. Do not copy these requirements into a tender without that review. Read with Procurement Act 2023: guidance documentsV: Verified against the primary source on 2026-11-05.
44 functional and 23 non-functional requirements, 28 of them Must, with a request for information, a requirements schedule, an evaluation method and contract clauses. Every requirement says how a supplier can prove it.
- Requirements schedule, pre-filled with every requirement (OpenDocument spreadsheet, 3 tabs)
- All requirements (CSV)
- Request for information questions (CSV)
- Contract clauses (CSV)
- Blank templates: schedule, RFI response form, evaluation and moderation, proof of concept log
Functional requirements by kind of tool
| ID | Kind of tool | Requirement | Priority | How to prove it | Capabilities | DAM Policy | Sources |
|---|---|---|---|---|---|---|---|
| FR-CAT-01 | Data catalogue and metadata management | Record every metadata property in the government guidance on describing data assets, with its obligation, in plain English. | Must | Create a record for one of your critical assets with every property filled in; show where each is held. | Data cataloguing and metadata management | DAM-R02, DAM-R13 | Using metadata to describe data assets in a data catalogueS: Found by web search; the site blocked automated checking, so open it before relying on it; Data Catalog Vocabulary (DCAT) version 3V: Verified against the primary source on 2026-11-05 |
| FR-CAT-02 | Data catalogue and metadata management | Export the records for critical data assets as DCAT in a form that can be reported to the centre, without manual rework. | Must | Export your test records and validate them against the reporting format. | Data cataloguing and metadata management, Central reporting, assurance and arm's length body coordination | DAM-R03 | Data Catalog Vocabulary (DCAT) version 3V: Verified against the primary source on 2026-11-05; Metadata standards for sharing and publishing dataV: Verified against the primary source on 2026-11-05 |
| FR-CAT-03 | Data catalogue and metadata management | Hold a named data owner, information asset owner and steward for each asset as roles, and record a successor when an owner leaves. | Must | Change an asset's owner and show the history and the successor field. | Data ownership and stewardship | DAM-R05, DAM-R10 | Using metadata to describe data assets in a data catalogueS: Found by web search; the site blocked automated checking, so open it before relying on it |
| FR-CAT-04 | Data catalogue and metadata management | Prompt owners to review each record at least once a year, and report which records are overdue. | Must | Show the review reminder and the overdue report for a record past its review date. | Data cataloguing and metadata management, Performance measurement and annual review | DAM-R04 | Using metadata to describe data assets in a data catalogueS: Found by web search; the site blocked automated checking, so open it before relying on it |
| FR-CAT-05 | Data catalogue and metadata management | Flag which assets are critical data assets, which of the seven purposes each supports, and its security classification. | Must | Filter the catalogue to critical assets by purpose and classification. | Identify and scope critical data assets | DAM-R01, DAM-R11 | Using metadata to describe data assets in a data catalogueS: Found by web search; the site blocked automated checking, so open it before relying on it |
| FR-CAT-06 | Data catalogue and metadata management | Link a distribution to the data set it comes from, and show the source data set on the distribution's record. | Should | Create a distribution and its source, and show the link in both records. | Data architecture and data services, Reference data, master data and authoritative sources | DAM-R12 | Data Catalog Vocabulary (DCAT) version 3V: Verified against the primary source on 2026-11-05 |
| FR-CAT-07 | Data catalogue and metadata management | Harvest technical metadata, such as tables, columns and types, from your data platforms on a schedule. | Should | Connect to one of your platforms and show a harvested schema refreshed on a schedule. | Data cataloguing and metadata management | DAM-R02 | Data Catalog Vocabulary (DCAT) version 3V: Verified against the primary source on 2026-11-05 |
| FR-CAT-08 | Data catalogue and metadata management | Let users search and browse in plain language, and request access to an asset from its record. | Should | A user with no training finds an asset and requests access during the demonstration. | Data cataloguing and metadata management, Data culture and engagement with users | DAM-R02 | Data Catalog Vocabulary (DCAT) version 3V: Verified against the primary source on 2026-11-05 |
| FR-CAT-09 | Data catalogue and metadata management | Show or hide records and fields according to the user's access rights and the asset's classification. | Should | Show the same record to two users with different rights. | Security classification and protective controls | DAM-R01 | Government Security ClassificationsV: Verified against the primary source on 2026-11-05 |
| FR-CAT-10 | Data catalogue and metadata management | Let you add custom properties without losing them on export. | Could | Add a custom property, export as DCAT and show it in the output. | Data cataloguing and metadata management, Interoperability, data standards and identifiers | DAM-R16 | Data Catalog Vocabulary (DCAT) version 3V: Verified against the primary source on 2026-11-05; SKOS: Simple Knowledge Organization System referenceV: Verified against the primary source on 2026-11-05 |
| FR-GLOS-01 | Business glossary and vocabularies | Hold terms with definitions, synonyms, broader and narrower terms, an owner and a status. | Must | Create a term with a broader term and a synonym and show its history. | Data cataloguing and metadata management, Interoperability, data standards and identifiers | DAM-R13 | SKOS: Simple Knowledge Organization System referenceV: Verified against the primary source on 2026-11-05 |
| FR-GLOS-02 | Business glossary and vocabularies | Import and export the glossary as SKOS without losing hierarchy, synonyms or links to assets. | Must | Export as SKOS, import into a test instance and compare. | Interoperability, data standards and identifiers, Avoiding future legacy: open standards, portability and exit | DAM-R16 | SKOS: Simple Knowledge Organization System referenceV: Verified against the primary source on 2026-11-05 |
| FR-GLOS-03 | Business glossary and vocabularies | Link terms to the data assets and fields that use them. | Should | Show a term and every asset and field linked to it. | Data cataloguing and metadata management | DAM-R02 | SKOS: Simple Knowledge Organization System referenceV: Verified against the primary source on 2026-11-05 |
| FR-GLOS-04 | Business glossary and vocabularies | Route proposed new or changed terms to their steward for approval, and record the decision. | Should | Propose a change, approve it as the steward and show the record. | Data ownership and stewardship | DAM-R05 | SKOS: Simple Knowledge Organization System referenceV: Verified against the primary source on 2026-11-05 |
| FR-DQ-01 | Data quality profiling, rules and monitoring | Profile a data set and run rules that measure the data quality dimensions your action plan uses. | Must | Profile one of your critical data sets and run three of your rules. | Data quality management through action plans | DAM-R06, DAM-R07 | Government Data Quality HubV: Verified against the primary source on 2026-11-05 |
| FR-DQ-02 | Data quality profiling, rules and monitoring | Hold rules in a readable form you can export and run elsewhere, not only inside the product. | Must | Export the rules and show their content. | Data quality management through action plans, Avoiding future legacy: open standards, portability and exit | DAM-R06 | Data on the Web Best Practices: Data Quality VocabularyV: Verified against the primary source on 2026-11-05; CSV on the Web (CSVW) primerV: Verified against the primary source on 2026-11-05 |
| FR-DQ-03 | Data quality profiling, rules and monitoring | Raise an issue when a rule fails, assign it to an owner, and track it to resolution. | Must | Fail a rule and follow the issue to closure. | Data quality issue management | DAM-R15 | Government Data Quality HubV: Verified against the primary source on 2026-11-05 |
| FR-DQ-04 | Data quality profiling, rules and monitoring | Prioritise issues with the government data quality issues framework: target range from importance and impact, priority from the band below target. | Should | Set importance and impact for an asset and show the target and priority produced. | Data quality issue management, Data quality management through action plans | DAM-R15 | Government Data Quality HubV: Verified against the primary source on 2026-11-05 |
| FR-DQ-05 | Data quality profiling, rules and monitoring | Publish results as DQV or through an open API so the catalogue can show them on the asset's record. | Should | Show a quality score on the catalogue record, taken from the tool through an open route. | Performance measurement and annual review, Data quality management through action plans | DAM-R06 | Data on the Web Best Practices: Data Quality VocabularyV: Verified against the primary source on 2026-11-05 |
| FR-DQ-06 | Data quality profiling, rules and monitoring | Show trends over time for each rule and dimension. | Should | Show a three-month trend for one rule. | Data quality management through action plans | DAM-R06 | Government Data Quality HubV: Verified against the primary source on 2026-11-05 |
| FR-DQ-07 | Data quality profiling, rules and monitoring | Compare quality across groups of people, such as completeness by age or ethnicity, to show where gaps fall unevenly. | Could | Show completeness of one field split by a protected characteristic in test data. | Data quality management through action plans, Equality and inclusion in data | DAM-R06 | Equality Act 2010V: Verified against the primary source on 2026-11-05; Public sector equality dutyV: Verified against the primary source on 2026-11-05 |
| FR-LIN-01 | Lineage and data observability | Show where a critical data set comes from and where it goes, across systems from more than one supplier. | Must | Trace one of your critical data sets from source to a report. | Data architecture and data services, Data life cycle management | DAM-R12 | OpenLineageV: Verified against the primary source on 2026-11-05 |
| FR-LIN-02 | Lineage and data observability | Emit and accept OpenLineage events, including from pipelines the supplier does not provide. | Should | Send an OpenLineage event from your own pipeline and show it in the tool. | Interoperability, data standards and identifiers, Avoiding future legacy: open standards, portability and exit | DAM-R16 | OpenLineageV: Verified against the primary source on 2026-11-05; PROV-O: the PROV ontologyV: Verified against the primary source on 2026-11-05 |
| FR-LIN-03 | Lineage and data observability | Alert the owner when a pipeline that feeds a critical asset fails or runs late. | Should | Stop a pipeline and show the alert. | Cyber resilience and incident response for data assets, Data quality management through action plans | DAM-R06 | OpenLineageV: Verified against the primary source on 2026-11-05 |
| FR-LIN-04 | Lineage and data observability | Show what depends on a system or table before it is changed or switched off. | Could | Select a table and list everything downstream. | Legacy migration and decommissioning | DAM-R12 | OpenLineageV: Verified against the primary source on 2026-11-05 |
| FR-MDM-01 | Reference and master data management | Hold a master record for each shared entity, with its identifier and source. | Must | Load two sources of the same entity and show the master record. | Reference data, master data and authoritative sources | DAM-R12 | Develop your data and APIs using a reference architectureV: Verified against the primary source on 2026-11-05 |
| FR-MDM-02 | Reference and master data management | Apply matching and survivorship rules you can read, change and export, and send doubtful matches to a steward. | Must | Run matching on test data and resolve a doubtful match. | Reference data, master data and authoritative sources, Data quality management through action plans | DAM-R06 | Develop your data and APIs using a reference architectureV: Verified against the primary source on 2026-11-05 |
| FR-MDM-03 | Reference and master data management | Extract master and reference data, rules and history in an open format, and serve them through a documented API. | Must | Export everything and call the API for one entity. | Reference data, master data and authoritative sources, Avoiding future legacy: open standards, portability and exit | DAM-R16 | API technical and data standardsV: Verified against the primary source on 2026-11-05; Managing technical lock-in in the cloudV: Verified against the primary source on 2026-11-05 |
| FR-MDM-04 | Reference and master data management | Use national identifiers and code lists, such as UPRN, company numbers and ONS geography codes, where they exist. | Should | Load a national code list and match local values to it. | Interoperability, data standards and identifiers, Reference data, master data and authoritative sources | DAM-R13 | Publish reference data for use across governmentV: Verified against the primary source on 2026-11-05; Identifying property and street information (UPRN and USRN)V: Verified against the primary source on 2026-11-05; Names and codes listings (GSS geography codes)V: Verified against the primary source on 2026-11-05 |
| FR-MDM-05 | Reference and master data management | Version reference lists and record who changed what and why. | Should | Change a code and show the version history. | Reference data, master data and authoritative sources | DAM-R04 | Publish reference data for use across governmentV: Verified against the primary source on 2026-11-05 |
| FR-MDM-06 | Reference and master data management | Publish reference lists for others to reuse, with persistent identifiers. | Could | Publish a list and resolve one of its identifiers. | Cross-boundary collaboration, Reference data, master data and authoritative sources | DAM-R16 | Publish reference data for use across governmentV: Verified against the primary source on 2026-11-05; SKOS: Simple Knowledge Organization System referenceV: Verified against the primary source on 2026-11-05 |
| FR-POL-01 | Governance workflow, policy and access | Route stewardship tasks, approvals and access requests to the named owner or steward, and keep the decision record. | Must | Raise an access request and approve it as the owner. | Data ownership and stewardship, Accountable leadership and policy oversight | DAM-R05, DAM-R09 | Data Sharing Governance FrameworkV: Verified against the primary source on 2026-11-05 |
| FR-POL-02 | Governance workflow, policy and access | Hold classifications and access policies that other tools can read through an API. | Must | Read an asset's classification from another tool through the API. | Security classification and protective controls | DAM-R01 | Government Security ClassificationsV: Verified against the primary source on 2026-11-05 |
| FR-POL-03 | Governance workflow, policy and access | Manage data sharing requests and agreements, with the lawful basis and legal gateway recorded. | Should | Record a sharing request with its gateway and approve it. | Data protection and lawful sharing, Cross-boundary collaboration | DAM-R09 | Data Sharing Governance FrameworkV: Verified against the primary source on 2026-11-05; Data sharing: a code of practice - data sharing agreementsS: Found by web search; the site blocked automated checking, so open it before relying on it |
| FR-POL-04 | Governance workflow, policy and access | Record exceptions to policy with an owner, a reason and an expiry date, and remind before expiry. | Should | Create an exception and show the expiry reminder. | Data risk management | DAM-R09 | The Orange Book: management of riskV: Verified against the primary source on 2026-11-05 |
| FR-CON-01 | Data contracts and data products | Store data contracts as ODCS files you can keep in your own repository. | Should | Export a contract and validate it against the ODCS schema. | Data architecture and data services, Data quality management through action plans | DAM-R06 | Open Data Contract Standard (ODCS)V: Verified against the primary source on 2026-11-05 |
| FR-CON-02 | Data contracts and data products | Check data against the contract's schema and quality thresholds, and tell the owner when it breaks. | Should | Break a contract in test data and show the notification. | Data quality management through action plans, Interoperability, data standards and identifiers | DAM-R06 | Open Data Contract Standard (ODCS)V: Verified against the primary source on 2026-11-05 |
| FR-CON-03 | Data contracts and data products | Describe data products with ODPS and link them to their catalogue records. | Could | Show a data product linked to its catalogue record. | Data cataloguing and metadata management | DAM-R02 | Open Data Product Standard (ODPS)V: Verified against the primary source on 2026-11-05 |
| FR-REC-01 | Records and content management | Apply your retention schedule and disposal actions, and record each disposal. | Must | Apply a schedule to a record and show the disposal record. | Records, retention and disposal | DAM-R04 | Manage information: guidance for governmentV: Verified against the primary source on 2026-11-05; ISO 15489-1:2016 Records management: concepts and principlesS: Found by web search; the site blocked automated checking, so open it before relying on it |
| FR-REC-02 | Records and content management | Share retention and disposal decisions with the catalogue so an asset and its records follow one schedule. | Should | Show the retention period on the asset's catalogue record. | Records, retention and disposal, Data cataloguing and metadata management | DAM-R02 | ISO 23081-1:2017 Metadata for records: principlesS: Found by web search; the site blocked automated checking, so open it before relying on it |
| FR-REC-03 | Records and content management | Prepare records for transfer to an archive in the format the archive accepts. | Could | Package one record for transfer. | Records, retention and disposal | DAM-R04 | Digital records transferV: Verified against the primary source on 2026-11-05 |
| FR-AI-01 | AI assistants and search over metadata | Let an assistant your organisation already approves read the catalogue through an open protocol or documented API. | Should | Ask an approved assistant a question answered from the catalogue. | AI readiness and data and AI ethics, Data culture and engagement with users | DAM-R02 | AI Playbook for the UK GovernmentV: Verified against the primary source on 2026-11-05; Model Context ProtocolV: Verified against the primary source on 2026-11-05 |
| FR-AI-02 | AI assistants and search over metadata | Apply the same access rules to an assistant as to the person using it, and never show restricted metadata. | Must | Ask about a restricted asset as a user without access and show the refusal. | Security classification and protective controls, AI readiness and data and AI ethics | DAM-R01 | AI Playbook for the UK GovernmentV: Verified against the primary source on 2026-11-05; Government Security ClassificationsV: Verified against the primary source on 2026-11-05 |
| FR-AI-03 | AI assistants and search over metadata | Show the sources behind every answer, and record use so it can be described in an algorithmic transparency record if one is needed. | Should | Ask a question and follow the source links in the answer. | AI readiness and data and AI ethics | DAM-R02 | AI Playbook for the UK GovernmentV: Verified against the primary source on 2026-11-05; Algorithmic Transparency Recording Standard hubV: Verified against the primary source on 2026-11-05 |
Non-functional requirements for every tool
| ID | Theme | Requirement | Priority | How to prove it | Capabilities | DAM Policy | Sources |
|---|---|---|---|---|---|---|---|
| NFR-01 | Accessibility | Every screen staff use meets WCAG 2.2 level AA, not only public pages, and the supplier provides an accessibility statement. | Must | An accessibility audit of the screens used in the proof of concept, and the statement. | Equality and inclusion in data, Data culture and engagement with users | All | Understanding accessibility requirements for public sector bodiesV: Verified against the primary source on 2026-11-05; Model accessibility statementV: Verified against the primary source on 2026-11-05 |
| NFR-02 | Accessibility | Works with screen readers, screen magnifiers, voice control and keyboard only. | Should | Complete a core task with a screen reader and with keyboard only. | Equality and inclusion in data | All | Understanding accessibility requirements for public sector bodiesV: Verified against the primary source on 2026-11-05 |
| NFR-03 | Security | Meets the security your data's classification requires, and the supplier shows how the service meets the NCSC cloud security principles. | Must | The supplier's statement against the principles, reviewed by your security team. | Security classification and protective controls, Cyber resilience and incident response for data assets | All | Government Security ClassificationsV: Verified against the primary source on 2026-11-05; Cloud security guidanceV: Verified against the primary source on 2026-11-05 |
| NFR-04 | Security | Data is encrypted in transit and at rest, and the supplier explains key management. | Must | Architecture description reviewed by your security team. | Security classification and protective controls | All | Secure by designV: Verified against the primary source on 2026-11-05; Government Functional Standard GovS 007: SecurityV: Verified against the primary source on 2026-11-05 |
| NFR-05 | Security | The supplier will tell you about an incident affecting your data within an agreed time, and support your response. | Should | The incident clause and the supplier's last incident report process. | Cyber resilience and incident response for data assets | All | Incident managementV: Verified against the primary source on 2026-11-05; Cyber Assessment Framework (CAF)V: Verified against the primary source on 2026-11-05 |
| NFR-06 | Security | The supplier has a plan for moving to post-quantum cryptography in line with the NCSC timelines. | Should | The supplier's written plan. | Cyber resilience and incident response for data assets, Security classification and protective controls | All | Timelines for migration to post-quantum cryptographyV: Verified against the primary source on 2026-11-05 |
| NFR-07 | Identity and access | Uses your identity provider for sign-in and roles, rather than its own user store. | Must | Sign in through your identity provider in the proof of concept. | Security classification and protective controls | All | Cloud security guidanceV: Verified against the primary source on 2026-11-05 |
| NFR-08 | Identity and access | Logs who viewed or changed what, and lets you export the logs to your own monitoring. | Should | Export a day of audit log. | Security classification and protective controls, Data risk management | All | 10 Steps to Cyber SecurityV: Verified against the primary source on 2026-11-05 |
| NFR-09 | Data protection | Processes personal data only on your instructions, under a data processing schedule, with the location of processing stated. | Must | The processing schedule and the list of sub-processors and locations. | Data protection and lawful sharing, Third-party and supplier data | All | Data Protection Act 2018V: Verified against the primary source on 2026-11-05; The Mid-Tier Contract: Schedule 20 (Processing Data)V: Verified against the primary source on 2026-11-05; PPN 020: Guidance on data protection legislationV: Verified against the primary source on 2026-11-05 |
| NFR-10 | Data protection | Lets you find, export and delete a person's data to meet their rights. | Should | Find and export one test person's data. | Data protection and lawful sharing | All | Data Protection Act 2018V: Verified against the primary source on 2026-11-05 |
| NFR-11 | Interoperability | Uses open standards at every boundary with other tools, and names the standard and version for each. | Must | The supplier's list of standards with versions, checked against the open standards for government. | Interoperability, data standards and identifiers, Avoiding future legacy: open standards, portability and exit | All | Procurement Policy Note 07/15: open standards for technologyV: Verified against the primary source on 2026-11-05; Technology Code of Practice point 4: make use of open standardsV: Verified against the primary source on 2026-11-05; Open standards for governmentV: Verified against the primary source on 2026-11-05 |
| NFR-12 | Interoperability | Every object and action in the interface is available through a documented API, described in OpenAPI. | Must | The OpenAPI description, and a call for one object you choose. | Interoperability, data standards and identifiers, Data architecture and data services | All | API technical and data standardsV: Verified against the primary source on 2026-11-05; OpenAPI SpecificationV: Verified against the primary source on 2026-11-05 |
| NFR-13 | Portability and exit | You can export all your content, including custom fields, history, owners, classifications and links, at any time, in open formats, without supplier help or extra charge. | Must | A full export in the proof of concept, compared with what was loaded. | Avoiding future legacy: open standards, portability and exit, Third-party and supplier data | All | Managing technical lock-in in the cloudV: Verified against the primary source on 2026-11-05; Technology Code of Practice point 11: define your purchasing strategyV: Verified against the primary source on 2026-11-05 |
| NFR-14 | Portability and exit | The supplier gives a costed exit plan and will help you move to another product at the end of the contract. | Must | The exit plan and the exit assistance terms. | Avoiding future legacy: open standards, portability and exit, Legacy migration and decommissioning | All | Managing technical lock-in in the cloudV: Verified against the primary source on 2026-11-05; Model Services ContractV: Verified against the primary source on 2026-11-05 |
| NFR-15 | Portability and exit | Each capability can be priced, bought and ended separately, even when sold as a suite. | Should | A price for each capability on its own. | Avoiding future legacy: open standards, portability and exit, Catalogue and quality tooling | All | Managing technical lock-in in the cloudV: Verified against the primary source on 2026-11-05 |
| NFR-16 | Hosting and resilience | States availability, recovery time and recovery point targets, and reports against them. | Should | The service level terms and the last year's performance. | Cyber resilience and incident response for data assets, Data architecture and data services | All | Government Cloud First policyV: Verified against the primary source on 2026-11-05; Cloud security guidanceV: Verified against the primary source on 2026-11-05 |
| NFR-17 | Hosting and resilience | Handles the number of assets, users and runs you expect in three years without a change of product tier you have not priced. | Should | A load test or reference site at that scale, and the price at that volume. | Data architecture and data services | All | Government Cloud First policyV: Verified against the primary source on 2026-11-05 |
| NFR-18 | Support and change | Gives notice of changes that affect you, lets you test them first, and supports versions for an agreed time. | Should | The release and support policy. | Catalogue and quality tooling, Ownership transition and handover to business as usual | All | Service StandardV: Verified against the primary source on 2026-11-05 |
| NFR-19 | Support and change | Provides training and guidance your staff can use without the supplier, in accessible formats. | Should | A sample of the training and guidance. | Data skills, capability and literacy | All | Service StandardV: Verified against the primary source on 2026-11-05 |
| NFR-20 | Records and retention | Lets you apply retention to the tool's own content and logs, and delete them when the schedule says. | Should | Set retention on a test record and show its deletion. | Records, retention and disposal | All | Manage information: guidance for governmentV: Verified against the primary source on 2026-11-05 |
| NFR-21 | AI and transparency | States any AI in the product, what it does with your data, and lets you turn it off. Your data is not used to train models without your agreement. | Must | The supplier's AI statement and the setting to turn it off. | AI readiness and data and AI ethics | All | AI Playbook for the UK GovernmentV: Verified against the primary source on 2026-11-05; Data and AI Ethics FrameworkV: Verified against the primary source on 2026-11-05 |
| NFR-22 | Open source and reuse | Open source components, or the whole product, are named with their licences, and anything built for you can be shared across government. | Could | The software bill of materials and the intellectual property terms. | Avoiding future legacy: open standards, portability and exit, Cross-boundary collaboration | All | Be open and use open sourceV: Verified against the primary source on 2026-11-05; Choosing technology: an introductionV: Verified against the primary source on 2026-11-05 |
| NFR-23 | Usability | People who look after data part time can do the common tasks without specialist training. | Should | Usability test with two of your stewards in the proof of concept. | Data culture and engagement with users, Data skills, capability and literacy | All | Service StandardV: Verified against the primary source on 2026-11-05 |
Request for information
Six sections. Copy the requirements you keep into sections B and D.
RFI-A: About you
- Describe your organisation and the product, and who builds and supports it.
- Which UK public sector bodies use the product for a similar purpose, and can we speak to one?
- Which buying routes is the product available through, such as G-Cloud?
RFI-B: Fit with our needs
For each requirement, say whether the product meets it now, partly, on a dated roadmap or not, and how you would show it.
Takes the functional requirements you keep from the table above.
RFI-C: Interoperability and exit
The questions from the Tools and interoperability page.
RFI-D: Security, accessibility and data protection
For each requirement, say how the product meets it and what evidence you can provide.
Takes the non-functional requirements you keep.
RFI-E: Commercial
- Describe the pricing model, what drives the price, and the price at our expected volume today and in three years.
- Can each capability be bought and ended separately?
- What are the renewal terms, and is any price increase capped?
- What does exit cost, and what help do you give?
RFI-F: Proof
- Would you take part in a proof of concept with our own test data, including a full export and re-import?
- What would you need from us for the proof of concept, and how long would it take?
Evaluating responses
- Agree the evaluation method with your commercial team before you publish anything, and publish it with the tender.
- Treat every Must as pass or fail. Score Should and Could requirements from 0 to 4 against the scale here.
- Weight the groups of requirements to reflect your priorities, and keep quality and price separate until both are scored.
- Score independently first, then moderate as a panel and record the reasons for each moderated score.
- Score what the supplier showed you, in the demonstration or proof of concept, above what they wrote.
- Keep the scoring sheets, the moderation notes and the decision. They are part of your assurance evidence.
| Score | Label | What it means |
|---|---|---|
| 4 | Exceeds | Fully meets the requirement, shown in the demonstration or proof of concept, with evidence of use in the public sector. |
| 3 | Meets | Fully meets the requirement, with credible evidence. |
| 2 | Mostly meets | Meets most of it; the gap is minor and has a dated plan. |
| 1 | Partly meets | Significant gaps, or depends on custom work or a third party. |
| 0 | Does not meet | Not met, not answered, or no evidence. |
Priorities: Must: Without this the tool cannot do the job, or the organisation cannot meet the DAM Policy. A response that does not meet it fails, however it scores elsewhere. Should: Important and expected. Scored; a gap needs a plan and a date. Could: Useful if it costs little. Scored lightly. Won't (this time): Out of scope for this purchase. Recorded so the decision is visible.
Contract clauses to ask for
| ID | Clause | What to include | Why it matters for the DAM Policy | Sources |
|---|---|---|---|---|
| CL-01 | Ownership of content | You own your data and everything you put into or create in the tool: metadata, glossary, rules, results, lineage and configuration. | Without it the assets you report under the policy, and their history, may not be yours to move. | Model Services ContractV: Verified against the primary source on 2026-11-05; Managing technical lock-in in the cloudV: Verified against the primary source on 2026-11-05 |
| CL-02 | Export in open formats | Full export at any time, in named open formats, at no extra charge, tested before go-live and before each renewal. | Keeps you able to report and to change product. | Managing technical lock-in in the cloudV: Verified against the primary source on 2026-11-05; Procurement Policy Note 07/15: open standards for technologyV: Verified against the primary source on 2026-11-05 |
| CL-03 | Exit plan and assistance | A costed exit plan in the contract, updated each year, with the supplier's help to move. | An exit you have not planned is the legacy of the future. | Model Services ContractV: Verified against the primary source on 2026-11-05; Managing technical lock-in in the cloudV: Verified against the primary source on 2026-11-05 |
| CL-04 | Data processing | A data processing schedule naming the processing, sub-processors and locations. | Needed whenever personal data is processed for you. | The Mid-Tier Contract: Schedule 20 (Processing Data)V: Verified against the primary source on 2026-11-05; PPN 020: Guidance on data protection legislationV: Verified against the primary source on 2026-11-05 |
| CL-05 | Separate prices | A price for each capability, and the right to end one without ending the rest. | Lets you replace one part without replacing everything. | Technology Code of Practice point 11: define your purchasing strategyV: Verified against the primary source on 2026-11-05 |
| CL-06 | Capped increases | A cap on price increases at renewal, and notice of any change. | Keeps the cost in the business case true. | Technology Code of Practice point 11: define your purchasing strategyV: Verified against the primary source on 2026-11-05 |
| CL-07 | Security and incidents | Security that matches the classification, notice of incidents within an agreed time, and help to respond. | Critical data assets must stay available and protected. | Government Security ClassificationsV: Verified against the primary source on 2026-11-05; Incident managementV: Verified against the primary source on 2026-11-05 |
| CL-08 | Accessibility | The tool meets WCAG 2.2 AA for staff screens, with an accessibility statement kept up to date. | The accessibility regulations apply to tools staff use. | Understanding accessibility requirements for public sector bodiesV: Verified against the primary source on 2026-11-05 |
| CL-09 | Service levels | Availability, recovery time and recovery point targets, reported each month, with remedies. | Owners need to know how long a critical asset could be unavailable. | Cloud security guidanceV: Verified against the primary source on 2026-11-05 |
| CL-10 | AI use of your data | No use of your data to train models without written agreement, and a setting to turn AI features off. | Keeps control of how your data is used. | AI Playbook for the UK GovernmentV: Verified against the primary source on 2026-11-05 |
Where to find out more
Each link is checked automatically every week.
Government policy and guidance
- Open Standards principlesV: Verified against the primary source on 2026-11-05
- Technology Code of Practice point 4: make use of open standardsV: Verified against the primary source on 2026-11-05
- Technology Code of Practice point 11: define your purchasing strategyV: Verified against the primary source on 2026-11-05
- Procurement Policy Note 07/15: open standards for technologyV: Verified against the primary source on 2026-11-05
- Managing technical lock-in in the cloudV: Verified against the primary source on 2026-11-05
- API technical and data standardsV: Verified against the primary source on 2026-11-05
- Develop your data and APIs using a reference architectureV: Verified against the primary source on 2026-11-05
- The Digital, Data and Technology PlaybookV: Verified against the primary source on 2026-11-05
- The Sourcing PlaybookV: Verified against the primary source on 2026-11-05
Data standards for government
- Metadata standards for sharing and publishing dataV: Verified against the primary source on 2026-11-05
- Data Standards Authority: Standards CatalogueV: Verified against the primary source on 2026-11-05
- Data Standards AuthorityV: Verified against the primary source on 2026-11-05
Open standards and reference projects
- Data Catalog Vocabulary (DCAT) version 3V: Verified against the primary source on 2026-11-05
- Data on the Web Best Practices: Data Quality VocabularyV: Verified against the primary source on 2026-11-05
- SKOS: Simple Knowledge Organization System referenceV: Verified against the primary source on 2026-11-05
- PROV-O: the PROV ontologyV: Verified against the primary source on 2026-11-05
- CSV on the Web (CSVW) primerV: Verified against the primary source on 2026-11-05
- OpenLineageV: Verified against the primary source on 2026-11-05
- Open Data Contract Standard (ODCS)V: Verified against the primary source on 2026-11-05
- Open Data Product Standard (ODPS)V: Verified against the primary source on 2026-11-05
- OpenAPI SpecificationV: Verified against the primary source on 2026-11-05
- Egeria open metadata and governanceV: Verified against the primary source on 2026-11-05
- Model Context ProtocolV: Verified against the primary source on 2026-11-05
Buying routes and market evidence
- G-Cloud 15 frameworkV: Verified against the primary source on 2026-11-05
- Digital Marketplace: search G-Cloud servicesV: Verified against the primary source on 2026-11-05
- Find a TenderV: Verified against the primary source on 2026-11-05
- Procurement Act 2023: guidance documentsV: Verified against the primary source on 2026-11-05
- Model Services ContractV: Verified against the primary source on 2026-11-05
- Cloud services market investigationV: Verified against the primary source on 2026-11-05
- CMA announces package of actions on business software and cloud servicesV: Verified against the primary source on 2026-11-05
- EU Data Act (Regulation (EU) 2023/2854)S: Found by web search; the site blocked automated checking, so open it before relying on it
The UK Cross-Government Metadata Exchange Model (xGov MEM)V: Verified against the primary source on 2026-11-05 is the government model for recording critical data assets; ask suppliers to show they support it.
Was this page useful? Tell us Tell us privately, without GitHub