Service · Web development

Custom certification portal development.

A custom portal for trade associations, professional bodies, quality marks, training institutes and certification bodies that issue certificates, coordinate audits and supervise members. From application and verification to issuing with a QR code, a public register, renewals and a revocation flow — set up around the rules of your scheme, not those of a generic package.

Application & verificationExam & audit plannerMultiple reviewerseIDAS QESPublic registerComplaints & revocation

A certification portal is not a form tool with a PDF export.

Anyone who issues certificates cares about one thing above all: trust. A certificate stands or falls with the credibility of its issuer — and that credibility rests largely on the system underneath. How is it established that an applicant genuinely meets the requirements? Who assessed them, when, and on what grounds? Can a client check for themselves whether a certificate will still be valid tomorrow? A certification portal handles that entire chain, so the issuing organisation can focus on the substance.

That is fundamentally different from a general web application: a certification portal links the application to an exam or audit, the assessment process to multiple independent reviewers, the outcome to a legally valid issuance, and the certificate to a searchable register. The scheme you operate — professional certification, quality mark, educational certificate or ISO management system — is the driving force behind the configuration.

We build these portals to order for organisations for which an off-the-shelf package is either too broad or just too limited: a trade association that issues its professional certification and wants to stay in control; a quality mark that coordinates member audits; a training institute that handles formal diploma recognition; a certification body that wants to move its client portal off an outdated Access environment. We start from the scheme and the rules of your profession, not from a feature list.

Three levels of certification portal.

The right level depends on your issuance volume, the number of assessors, the weight of compliance (eIDAS, GDPR, accreditation requirements) and the extent to which the system also needs to invoice, integrate and publish. We advise on this in the first introductory conversation.

Compact project · fixed sprint budget

Application and issuance portal

A clearly scoped portal for a single scheme: candidates or companies apply, upload supporting documents, pay exam or audit fees and, after assessment, receive a digital certificate with a QR code. A simple assessor workspace and a simple public register. Enough to get away from Excel lists and loose PDF certificates.

ApplicationPaymentIssuance with QRPublic register
Mid-sized project · fixed sprint budget

Scheme-driven certification platform

The rules of your scheme built in: multiple certificates per person or company, exam and audit planning, assessment by multiple independent reviewers with conflict detection, renewal cycles with automatic reminders, a complaints and revocation flow, and a public register that a client can rely on with a single click.

Multiple reviewersAudit plannerRenewalsRevocation flow
Larger project · fixed sprint budget

Multi-scheme platform with deep integration

Mission-critical portal for organisations that manage multiple schemes in parallel. Separate scheme data per scheme owner, client portals in their own branding, integrations with accounting, PSPs, e-sign providers and accreditation bodies, and webhook APIs for external registers. Includes eIDAS QES, an anchored integrity hash for public verifiability and a formal handover of management to your IT team.

If you manage amusement rides or playground equipment, each item has its own certificate and file. That is covered on the page about inspection file software for amusement rides.

Multi-schemeeIDAS QESWebhook APIAnchored integrity

What a custom certification portal includes at a minimum.

