Publish the rules people are assessed against
Define framework governance, participant roles and evidence requirements. Published scheme versions remain unchanged; revised rules use a new version.
Give industry schemes, partner networks and data-sharing communities a clear basis for participation. dc:trust connects scheme rules, participant agreements, role-specific evidence and assessment, with approval by someone other than the assessor.
Connect member workflows, scoped decisions and ongoing assurance to the services your network operates, with clear responsibility for integration and support.
Discuss your framework Plan framework assuranceDefine framework governance, participant roles and evidence requirements. Published scheme versions remain unchanged; revised rules use a new version.
Record the organization, the scheme role it seeks and the agreement it has accepted. Control whether its current accreditation appears in a public directory.
Keep evidence references, expiry and integrity details alongside findings. Assess requirements in the context of the participant’s role.
Require a different person to approve accreditation. Retain the assessment, decision and history so reviewers can understand the basis for approval.
Track renewal, evidence freshness and suspension. Expired or suspended status affects current eligibility, while the earlier history is retained.
Publish only approved directory information. Keep evidence, contacts and user identities out of the public directory.
Agree the governing body, role requirements, agreement wording, assessors and approvers.
Give the assessment a stable set of rules and record changes through a new version.
Register a participant, record agreement acceptance and assess current, relevant evidence.
Confirm the assessed role and validity through a separate approver, with a recorded rationale.
Track expiry and renewal, record changes and suspend participation when the current basis for trust no longer holds.
Let participants submit applications, evidence, agreement acceptance and review requests through a connected member service, while operators retain independent assessment and approval.
Scoped decisions, change feeds and protected archival connect assurance to operational workflows. Configure decision checks, retention and service permissions around the framework’s rules.
dc:id provides authentication. dc:pki provides certificate authorities and certificate operations. dc:trust owns scheme governance and assurance decisions. Each responsibility remains clear as the solution grows.
Understand how the services fit Plan your integrationStart with your governing body’s own requirements, roles and agreements. A reusable application gives those decisions a consistent home; it does not define their legal effect or make a scheme independently certified.
Agree who may assess, who may approve, how participants are represented, how appeals and exceptions are handled, and what evidence must be retained. The service focuses on framework governance and participant assurance, with identity and certificate operations owned by dc:id and dc:pki.
Discuss your scheme and responsibilities Review service scopeTell us who needs to connect, what they need to do and what evidence would give your organization confidence. We can explore dc:id, dc:pki, dc:trust or a combination, then agree a focused next step.
For dc:trust, include the scheme or network you operate and the roles you need to assess. For identity or certificates, name the application or service connection. UK-based support and availability in other regions are agreed around your requirements.
Discuss Identity and Trust servicesExplore Data Clan’s data, technology and organizational expertise, meet the people and review the work behind our approach.
Data Clan — company and expertise Meet the Clan Policies and supplier assurance