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 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.
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.
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.
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.
The learner receives the credential directly. It's theirs to keep — portable, and independent of any single platform or vendor.
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.
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.
We'll walk through setting up a credential in your actual platform.