The machine does the setup. You do the judging.
Oksara is a teaching platform for secondary schools. It does the hours of preparation around a lesson — the plan, the tasks, the groupings, the first pass at marking — and gives each one back to you as a decision rather than a blank form.
Start here
- Join with a class codeYour facilitator gave you a code.
- Sign inYou already have an account.
- Set up an institutionYou want this running at your school.
Teaching at a school already using Oksara? Create your account with the code your school gave you.
What it does
Seven pieces of work that used to be yours. Each one ends with you approving, adjusting or refusing what it produced.
It reads the syllabus
Upload the document you were given. Oksara returns a competency tree, a week-by-week scheme of work and the assessment points, with every line traceable back to the sentence it came from. You approve it or change it.
It writes the practical work
Tasks grounded in something a student can actually do, at three levels of difficulty, so one class does not need three sets of worksheets. Every task also comes in a version that needs nothing but paper.
It decides who sits with whom
Teams built on evidence of what each student can already do, for the outcome you pick — balanced, peer teaching, complementary skills. The reasoning for every placement is on screen, and you can swap anyone.
It marks the first pass
Work is scored criterion by criterion against your rubric, with the evidence quoted from the student's own answer. You adjust what you disagree with and release it. Nothing reaches a student before you do.
It notices what you cannot
Where a class is quietly getting the same thing wrong, where a student has stopped handing work in, where a question is being misread rather than failed. Each observation arrives with one thing you could do about it.
It rolls up to the department and the school
Coverage, marking turnaround, and where a colleague is carrying too much — at class, department and school level. Every figure says what it is being compared against.
It reads handwriting
Photograph a handwritten script and Oksara transcribes it, learning the letters each student actually forms so it gets better at reading that student. Anything it is unsure of is handed back to be confirmed, never guessed at.
What it will not do
These are constraints in the code, not promises in a policy.
It does not invent
Every outcome in a generated plan is anchored to a span of the document you uploaded. Anything the model produces without one is discarded before you ever see it.
It does not decide
A plan, a task, a team and a mark are all proposals until a person approves them. There is no path through the product where generated work reaches a student on its own.
It does not rank teachers
A department head sees who needs support and why. There is no league table, and no endpoint that could produce one.
It does not accuse a student
Where a piece of work looks unusual you are shown what was observed. Oksara records observations; the judgement is yours.
Built for the room it runs in
It works with the network off
A student handing work in and a facilitator marking it both work offline. What you did is held on the device and sent when the connection returns, and the screen always tells you which state you are in.
It works on the phone that is actually there
Designed at 360px first, with everything reachable in the thumb zone. The wide screen is the widened case, not the other way round.
It works on paper
Every practical task has a version that needs no equipment, and handwritten work can be photographed and handed in.
Bring it to your school
Oksara runs per institution, with departments, terms and classes set up before anyone signs in. Read what that involves and what to send us.
What setting up involves