PECTECH · Education
Phoenix Nest
A management information system designed around the work a school actually does.
Schools and school groups · product in design
A school record that includes the whole pupil.
Phoenix Nest is being designed as a complete school management information system. Attendance, learning, wellbeing, SEND and statutory work belong around the same pupil record, so support is visible in everyday school operations.
Visit the public product siteAvailability and evidence ↓
Make inclusion part of the core
The design puts wellbeing and SEND alongside the school’s ordinary pupil information, with the assessment and support experience of Ember informing the product.
Run the school’s real work
The specification covers the connected work of records, attendance, assessment, admissions, exams, communication and statutory returns. These are design commitments, not a list of released modules.
Make a switch possible
Migration, interoperability and data portability are part of the design because a school cannot leave its accumulated record behind when it changes systems.
Design relationship · Phoenix Nest
One pupil. Not six disconnected records.
- Attendance
- Learning
- Wellbeing
- SEND
- School operations
- Statutory returns
The design connects these responsibilities. A working school pilot is still the next proof.
Availability and evidence
In design.
PECTECH owns the product and its product IP. Zero Drift is the contracted software builder.
In design for 2027. The public PECTECH brief says it is not yet in build or school use.
The published design horizon is 2027; no released module or school pilot is claimed.
Next evidence: A working school pilot completing core MIS workflows end to end.