Whatever the level, we deliver a number of core components as separate modules, so you can later scale from a single scheme to a platform without redesigning your architecture.

  • Scheme engine as a first-class componentWe define schemes as configuration: requirements, evidence, scoring rules, validity period and renewal conditions. A scheme administrator can change requirements or publish a new version without a release; every version is traceable in the audit trail. Builds on our approach to workflow software.
  • Registration with identity verificationApplicants register through a scheme-specific wizard. Identification is via iDIN, DigiD, eHerkenning, KvK verification or passport upload with OCR checking. For educational certificates, an integration with the BRP (population register) or DUO; for professional certification, a match against previous registrations.
  • Payment and invoicing per schemeExam fees, audit rates and renewal fees are paid via Mollie, Adyen or Buckaroo. Invoicing runs through an integration with Exact, AFAS, e-Boekhouden or Twinfield. For membership fees, we integrate with your existing membership system so that a suspension automatically affects the certificate status.
  • Exam and audit plannerExam locations, examiners, auditors and candidates are mapped with capacity monitoring, conflict detection (no assessment by their own employer), travel-time optimisation and rescheduling. For digital exams, an integration with your surveillance or proctoring provider.
  • Document upload with integrity hashApplicants and auditees upload evidence that lands in a file-bound document store (S3-compatible, EU-hosted). Each file receives an integrity hash so that it can later be proven the document is unchanged, similar to our approach to file management.
  • Assessment by multiple reviewersAn asynchronous review flow in which two or three independent assessors review the same application without seeing each other's scores until after their own judgement. Disputes escalate to an arbitration role or committee. The review environment shows only the relevant parts of the file for each reviewer role.
  • Issuance with eIDAS QES and QR verificationApproved applications result in a digital certificate signed with a qualified electronic signature (QES) under eIDAS, legally equivalent to a handwritten signature. The certificate contains a QR code that links to the current status in your register; even after revocation the QR code keeps working and then shows that the certificate is no longer valid.
  • Renewal and continuing education cycleCertificates with a validity period are automatically identified for renewal, with reminders before expiry. Continuing education requirements, PE points or audit cycles are configurable per scheme. A missed renewal leads to a controlled expired status in the register, not to a certificate that silently stays valid.
  • Public register with APIA searchable public register where clients and consumers can check whether a certificate is valid, for which scheme and until when. Full-text search, filters, and an open API so external systems (tenders, training providers, marketplaces) can retrieve the current status in real time.
  • Complaint, sanction and revocation flowA complaints workflow in which a complainant files formally, a committee hears the case and decides, and the outcome (warning, suspension, revocation) automatically updates the status in the public register. With logging that is demonstrable to accreditation bodies.
  • Record-level audit trailWho assessed which application, when, with what score, under which scheme version, and which decision-maker signed off a revocation. Immutable and time-stamped, aligned with ISO 27001 and, for accreditation-compliant schemes, complementary to ISO/IEC 17024 or 17065.
  • Role-based access control (RBAC)Access per role: applicants see only their own file, examiners only their assigned exams, assessors only their assigned review work, the committee the decisions, and accreditation auditors aggregates without personal data. Least privilege is the starting point; conflict-of-interest detection is a feature, not a manual check.

When a certification portal is the right choice.

For a small certification with a handful of issuances per year, a spreadsheet and a PDF template are often still workable. We only come into the picture when one or more of the patterns below apply. In the intake we will discuss, without obligation, whether a custom solution fits, or whether a lighter alternative will do.

Scheme discipline

Requirements are interpreted differently

You notice that different assessors interpret your scheme's requirements differently in practice. A scheme-driven portal enforces the same definitions and evidence for every application, and every assessor gets the same rubric.

Independence

Multiple reviewers and conflict detection

For accreditation-compliant certification (ISO/IEC 17024, 17065), independent assessment by multiple reviewers with demonstrable conflict-of-interest checks is a requirement. Off-the-shelf tools rarely handle this well.

Public register

Clients need to be able to verify for themselves

You want a contracting authority, training provider or consumer to be able to check for themselves whether a certificate is valid. A PDF on a personal page does not do that; a searchable register with an API and QR verification does.

Renewals

Cycle too complex for reminder emails

Continuing education points, audit cycles and renewal requirements differ per scheme. Excel lists work up to roughly a hundred certificates. Beyond that, you need a system that keeps the cycle under control.

Multi-scheme

Multiple certifications in parallel

For industry associations that manage more than one scheme, or a platform that hosts schemes from different scheme owners: separate data per scheme with central identity and payment. A design choice, not a plugin.

Integrations

Exam, payment and register fully connected

When exam software, payment processing and register publication live in separate tools and your team synchronises them by hand every month. A single portal that carries the whole chain saves manual work and delivers better management information.

Certification by use case.

The rules and integrations differ greatly per type of certification. A selection of the contexts for which we have built or advised on certification and register systems.

Professional and personnel certification

Tradespeople, installers and self-employed professions

