Start the project. The dates set themselves.
Enter the start date, the qualification and the funder. Sidus works out the key compliance dates and shows it clearly if anyone later types over one.
Sidus runs a funded training project from the first enrolment to audit day. It is built around SETA and QCTO compliance, so your projects are ready for a verifier on any day, not only the week before.
Already using Sidus? Log in to your provider account
Built for programmes funded or quality-assured by
Sidus was not designed in a boardroom. It was designed in training rooms, at assessment tables and in front of POE boxes.
For more than eleven years I have worked inside SETA-funded projects as a facilitator, assessor and moderator. The people were good. The learners showed up. The work was done.
What failed, again and again, was everything around the work: the same gaps, at every provider, on every project. So I wrote them down, and built the system that closes them.
Every report is rebuilt by hand from registers, spreadsheets and memory, usually the night before it is due.
The same learner is captured in Excel, in an email, on a form and in a folder. No two copies agree.
Compliance dates live in one person's head. When that person is busy or away, the date passes quietly.
An ID number, a start date, a signed register. Nobody notices it is missing until a claim depends on it.
Each person holds one piece. Managers and owners find out a project is in trouble when it is already late.
Registers and dropout requests travel by WhatsApp and word of mouth. The office hears days later, or never.
Six gaps. One system that closes each of them.
Scroll through the life of a funded project. Each stop shows what Sidus does and which gap it closes, and is marked as live today or coming next.
Enter the start date, the qualification and the funder. Sidus works out the key compliance dates and shows it clearly if anyone later types over one.
Upload the class list. Every row is checked before anything is saved, and you are told exactly which rows need fixing and why.
Module dates move with days off and extra days. Once training has started, a change needs a reason and is kept on record.
The facilitator marks attendance per training day, once. The office sees it straight away. Print a blank register for signatures whenever you need one.
A to-do list per role: registers missing, results due, reports due, dropout requests waiting for a decision. Nothing relies on someone remembering to ask.
Assessors record competent or not yet competent per learner. Moderators sample, then agree or overturn with a reason. Nobody moderates their own finding.
Every handover of the portfolios of evidence has a planned date and a recorded actual date, from the facilitator through to external readiness.
Budget, rates and payment tranches are kept with the project, visible to the office and hidden from practitioners. Stipend payments and finance exports are next.
Because registers, results and moderation are already in Sidus, the project report, the NLRD file and the WSP / ATR export come from what was captured, not from a weekend of typing.
Who changed the plan, who corrected an ID number, who approved a dropout, when and why. It is all on record, for every project.
A small working sample of Sidus. Do the two jobs on the to-do list and watch the project respond.
DEMO-26-01-01 · Business Administration · NQF 3
Today's register is not capturedModule 2 · Day 3 of 8
Module 1 results are due6 learners · summative assessment
Nothing owed. This project is up to date.
Module 2 · Day 3 of 8 · today
| Learner | Attendance |
|---|
Register saved.
Module 1 · summative · C = competent, NYC = not yet competent
| Learner | Result |
|---|
Results saved.
Register captured, results recorded, nothing owed. Imagine that across every project you run.
A simplified sample. The names are made up and nothing you click here is saved or sent anywhere.
From the owner who needs the whole picture to the learner who wants to know where they stand. Each person logs in to a screen made for their job and sees only what they should.
Every project, every learner and everything that is owed, on one screen. Know which projects are healthy and which need you, before a funder tells you.
LivePlans, practitioners and compliance dates across all projects. Approve changes with a reason on record.
LiveSet up the project, link the team, watch the timeline, and decide dropout requests.
LivePOE handovers, calendars and who is doing what, without chasing people for an update.
LiveCapture learners once, import from Excel, and stop retyping the same details into five places.
LiveProject budgets and tranches today. Stipend payments, tracking and exports are next.
Budget liveStipends comingWhich agreements are ending soon, who you have worked with, and who is worth another conversation.
ComingA morning to-do list, registers per training day, and dropout requests sent to the office with a reason.
LiveRecord results per learner, re-assess with every attempt kept, and see what the moderator decided.
LiveSample learners per module, agree or overturn with a reason. Never moderate your own finding.
LiveTheir own journey at their fingertips: a mobile app where a learner can follow their attendance, their results and how far they are from the finish line.
Mobile app comingA short online session. You see the real system and ask every awkward question you have.
Load one of your own projects and use Sidus for a month with your own team.
You have seen it work on your own project, so you decide whether to carry on.
We are opening Sidus to a small group of South African training providers. Founding providers work directly with the person who builds it, and their feedback decides what gets built next.
Ask about the pilotTell us a little about your organisation and we will set up a time. Or skip the form and just say hello.