Hudace

Hudace guide

Write a school ERP RFP before demos

Demos show what a product does well. An RFP makes every vendor answer what your school actually needs.

Keep it to 12 to 20 pages

Cover the school, current systems, modules needed, data protection, migration, training, support, pricing model and how answers are scored.

Write requirements as real tasks

For example: the bursar sends a fee reminder to every parent with a balance over 30 days, in two clicks.

Ask for demos on your own data

Ask to see a family with three children, a sibling discount and a mid-term transport change, including the parent statement.

Ask where your data is hosted

Schools hold sensitive data on children. Ask about hosting region, who at the vendor can access records, and breach reporting.

Takeaway: agree the scoring first

Set weighted criteria before any vendor presents, so trustees can see why one response scored higher than another.

Want the full picture?

A school ERP RFP makes every vendor answer the same questions. What to include, which demos to ask for, and how to score responses fairly.

Book a SchoolOS demo Read the full guide
Book a SchoolOS demo