Decision support

Compare standards by the job they do

Place up to three profiles side by side. Compare their architectural role, lifecycle reach, and first limitation to test. No single standard covers every layer.

Choose profiles

1 of 3 selected

ISO/IEC 27560Standard

Compare roles before choosing an implementation.

The useful question is not “Which standard wins?” It is “Which job must this part of the architecture perform, and what remains uncovered?”

  1. Start with the job

    Decide whether you need guidance, a domain payload, exchange, semantics, governance, or a reusable release.

  2. Map lifecycle reach

    Use the matrix to see where each profile has a direct role. A filled cell is coverage, not a quality score.

  3. Test the boundary

    Read what each option leaves unresolved before judging maturity or implementation fit.

Review lifecycle coverage and practical fit.

Read left to right. Lifecycle reach comes first; a maturity label never overrides a scope mismatch.

Where each profile contributes directly

Coverage shows a recorded role at that readiness stage. It does not imply end-to-end implementation.

Readiness-stage coverage for ISO/IEC TS 27560 Consent Record Information Structure
ProfilePlanAcquireHarmonizeExchangeLearn + reuse
ISO/IEC 27560StandardISO/IEC TS 27560 Consent Record Information Structure has a direct role in Plan.ISO/IEC TS 27560 Consent Record Information Structure has a direct role in Acquire.ISO/IEC TS 27560 Consent Record Information Structure has no direct role recorded in Harmonize.ISO/IEC TS 27560 Consent Record Information Structure has a direct role in Exchange.ISO/IEC TS 27560 Consent Record Information Structure has a direct role in Learn + reuse.
Direct role recordedNo direct role recorded

What each option does not cover

These are design boundaries, not faults. Use them to identify the companion layers your architecture still needs.

ISO/IEC 27560

Stage boundary
No direct role is recorded for Harmonize.
Known limitation
A conforming record does not prove that consent was informed, freely given, current, or the correct lawful basis; jurisdictional and ethical requirements remain controlling, and the standard is being revised.

Check the fit and source behind the map

Use the official source, version, and limitation together. A higher maturity label does not erase a scope mismatch.

Detailed comparison of ISO/IEC TS 27560 Consent Record Information Structure
AssessmentISO/IEC 27560ISO/IEC TS 27560 Consent Record Information Structure
Purpose & coverage

An interoperable, open, and extensible information structure for consent records and receipts, including exchange and lifecycle management of consent for processing personally identifiable information.

Best fitSystems that must record what a person consented to, provide a receipt, exchange consent information, and manage changes or withdrawal over time.

Readiness stages
PlanAcquireExchangeLearn + reuse
AI-ready contributionSupports automated consent-state and permitted-processing checks, but an agent cannot infer legal validity, contextual integrity, or acceptable secondary use from structure alone.
First limitation to testA conforming record does not prove that consent was informed, freely given, current, or the correct lawful basis; jurisdictional and ethical requirements remain controlling, and the standard is being revised.
Maturity

Scaling

Published Technical Specification; ISO marks it for revision and a successor committee draft is underway

Sources & links