Register New Community

Instructions for registering a new UNTP implementation community and starting implementation through the UNTP Community Activation Plan (CAP).

How to Register

Registering a new community starts with a clearly defined scope, accountable ownership, and a minimum set of launch details that can be shared with members. The registration stage should make it clear who the community serves, what implementation outcomes it targets, and how members will coordinate decisions. A complete submission reduces onboarding time and helps the forum publish your community profile quickly.

  1. Define Scope and Sponsorship

    Confirm sector scope, value-chain boundary, and sponsoring organization that will host launch coordination and communications.

    Output: One-page scope statement with intended members and first-year goals.
  2. Nominate a Community Owner

    Assign a named owner responsible for governance, member onboarding, forum coordination, and publication of implementation updates.

    Output: Owner profile with role, organization, email, and governance responsibility.
  3. Submit Registration Information

    Submit community profile, purpose statement, governance model, communication channels, and initial implementation priorities.

    Output: Published community tile and profile page on the forum site.
  4. Confirm Launch Readiness

    Validate member commitment, identify pilot candidates, and schedule the first implementation workshop.

    Output: Launch plan covering first 90 days of Community Activation Plan execution.
Resources

Registration Package

Community Profile
  • Community name and short description.
  • Purpose statement and target participant groups.
  • Sector scope and value-chain boundary.
Ownership and Governance
  • Community Owner name, role, organization, and contact.
  • Governance model, voting/decision process, and meeting cadence.
  • Defined responsibilities for coordination and reporting.
Implementation Readiness
  • Priority use cases for traceability and transparency.
  • Initial pilot list with participating organizations.
  • Communication channels and onboarding process for members.

Community Activation Plan (CAP) Starter

Use the Community Activation Plan to coordinate implementation from first registration to pilot delivery and outcome reporting. The CAP provides a practical structure for organizing governance, technical implementation, and evidence collection in parallel. Teams that define clear workstreams early are usually able to move from planning to validated pilots faster.

Minimum CAP Checklist

  • Purpose and scope of implementation.
  • Priority traceability and transparency use cases.
  • Initial pilot implementation plan and timeline.
  • Outcome reporting approach for case studies.
  • Community-level governance and decision process.
  • Communication channels (mailing list and chat).

CAP Workstreams

  1. Workstream 1 Governance and Community Operations

    Set up meeting rhythm, decision checkpoints, and responsibilities for technical, policy, and reporting tracks.

  2. Workstream 2 Data and Credential Implementation

    Define the minimum UNTP-aligned data set, credential profile choices, and extension requirements for pilots.

  3. Workstream 3 Pilot Execution

    Run pilots with real participants, collect evidence, and track implementation blockers and interoperability gaps.

  4. Workstream 4 Reporting and Scale-Up

    Publish outcome reports (case studies), capture lessons learned, and approve next implementation wave.

First 90 Days and Outcome Reports

The first ninety days should focus on momentum, not perfection: align participants, execute at least one pilot, and publish verifiable lessons learned. This initial cycle establishes trust among members and creates reusable patterns for future community activations. Outcome reports should be written as practical case studies that other sectors can replicate.

  1. Days 1-30: Mobilize

    Stand up governance, publish onboarding guidance, and align members on the minimum implementation baseline.

  2. Days 31-60: Implement

    Run pilot implementations, collect implementation evidence, and resolve data exchange and interoperability issues.

  3. Days 61-90: Report

    Publish outcome reports (case studies), refine the CAP, and confirm the next wave of community onboarding.

Include in Outcome Reports
  • Pilot objective, scope, and participating organizations.
  • Implementation approach and standards/extensions used.
  • Observed results, evidence, and measurable outcomes.
  • Issues encountered and how they were resolved.
  • Recommendations for replication by other communities.
  • Next-step roadmap and ownership for follow-up actions.