Skip to content
motifuse

Bonafide certificate template

The bonafide certificate institutions issue daily: student, programme, and period certified on letterhead, the purpose it is issued for, and a QR verification corner - generated per request in seconds.

Try this template

1 · Edit the data

2 · Download the PDF

Generated locally in your browser. Nothing you type here is uploaded, stored, or sent to a server.

Live preview — Bonafide certificate
The preview appears here.

Edit the values and download the PDF — generated locally in your browser, no account needed.

What this document is

A bonafide certificate confirms that a named student is genuinely enrolled in a named programme for a stated period. Because banks, consulates, and scholarship boards each want it worded for their own purpose, this template makes that purpose an explicit field rather than leaving it generic.

Who uses it

School and college offices, registrars handling daily student requests, and training institutes certifying enrolment for visa or loan applications.

When to send it

Issue on request, usually the same day. Offices that collect requests across the week can clear the queue as one generated batch.

How to run a bonafide certificate batch

  1. 1Ask what the certificate is for before generating it. A bank, a consulate and a scholarship board each expect a different statement of purpose, which is why purpose is its own field rather than fixed wording.
  2. 2Take enrolment dates from the student register rather than the request form. The verifying office checks them against the institution's records, not against what the student wrote.
  3. 3Include the conduct line only where institute records actually support it. It is optional for exactly that reason.
  4. 4Batch the week's requests into one run — the queue at a registrar's office is the workflow this template exists for.
  5. 5Publish the verification page before distributing certificates whose QR code points at it — a scan that resolves to a 404 does more damage to the certificate's credibility than having no QR code at all.

Common mistakes to avoid

  • One all-purpose wording for every request; a bank, a consulate, and a scholarship body are each looking for a different statement of purpose.
  • Enrolment periods that contradict the student register, which is the first thing a verifying office checks.
  • Adding conduct or attendance claims the institute's records do not actually support, which is why the conduct line is optional.

Fields worth a second look

certificate_purpose
Written into the certificate body. Generic wording is the main reason a certificate comes back for reissue.
enrollment_period
Must match the student register — this is the field a verifying office checks first.
conduct_line
Optional. Leave it out rather than asserting conduct the institution cannot evidence.
verification_url
Encoded in the QR corner. Publish the page first; a QR code resolving to a 404 undermines the certificate.

Privacy

The preview above and all local batches run entirely in your browser — names, amounts, and other values are never uploaded. Cloud batches are explicit, isolated per workspace, protected by short-lived signed links, and deleted at the end of a visible retention window (or earlier, on your request).

For this document specifically: Student identifiers and enrolment details are personal data, frequently about minors. Issue certificates to the student or the named verifying party only, and do not leave generated batches on shared machines.

Template-specific check: Student enrolment data is personal data, and only the institution holding the records may certify enrolment, conduct, or attendance.

Only the institution holding the records may certify enrolment, conduct or attendance. A generated certificate carries the authority of whoever signs it and nothing more.

DocForge produces the document. It does not provide legal, tax or HR advice, and nothing here has been reviewed against the rules of any particular jurisdiction.

Frequently asked questions