If you have ever finished a training, workshop or course and then faced a spreadsheet of names that all need individual certificates, you already know the operational problem. Copying each name into Word or Canva, exporting the file and repeating the process is slow, difficult to audit and easy to get wrong.

Centaora Certify turns that work into a controlled production sequence. You configure the issuer and design once, add participant names, preview the result, generate the batch and download verified PDFs from one workspace.

This guide focuses on the practical tool workflow. It explains what to click, what to prepare before each step, what Centaora Certify generates automatically and where human review still matters.

Start here  Explore Centaora Certify to review the live workflow, available tiers and current certificate capacity.

Centaora Certify brings recipient data, certificate design and human quality control into one repeatable production process.

The Centaora Certify workflow at a glance

The platform follows a six-stage path. The first run takes longer because you are establishing the issuer identity and reusable template; later batches can begin with an existing design and move directly to participant data.

1. Activate an account and choose capacity for the expected cohort.

2.  Set the official issuer name and build a reusable certificate template.

3.  Open New batch and confirm the programme title and date.

4.  Type participant names or upload a clean CSV file.

5.  Preview the design, wording, signatures, badge and QR placement.

6.  Generate the batch, review it in History, download the ZIP and test verification.

The sequence matters because each stage controls a different kind of risk. Template decisions protect brand consistency, participant checks protect accuracy, preview protects layout, and QR testing protects the credibility of the verification record.

The production sequence moves from participant data to a reusable design, a complete batch, human review and verified delivery.

Before you open Centaora Certify

Prepare the decisions and files that the tool will ask for. This short preparation step prevents repeated edits once the template and batch are in production.

• The exact public name of the issuing organisation, institution, trainer or professional.
• The programme or course title and the date wording that should appear on the certificate.
• The certificate type: completion or participation.
• A checked participant list, ideally saved as CSV UTF-8 for larger groups.
• A clear logo file and signature images if the selected paid tier will print them.
• The authorised signers, their titles and the internal person who will approve release.
• A plan for delivery and storage after the batch is downloaded.

Treat the participant list as the authoritative record. If a name changes, correct the source data first and regenerate from the corrected record instead of editing a finished PDF.

Step 1: Request access and choose the right capacity

Begin on the Centaora Certify product page and choose the tier that matches the cohort size and design requirements. The live page shows the current certificate credits, maximum rows per CSV, number of signatures, available layouts, logo access, badge options and analytics features for each tier.

Trial is useful for testing the complete flow with Centaora branding. Paid tiers remove the watermark, allow a custom logo and provide increasing production and design capacity.

Take action  Request Centaora Certify access and provide the programme, organisation, preferred tier and payment method requested on the form.

For paid requests, Centaora sends the payment instructions by email; no payment is collected on the request page. Once access is approved, use the credentials supplied to open the issuer workspace.

Step 2: Log in and read the dashboard before producing

After signing in, check the dashboard counters before beginning. Credits remaining shows how many valid certificates the account can produce, while Max rows per upload shows the largest participant list that can be processed in one batch.

The workspace is organised into six areas: New batch, Preview, Templates, History, Account and Upgrade. Understanding that structure makes the rest of the workflow straightforward.

• New batch selects a saved template, programme details and participant names.
• Preview shows the chosen design before generation.
• Templates creates, previews, edits, uses or deletes reusable designs.
• History holds completed batches and their preview and download actions.
• Account controls the issuer name used on public verification records.
• Upgrade requests more credits or a different tier when capacity is insufficient.

Step 3: Set the official issuer name

Open Templates or Account and enter the exact public issuer name. The issuer is the organisation, trainer or institution responsible for the programme; Centaora Certify is the platform hosting the record.

This name appears on the public verification page, so it should match the organisation name used on the certificate, website and programme materials. A verifier should not have to guess whether two slightly different names refer to the same issuer.

Only the issuer name is displayed as the public account identity. The account email and other private account information are not shown on the verification record.

Step 4: Build one reusable certificate template

Open Templates and create the design that will control the batch. Give it a clear internal name that helps a future user recognise the audience, layout and year, such as NGO Workshop Formal Blue 2026.

Configure the template in this order so that visual choices follow the credential meaning rather than distract from it.

1.  Enter the default course or programme title. It can still be changed for a specific batch.

2.  Choose Completion for an achieved programme or Participation for attendance.

3.  Select the layout, theme and colours that fit the issuer brand.

4.  Upload the organisation logo where the selected tier permits custom branding.

5.  Add signer names, titles and signature images, or leave suitable space for hand signing.

