KENYA · GUIDE 0628 · EDITION 4.2
Computer basics lessons in Kenya: Operations and Quality Checks
Deliver the agreed result consistently
Teach computer basics using the devices and everyday tasks learners will actually use, agreeing starting skills, account access, accessibility needs, and safe practice materials.
The operating sequence for this offer is:
- Confirm the beginner's device access and desired task, then prepare fictional files and a simple checklist for the lesson.
- Demonstrate one action at a time and let the learner perform it, keeping real passwords and personal account details private.
- Ask the learner to create, save and reopen a new document independently, and record which steps still require practice.
Put acceptance into the job record
Each learner completes the practical task without handing over confidential account credentials.
Ask learners to create, save, reopen, and share a practice document independently, checking file location and basic error recovery rather than copied mouse movements alone.
Inspect at the point where a correction is still possible, then again at handover. Record rejected or incomplete output separately from accepted output. A completed task is not automatically an accepted task, and an invoice does not establish that the customer received the right result.
Measure real capacity
Time preparation, the main operation, transport, cleaning, approvals and correction as applicable. The slowest stage determines how much you can promise. Where two orders need the same person, space or equipment at the same time, resolve the conflict before confirming both deadlines. An additional enquiry should not erase a commitment already made.
| Operating checkpoint | Evidence for this business |
|---|---|
| Before starting | Teach computer basics using the devices and everyday tasks learners will actually use, agreeing starting skills, account access, accessibility needs, and safe practice materials. |
| During delivery | Demonstrate one action at a time and let the learner perform it, keeping real passwords and personal account details private. |
| At acceptance | Ask learners to create, save, reopen, and share a practice document independently, checking file location and basic error recovery rather than copied mouse movements alone. |
| At the pilot review | Track starting skills, independently completed tasks, navigation mistakes, saved-file retrieval, access barriers, and learner questions that should change the pacing of future computer lessons. |
Keep a correction and escalation rule
When inputs, access, specifications or customer instructions change, pause the affected work and confirm the effect on time and cost. Do not quietly lower the acceptance standard to avoid a delayed delivery. Keep rework caused by your error distinct from a customer-requested change of scope and agree the remedy clearly.
Lessons fail when learners can follow clicks while the instructor watches but cannot find their saved work or distinguish a local file from an online document.
Retain the minimum records needed to investigate a complaint without disclosing unrelated personal information. Use measured delivery and actual acceptance as the basis for expanding capacity, rather than the maximum theoretical output of a tool or production line.
Operating control points for this exact offer
| Sequence | Work method | Release checkpoint |
|---|---|---|
| 1 | Use an owner-approved local practice location. | Owner enters any login privately. |
| 2 | Create Practice and explain filename versus folder. | Learner locates it independently. |
| 3 | Enter rice, soap and tea on separate lines; save list.txt. | Check exact location and extension. |
| 4 | Close editor and reopen from saved folder. | Unsaved screen text is not accepted as saved work. |
| 5 | Show deleting only the disposable practice file and signing out. | No unrelated files changed or credentials retained. |
Do not substitute a tick for an observation: record the count, measurement, approved sample or evidence reference used at each checkpoint. Mark unresolved work as held and identify who can approve the recheck.
Diagnose a failure before repeating it
| Observed symptom to investigate | Check the cause | Proposed response |
|---|---|---|
| File missing | Check save location and extension. | Search only approved practice folder. |
| Wrong file opens | Compare filename/path. | Rename practice examples clearly. |
| Login blocks lesson | Ask owner to sign in privately. | Do not request password or bypass access. |
These are diagnostic prompts, not proof of the cause in a real incident. Separate suspect output, record any correction and repeat the relevant acceptance check. Link rejected units, rework time, replacement materials, customer credits and collection delays to the actual job result.