For trade bodies that issue their own professional certification to individual practitioners (under schemes such as CCV, CKB, KOMO craftsmanship or similar professional certifications), we build portals where candidates register, sit theory and practical assessments, receive a personal certificate with a QES and QR code, and keep track of their continuing-education points. A public register lets clients and consumers check credentials directly.

Personal certificateTheory + practicalContinuing educationPublic register
Quality marks and hallmarks

Product certification and quality mark audits

For quality marks in ornamental horticulture (MPS), forestry and paper (FSC, FFP), horticulture (GLOBALG.A.P.) and food, we coordinate the entire audit process: annual planning, self-assessments, on-site inspections with mobile data entry, scoring according to the scheme, issuance with a validity date, and publication in an open register that trading partners use to verify origin and quality.

On-site auditsMobile data entryAudit reportSupply chain traceability
Educational certification and diplomas

Examination boards and training institutes

For training institutes, examination boards and organisations that issue formal diplomas or educational certificates (comparable in scale to CITO or the operations of CAOP), we build portals for enrolment, examination, assessment by multiple independent markers, diploma issuance with a QES, and an integration with DUO or the Diploma Register. This builds on our wider education app development.

ExaminationTwo markersDiploma issuanceDUO integration
Trade associations and professional bodies

Member certification with supervision and sanctions

For trade associations and professional bodies that link membership to certification (with continuing-education requirements, codes of conduct and a supervision and sanctions procedure), we build portals that connect membership, certification and fees. A suspension automatically affects the certification, a complaint about a member runs through a structured committee flow, and the register shows the current status.

Members + certificateCPD pointsComplaints committeeSanctions flow
Company certification and management systems

ISO 9001, IATF 16949, AS9100 and sector variants

For certification bodies that issue company certification based on international management system standards (ISO 9001, 14001, 27001, IATF 16949 for automotive, AS9100 for aerospace), we build customer portals for audit planning, certificate history, transfers between bodies, IAF reporting and an integration with the accreditation body (RvA). The portal is the customer-facing side alongside your internal audit management system.

Customer portalAudit historyRvA reportingTransfer protocol
Damage insurance and repair sector

Repair companies, FCN-style certification

For insurance-related certification, where approved repair companies (Focwa, FCN-style) or assessment firms are audited periodically on quality, environment, safety and customer focus, we build portals that combine the audit cycle, mystery-shopper results, customer NPS and claims statistics into a current certification status. They include integrations with insurers who use that status to steer claim allocation.

Periodic auditCustomer satisfactionInsurer APIClaims statistics

Scheme engine, multiple reviewers and eIDAS explained.

Four modules that clients want to hear more about in a first conversation. How we build them, and why we make some choices differently from an off-the-shelf package.

  • Scheme engine as data, not codeWe define schemes as configuration: requirements, evidence, scoring rubrics, weighting factors, pass thresholds, validity periods and grounds for revocation. A scheme administrator publishes a new version without us having to ship a release, and every version is kept as a historical snapshot. In an accreditation audit you can show which scheme applied on which date, which is crucial for ISO/IEC 17024 and 17065 conformity.
  • Multiple reviewers with blind review and escalationApplications are assigned in parallel to two or three independent assessors. Until they have submitted their own judgement, reviewers cannot see each other's scores. If opinions differ, the case escalates automatically to an arbitration role or committee. Conflict-of-interest detection checks employer, region and previous relationships, so an application is never assigned to an assessor who knows the applicant.
  • eIDAS QES, AES and public verifiabilityFor certificates with legal consequences, we sign with QES via a Qualified Trust Service Provider (Signhost QTSP, ValidSign QTSP, KIK-cap). Regular certificates use AES. On top of that, public verifiability via a published hash (RFC 3161 timestamp or blockchain anchoring) means anyone can independently check that a certificate has not been altered after the fact.
  • Public register with webhooks to the marketThe register is also a live data source. External systems, such as tendering platforms, marketplaces, insurers and industry umbrella bodies, subscribe to webhooks that fire on every status change. That removes the need for daily export files. The API is documented, versioned and has clear rate limits.
Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

