How to issue your first 100 digital credentials: a 10-step playbook
The first 100 digital credentials your organization issues are the hardest. They are when you debug your data, your design, your delivery email, your recipient experience, and the questions your stakeholders ask you the day after launch. The next 1,000 are easy because the first 100 forced you to fix every issue. This playbook walks through the 10 steps that get a first-time issuer from zero to 100 credentials in production.
Plan for two to four weeks from start to first-100 shipped. Solo project managers move on the fast end; cross-functional teams take longer because of coordination overhead. Either way, the steps are the same.
Step 1: name the credential clearly
Before you choose a platform, write the name of the credential out. “Excel Pivot Table Construction” is a name. “Data Analysis Module 3 Completion” is not. The first is a skill the hiring market reads; the second is a course event. If the name does not pass the hiring-market read, the credential will not either.
For the format-level distinction between skill claims and completion milestones, see the badging meaning essay.
Step 2: define the evidence
What does a recipient have to do to earn the credential? Pass an assessment with what score? Submit a project meeting which criteria? Complete a peer-reviewed work product? Write this down before issuing anything. The evidence definition is what makes the credential meaningful to the recipient and defensible to the verifier.
If the only evidence is “attended the course,” you are issuing a certificate of attendance. That is a fine artifact for some programs, but it is not a skill credential and should not be marketed as one.
Step 3: pick the platform
Three filters. First, must issue Open Badges 3.0 with cryptographic signing (not 2.0 relabeled). Second, must offer self-serve onboarding so you can ship without a sales cycle. Third, must have a recipient experience that supports one-click LinkedIn add. For the platform comparison, see our 2026 buyer’s guide.
Step 4: design the credential image
The credential image is shared on LinkedIn, in email signatures, and on recipient portfolios. It needs to look like your brand and read at small sizes. Most platforms include an in-platform design studio; use it. The image should include your organization’s wordmark, the skill name, and an accent color that ties to your brand.
Avoid generic templates. The recipient is going to display the image on their profile for years; it should not look like every other badge in the category.
Step 5: write the metadata
The credential metadata is what the modern hiring stack actually reads. Required fields under Open Badges 3.0: issuer (your organization), recipient identifier, achievement name, criteria (what the recipient did), evidence reference (assessment, project, work product), and issuance date.
Optional but high-value fields: expiry date (where applicable), competency framework alignment (for standards-conscious recipients), tags, and a short description aimed at the verifier.
Step 6: build the recipient delivery email
This email is where most first-time programs underperform. It is the moment the recipient decides whether to share the credential or file it. Three rules.
First, congratulate the recipient by name with the specific skill named. Generic templates kill engagement. Second, include the credential image inline so the recipient sees it without clicking. Third, include the one-click LinkedIn add button prominently. Most platforms supply this; the recipient still needs to be nudged toward it in the email copy.
Step 7: prepare your recipient data
You need a clean CSV with three columns minimum: full name, email address, and the date the recipient earned the credential. For more granular programs: also the specific evidence reference (assessment score, project link, etc.).
Data hygiene matters. Trailing whitespace in names, inconsistent capitalization, and bounced email addresses are the most common debugging headaches in first-100 launches. Run a dedup pass and an email-validity check before issuing.
Step 8: issue 10 test credentials to yourself and your team
Do not ship 100 credentials cold. Issue 10 test credentials first, addressed to your own team. Verify that each delivery email looks right, that the LinkedIn add button works, that the verification link resolves, and that the credential image renders correctly at LinkedIn’s compression. Fix any issues before mass issuance.
Step 9: ship the first 100
Upload the CSV and issue. Most platforms send delivery emails within minutes. Some throttle to avoid email-provider spam-flagging; if so, expect the full 100 to land within a few hours.
Monitor delivery rates. If more than 5% of emails bounce, your recipient data has a hygiene issue worth fixing before the next batch.
Step 10: measure recipient share rate at day 7
Most credentialing platforms surface a recipient-share metric in their analytics dashboard. At day 7 post-issuance, check the percentage of recipients who have added the credential to LinkedIn or shared it elsewhere. Benchmark: 40-70% is typical for well-designed first-100 launches.
Below 40% means the delivery email, the credential image, or the recipient experience needs iteration before scaling. Above 70% means you are ready to issue the next 1,000.
The 10-step playbook at a glance
| Step | Action | Time |
|---|---|---|
| 1 | Name the credential | 1 hour |
| 2 | Define the evidence | 2-4 hours |
| 3 | Pick the platform | 1 week (evaluation) |
| 4 | Design the credential image | 2-6 hours |
| 5 | Write the metadata | 1 hour |
| 6 | Build the recipient delivery email | 2-4 hours |
| 7 | Prepare recipient data | 2-4 hours |
| 8 | Issue 10 test credentials | 1 day (review) |
| 9 | Ship the first 100 | 1 hour (issue), 1 day (delivery) |
| 10 | Measure share rate at day 7 | 15 min |
Common first-100 mistakes
Three patterns sink first-100 launches. Skipping the test-10 step (most common). Generic delivery email that fails to nudge LinkedIn add. Choosing a platform that issues 2.0 relabeled as 3.0 (the credentials work but lose long-term portability). All three are avoidable.
What to do after the first 100
If recipient share rate is over 50% at day 7, scale to the next batch (typical: 500, then 5,000). Use the data from the first 100 to refine credential naming, evidence definition, and recipient experience.
If share rate is under 40%, the playbook is not broken; one of the components is. Most often it’s the delivery email or the credential image. Iterate, re-test with 10 new recipients, then resume.
Frequently asked questions
How long does it take to issue your first 100 digital credentials?
Two to four weeks from project kickoff to first-100 shipped, for most first-time issuers. The longest steps are platform evaluation (1 week) and credential image design (2-6 hours, but often slowed by stakeholder review cycles).
What is a good recipient share rate at day 7?
40-70% is typical for well-designed launches. Above 70% means recipients found the credential genuinely useful and the delivery experience nudged the share. Below 40% indicates the delivery email or the credential design needs iteration.
How much does it cost to issue 100 digital credentials?
For self-serve platforms with free tiers (Sertifier, Certifier.io, Open Badge Factory), 100 credentials typically fits within the free tier or starter tier ($0-$50/month). For programs scaling beyond 100 per year, plan for $3,000-$7,000 annual subscription.
Do I need a developer to issue digital credentials?
No. Modern self-serve platforms let non-developers complete the full first-100 issuance through a CSV upload and in-platform design studio. Developers are needed only for scaled API integration with LMS or HRIS systems (relevant from batch 1,000+).
Next steps
Start with step 1 today: write the name of the credential. The rest of the playbook follows in sequence. For the platform-selection step, see our 2026 buyer’s guide. For Sertifier specifically, see pricing and the free-tier entry point.
