Plan framework governance and assurance.
Define the scheme you own
Identify the governing body, participating organizations and the roles they may seek. Review the scheme’s own requirements and agreements rather than treating a software template as a governing decision.
Publish a stable assessment basis
In dc:trust, published scheme versions remain unchanged. Introduce revised requirements through a new version and agree how existing participants transition.
Connect requirements to evidence
Specify relevant evidence, freshness and expiry for each role. Record agreement acceptance and assessor findings with a clear rationale.
Approve independently
Use a different person for approval from the latest assessor. Establish who is competent to make each decision and how exceptions, appeals and conflicts are handled.
Keep assurance current
Evaluate expiry, suspension, renewal and public-directory eligibility alongside the successful operator journey. Retain historical decisions and evidence references.
Plan connected participation separately
Connect member submissions, scoped decisions, change feeds and protected archival to the services your framework operates. Confirm identity, authorization, denial cases and operating responsibilities as part of implementation.