Print it from the record, not from a retyped list

Build a template once and issue it to any student or staff member, with a record of who received what and when.

Book a demo

What this usually looks like today

A student needs a character certificate. Somebody opens last year's file, changes the name and the dates, and prints it - occasionally missing one of the fields, which is how a certificate goes out with the wrong session on it.

Six months later that student asks for a duplicate. Nobody can say whether one was issued, when, or what it said, so the whole exercise happens again.

What it handles

Deliberately a small module. This is what it covers.

Reusable templates

Built once, cloneable and editable, so a new certificate type is a variation rather than a fresh document.

ID cards

Student and staff cards populated from the record, including the photograph already on file.

Certificates and letters

Character certificates, leaving certificates and bonafide letters with the details filled from the record.

Examination admit cards

Generated against the examination and the candidate, carrying the seat and schedule.

Preview before issuing

See exactly what will print before it prints, which is where most template mistakes are caught.

A record of every issue

Who received which document and when, so a duplicate request is answered from record rather than from memory.

The cases most systems get wrong

The certificate with last year's session. Adapted from a previous file, one field missed. It goes out wrong and the school finds out when somebody official reads it.

The duplicate nobody can confirm. A student asks for another copy. Without an issue record, nobody knows whether one was ever produced or what it said.

Who touches it

The office

Builds templates, issues documents and answers duplicate requests from the record.

Families and students

Receive documents that are correct because they were generated rather than retyped.

What it shares records with

Templates read the student and staff records the institution already maintains, so a document is correct because the record is correct rather than because somebody typed carefully.

Admit cards draw on the examination and seating. Every issue is recorded against the person, so a duplicate request years later is a lookup.

Questions we get asked

Can we use our own certificate designs?
Yes. Templates are built by you and cloneable, so a new certificate type is a variation on an existing one rather than a document started from scratch.
Do we have to type the student details in?
No - they come from the record, which is what stops a certificate going out with last year's session on it because somebody adapted an old file.
Can we tell whether a document was already issued?
Yes. Every issue is recorded against the person, so a duplicate request is answered from record rather than from memory.
Can we preview before printing?
Yes, and it is worth doing - a preview is where most template mistakes are caught, rather than after fifty copies.

Bring a certificate you issue often

We will build the template in front of you. That shows the effort more honestly than a feature list.

Book a demo