How it works

The credential lifecycle, start to signed.

Seven steps from evidence submitted in your platform to a portable, verifiable credential the learner owns. No new tools for learners to adopt — the work stays inside your community.

Connect Submit Review Sign Deliver Verify Share

How we work together.

You're never left to set it up alone. Every RecWorks program starts the same way.

1

Design

We work with you to decide what to recognize, what evidence to ask for, and who reviews it.

2

Set up

We build the credential inside your Circle, Notion or Thinkific community and onboard your reviewers.

3

Launch and support

You issue credentials under your organization's name, starting with a pilot cohort, and we stay with you as your programs grow.

Working on something bigger, like a community, a network or a way to show funders what's working? That's what Community Works Collective does. →

1

Meet learners where they are

Connect it to where your community already meets — Circle, Notion, Thinkific, or wherever your programs run. You define the credential and the conditions that earn it — modules completed, prerequisite badges held.

2

Learner submits evidence

The learner completes the submission without leaving the community. RecWorks collects only what's needed to review, issue, and deliver the credential — name, email, and the evidence your criteria ask for, such as a reflection or a file.

3

Review — or auto-issue

A reviewer evaluates the evidence against your criteria, or issuance runs automatically for completion-based recognition. Multi-condition logic is evaluated before anything is signed. For organizations with scoped reviewers, submissions route by tag — read from your platform's API where it's exposed (Circle, today), or from an uploaded roster.

4
The pivot

Signed OBI 3.0 credential

The credential is issued as an Open Badges 3.0 / W3C Verifiable Credential, cryptographically signed and issued in your organization's name, with a published issuer identity (did:web) any verifier can check.

5

Delivered by email

The learner receives the credential directly. It's theirs to keep — portable, and independent of any single platform or vendor.

6

Publicly verifiable page

Every credential has a public verification page anyone can check against the cryptographic signature — no login, no learner account, nothing to install. The signed credential itself is portable and belongs to the learner.

7

Added to LinkedIn in one click

Learners add the credential to their LinkedIn profile in one click — name, issuer, date, and verification link filled in — or share it as a post. Recognition travels with the person, wherever their work takes them next.

Want to see it in your community?

We'll walk through setting up a credential in your actual platform.

Plan your credential program