Certificate
Certificate proof
The selected certificate template and school-approved issue fields appear here before generation.
Design, issue, and register

Feature identity
Certificate Generation
An illustration, not a screenshot. The interactive example below shows what this capability actually does.
Design, issue, and register
Certificate output. Rendered by the shipped certificate PDF renderer without a tenant verification URL, so no QR can be generated.
Certificate proof
The selected certificate template and school-approved issue fields appear here before generation.
Product scope
Issue serialized, QR-verifiable, brand-themed PDF certificates — Transfer, Bonafide, Character, Transcript, No-Dues, Fee-Paid, Promotion and staff Experience letters — each with the holder's identity frozen at issue. The Certificate Builder designs custom certificates with {{merge_fields}}, and anyone can verify a certificate by scanning its QR — a revoked one scans invalid.
The school problem
School teams need a dependable way to handle Certificate Generation: Design, issue, and register. The required records, assigned roles and review boundary must remain explicit.
Day-to-day work
Design, issue, and register.
Operational result
Serialized, branded and QR-verifiable certificates with issue, re-download and revocation evidence.
Access and ownership
What each person can actually see depends on the role you give them and which classes or records you assign.
Availability and setup
Included from Starter
Verified certificate records and authenticated document output.
Flagship workflow deep dive
Issued once. Verifiable by anyone.
Issue serialised, QR-verifiable, brand-themed PDF certificates — transfer, bonafide, character, transcript, no-dues, fee-paid, promotion and staff experience letters — each freezing the holder's identity at the moment of issue. A design studio builds custom certificates from merge fields, and any holder's certificate can be checked from its QR without a login.
Interactive operating model
Follow one certificate from the gate it must clear to the QR an outsider scans.
Stage 1 of 5
Request raised
An authorised person requests a certificate against a specific student or employee record.
Control point
Only permissioned staff issue, and the requesting actor is recorded.
Evidence retained
Request, source record and issuing actor.
Core workflows and features
Issued under school control
Numbering, identity snapshotting and the fee gate are deterministic controls. Nothing about issuance is a model output, and no certificate is generated without an authorised person asking for it.
Human boundary
Issuing is a permissioned human action with a recorded issuer. The platform does not attest to facts the school has not recorded, does not sign on the school's behalf, and a verification page reports only what the school issued and whether it is still valid.
Key daily uses
Used by
Actual access follows the school's plan, role permissions and record scope.
Measurable operating indicators
Establish a baseline before rollout, agree the reporting period, then compare the school's own source evidence.
Issued certificates against allocated serials
Confirms the register has neither gaps nor duplicates as issuance volume grows.
Public verification checks against certificates issued
Shows whether the QR route is actually replacing calls to the office.
No-dues requests blocked by outstanding fees and overrides recorded
Makes the exception path visible instead of letting a bypass become routine.
Prerequisites and availability
Certificates on a plan that includes it · template and issuer configuration required
Connected operating context
These are the documented neighbouring capabilities that school teams may review with this module. A related page does not imply that every hand-off is automatic or enabled in every plan.
Buyer questions
The questions school owners ask before they subscribe: what it does, who can see it, and what to set up first.
Yes. Each certificate carries a QR that resolves to a public verification page showing whether it is valid and the fields printed on it — nothing wider from the student's record. A revoked certificate verifies as invalid.
Not silently. Outstanding dues block a no-dues certificate, and proceeding requires an authorised person to record an override — so the exception is visible in the register rather than indistinguishable from a clean issue.
Document Management, Student Reports, Pending Fee Tracking, Export PDF are the documented neighbouring capabilities. They help a school evaluate the surrounding hand-offs, but a related page does not mean every integration is automatic or included in every plan.
A plan that includes Certificates. Configured certificate type/template and authorised source record. Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.
No AI capability is asserted for Certificate Generation. Its documented work remains controlled by school records, roles and permissions.
Certificate Generation is included from Starter in the current public plan matrix. Final rollout scope, services and external dependencies are confirmed in your written proposal.
See it in your school context
See how this workflow fits your school's current records, roles, plan and rollout requirements.