We think this is how a school should run. Here is why.
A clear product argument, with links to the screens that show each workflow.
What we believe
Good teaching should be normal in every section.
School leaders want every section to benefit from clear plans, useful feedback and timely support, regardless of who is teaching that class.
Peach helps schools share those routines across sections while each teacher keeps their professional judgement.
Where common tools stop
Useful tools often cover only one part of the school day.
Videos and question banks help with instruction. Schools still need a place for planning, assessment, attendance and reporting workflows.
Dashboards can show results clearly. Peach also connects the result to the work behind it and the next action a teacher can take.
A general chatbot can use the context supplied in a conversation. Peach is connected to authorised school records and places its output inside school workflows.
What Peach does instead
Peach prepares work inside the school's own controls.
It writes the unit plan from your coordinator's template and proposes marking against your rubric. It drafts the notice home and fills the register from the earlier period.
The school's AI grading policy controls review before release. Attendance and messages to guardians always wait for staff confirmation.
It reads the template, the rubric, the submissions and the outcomes for that section. That is why the draft is worth editing rather than starting over.
Attendance, plans, marks, reports and every approval sit on one record. A change in the register reaches the report without anyone retyping it.
Your school's own templates, whichever board you follow. Guardian notices in five supported languages, with the authored original for other locales. The register, the unit test and the PTM use the words your staff use.
Automation follows the policies the school has chosen.
Review rules, confirmations, permissions and history make it clear what Peach prepared and what the school released.
Where we stay honest
Three claims you will not find on this site.
We separate what the product does today from outcomes that still need to be measured.
We have not measured one, so there is not one here. What you get is the weak section in week two, and you close the loop.
Peach is in use at Woodstock School and Simple Education Foundation. That is the list, and it is the whole list.
It does not. Peach supports teaching and school workflows; the school sets the policies and remains responsible for the result.
Compared with a general chatbot
How Peach differs from a general chatbot.
General chat tools can help staff think and draft. Peach adds school records, roles, policies and workflow history around that assistance.
Compared with Google Classroom
How Peach complements or differs from Google Classroom.
Classroom is widely used to distribute and collect work. Peach covers additional school workflows; exact Classroom capabilities vary by edition and administrator settings.
See how Peach would work in your school.
Set up your classes, import your people, and run one section on it this term.
Prefer email? kanishk@peach.study