A learning platform that holds up on exam day

Usually a mix. We already own a learning and testing platform that covers courses, groups, assessments, certificates and reporting, so most jobs start there and we build only what is particular to your organization. If you already pay for an off-the-shelf platform, we can extend it, join it up with your other tools, or replace the parts it cannot do. The first call is where we work out which of those costs you least, and the answer goes into a written price before anything is built.

That is the whole test of a learning platform. Exam traffic does not spread itself across the week. It lands in one window, often the same window for every learner. We size the platform for the biggest sitting you expect, test it against that before it goes live rather than after, and keep a way to undo a release that goes wrong. Once live it sits under constant watch with alerts. Timed sittings, attempt limits and automatic saving mean a dropped connection does not cost somebody their paper.

Every job starts with a call, then a written price, a date and a list, before any code is written. You are not billed by the hour against an open-ended discovery. The price depends on how much of the platform we already own fits you and how much is particular to your rules, so the call is where that gets decided. After launch, keeping it going is a separate monthly fee: somebody watching it, fixes within a promised time, security updates, improvements and a written report. Both numbers are on the table before you commit to either.

We keep it going. That is half of what we do, and it is a paid monthly arrangement rather than a favor. It covers alerts, fixes within a promised time, security updates, and a queue of improvements that you put in order. Every month you get a written report: what changed, what broke, what we fixed and what is next. The people who built the platform are the people who maintain it, so nothing is handed to a support desk that has never seen it.

You do. Learner details, attempt logs and certificate history are yours, and so is the code. We build export routes so you can pull all of it out in a usable file without asking us first. You set how long records are kept and the platform enforces it, so they last exactly as long as your awarding body, regulator or employer contracts require, and no longer. Attempt logs and marker actions are timestamped and cannot be quietly altered, which is usually what an auditor wants to see. Where you have to, we can pin which country the records sit in.

Yes, and it is a proper part of the build, not an afterthought. First we write down what you hold now: a download from your current platform, old course files, spreadsheets, or a mix of all three. Then we agree what comes over: learner records, completion history, certificates with their expiry dates, and question banks. The move is rehearsed on a copy first, so you see the result before it becomes real. Where old course material has to keep working, we support the common file formats rather than asking you to rebuild every course.