Roadmap
Last updated 21 September 2026
What has our attention now, what follows it, and what sits further out. There are no dates here and nothing on this page is a commitment — it is here so you can see what we think is missing before you ask.
Most of what follows is not new functionality. It is the list of things we already tell people we do not have — on our trust centre, and on the continuity and resilience pages beneath it — set out in the order we are closing them. You can check every line on this page against something we have already published against our own interest.
We do not put dates on it. A supplier our size that publishes a delivery date is making a promise it may not be able to keep, and we would rather be held to the support commitment, which we wrote to be keepable every time.
Now
has our attention this term- An independent security test
We sell assurance and we do not think a supplier should self-certify. Our own code has been reviewed thoroughly in-house and the findings fixed; an external test by an accredited firm is the piece that is missing, and arranging it is live work rather than an intention.
- Insurance cover
Professional indemnity and cyber cover are being arranged. We would rather tell a trust where this has got to than have it discovered at questionnaire stage.
- One guide an administrator is handed on day one
There are seventy-odd help articles and they are good, but nobody should have to assemble their own onboarding from them. This is packaging what already exists, not writing new material.
- Walking every surface as a school before anyone relies on it
Parts of the response half — the plan, incidents, the first thirty days — have not been opened by a person since they shipped. We are working through them the way a school would, and fixing what that finds.
Next
picked up as the work above clears- Take everything with you, in one go
You can already export your audit log, your registers and every generated document whenever you like. What does not exist is a single archive of the lot. Until it does, ask us and we will produce it.
- A status page you can check without asking us
Today, if the service is unavailable we email the contacts on your account. That is fine for a handful of schools and stops being fine well before it stops being possible.
- A recovery time we have actually measured
Our restore drills have reached a ready database in minutes, but that measures a restored server rather than a working product. The next drill is specified to time the whole path, so we can give you a real number instead of a partial one.
- Reporting that needs no editing before a governors' meeting
The termly pack is written for a volunteer reading it the evening before. Making more of it true without a human tidying it first is where the next reporting effort goes.
Later
agreed direction, not yet scheduled- A second pair of hands on recovery
Our procedures are documented; nobody other than the founder has executed them. Changing that — through escrow, a named deputy, or both — is a question of company shape as much as engineering, and it gets harder to defer as more schools rely on the service.
- More systems worth connecting
We add a connected system when it answers a question a school is already asking, and we say exactly what each one reads. We would rather read two things honestly than claim five.
- Evidence that assembles itself across a trust
A trust answers for every academy and currently does some of that assembly by hand. Doing more of it centrally, without flattening what makes each academy different, is the direction.
If something you need is not here
Tell us. What a school actually asks for beats our own ordering, and a requirement that arrives with a customer attached to it moves up this page faster than anything we thought of on our own. Email hello@ceidwad.co.uk.