What a school board or buying committee should ask a software vendor to put in writing

A head teacher can judge a demo in an hour. A board, a proprietor or a buying committee has a harder job. It must compare two or three vendors, justify the choice to parents, and live with the contract for years. Demos do not help much here, because every demo looks good. Written answers do help, because they can be compared and kept.
This guide is for that committee. It is not legal advice. For a contract, ask your own advocate.
Why compare written answers and not demos?
A vendor who answers on a call can change the answer next week. A vendor who writes it down is held to it. Send the same list to each vendor, with a date to reply by. The answers that come back late, vague or "we will discuss on a call" tell you something too.
What does the Office of the Data Protection Commissioner say about buying from a vendor?
The ODPC's Guidance Note for the Education Sector (December 2023) has a section called "Engagement of Data Processors". It says a school that uses a vendor stays responsible as a data controller. The school must show due diligence about the vendor's ability to protect personal data. It also says there must be a written contract between the school and the vendor.
The note lists what that contract should include. This list is useful as a checklist for the committee.
| Contract element named in the ODPC note | Ask the vendor |
|---|---|
| Subject matter of the processing, type of personal data, nature and duration | Where in the contract is this written? |
| Security measures, including regular backups | What do you do, and how often do you test a restore? |
| Staff confidentiality | Are your staff bound by a duty of confidence? |
| Prior authorisation from the school | What may you do with our data only after we agree? |
| Help for the school in meeting its own duties | How do you help with a parent's request to see or correct a record? |
| Delete or return the data at the end of the contract | How do we get our records back, in what form, and when is the rest deleted? |
| Audit and inspection | May we check your measures? |
| Liability if the vendor breaches the contract or acts outside our instructions | What does the contract say? |
The note's example contract has the vendor report any breach promptly to the school. It also says education institutions are expected to register with the ODPC as controllers or processors. Ask each vendor whether it holds its own registration, and ask to see the certificate.
What are the ten questions?
- Price. What is the total per term for my number of learners, in writing, with every module listed? How are learners counted for billing?
- Start-up. What is the setup fee, and what exactly is included in it?
- Moving old records. Which records will you move for us, in what form, and who checks them? Is any of it extra?
- Terms. How long is the contract, how do prices change, and what notice do we give to leave?
- Contract points. Does your processor contract cover every row in the table above? May our advocate read it before we decide?
- Registration. Are you registered with the ODPC? Show us.
- Access and records. Who in our school can see what? Is every change to money, marks and records kept in a trail with a name and a time?
- Leaving. In what form do we take all our records out, and how fast?
- Limits. What can the system not do today? List them in writing.
- Support. Who answers when the bursar is stuck on a Monday, and by what route?
How does Opero answer today?
We would rather say it plainly than leave it for the call.
- Price. KSh 250 per learner per term. Add-ons are flat fees per term by school size: Fees 12,000, 20,000 or 30,000, Transport 10,000, 18,000 or 28,000, and HR and Payroll 8,000, 15,000 or 22,000, for up to 300, 301 to 600 and over 600 learners. Setup is KSh 20,000, or KSh 0 for a school switching from another system. Billing is per term in week 3. There is no discount and no free trial. Ask us to state how learners are counted in the written quote.
- Moving old records. The setup waiver covers the setup fee only. The scope of moving your records is agreed in writing before work starts.
- Contract. Our terms page says the school owns its data and can export it. Our full processor agreement is still a draft for legal review, so have your advocate read it.
- Registration. Opero does not claim to be ODPC-registered or certified. Our own filing is still in preparation.
- Access and records. Staff roles control who sees what, and changes to fees and records go to an audit trail. The system is hosted in Kenya.
- Limits. No SMS, WhatsApp or email alerts to parents yet. No offline use. No timetable builder. No live bus tracking. No screens that join several campuses. Parents see notices in the parent portal. Our own invoice to your school is settled by hand.
If a vendor's list of limits is shorter than ours, ask why.
How should the committee score the answers?
Make a simple table with one row per question and one column per vendor. Mark each cell as "written and clear", "written but vague", or "not given". A vendor with three "not given" cells on questions 3, 5 and 8 has told you how an exit will go. Keep the table with the minutes. It protects the board if a parent asks later why you chose as you did.
Frequently asked questions
Should a school sign a contract before a demo? No. Look at the demo, send the ten questions, read the written answers, and only then take a contract to your advocate.
Does a school stay responsible when the vendor holds its data? Yes. The ODPC education note says the school remains the data controller and must show due diligence about the vendor.
Is Opero registered with the ODPC? No. Our filing is in preparation, and we do not claim registration or certification.
Can one Opero account serve several campuses? Opero has no screens that join several campuses today. Each school is its own account. If you need a joined view, ask us in writing first.
What should we check about leaving a vendor? The form of the export, how fast you get it, and when the vendor deletes the rest. Ask for all three in the contract.
Next step: See Opero's price and Ask for a demo.
Sources: Office of the Data Protection Commissioner, Guidance Note for the Education Sector, December 2023, section "Engagement of Data Processors" and the controller checklist (odpc.go.ke), read on 19 November 2026. Opero's price card and terms page (opero.co.ke/welcome and opero.co.ke/terms, last updated 13 September 2026), read on 19 November 2026, and Opero's own product code, checked on 19 November 2026. This is not legal advice. Written by the Opero team.