Classroom teachers
Break a scheme of work into concepts once, then pull practice and assessment questions from it all year.
A workshop for teachers human-guided AI
KIE is a workshop, not a shop. Nothing is pre-made and nothing is sold to you off a shelf. You bring your own course material, break it into concepts, connect them, and generate questions from the structure you approved. AI is the tool on the bench — you're the one making the thing.
KIE specialises in three areas of question intelligence.
Start with an existing or past-paper question. KIE breaks it back into the concepts, relationships, information, reasoning path and thinking demand behind it. The teacher can then rebuild the same knowledge into a new question without simply copying the original.
Explore reverse engineering → 02 Multi-concept engineeringCombine one, two or more approved concepts only when their relationship matters. KIE lets the teacher control which concepts are joined, how they interact and how much conceptual load the learner must handle in a single question.
Explore multi-concept questions → 03 Higher-order thinkingMove beyond easy, medium and hard. Build questions that require learners to understand, apply, analyse, evaluate, create or transfer knowledge. Difficulty comes from the reasoning architecture, not simply from longer wording or larger calculations.
Explore higher-order thinking →KIE — Knowledge Intelligence Engine. Three words, and each one is doing a job.
Not files and not text. The subject broken into concepts, the links between them, worked explanations, examples and the mistakes learners actually make — held in a structure you can open and edit.
Reasoning about that structure: which concept a question really tests, what depth it demands, which relationship it depends on, and what a correct answer has to show.
Something you build once and run repeatedly. Engineer a concept properly and it keeps producing questions, explanations and practice for as long as you teach the subject.
Put together: KIE engineers knowledge rather than generating text. A chatbot writes a plausible question and forgets it. A shop sells you someone else's. An engine builds the knowledge first, keeps it, and derives the question from it — which is why the work you put in on Monday is still working for you next term.
It isn't a study chatbot and students don't use it to generate anything. A teacher engineers the knowledge and approves the questions; students get a practice area containing only what that teacher published.
Which suits three kinds of teaching in particular:
Break a scheme of work into concepts once, then pull practice and assessment questions from it all year.
Take a past paper question, see exactly what it tests, and produce a new one at the same standard in a different setting.
Agree the concept map as a department so everyone teaches and tests against the same approved structure.
The first topic takes real work — this is a workshop, not a vending machine. What you get for it is a structure that keeps producing questions long after the setup is done, and each step leaves something you can check before the next one starts.
Add books, notes and handouts, and set the subject boundary so unrelated material stays out.
Large subjects become topics, subtopics and concepts small enough to teach, check and reuse on their own.
Say how concepts relate: what depends on what, what explains what, what should be compared with what.
Add the meaning, the first principle, a worked example, a real-world use and the mistake learners usually make.
Choose the concepts, the type of thinking and the context. KIE drafts the questions; you keep the ones that work.
Approved questions and explanations go to the practice area, where learners work through them at their own pace.
This is the knowledge engineering loop in full. Three things feed the engine: your approved subject content, your rules about what counts as correct, and a language model that drafts and analyses. Nothing leaves the engine without passing you first.
Every draft stops at your review. That one gate is the difference between a question bank you trust and one you have to re-check.
Approved material is stored and reused for later questions, so the same ground isn't paid for twice and the wording stays consistent.
Saving, loading and approving are free. The model is called when you ask it to draft or analyse, and not otherwise.
Most tools generate a question and forget it. KIE keeps six layers connected, so you can always open a question and see which concept it tests, which relationship it depends on, and which part of your source material it came from.
Sets the boundary. Nothing outside it can leak into a question.
A major area of the subject, roughly the size of a unit.
A narrower area inside the topic, closer to a single lesson.
The principle, process or idea a learner has to understand.
How one concept depends on, explains or contrasts with another.
Tests recall, application, reasoning, comparison or transfer.
A reworded question tests the same thing twice. KIE changes what the question asks the learner to do — and it works in both directions: from a concept to a question, and from a question back to the concepts behind it.
When the learning objective is clear, one concept is enough. No padding, no unrelated data to wade through.
Combine concepts when the link between them is the point. Two is the normal case. Three at once only where the question genuinely needs all three, otherwise you're testing stamina rather than understanding.
Paste in a past paper question. KIE works out what it really tests, what reasoning it needs, and what information in it is doing nothing.
The same reasoning, moved to a different organisation, sector, role or constraint. This is where you find out whether it was understood or memorised.
A learner can know NPV and know what a discount rate is, and still not see how one moves the other. That gap only shows up when a question makes them use both at once. KIE builds those questions from the relationship you have already approved, so the connection being tested is one you chose.
Enough to test a relationship without burying it in detail.
For genuinely integrated questions. Past that you're testing stamina, not understanding.
Concepts are only combined inside the same subject, so nothing unrelated leaks in.
If you haven't approved both concepts and the link between them, KIE won't combine them.
A higher discount rate cuts the present value of later cash flows more than earlier ones.
The board wants the appraisal redone at 12% rather than 8%. Explain which of the two projects now ranks higher, and why the timing of the cash flows matters more here than the total.
Once the question exists, the same structure runs backwards: KIE reverse engineers the reasoning and writes a fresh question on it for a different company, sector or set of constraints.
KIE develops the concept itself first — what it means, the principle underneath it, how the process runs, what it connects to, where it is used and where learners usually go wrong. The question engine then has something solid to work from instead of guessing.
Paste in a past paper question. KIE works out which concepts it draws on, which relationships it depends on, its dimension and depth, the reasoning pattern it expects, and which numbers in it are doing nothing at all. Then it writes a new question that tests the same knowledge somewhere else.
Useful two ways round: to check that a question you wrote tests what you think it does, and to turn one past paper question into a set.
Two questions can carry the same marks and still ask for completely different work. In KIE you set the level of thinking a question demands — understanding, application, analysis, evaluation, creation or reasoning across several concepts at once.
Meaning, first principles and why the concept works, before anything is manipulated.
Calculations, decisions and practical situations, including examples not seen in class.
Spot the concepts, assumptions, relevant data and the reasoning path a solution needs.
Weigh alternatives, explain trade-offs and say when a method stops being suitable.
Design a solution, a scenario or a question by combining approved concepts.
Same principle, new setting. The clearest test of whether learning has stuck, and where multi-concept questions do most of their work.
A hard concept gets easier when it is attached to a familiar place, object or decision. KIE can open with that experience and walk outwards from it, one step at a time.
KIE uses AI to suggest and analyse, never to publish. Knowledge, relationships and questions all sit in a review queue until you approve them — and once approved, they are reused instead of regenerated, so the same material doesn't drift between lessons.
AI suggests concepts, relationships, explanations and questions.
You check the accuracy, the terminology and whether it's worth teaching.
Approved material becomes part of the trusted structure learners see.
It's stored and reused for later questions, so nothing is generated twice.
A score on its own says very little. The learning layer we're building reads a learner's answers as evidence — what they understand, which relationships are weak, which misconception keeps returning — and uses that to choose the next explanation or question. It isn't finished yet, and this page will say so until it is.
No. It drafts, and you decide. Nothing reaches a learner until you have read it and approved it, and you can rewrite anything before you do.
Any subject you can describe as concepts and relationships. Boards have been built for maths, chemistry and financial management so far; the structure itself is subject-neutral.
Questions are generated from concepts you have already approved, inside a subject boundary. Where a real-world example is used, KIE is told not to present it as current fact unless it appears in your source material.
No. Saving, loading and approving are free. Only the generate and analyse actions call the model, and approved answers are stored and reused rather than regenerated.
Reverse engineering is the quickest way in — paste a past paper question and you get the concepts behind it plus new versions in minutes, and the concepts are saved as you go. Building a topic properly from scratch takes a few hours. That's the trade: more work at the start, a structure that keeps producing afterwards.
Email hello@kieindia.online with your subject and level, and we'll set you up with a workspace and a sample board.
Your judgement, AI on the bench, and a structure you can actually see.