Parchment
Overview
Section titled “Overview”TCR uses Parchment for transcript requests — the intake side of getting a student’s transcript to wherever it needs to go (another institution, an employer, the student themselves). Parchment is distinct from the TCR Transcript App, which is what the registrar actually uses to look up a student and generate the transcript document itself.
Why it exists
Section titled “Why it exists”Parchment is a widely used transcript exchange platform in higher ed, handling the request/delivery side of transcripts (identity verification, tracking, secure delivery to the receiving institution) rather than TCR building that infrastructure itself.
Integrations
Section titled “Integrations”- TCR Transcript App: the registrar generates the actual transcript PDF (with or without an official seal) here to fulfill requests that come in through Parchment.
Not yet documented: the exact hand-off mechanics between a Parchment request landing and the registrar producing/uploading the fulfillment — e.g. whether this is a fully manual step, or whether anything is automated (potentially via n8n).
Access
Section titled “Access”Not yet documented: who has admin access to TCR’s Parchment account.
Dependencies
Section titled “Dependencies”Not yet documented.
Backup & recovery
Section titled “Backup & recovery”Vendor-managed, as a third-party SaaS platform.
This page is deliberately narrow — expand it once the Parchment-to-Transcript-App workflow is documented in more depth.