Building a co-curricular record your campus will maintain

A co-curricular record is an institutionally validated record of a student’s verified learning outside the classroom: leadership roles, service, structured programs, competencies demonstrated. It differs from a résumé in that someone on staff has verified each entry, and from a transcript in that it carries no academic credit.

Most co-curricular record projects begin with a platform evaluation and stall six months later. The reason is almost never the software. It is that the institution never decided what qualifies, so every advisor applied their own standard, the record filled with unlike things, and it lost the only property that made it worth building: that an entry means something specific.

Here is the order that works.

Decide the taxonomy before you look at software

Write down a small set of categories, and for each one a single-sentence inclusion rule and a named person who validates entries in it.

Five categories with hard rules produce a usable record. Twenty categories with soft rules produce a database. A workable starting set:

• Leadership roles: an elected or appointed position with defined responsibility, verified by the advisor of record.
• Structured program completion: a defined sequence with a completion standard, verified by the program owner.
• Service and community engagement: hours or a project with a community partner, verified by the partner or the service office.
• Competency demonstration: a specific skill evidenced by an artifact, verified against a rubric.
• Recognition: an award or honor conferred by a body with published criteria, verified by the conferring office.

Notice that every rule names both the standard and the person. A category with a standard and no validator will fill with self-reported entries within a year.

Verification is the entire value proposition

An unverified record is a résumé on institutional letterhead. The verification is what a graduate admissions reader or an employer is implicitly trusting, and it is the only thing you are actually offering.

So define what evidence an entry requires before you accept any. Attendance data pulled from a system, a supervisor sign-off, a completed artifact against a rubric, a partner confirmation. Then hold the line, especially when a well-liked colleague asks for an exception for a good student. The first exception is the end of the standard.

Be equally careful with what the record does not assert. A co-curricular record carries no credit. If any entry involves a credit recommendation from a review body, that is a recommendation that institutions consider awarding credit, not credit itself, and whether it transfers varies by institution. Our accreditation and credit explainer sets out the distinctions a registrar will insist on. Never let record vocabulary blur that line.

Name the destinations up front

A record nobody can use is an administrative artifact, and the intended use determines how much verification you need. Decide among these before launch:

A document a student attaches to an application. Needs to be exportable, readable by someone with no knowledge of your campus, and dated.

A source a recommender draws on. Needs to be visible to faculty and staff who write letters, and specific enough to quote.

Structured input to an ePortfolio. ePortfolios are one of the high-impact practices AAC&U catalogues, and a co-curricular record is the cheapest way to feed one with verified rather than asserted content.

A notation alongside the academic transcript. The highest-value destination and the one requiring registrar agreement, a governance conversation, and a verification standard that will survive audit. Start that conversation early or not at all.

Make entries a byproduct, never a task

This single design choice determines whether the record survives a staff departure.

If completing a program automatically writes an entry, because completion is already recorded somewhere and the record reads from it, the record stays current on its own. If someone has to remember to type entries in at the end of each term, the record will be complete for about two years and then quietly stop, and nobody will notice until a report comes back thin.

Practically: start with the two or three programs that already track completion rigorously, wire those in, and let coverage grow. A partial record that is accurate beats a comprehensive record that is stale, because students and reviewers both learn quickly which one they are looking at.

Record competencies, not only titles

“Chapter president” tells a reader about a role. “Facilitated 14 peer sessions and led a six-person community project” tells them what the student can do.

The second version is more work to capture and worth it twice over. It is what an employer screens for, and it gives the student the language they will need in an interview. That articulation gap is measurable: our State of Higher Ed 2026 research found 83.8% of undergraduates say their education prepared them for the workforce while only 37% of recruiters agree that graduates are prepared. Students are not short of experience so much as short of a defensible way to describe it, and a competency-level record hands them one.

Keep the phrasing concrete and countable. Verbs and numbers, not adjectives.

Then use it as assessment data

A co-curricular record built this way is also the cleanest participation dataset your division will ever have: verified, defined, and tied to student identifiers. That makes it the natural input to the questions in our guide to measuring student outcomes: who participates, who does not, and how participation distributes across first-generation, commuter, part-time, and online students.

One caution carried over from that guide: participation in the record is self-selected, so a comparison between students with rich records and the institutional average overstates the effect. Say so in the same paragraph as the finding.

Do this next

Draft the taxonomy (five categories, one inclusion rule each, one named validator each) and circulate it before any vendor conversation. If your colleagues cannot agree on the five rules, no platform will resolve the disagreement, and finding that out on a single page costs a great deal less than finding it out in year two of an implementation.