Time per task
Minutes to prepare a report or complete an agreed office task.
GOVERNMENT · SPONSORS · EDUCATION PARTNERS
Better school days.
A measurable start.
Explore a connected school platform through a focused pilot, with evidence to guide expansion.
PROPOSED PILOT
1
schoolOne accountable lead
2–3
workflowsChosen with the school
1
school termEvaluation period to agree
Scope and duration are a starting proposal.
THE WHOLE SCHOOL, IN VIEW
Connected work.
Clearer oversight.
Director
Oversight & approvals
Finance
Accounting & payment trends
HR & admin
People & school operations
Teaching & families
Grades, reports & access
Communication
Staff & family conversations
AI & insights
Questions & review signals
MEASURE THE WORK THAT CHANGES
Agree. Observe.
Review.
Capture a baseline, use the selected workflows and compare equivalent periods. These are proposed measures, not achieved results.
Follow-up effort
Office calls, follow-up time, family participation and access barriers.
Time to review
Time spent reviewing overdue accounts or acting on a learner-support signal.
Agree the baseline, target, evidence owner and review date before starting.
Build a school pilot briefA CLEAR VIEW OF READINESS
What you can
review today.
A demonstration shows the product. Each school rollout also needs its own acceptance evidence.
| Evidence | Current position | Next checkpoint |
|---|---|---|
| Product sourceSchool modules | Director, finance, HR, administration, teaching, families, messaging and AI are represented in the product. | Agree the specific workflows in scope. |
| Local demonstrationFictional accounts | Actual captures show two-way messaging, saved assessments, a refreshed draft report, a leave approval and fee records. | Review the walkthrough and agree remaining acceptance checks. |
| Before rolloutSchool acceptance | Full workflow, access, recovery and customer-environment acceptance remain to be completed. | Record evidence and approve the launch decision. |
CLEAR OWNERSHIP. CLEAR COSTS.
A shared plan
for the pilot.
Your written quote covers
Setup & training + Ongoing service + Agreed provider usage
See the pricing approachThe school
Names a lead, authorises data, involves staff and reviews the outcomes.
Renele
Scopes configuration, training, support and the evidence review.
The public-sector partner or sponsor
Agrees beneficiaries, budget, procurement route and reporting needs.
FOR YOUR REVIEW TEAM
The implementation details.
School environment & access
The installation model separates each school’s deployment, database, files and credentials. Access is assigned by role. School-specific permission and isolation checks form part of acceptance.
Data handling & recovery
Agree authorised imports, retention, access, data export, backup and recovery arrangements. Production evidence for these controls must be reviewed before launch; architecture alone is not certification.
Curriculum & statutory reporting
Confirm assessment structures, reports and required reporting processes. Any SA-SAMS data exchange must be separately scoped and tested. This proposal does not claim an existing integration or government endorsement.
Connectivity, training & support
Validate school devices, connectivity, low-data/mobile use, language and practical access needs. Agree training, coverage hours, escalation and service terms. Offline operation and connectivity performance are not yet established for a school rollout.
AI & human review
AI can support questions, analysis and signals for review. Staff remain responsible for learner-support and financial decisions. Data access, outputs and provider usage require validation in the agreed environment.
Evaluation & publication
Define comparable periods and record staffing or term changes. Review user feedback alongside measures. Publish school identities or case studies only with approval; no pilot results are claimed here.
BRING THE RIGHT PEOPLE TOGETHER
Start with
a review meeting.
Walk through the product, choose a pilot focus and agree the evidence your team needs.
Download the review brief