KENYA · GUIDE 0583 · EDITION 4.2
School website maintenance in Kenya: Risks and Launch Plan
Set the conditions for a safe commercial test
- Child-data exposure
- lost content
- unauthorized notices
A school site loses trust when last year's admissions dates remain prominent or personal student information appears without the institution's authorized process.
A risk list is useful only when it changes a decision. For each risk, write the observable warning, who checks it and the response before the next commitment. Do not treat a reserve of money as permission to continue unsafe or unauthorized work.
Use a small, measurable pilot
Perform one backed-up update using approved non-sensitive material.
The pilot scope is: Maintain school-approved pages with named content owners, term-date checks, staff access controls, and a clear process for sensitive student-related material.
| Gate | Evidence before continuing |
|---|---|
| Scope agreed | Maintain school-approved pages with named content owners, term-date checks, staff access controls, and a clear process for sensitive student-related material. |
| Output acceptable | Ask school staff to verify term information, admissions contacts, downloadable forms, and restricted material, checking that obsolete announcements are clearly removed. |
| Costs recorded | Include update collection, approval coordination, file preparation, link checking, account maintenance, and urgent corrections when schedules or staff responsibilities change unexpectedly. |
| Buyer response recorded | Keep approved changes, source contacts, outdated pages found, access reviews, broken downloads, publication checks, and school acceptance of each maintenance batch. |
Stage the launch around prerequisites
First confirm the buyer specification and activity requirements. Then compare suppliers, establish suitable facilities and prepare the operating record. Run the bounded trial when those prerequisites are in place. Review actual costs, quality failures and cash collected before increasing the commitment.
This sequence is not a promise that the complete business cycle fits into 30 days. Growing periods, qualifications, approvals, seasonal access and customer buying cycles can require longer. Revise the schedule when a prerequisite changes rather than skipping it to meet a launch date.
Choose continue, revise, pause or stop
Continue only when the scoped result is accepted and direct costs and payment timing are workable. Revise one part of the offer if the problem is identifiable and affordable to test again. Pause when required information, permission, skills or resources are missing. Stop the affected work when safety, consent or lawful authority is uncertain.
Keep a maximum test loss and unpaid-balance limit suited to your actual funds. A successful single delivery is useful evidence, but it does not establish year-round demand or justify committing every available resource.
Tie launch milestones to observable checks
| Risk signal | Evidence to inspect | Response to test |
|---|---|---|
| Notice exposes pupil details | Check approval and attachment contents. | Pause publication and route to school's authorised privacy lead. |
| Plugin update breaks downloads | Compare staging versions and test results. | Restore staging and investigate compatibility before any live release. |
| Term date is last year's | Compare source year with page and calendar. | Correct all occurrences and reproof the eight-date list. |
Outstanding go / hold conditions
- School approval, backup restoration and actual software compatibility unverified.
- No real school site or pupil data accessed.
Assign an owner, evidence reference and review date to each unresolved condition. Do not give every milestone a fixed calendar date when it depends on a crop, production, approval or competence cycle. Run only a suitable limited trial, reconcile accepted output and actual cash, and record whether the evidence supports holding, revising, proceeding within the limit or stopping.