How a certification portal project works with us.

1

Introduction and intake

A no-obligation conversation in which we map out your schemes, estimate issuance volumes, go through the compliance requirements (GDPR, eIDAS, ISO/IEC 17024 or 17065, RvA requirements) and assess whether a custom build is the right choice or an existing certification package. Sometimes we recommend the latter, which saves you time and budget.

2

Discovery with your scheme and workflow

A working session with your scheme owner, assessors, planners and a few certificate holders. We map out the scheme, identify the real pain points (where assessors deviate, where renewal deadlines slip, where the market fails to consult the register) and capture the scope in an initial screen flow.

3

Scheme modelling and compliance design

We translate the scheme into a formal data model: requirements, evidence, rubric, scoring, validity, renewal, revocation. At the same time, we establish the privacy and security design: data classification, GDPR legal bases per data flow, and a DPIA where justified. For accreditation-compliant schemes, we test against ISO/IEC 17024 or 17065.

4

Building in sprints

Application and issuance flow first, then scheme management, then the multi-reviewer review flow, then the public register and the API, then eIDAS QES and the complaints and revocation flow, then the integrations with payment, accounting and external registers. You test along, scheme administrators test along and, where possible, so do real applicants and assessors.

5

Migrating existing certificates

We migrate whatever existing certificates and historical audit reports live in your current system, Excel lists or Access environment in phases: new applications go into the new portal first, followed by historical certificates with integrity hashing and a link to the scheme version that applied at the time.

6

Pilot, training and go-live

A pilot group of assessors and a test group of applicants work in parallel in the old and new systems, and any differences are resolved. We run training sessions for scheme administrators and assessors, provide short videos for applicants, and go live with a clear fallback procedure.

7

Management and further development

After go-live, we monitor performance, security and usage. New scheme versions, extra integrations or an entirely new scheme are handled in small development sprints, so your portal keeps pace with new standards and accreditation requirements.

Compliance: GDPR, eIDAS and publication requirements.

What sets a certification portal apart is that compliance isn't a coat of paint but the blueprint itself. We build the rules into the system so they can't be bypassed, even by accident, and so that an accreditation audit of the system holds no surprises.

GDPR and special category personal data. Application files contain personal data and, depending on the scheme, CV data, exam scores and possibly health data or criminal-record information. For every processing activity we record the legal basis, restrict access to what is strictly necessary, and maintain a record of processing activities that updates automatically. A data protection officer can run a report without needing a developer.

eIDAS QES and AES. For certificates with formal legal status, we work with a Qualified Trust Service Provider that signs with a QES, which is legally equivalent to a handwritten signature. For regular certificates, an AES is sufficient. The signature certificate and timestamp are stored in the audit trail, so a client can later establish that your organisation issued the document at a given moment.

Publication requirements and the right to erasure. Set against the confidentiality of the file is the requirement to publish in the register. We build the register so that only data that may be public is public (name, scheme, validity, scope), while personal data and file contents remain strictly separate. The GDPR right to erasure runs through a separate workflow that respects your retention obligations.

NEN 7510 and ISO 27001 where applicable. For certifications with a healthcare link, we align with NEN 7510. For the portal itself, we build to ISO 27001 requirements so your organisation can include the system in its own management system certification.

The technology choices we make along the way.

Our stack is deliberately conservative: certificates with validity periods of several years and renewal cycles that can run for decades call for a foundation that isn't rebuilt time and again.

Backend in Postgres with RBAC. Row-level security for multi-scheme separation. The roles and permissions model lives in the database, so even an ad-hoc query goes through the same access control. For the public register, we use a separate read replica so that a public traffic spike doesn't affect assessors' work.

Frontend in Astro or Next.js. For your visibility, the public register is a marketing tool; we build it so that search engines index every certificate as its own page. For the assessor workspace, we use React with TanStack Table for the heavier data table screens.

Document store on S3-compatible storage with KMS. Object storage (AWS S3, GCS, Azure Blob or an EU-hosted alternative), with encryption at rest using KMS keys that you manage; MinIO for on-premises. Versions are stored immutably with object lock where retention obligations require it, and every upload gets an integrity hash in the audit trail.