6.  Choose an optional badge if it strengthens the hierarchy without competing with the recipient name or QR code.

Select Save template when you want to keep refining the template library. Select Save and use template when the design is ready and you want Centaora Certify to open New batch with that template already selected.

A saved template is reusable, but it is not untouchable. Use Edit design for changes to colours, logo, signers, badge or wording, and use Quick update when only the default course title or certificate type needs adjustment.

Step 5: Start a new batch and confirm programme details

Open New batch and select the saved template. Confirm the course or programme title and enter the date exactly as it should appear on the certificate.

This is the moment to separate genuinely different cohorts. If the issuer, wording, signatory or credential type changes materially, create a separate batch rather than forcing several variations into one production run.

Check that the participant count will remain within both the available credits and the plan row limit. If it does not, split the list deliberately or request additional capacity before generation.

Step 6: Add participant names manually or by CSV

Centaora Certify supports two practical input routes. Manual entry is appropriate for a short list or a final correction; CSV upload is the efficient route for a larger cohort.

Manual entry for a short list

Enter one participant per row and review the spelling before moving to preview. Manual entry is simple, but it should not become a substitute for a controlled source list when the cohort is large.

CSV upload for a larger group

Use a first row of column headings and place the participant name in a column called name. Optional columns can hold useful record data such as email, department, hours or score where the workflow supports them.

Before uploading, remove blank rows and duplicates, preserve the recipient’s preferred spelling and capitalisation, and save the file as CSV UTF-8. UTF-8 matters for names containing accents and other non-English characters.

• Use one person per row.
• Keep the name heading simple and exact.
• Remove formulas, merged cells and decorative headings.
• Test the longest name and the longest programme title in the cohort.
• Retain only the personal data that is necessary for issuing and delivery.

If the file is rejected, first check the encoding, the name heading, blank leading rows, remaining credits and the plan’s maximum rows. Those checks resolve many upload failures before support is needed.

Step 7: Preview before using any credits

Preview is the final design gate before production. It should show the A4 landscape proportions and the template choices that Centaora Certify will use for the batch.

Review the preview as a certificate issuer, not only as a designer. The question is whether the document is accurate, legible and credible when someone receives, prints or verifies it.

• Completion or participation wording is correct.
• The recipient name remains prominent and has enough space for long entries.
• The programme title and date are accurate and wrap cleanly.
• The logo, colours and texture support rather than overpower the content.
• Signer names, titles and images are correct.
• The optional badge remains clear of the certificate ID and verification area.
• The certificate ID and QR code sit visibly at the lower right.

The browser preview is a close guide, but it is not the final file. Always inspect at least one generated PDF before releasing a complete batch.

Step 8: Generate the certificate batch

Return to New batch after the preview is approved. Reconfirm the template, programme title, course date and participant count, then start generation and keep the browser open until the process finishes.

Centaora Certify then performs the repetitive production work automatically.

• It gives each participant a unique certificate ID.
• It creates a QR code linked to the corresponding public verification record.
• It validates each PDF before deducting a certificate credit.
• It assembles valid PDFs into a downloadable ZIP file.
• It marks the batch complete only when a readable ZIP exists.
• It emails the completed ZIP when practical or provides a secure download link for a larger file.

Do not refresh or close the page while a batch is processing. If an error appears, read it before retrying so that you do not create duplicate batches or lose the information needed for support.

Step 9: Review the generated certificates in History

Open History when generation is complete. The batch record shows the course, row count, date, status and the actions available for review and download.

• Preview first opens one generated certificate for a rapid check.
• Preview all opens the batch in manageable pages for wider review.
• Download ZIP retrieves every valid certificate PDF in the batch.
• Delete download removes the stored ZIP while leaving the issued certificates and verification records valid.

Open at least three PDFs, including the first recipient, the last recipient and the record with the longest name. Confirm that the generated count matches the approved source list before anyone receives a certificate.

Step 10: Test QR verification before distribution

Open one generated PDF and scan its QR code with a phone. The public page should report a valid certificate and show the issuer name, recipient name, programme, certificate ID and issue date.

Compare every displayed field with the PDF. If scanning is unavailable, the certificate ID can be checked manually on the Centaora verification page.

The QR code is a route to evidence, not proof by appearance alone. A standard PDF becomes more useful when it is linked to an issuer-controlled record, although it should not be described as an Open Badges 3.0 credential or a W3C Verifiable Credential unless it actually implements those standards.

