From Transcript to Track Record: How One Student's Question Became a Course

In the feedback from our embedded credentials pilot, one student comment weighed heavily and would not leave me alone. The student had done everything the program asked. They enrolled in a course, worked through the practice materials, sat for a proctored industry exam, and passed it. Then they wrote: "I don't know what to do with my certification. Do I put it on my resume and LinkedIn or not?"

I wrote about the pilot itself in an earlier report. The short version is that the model worked: across two semesters, students at Columbus State earned roughly 380 industry credentials inside courses they were already taking, at no additional cost, with no new courses built. But the comment above pointed at something the participation and pass rates could not see. We had built a complete pipeline to credential attainment and left the final step—converting attainment into a signal someone can use—to chance.

Some students did not need the help. They claimed their digital badges and posted them to LinkedIn without being asked; a few are there now, wearing their first professional credential in public. Others earned exactly the same thing and did not know what it was worth or where it belonged. The difference between those two groups was not ability, and it was not effort. It was articulation—the learned skill of naming what you can do in words the working world recognizes.

The skill nobody teaches

Articulation is hidden curriculum. Students whose parents interview people for a living absorb it at the dinner table: how to turn a shift at a restaurant into a sentence about working under pressure, how to make a group project sound like collaboration rather than survival. Students without that inheritance are left to guess, and most guess wrong in the same direction. They undersell. They describe the job title instead of the capability. They say "I was a cashier" when the true sentence is "I handled money, conflict, and time pressure for eight hours at a stretch, and the drawer balanced."

I recognize that student because I was that student. I am the first in my family to finish college, and no one at my kitchen table could have told me what a hiring manager hears in the word "cross-functional." What I know now about naming skills, I learned late, in pieces, mostly by watching people who had been taught early. It is not a talent. It is a code, and codes can be taught.

The pilot made the cost of not teaching it visible. A credential is a signal only if the student knows how to send it. A transcript has the same problem, at larger scale: it lists the classes you took and the grades you earned, and both are real, but neither one tells an employer what you can do. In an interview, nobody asks to see your syllabus. They ask you.

Building the last mile

My first instinct was small: a handout at the testing center, a fifteen-minute claim-your-badge module, a workshop with career services. All worth doing. But articulation is not information a student lacks; it is a skill a student has never practiced, and skills are built through repetition, feedback, and revision—not through a handout. If the gap is a practice gap, the fix has to be a practice structure.

So this fall I am teaching one. PERS 1506, From Transcript to Track Record, is a one-credit, fully online course in CSU's Core IMPACTS curriculum. It runs on a simple three-move rhythm, repeated until it becomes reflex: see it, name it, say it. Each module, a student identifies one real skill they have built—in a class, on a job, in the rest of their life—names it in employer-ready language backed by a specific piece of evidence, and then proves it out loud in a thirty-second recording. No adjectives without receipts. Classmates, working in coaching groups of fourteen, respond with three lines: the skill they heard, the most specific moment, and one honest question. Then the student revises. Seven cycles of that, a midpoint portfolio, and a two-minute capstone pitch.

Two design choices matter more than the rest. The first is that every Skill Card a student completes feeds a running inventory, and at the end of the term the course hands each student their inventory back: their skills, their evidence, their words, on one page. A transcript sits locked in a registrar's office. This goes wherever they do. The second is that the course uses AI on purpose and out in the open. Twice, students have an AI tool draft a version of their skills—and then their job is to mark every line that is not specifically true of them and replace it with a real moment only they have. The exercise teaches the difference between smooth and true, which may be the most durable professional skill of the decade.

The same idea, twice

It took me a while to see that I had built the same thing again. The embedded credentials pilot worked because it refused to create a separate, precious program that students would have to find, fund, and fit into their lives; it put the credential inside courses students were already taking. This course applies the identical principle to articulation. It does not ask students to seek out a workshop they do not know they need. It puts the practice inside the credit hour, inside the degree plan, inside the structure they already inhabit.

I will also say plainly what the course is underneath the workforce vocabulary, because I think it strengthens rather than undermines the case. Know what you know. Support every claim with evidence. Say it clearly, out loud, to other people, and revise when they push back. That is O*NET and the NACE competencies on the surface, and it is a liberal education underneath—self-knowledge, evidence, rhetoric, revision. The oldest curriculum there is, dressed for the labor market it has to serve. I have stopped treating those as competing commitments. They are the same commitment.

What I will be watching

The course launched with a hundred seats and filled them, which tells me the demand did not need to be manufactured. A hundred students, one instructor, and one credit hour also impose their own discipline: the course is built to run on structure rather than heroics, and whether that design holds is one of the things this year will teach me. I will report what happens, including what does not work—the pilot earned whatever credibility it has by counting its failures out loud, and I intend to keep the habit.

Mostly, though, I think about the student who asked the question. They were holding something valuable and did not know its name. The honest answer to "do I put it on my resume and LinkedIn or not" turned out to be too long for an email reply. It was a course. This fall, it runs.