KCSE common mistakes
KCSE · Understand the traps and how to avoid them.
In Business Studies and Accounting questions, the candidate writes a narrative paragraph describing a ledger, trial balance or cash-flow statement instead of presenting the ruled account with debit and credit columns, dates, particulars and balanced totals. Marks are lost even when the underlying arithmetic is right.
Candidates memorise definitions and revise by reading notes rather than practising the layout. Under exam pressure they default to prose because it feels faster, and many have never been drilled on the requirement that a 'prepared' account must show its format and be balanced.
What to do instead
Build a one-page template sheet for every account type examined (three-column ledger, trial balance, petty cash book, manufacturing account, departmental trading account, cash-flow statement). Practise ten past-paper items per template until the layout is automatic, and always finish with a double underline and the words 'balance c/d' or 'balance b/d' where required. In the exam, draw the ruling first, then fill figures.
In technical drawing and workshop-technology items, the candidate produces a freehand sketch with no construction lines, no scale statement, no title block and no dimensions, when the question asks for a drawing to a stated scale.
Candidates confuse 'sketch' with 'draw' and underestimate how much of the mark scheme is allocated to construction accuracy, line types and standard conventions. Time pressure in a paper with several drawing questions encourages rushing the setup.
What to do instead
Learn the mark allocation pattern: typically marks for outline, hidden detail, centre lines, dimensions, scale and title block. In practice, time yourself doing full drawings with instruments, including the title block, and mark your own work against the checklist. In the exam do the title block and border first so they cannot be forgotten.
In Agriculture and Biology practical items, the candidate describes a specimen or a farm practice in general terms ('the soil is good', 'the plant is healthy') instead of making specific observations tied to named features, measurements or reasons.
Candidates revise content topics but not the observation-and-inference skill. They do not know that practical questions reward named structures, stated functions and justified conclusions, so they write what they remember rather than what they can see or infer.
What to do instead
Practise with real specimens: for each one write three observable features, one measurement, and one inference with a reason. Learn the vocabulary of description (colour, texture, shape, margin, venation, root type). In the exam, answer observation first, then inference, and always attach 'because...' to any judgement.
In Business Studies case-study questions, the candidate ignores the scenario and writes a textbook answer about 'a business' in general, missing the named firm, its figures and the specific decision asked for.
Candidates treat case studies as decoration around a recall question. They have practised definitions but not application, and application marks are usually the largest block in the mark scheme.
What to do instead
Adopt a fixed routine: underline the firm's name, the figures and the instruction verb (advise, evaluate, recommend). Then write every point using the firm's name and at least one figure from the case. Practise by rewriting generic answers into applied ones and comparing against mark schemes to see where application marks sit.
In Computer Studies and technical subjects, the candidate writes program code or a procedure as an unindented block with no declared variables, no input/output statements and no error handling, when the question asks for an algorithm or pseudocode.
Candidates learn syntax by reading rather than writing, so they omit declarations and I/O. They also do not realise that pseudocode is marked for logical structure, not for compiling correctly.
What to do instead
Use a standard pseudocode convention and stick to it: START/STOP, declare variables, INPUT and OUTPUT statements, indented IF and LOOP blocks. Hand-write solutions to past-paper algorithm questions and trace them with sample data on paper to prove they work. Include a validation step whenever input is mentioned.
In Mathematics and Physics items inside technical and applied papers, the candidate writes only the final answer with no formula, substitution or units, and loses method marks even when the answer is correct.
Candidates believe the answer is what is marked and are anxious about running out of time. Many have never seen a mark scheme showing that method carries most of the marks.
What to do instead
Train a four-line habit: state the formula, substitute with units, compute, then state the answer with units and appropriate significant figures. Do timed sets of ten numerical questions where you mark only the method lines. Never erase working; cross out cleanly if you revise it.
In Home Science, Clothing and Textiles, and Art and Design papers, the candidate answers the 'design' or 'practical' question with a written description only, omitting the labelled diagram, colour key or pattern layout that the question explicitly requires.
Candidates avoid drawing because they lack confidence and because they revise theory sections only. They misread 'illustrate' or 'show' as 'describe'.
What to do instead
Keep a list of instruction verbs that demand a visual response (draw, illustrate, label, show, design, indicate) and rehearse a response for each. Practise producing labelled diagrams with a ruler, clear labels outside the drawing and a key where colour or shading is used. Budget time for the drawing before starting the written part.
In Business Studies and Accounting, the candidate confuses terms that look similar, for example capital versus revenue expenditure, profit versus cash, or a balance sheet versus a profit and loss account, and uses them interchangeably in the same answer.
These pairs are learned as vocabulary lists rather than as concepts with distinct treatments in the accounts. Candidates do not test themselves on discriminating between them, so the confusion survives into the exam.
What to do instead
Build a contrast table for each confusable pair: definition, one example, where it appears in the final accounts, and effect on profit. Then answer past-paper questions that deliberately test the distinction, and explain aloud why the wrong option is wrong. Ask yourself before writing: does this item change profit, cash, or both?
The candidate answers more questions than required in a section, or splits effort across all optional questions, so none is completed to full depth and time runs out before the compulsory section is finished.
Fear of leaving a question blank and poor time budgeting. Candidates do not read the rubric carefully and do not know the mark value per section before starting.
What to do instead
In the first two minutes, read the rubric and write the mark allocation and a time budget beside each section. Decide optional questions before writing anything. Practise full papers under timed conditions and review where time was lost. If a question stalls, leave a gap and return, but never start an extra optional question.
In technical and applied practical papers, the candidate writes a procedure or method as a vague list ('set up the apparatus, take readings, conclude') without stating quantities, instruments, safety precautions or how the result will be used.
Candidates recall the shape of a method but not its operational detail, and they have rarely written a method that someone else could follow. Mark schemes reward precision: named apparatus, stated measurements, controlled variables and a stated inference.
What to do instead
Write methods for past-paper practicals in numbered steps, and for each step state the instrument, the quantity and the unit. Add a controlled-variables line, a safety line and a data-handling line. Swap methods with a classmate and check whether they could repeat the work from your instructions alone; revise until they can.