Digital Credential Packaging

A digital credential package cites an official award and the evidence artifacts that support that award. If the award is not posted on the academic record, the package stays empty. Do not invent a badge. Do not promote a draft graphic. Do not publish because a program office wants the learner to have something to share.

The posted award is the trigger. A final grade in the LMS is not an award. A completed course is not an award. A line on a commencement list is not an award. The award is the registrar's official posting: degree conferred, certificate recorded, micro-credential entered on the student record.

Credentialing staff often sit between academic programs and the registrar and absorb requests to move faster than the record. The hold is a records rule. Student information systems in the Ellucian, Workday, and Anthology class are where conferral lives. Learning systems in the Canvas class are where course-level completion often lives. Completion can become an evidence cite later. It cannot open the package.

Work that happens before conferral belongs upstream. An automated degree audit can show that requirements appear satisfied. Graduation requirement gap alerts can show that they are not. Neither message is a posted award. Do not treat an all-clear audit as permission to mint a credential.

When the award is missing, the correct output is an empty package with a reason staff can explain: award not posted. Empty is not a pipeline failure. Empty is the pipeline refusing to invent academic history.

After the award posts, the package may include evidence cites. A cite is a pointer to an artifact the institution already recorded: a transcript course, a completed assessment, a competency statement, a clinical-hours total, a prior-learning credit decision. The cite must match the student, the term, and a completed status.

Do not attach a file because it sits in the learner's folder. Do not attach a Canvas submission that is ungraded, missing, or from a different offering. Do not attach a prior-learning portfolio that was received but not awarded. If prior learning assessment evaluation produced an official credit decision, cite that decision and how it supports the posted award. Cite the decision, not the raw packet, unless policy names the packet as the retained evidence of record.

If an expected artifact is absent, omit the cite. A package with fewer cites that all resolve is a quality package. A package stuffed with unfinished or mismatched work is a defective credential even when the award itself is real.

Competency transcript generation can feed structured cites when the award is competency-based. The transcript still does not create the award, and it does not license publication.

Identity mismatches stop packaging. If the evidence record's student identifier does not match the award, drop the cite and flag it. Do not attach the closest matching file.

Packaging is assembly. Read the posted award fields (award type, program, conferral date, student identity) and attach only the evidence cites that survive the checks above. Produce a package the registry can accept later. Keep issuer, signature, and public state unissued.

This step is where draft badges leak into production. A badge studio mockup, a vendor sandbox credential, or a program-designed icon is not the official credential. Copying that draft into the package, or sending it to the learner as close enough, treats design work as issuance. The registrar still issues. The pipeline does not.

Read Ellucian, Workday, Anthology, and Canvas as a class of campus systems that already hold awards and evidence. Use the records your institution actually stores. Do not assume a connector, a wallet feature, or an auto-issue switch those products may or may not provide. If your integration is allowed to write, write only under registrar control, and never write an award the SIS has not posted.

Illustrative example: A learner finishes the last course of a graduate certificate on Friday. Canvas shows the course complete. The program director asks credentialing to push a digital certificate the same day so the learner can attach it to a Monday application. The SIS conferral process has not posted the certificate. The correct package is empty: no badge image, no registry identifier, no shareable pending credential. After the certificate posts, packaging cites the official award and the completed courses already used to satisfy the certificate rules. The registrar reviews that package and issues. Only then does the registry receive a publishable record.

If Friday's empty result is inconvenient, the answer is the conferral calendar, not a workaround badge.

Publication is not the last line of the packager. It is a separate act. Queue the package, show an internal preview, and block learner-facing and public release until the registrar's issue event is recorded.

A draft in the registry that a learner can open is a published credential in practice. If the registry cannot hide drafts, do not send the record until issuance. If a wallet or portal would display it, the display must wait.

When an award posts after a delay, do not publish the earlier draft that was built from LMS completion or from an audit snapshot. Re-confirm the posted award, re-resolve every evidence cite, then present the new package for issuance. Stale packages are how the wrong program name, the wrong conferral date, or the wrong evidence set goes live.

Staff communicating with learners should describe the sequence in records language: the credential publishes after the award is on the record and the registrar has issued it.

Three failure modes show up in this workflow.

Publishing before the award posts. LMS completion, an audit that shows requirements met, or a ceremony roster is treated as conferral. The registry then holds a credential the academic record does not. If conferral is delayed, denied, or posted under a different program or date, you must retract a public record you should never have created.

Embedding evidence the student did not complete. Withdrawn courses, incomplete assignments, PLA submissions that were not awarded, or another person's artifact attached through an identifier mix-up. The package looks complete and is false. Prefer omitted cites.

Treating a draft badge as official. Preview images and sandbox credentials get forwarded to employers. Staff then try to make the SIS match the badge. Reverse that. The academic record leads. Artwork follows issuance, if artwork is even part of the official package.

Controls that match those failures: a posted-award key before the package can leave empty; each evidence cite must resolve to a completed record with a matching student identifier; an explicit registrar issue event before any registry publish; a ban on copying sandbox identifiers or draft badge artwork into the official package. Quality here means the package cites what the institution actually awarded and what the learner actually completed. If either is missing, empty stays empty.