Accredited workplace training · 6 staff · 13 multinationals across 26 countries
One programme, 13 platforms
Open a part, then hover a box for detail or a button to see it working.
AutomatedAIPersonYes or noSourceDataResult
One spine out to 13 platforms, and support back in · hover anything, or click it to open that part
A · Win the work
A referral from an earlier client, then the real goal named: procurement, platform standards and mandated completion, all outside the provider's walls.
A 2-day workshop pitched at chief executive level gave a large buyer something to say yes to.
B · Accredited spine
One accredited course, written for UK construction sites, rewritten for the petrochemical industry:
Different hazards, site language and scenarios
A different chain of command
Ofqual and NCFE accreditation held through the full rewrite.
C · Client layer
Each buyer's house terminology, site rules and induction context, written in on top of the sector rewrite, with animation briefed the same way each time.
Course personalisation from 3 to 4 weeks down to 8 days (observed).
D · SCORM package
Packaged to the standard each client's own learning platform accepts, with platform behaviour, access and completion rules set per estate.
Hands-on effort per client from 40 hours down to 18 (observed).
E · Learner completes
The custom web app caches every page as it completes, even with no internet.
Built for someone completing a mandated course in a portacabin, offshore, or on a site with poor connectivity.
F · Support board
Every issue becomes a ticket on the ClickUp board, tagged by client, deployment, type and severity.
Priority access is a tier on the same board, so what has to move first does.
Outcomes held?
A person confirms the accredited learning outcomes still hold before any version ships.
The sector rewrite and every client adaptation pass this gate.
13 client estates
13 multinationals across 26 countries, each running the programme inside its own learning platform, with its own completion rules.
Measured, and published by the provider. Letters stand in for the clients.
Slack
Tickets route through Slack to the developer: one hop from a learner's problem to the person who can fix it.
Developer
Fixes go back out to the estate that raised them.
Access grants and progress resets run in bulk, at the volume an enterprise rollout produces.
Directors’ metrics
The metrics and reporting the directors ran the business on.
5 years as fractional commercial and operations lead, advising the directors throughout.
Accredited byOfqualNCFE
No: back to the rewrite
No: back to adapting
Yes: restored from backup
Tagged byClientDeploymentTypeSeverity
No: the main queue
BAccredited spineOne accredited spine with 13 deployments on top, illustrative
One accredited spine, 13 deployments on topillustrative · letters stand in for the 13 multinationals
Own learning platform
Each client runs the programme inside its own learning system, on its own standards, as part of contractor induction.
The client's own administrators run the package inside their own system.
Deployment layer
Set per estate:
Platform behaviour
Access arrangements
Completion rules
The single decision that let 6 people service 13 enterprise estates at once.
Client layer
Rewritten for each buyer:
House terminology
Site rules
Induction context
Course personalisation from 3 to 4 weeks down to 8 days (observed).
Sector layer
The course moved out of UK construction and into the petrochemical industry:
Different hazards
Different site language
Different scenarios
A different chain of command
Accredited spine
The accredited learning outcomes every version keeps.
Ofqual and NCFE accreditation held through a full rewrite into a new sector.
Client A
Its own learning platform, its own completion rules and access arrangements, and its own house terms, site rules and induction context.
The same accredited spine and the same sector rewrite underneath.
IllustrativeClient name withheld
Client B
Its own learning platform, its own completion rules and access arrangements, and its own house terms, site rules and induction context.
The same accredited spine and the same sector rewrite underneath.
IllustrativeClient name withheld
Client C
Its own learning platform, its own completion rules and access arrangements, and its own house terms, site rules and induction context.
The same accredited spine and the same sector rewrite underneath.
IllustrativeClient name withheld
Client D
Its own learning platform, its own completion rules and access arrangements, and its own house terms, site rules and induction context.
The same accredited spine and the same sector rewrite underneath.
IllustrativeClient name withheld
Client E
Its own learning platform, its own completion rules and access arrangements, and its own house terms, site rules and induction context.
The same accredited spine and the same sector rewrite underneath.
IllustrativeClient name withheld
Client F
Its own learning platform, its own completion rules and access arrangements, and its own house terms, site rules and induction context.
The same accredited spine and the same sector rewrite underneath.
IllustrativeClient name withheld
Client G
Its own learning platform, its own completion rules and access arrangements, and its own house terms, site rules and induction context.
The same accredited spine and the same sector rewrite underneath.
IllustrativeClient name withheld
Client H
Its own learning platform, its own completion rules and access arrangements, and its own house terms, site rules and induction context.
The same accredited spine and the same sector rewrite underneath.
IllustrativeClient name withheld
Client I
Its own learning platform, its own completion rules and access arrangements, and its own house terms, site rules and induction context.
The same accredited spine and the same sector rewrite underneath.
IllustrativeClient name withheld
Client J
Its own learning platform, its own completion rules and access arrangements, and its own house terms, site rules and induction context.
The same accredited spine and the same sector rewrite underneath.
IllustrativeClient name withheld
Client K
Its own learning platform, its own completion rules and access arrangements, and its own house terms, site rules and induction context.
The same accredited spine and the same sector rewrite underneath.
IllustrativeClient name withheld
Client L
Its own learning platform, its own completion rules and access arrangements, and its own house terms, site rules and induction context.
The same accredited spine and the same sector rewrite underneath.
IllustrativeClient name withheld
Client M
Its own learning platform, its own completion rules and access arrangements, and its own house terms, site rules and induction context.
The same accredited spine and the same sector rewrite underneath.
IllustrativeClient name withheld
Every client’s variation sits in the two layers above the rewrite, so the accredited outcomes underneath stay the same in every version. Hover a layer or a client for detail.
●QualityAccreditedOfqual and NCFE, held through a full rewrite
●Efficiency6 staffserviced 13 enterprise estates at once
ELearner + recoveryWhat happens to progress when the signal drops, illustrative
What a dropped connection did to progress, before and afterillustrative · an example course of 8 pages
Progress was lost in live use, on a mandated course. The response ran in two steps, and the order is the story: restore from backup first, because people needed their afternoon back, then cache every page as it completes so a dropped connection costs nobody anything.
FSupport + metricsThe ticket flow to the developer, and the directors' view, on synthetic data
The support board, one morningillustrative · synthetic tickets on a ClickUp-style board
New
Triaged
With the developer
Done
Priority tiermoves first
Access needed before a site induction
Client DClient platformAccessHigh
Course behaves differently after a change at the client's end
Client AClient platformDeploymentHigh
Main queuesorted by tags
Reset progress for a cohort
Client FClient platformAccessNormal
Update house terms in one unit
Client KClient layerContentNormal
Progress lost mid-course
Client CWeb appProgressHigh
Grant access to new starters
Client HClient platformAccessNormal
Reissue a completion certificate
Client BWeb appCertificateLow
Slack, to the developerPriority · Client A · Deployment · Highmoved to With the developer
Every ticket carries four tags: client, deployment, type and severity. The tags and the priority tier sort the queue, and the team decides which client’s issue matters most this morning. Hover a ticket for what happens next.
The directors’ viewillustrative layout · the tiles are real, the chart synthetic
▼Time saved3–4 wks → 8 daysto personalise a courseobserved
▼Time saved40h → 18hhands-on per clientobserved
Tickets this quarter, by type, across the 13 clients
The three tiles carry the real figures, each marked. The chart runs on synthetic tickets to show the shape of the view the directors ran the business on.
Referral
The work arrived as a referral from an earlier client, who had watched a CRM and then a tender engine being built.
Work delivered well at one client bought the next one.
Real goal named
The stated goal was more sales. The real one sat outside the provider's walls:
Procurement
Platform standards
Mandated-completion mechanics
A global operator mandates training through its own learning system, on its own standards, as part of contractor induction.
2-day workshop
A 2-day workshop pitched at chief executive level, built off the founder's contact at a global operator.
It gives a large buyer something specific to say yes to.
Sales process
The sales process that carried a 6-person UK provider into a multinational client base, with the value set out in the buyer's own terms:
Efficiency up
Labour cost down
Revenue up
The partnership development that reached the client base was supported alongside.
Accredited course
One course that worked, written for UK construction sites.
Ofqual and NCFE accredited
The accreditation is a large part of what the buyer pays for
Sector rewrite
Rewritten for the petrochemical industry:
Different hazards
Different site language
Different scenarios
A different chain of command
Harder than writing a new course, because the learning outcomes have to survive the rewrite intact.
Outcomes held?
A person checks the accredited learning outcomes still hold before any version moves on.
The moment the outcomes move, the accreditation stops holding.
Fixed spine
The spine every version keeps. Ofqual and NCFE accreditation held through the full rewrite into a new sector.
Every client's variation goes into the layers above it.
Client brief
Each of the 13 buyers brings its own:
House terminology
Site rules
Induction context
Adapted
The content is rewritten for that buyer on top of the sector rewrite. The spine underneath stays as it is.
Animation brief
Animations carried a large share of the content. Each brief goes to the animation team in one repeatable shape.
At 6 staff, nobody has to remember how last time worked.
Assets back
Assets come back in a repeatable shape, ready to drop into that client's version.
Outcomes held?
No adaptation ships until a person confirms the accredited outcomes still hold.
On subject matter this sensitive, the review gate is the product.
8 days
Course personalisation from 3 to 4 weeks down to 8 days.
Observed across those engagements.
Client version
The spine, the sector rewrite and that client's layer, ready to package.
SCORM package
Packaged to the standard each client's own learning platform accepts.
The infrastructure was specified and directed here, and the packaging coordinated. The packages were authored by others.
Client platform
Each buyer runs the programme inside its own learning system, as part of contractor induction, and its own administrators run the package.
A course anywhere else is a course nobody is required to complete.
Set per estate
Every deployment is slightly different, so each estate gets its own settings:
Platform behaviour
Access arrangements
Completion rules
Hands-on effort per client came down from 40 hours to 18 (observed).
Bulk access
Access grants and progress resets at the volume an enterprise rollout produces, handled in batches.
Priority access is a tier of its own, so the clients who must move first do.
13 · 26
13 multinationals across 26 countries, measured and published by the provider.
6 staff serviced 13 enterprise estates at once, because the variation sits in the deployment layer.
Learner starts
Someone completing a mandated course in a portacabin, offshore, or on a site with poor connectivity.
Page completes
Each page saves the moment it is finished.
Cached per page
The custom web app caches every page automatically, even with no internet.
Progress survives a lost connection.
Progress lost?
When progress was lost in live use, the fix ran in two steps:
First, restore from backup, so people got their afternoon back
Then remove the cause, by caching every page as it completed
Completed
Learners on sites with no connectivity completed and recovered a mandated course.
Routes on the provider's own platform issue a completion certificate.
Issue raised
A learner's problem, a client's request, or a change at one client's end that surfaces with no obvious cause.
Tagged
Every issue becomes a ticket on the ClickUp product board, tagged so the queue sorts:
By client
By deployment
By type
By severity
Priority tier?
Priority access is a tier on the same board, so the clients and issues that have to move first do.
Triage
A person stays on the triage. The tags and the tier sort the queue, and the team decides which client's issue matters most this morning.
Slack to developer
Tickets route through Slack to the developer, so a learner's problem is one hop from the person who can fix it.
Directors' metrics
The metrics and reporting the directors ran the business on, so every change could be checked against something.
5 years as fractional commercial and operations lead, advising the directors throughout.
Sell · Deliver · Train
Every engagement has the same shape:
Sell: finding the real problem, and winning the work
Deliver: building what fixes it
Train: handing it over so the team runs it
When a client gets the value they want, they're more inclined to do more.
Once they see what is possible, they bring their own ideas to the table, ready to be implemented.
Slack, to the developer