At enrollment
Offer letters, acceptance packs, fee schedules, and consent forms can reuse applicant and institution data. Keep approval and signature requirements in the enrollment workflow rather than inferring them in the document.
Education
From each student record
From each student record
to approved document
Automatically generate accredited certificates, academic transcripts, and report cards from LMS course completions and student records.
Free account, no credit card
Built for education workflows
Certificates & Diplomas
Fill an approved credential layout with the recipient, award, date, institution, and verification reference.
Transcripts
Lay out courses, grades, totals, and institution details from the registrar's source record.
Report Cards
Merge term grades, approved comments, and attendance values into a reusable report layout.
Course Materials
Render handouts, syllabi, and study guides from structured data, HTML, or maintained content.
Event Badges
Create badges and event passes from registration data, with the size and output format the event requires.
LMS Integration
Use a supported connector, webhook, or API call to turn an LMS event into a document request.
How it works
1
Approve the template
Start from a gallery item or your own HTML. Add institution assets and test the layout with representative names and records.
2
Map the source record
Connect the LMS, student system, or spreadsheet and map only the approved student, course, grade, and credential fields.
3
Issue and route each result
Submit one record or a batch, track every result, and hand the finished file to your email, storage, or student-portal workflow.
One template, a row per student
A cohort of 200 means 200 renders from one approved layout and 200 source records. Select a student below to see which values change while the template structure stays in place.
The class list
| Name | Grade |
|---|---|
| A | |
| B | |
| A | |
| C |
1 of 4
The certificate it produces
Certificate of completion
Amelia Okonkwo
has completed Advanced Data Analysis with a grade of A
Awarded with distinction
14 June 2026
Test the values that strain the layout: long names, accented and non-Latin text, missing optional fields, and award labels of different lengths. Check each case before issuing the full cohort, not after the files have entered the delivery workflow.
What one academic year produces
Education documents arrive at different points in the year and often share student, institution, and course data. Map each event to the document it actually requires, then keep the source record and template version needed for a later reissue.
Through the term
Permission forms, medical authorizations, attendance letters, and progress reports each begin with a different event. Conditions can tailor approved sections to the supplied answers or student record.
At assessment
Report cards, transcripts, and result letters place per-student values into a controlled structure. Validate grades and totals before rendering, then reconcile the output count with the source roster.
At completion
Certificates, diplomas, and credential letters may be issued in one concentrated run. Submit them asynchronously, track failures by student record, and leave enough time to review corrections before the delivery date.
Afterwards, for years
Transcript copies and verification letters depend on retained source data, approved templates, and institution policy. Store the version and assets needed to explain what was issued and when a later copy was produced.
For the institution itself
Compliance returns, inspection evidence, funding documents, and board papers can also use reusable layouts. Their approval, retention, and access rules may differ from student-facing documents and should stay explicit.
Where a manual merge needs checking
A mail merge can work for a small run, but it leaves validation, version ownership, and delivery tracking outside the document step. These are the points to make explicit when moving the workflow into templates and queued renders.
- Test more than the typical record. A short sample name does not prove that a long surname, accented text, an empty optional field, or a right-to-left name will fit. Build a test set for these cases and review the output before running the roster.
- Give the template a named owner. Record who can change the layout, which version is approved, and where shared assets live. HTML and CSS make the source portable, while workspace roles and history make the change process visible to the team.
- Work backward from the issue date. A ceremony or completion date can leave little room for corrections. Schedule roster validation, sample renders, the full run, review, and delivery as separate checkpoints.
- Keep enough context for a reissue. A later transcript request needs the student record, the applicable template version, institution assets, and the dates that distinguish the original award from the new copy. Define how long each item is retained.
- Index forms by the record people search for. A folder of files is difficult to use when staff need one student's consent or the forms for one trip. Carry stable student and event identifiers into the workflow and storage path so retrieval does not depend on filenames alone.
A certificate somebody can check
A PDF alone is not a credential registry. Give each issued document a reference that an employer or institution can check against a verification service you control. The render displays that reference; your system decides whether it is valid.
- Create the credential reference first. Store it with the student and award record before rendering. A retry can then reuse the same identifier instead of creating another credential record.
- Point to a verification service you operate. A QR code or short link can carry the lookup URL. Keep the page, access rules, status meanings, and availability under the institution's control.
- Separate award, issue, and copy dates. Supply the dates your policy requires so a later copy does not appear to be a newly awarded credential.
- Choose access controls for the delivery path. PDF permissions or passwords can be part of the output, and supported own-storage delivery can keep files in infrastructure governed by your policies.
- Keep an issuance record outside the PDF. Record the credential, template version, render result, and later status changes so a verification request does not depend on an email archive.
Credential Verification
Render the evidence your registry can verify
A certificate can embed a QR code that links to a verification page on your domain. Your credential system supplies the reference, recipient, award, dates, and status; the template places the approved fields in the document. Use a batch when a cohort finishes together.
An available LMS event can start the workflow through a connector or webhook. Validate the completion record before rendering. If a credential later expires or is revoked, update the registry that powers verification; regenerate the displayed document only when your policy calls for it.
QR Verification
Encode the credential's verification URL in a QR element so a reader can check the record in your service.
Batch Issuance
Submit a cohort from validated CSV or API data and reconcile each render result with its student record.
LMS Webhooks
Use an LMS event or webhook to start the render after your workflow confirms completion.
Credential Status
Keep active, expired, and revoked states in the credential registry that answers verification requests.
Education workflow examples
Teachable to branded certificate
- Receive the course-completion event in the chosen workflow.
- Confirm the student, course, and award record.
- Map the approved fields and verification URL into the template.
- cloudlayer.io renders the certificate and QR code.
- The workflow routes the result to the required destination.
University to batch transcripts
- The registrar exports an approved semester record.
- The workflow validates and maps each row.
- A batch request renders one transcript per student record.
- Completion events reconcile and route each result.
When do the certificates actually get issued?
Certificate demand often arrives as a cohort rather than a steady stream. A course with 400 qualifying students and one certificate each requires 400 renders. Count any transcript, corrected copy, or other output separately, then compare the total and delivery deadline with plan volume and concurrency.
What the spike is made of
- One render for each certificate the workflow produces.
- Another render for each transcript or result sheet produced as a separate file.
- Correction renders for records changed after review.
- Any other generated file in the credential package; a verification web page is not itself a document render.
How to choose capacity for the burst
Plan allowances are monthly. Add every output expected in that month, including other workflows in the same account, then choose the plan volume that covers the total and its published overage terms.
Concurrency affects how quickly queued work can run. Estimate the completion window from representative render times and the plan's concurrency, then test a smaller batch before relying on that estimate for a ceremony deadline.
Design correction and reissue behavior before the first batch. Keep the credential reference in the source record so a corrected render can use the intended identifier. Your credential system decides whether the new file replaces, supplements, or records a new version of the old one. Record that decision with the issue event so later verification has an audit trail.
Questions, answered
How do I produce certificates for a whole cohort at once?
Use one approved template and one data record per student. A cohort of 200 certificates uses 200 renders. Submit the work as a batch or async jobs, track each result, and plan the queue around published concurrency: 2 renders on the entry tier, 8 on Business, and 25 on Enterprise.
What happens to a very long name, or a name with accents?
The template can wrap long names and load fonts with the required glyphs. It still needs testing. Use long, accented, non-Latin, and right-to-left examples from the population you serve before issuing the full cohort.
Can an employer verify a certificate we issued?
Add a credential reference and a QR code or short link that points to a verification page you operate. Create and store the reference in the credential system before rendering so a retry can reuse the same record.
Can we reissue a transcript years later?
Yes, if your archive keeps the source record, template version, and required assets. A reissue can show both the original award date and the date the copy was produced. It uses one render, and finished files can be delivered to your own bucket through six supported storage providers. Your retention policy remains yours to define.
Do students and parents count as users on our plan?
Public form respondents are not internal workspace users. Plan limits on internal users apply to staff who work inside the account, such as template authors and administrators. Check the plan table for the number of internal users included.
Can a permission form change based on the answers?
Yes. Form and template conditions can show different questions or document sections based on supplied answers. Define and test each branch, including the rule that determines whether a guardian signature is required.
How do I issue certificates automatically when a student finishes a course?
Receive the completion event from your LMS or automation workflow, validate the student and course fields, then submit them with the certificate template.
Can I generate transcripts in bulk?
Yes. Submit a batch of validated student records and track the result for each transcript as it completes.
Can certificates include a verification code or QR code?
Yes. Add a barcode or QR-code element and supply the credential reference or verification URL with each record.
Do certificates work for online course platforms?
A course platform can start the workflow when it exposes a suitable event through a supported connector or webhook. Use a custom integration when its event and fields are not covered.
Test one credential workflow
from record to verification
Use a real completion record to check the template, identifier, render result, and delivery path before issuing a cohort.
No credit card required.