Before distribution, scan a generated QR code and compare the public verification record with the certificate PDF.

Step 11: Download and distribute the approved batch

Download the completed ZIP and store it in the controlled location used by the programme team. Keep the original approved participant list, the template name and the batch date with the issuance record so that later questions can be answered efficiently.

Distribute each PDF through a method appropriate to the programme and sensitivity of the recipient information. Avoid placing an entire batch in a public folder when individual delivery or controlled access is available.

Collect only the recipient information needed for issuance and delivery, restrict who can access the working files and define when temporary exports will be removed. The European Commission data-protection principles provide a useful benchmark for data minimisation, accuracy, storage limitation, integrity and confidentiality, alongside the laws and policies that apply in the issuer’s jurisdiction.

What Centaora Certify automates and what people must govern

A bulk certificate generator is most reliable when the organisation understands the boundary between automation and judgement. Centaora Certify can generate consistently, but it cannot decide who has legitimately met the programme requirements.

Automation reduces repetitive work; it does not transfer accountability. The issuer remains responsible for the programme and the credential, while Centaora Certify provides the production and verification infrastructure.

Confirm the following production checklist before release

• Issuer name matches the organisation’s public identity.
• Correct saved template is selected and visually previewed.
• Certificate type, course title and date are final.
• Participant list is approved, deduplicated and within capacity.
• Long names and special characters have been tested.
• Signer details, logo, badge and colours are correct.
• Generated count matches the approved participant count.
• At least three PDFs have been inspected.
• One QR code and public verification record have been tested.
• ZIP storage and recipient delivery method are approved.

Common problems and the quickest response

The CSV is rejected

Confirm that the file is CSV UTF-8, the participant column is headed name, there are no blank leading rows and the row count fits the account limit. Remove merged cells, formulas and decorative headings before uploading again.

The account does not have enough credits

Reduce or split the participant list only when the cohorts can remain clearly labelled and reconciled. Otherwise, open Upgrade and request the capacity needed for the approved list.

The template looks wrong

Return to Templates and use Edit design. Recheck the layout, colours, logo, signer information, wording and badge before previewing again.

The PDF generation fails

Read the displayed message and retry once. A PDF that fails validation should not consume a credit; if the problem continues, contact Centaora with the batch course and approximate time of the error.

The ZIP is unavailable

Open History and try Download ZIP again. Preserve the batch details if support is required, rather than starting a duplicate production run immediately.

The QR code does not verify

Confirm that the full QR is visible and undamaged, then enter the printed certificate ID manually on the verification page. Do not distribute the remaining batch until the issuer, recipient, course, ID and date all match.

When Centaora Certify is the right tool

A design application remains reasonable for a rare, single certificate. Centaora Certify becomes more valuable when certificate production is recurring, involves a participant list, must follow an approved brand or needs a verification record that can be checked later.

The useful decision is not based on volume alone. Frequency, number of variable fields, verification needs, staff time, replacement requests and the cost of an incorrect certificate all influence the case for automation.

• Training providers and professional-development programmes.
• Universities, schools and academies.
• Conferences, webinars and membership organisations.
• Non-profits delivering capacity-building programmes.
• Businesses certifying employees, partners or customers.
• Any issuer that needs consistent records, reissue support and public verification..

Generate certificates in bulk without losing control

The practical advantage of Centaora Certify is not simply faster PDF creation. It is the combination of a reusable template, structured participant input, consistent batch generation, human review and an issuer-linked verification record.

That workflow allows organisations to generate certificates in bulk while keeping the decisions that matter under human control. The result is quicker delivery, fewer avoidable errors and a credential that is easier for recipients and third parties to trust.

Next step  Explore Centaora Certify or request access for the tier that matches your programme. For larger or specialised requirements, contact the Centaora team.

Continue exploring Centaora

Bulk Certificate Generation explains why manual post-training certificate work creates delays and avoidable rework.

The Shift to Verifiable Digital Credentials explores the trust gap between an ordinary PDF and an issuer-linked verification record.

Centaora Resources brings together practical tools, guides and learning resources for people and organisations.

Centaora Insights provides further thinking on human capacity, strategy, intelligence and practical systems.

Sources and further reading

Centaora Certify product page: current product workflow, tier capacity, template features and verification overview.

1EdTech Open Badges: a formal standard for packaging verifiable achievement information about an issuer, earner and credential.

W3C Verifiable Credentials Data Model 2.0: a technical reference for machine-verifiable digital credentials.

European Commission data-protection principles: practical principles for minimising, protecting and retaining participant data.