Training compliance tracking and certificates, handled
Training providers and in-house training teams issue certificates, keep records and remind people about refreshers, often from spreadsheets. We build a workflow that reads completions from your LMS or registers, issues certificates once the trainer confirms, keeps records per learner and employer, sends refresher reminders before qualifications expire and prepares compliance reports for employer clients. A typical build costs $1,000 to $2,500 and takes about four weeks.
The problem
Why training records and refreshers slip
Certificates are often made by hand from a template after each course, and records of who completed what live in the LMS, a register and a spreadsheet that do not quite agree.
Many qualifications need refreshing. Employers expect a reminder before their staff's training lapses, and a provider that sends one keeps the repeat booking. Without automation, reminders depend on someone checking the spreadsheet.
What we build
What our training compliance tracking includes
Completion capture
Completions read from Moodle, Canvas or your registers once the trainer confirms attendance and assessment.
Certificate issue
Certificates generated from your template with a unique number and QR verification link, and emailed to the learner.
Training records
One record per learner with courses, dates, certificate numbers and expiry dates, grouped by employer.
Refresher reminders
Reminders to learners and employers before expiry, with a booking link for the next course.
Employer reports
A report per employer client of staff trained, due and overdue.
Verification page
A simple page where an employer can check a certificate number is genuine.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Course completed
The trainer confirms attendance and assessment in the LMS or register.
-
02
Automated
Certificate issued
A numbered certificate is generated and sent.
-
03
Automated
Expiry tracked
The record stores the expiry date and schedules reminders.
-
04
Staff review
Team checks
Staff check certificates for unusual cases and employer reports.
-
05
Head of school or programme lead decides
Assessment outcome
Whether a learner has passed is decided by the trainer or assessor, never by the workflow.
How it behaves
How certificates and reminders behave
What learners and employers see
- A certificate soon after completion
- A reminder before training expires, with a booking link
- Regular reports for employer clients
What the course team sees
- One record per learner and employer
- Certificates to check in unusual cases
- Upcoming expiries and refresher bookings
What the automation does
- Issues certificates after trainer confirmation
- Schedules refresher reminders
- Never decides an assessment outcome
Edge cases and fallbacks
- Learner completes part of a course
- No certificate; the record shows partial completion for staff.
- Name spelt wrongly on a certificate
- Staff correct the record and the certificate is reissued with the same number.
- Employer no longer a client
- Reminders go to the learner only.
- LMS or n8n outage
- Certificates are issued once the run retries, and staff are alerted.
Architecture
Training records and certificates at a glance.
- Input
- Logic and services
- Output
- Data
- People
How it flows
- 1 Completions confirmed by the trainer are read from the LMS or register.
- 2 Numbered certificates with a verification link are issued and records updated.
- 3 Refresher reminders go to learners and employers before expiry.
- 4 The course team checks unusual cases and sends employer reports.
Project planner
How the project runs, phase by phase.
Training records, certificates & refresher reminders project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
Courses, certificate templates, expiry rules, LMS data and employer reporting.
-
02
Design
2 to 3 days
Record layout, certificate numbering, reminder timing and report format.
-
03
Build
1 to 2 weeks
Completion capture, certificates, records, reminders and verification page.
-
04
Shadow run
About 1 week
Certificates generated alongside the manual process and compared.
-
05
Launch
1 to 2 days
Switch on and import existing records.
-
06
Support
Ongoing
New courses, templates and expiry rules.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Courses, templates, expiry rules and reports.
$200 – $400
-
Build
Completion capture, certificates, records and reminders.
$500 – $1,300
-
Integrations
LMS, storage and email.
$150 – $400
-
Testing and shadow run
Certificates compared with the manual process.
$100 – $250
-
Launch and training
Record import and team walkthrough.
$50 – $150
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Importing large historical records may add to the build. LMS, storage and n8n are billed to you directly.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- Storage and email: Your Microsoft 365 or Google Workspace plan.
- n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
EU and UK: learner records
Learners are told how long their training records are kept and who sees them, as GDPR Article 13 (and UK GDPR) requires.
Source: gdpr-info.euAssessment stays human
Certificates are issued only after a trainer or assessor confirms the outcome; the workflow never marks anyone as passed.
EU AI Act: no automated assessment
AI systems used to evaluate learning outcomes are listed as high-risk in Annex III, so we do not use AI to grade or pass learners.
Source: artificialintelligenceact.euFree tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Training records, certificates & refresher reminders questions, answered.
Keeping a record of who has completed which training, when it expires and who is due a refresher, and being able to report it to employers or auditors.
Yes. Records are grouped by employer, and each client can get a regular report of staff trained, due and overdue.
Each certificate has a unique number and a QR link to a verification page that confirms the learner, course and date.
No. The trainer or assessor confirms the outcome in the LMS or register, and only then is a certificate issued.
Yes. We clean and import existing records so reminders start from day one.
Certificates issued on the day of completion, refresher bookings from reminders, overdue learners per employer and time spent producing reports.
Free 20-minute call
Want this for your schools & training?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for schools & training
All servicesEducation CRM & enquiry pipeline
Every family or learner enquiry from web, phone, open days and social in one education CRM, with tour bookings, polite follow-ups and a weekly view of enquiries, visits and applications by source.
From $1,000 · About 4 weeks Details
Admissions documents, offers & enrollment
Applications checked for missing documents, reminders sent to families, assessment and interview slots booked, offer and acceptance steps tracked and enrollment forms collected before the first day.
From $1,000 · About 4 to 5 weeks Details
AI assistant for parents & learners
An AI assistant on your website and help inbox that answers term dates, fees, uniform, transport, course and policy questions from your approved information, in several languages, and passes anything personal or sensitive to staff.
From $2,500 · About 5 to 8 weeks Details