Authentication via SSO, iDIN, eHerkenning and magic links. SSO on your existing identity provider with MFA for staff. iDIN, eHerkenning or magic links for applicants. Scoped, rate-limited API keys for external clients accessing the register.

Webhooks, retries and API versioning. A retry policy with exponential back-off, a dead-letter queue for failed events, signed payloads, and clear versioning so an integration doesn't break when you add a field to a scheme.

Frequently asked questions.

The questions we get in almost every first conversation.

What is the difference between a certification portal and an LMS?
An LMS handles learning content, progress and, optionally, an exam. A certification portal handles formal issuance: registration, identity verification, payment, assessment by independent reviewers, issuance with legal status (eIDAS QES), a public register, renewals and a revocation flow. The two can complement each other; for training institutes we often build a combination.
Are you replacing an existing certification package or audit management system?
For a small certification, usually not. We come into the picture when your scheme, integrations or publication requirements are so specific that an off-the-shelf package only works with expensive customisation. During the intake, we set your current licence and customisation costs against a custom build. Some clients keep their audit management system in-house and only have us build the customer and register portal.
How do you technically ensure the independence of assessors?
Conflict-of-interest detection runs automatically on employer, previous relationship and region, and blocks assignment as soon as a match is found. Reviewers work blind: they cannot see each other's scores before submitting their own assessment. If their assessments differ, the application is escalated automatically. Every assessment is traceable in the audit trail.
Which eIDAS providers do you integrate with?
Signhost (Evidos), ValidSign, KENA, Adobe Sign, DocuSign and, for specific domains, domain-specific QTSPs. For QES, we work with QTSPs that have a valid status on the EU Trusted List. Which provider fits depends on the scheme, the cost per issuance and your contractual situation; we advise on this.
How well is the public register protected against misuse or scraping?
We build in rate limiting, CAPTCHA for abnormal patterns, and a structured API for parties that need large volumes (with API keys, a contract and logging). Bulk export goes through a formal connection, not through scraping. For sensitive schemes, we can restrict search to an exact match on certificate number.
How do you handle the right to be forgotten for revoked certificates?
A revocation leaves the certificate visible with the status 'revoked' and the date, which is precisely the purpose of publication. Personal data of an applicant who was never certified is destroyed after the retention period. For revoked certificates, a retention obligation often applies on your side; we build this trade-off as an explicit workflow with a final check by your data protection officer.
Do you work with our current IT partner or our internal IT team?
More often than not, yes. We deliver the codebase, build instructions, architecture overview and runbook so that an external maintenance provider can take over, a deliberate design choice to avoid vendor lock-in. Some clients keep us on under a maintenance contract; others hand maintenance to their own team.
Can a certification portal run on-premises, or does it have to be in the cloud?
Both are possible. For government or accreditation-sensitive environments, we run the stack in a Dutch single-tenant private cloud or your own data centre. For other contexts, we use an EU-based cloud in consultation with you. In both scenarios, the encryption keys stay with you.
What if we want to add an extra scheme along the way?
That is why we build the scheme engine as data, not as code. A scheme administrator can set up a new scheme or a new version themselves via an editorial interface. For schemes with entirely new technical requirements, we do a short further-development sprint.
What determines the cost?
The biggest cost drivers are the number of schemes, the complexity of the assessment process, the depth of the integrations (payment, accounting, external registers, accreditation reporting), the requirements around eIDAS QES and publication, and the migration of existing certificates. We work with fixed sprint budgets so you can adjust the scope sprint by sprint.

Talk to us about your certification portal.

A no-obligation introductory call of half an hour. We listen to your scheme, ask about your issuance volumes, assessment process and publication requirements, and give you direction you can actually use — even if the outcome is that an existing package suits you better than custom software. You can find more about our approach on the web development overview page.

Fabian van Dijk Business developer fabian.vandijk@appfront.nl
Share LinkedIn Email

Edit content