This guide gives superintendents, school business officials, and facilities directors a practical way to evaluate school operations software: how to scope the project, the questions that separate strong vendors from weak ones, procurement realities, red flags, and a checklist you can bring to every demo.
Why does school operations software feel so fragmented?
Most districts and independent schools did not choose their operations stack. It accumulated. Facilities runs work orders in one system. The front office manages visitors in another. Parent communication lives in a third app, or in two apps plus email plus paper flyers in backpacks. Facility rentals for community groups run on a shared spreadsheet and a payment link. Field trip permission slips are still paper.
Each tool was a reasonable purchase on its own. Together they create real problems. Staff learn and juggle five logins. Data never connects, so a closed gym in the work order system does not block a booking in the rental system. Nobody can answer a simple question like "who was on campus last Tuesday afternoon" without checking three places.
When you evaluate new software, the first strategic decision is whether you are replacing one broken tool or consolidating several. That choice shapes everything else in this guide. For background on how a single platform approaches this, see what URBI is and the URBI for schools overview.
How should you scope the evaluation?
Before you talk to any vendor, do three things internally.
Inventory what you already pay for. List every operations tool in use: work orders, visitor management, parent messaging, facility rentals, event ticketing, package handling, board voting. Include the informal ones, like the spreadsheet the athletic director uses for gym bookings, and note each renewal date.
Name the workflows that hurt. Be specific. "Communication is bad" is not a requirement. "An urgent weather closure takes 40 minutes to reach every parent, and we cannot confirm who saw it" is a requirement a vendor can demo against.
Decide who is in the room. Facilities, front office, the business office, IT, and at least one principal should score demos. The people who will live in the software daily will make or break adoption, and they spot weaknesses executives miss.
Then write a short requirements document, five pages at most, organized around workflows rather than feature names. Ask vendors to demo your workflows, not their slide deck.
What questions should you ask every vendor?
One system or five?
Ask the vendor to map your inventory list against their product, honestly. Which of your current tools does it replace outright, which does it partially replace, and which stays? A vendor who claims to replace everything is usually overselling. A vendor who replaces nothing is just adding a sixth login. URBI's answer here is genuinely strong for schools: work orders, parent communication, visitor check in, facility bookings, events, documents, and board governance run in one platform, with one login for staff and one app for parents. Dedicated facilities tools like Brightly and FMX go deeper on some maintenance features; if facilities is your only pain point, read the honest comparisons in URBI vs Brightly and URBI vs FMX.
Who holds facility rental payments?
If community groups pay to use your gym or auditorium, ask exactly where that money sits between payment and deposit. Some platforms hold funds in their own account and remit later. That creates float risk, reconciliation work, and awkward answers in an audit. The better model is direct settlement: URBI sets each school up with its own Stripe connected account, so rental fees, event ticket sales, and activity fees land in the school's own balance. The platform never holds the money. There is a deeper discussion of why this matters in how booking deposits and payments should work.
Can you show me the audit trail?
Public districts answer to boards, auditors, and records requests. Independent schools answer to trustees and accreditors. Either way, ask the vendor to show, live, the log of who did what and when: who approved a vendor, who changed a permission, who voted on a procurement decision, who entered the building and why an entry was denied. In URBI every action, role change, board vote, waiver, check in, payment, and AI action writes to a permanent audit trail. If a vendor cannot pull this up in a demo, assume it does not exist.
How does visitor check in actually protect the campus?
Ask what happens at the front desk when someone arrives. A good system issues QR passes for expected guests, distinguishes guest types like contractor, delivery, and service, notifies the host on arrival, and records every entry attempt with a reason when access is denied, such as an expired clearance or a missing signed waiver. Ask whether contractor background checks and insurance certificates carry expiry dates, so nobody is on campus with stale clearance. And ask about emergencies. URBI pairs check in logging with urgent push messaging to every parent and an emergency takeover on campus display screens, described in real time building communication with URBI Display.
Can every parent actually receive and read your messages?
Reach is the whole game in parent communication. Ask how the system reaches families without an app download, and families who prefer a phone call in their own language. URBI's answer: parents get one app for everything, non account holders like grandparents use a simple one time code portal with no download, and Arthur, the parent facing AI assistant, answers calls, texts, and emails in ten languages. Urgent posts push immediately and the school can see who has seen them.
Will staff actually use it?
Ask three adoption questions. First, how many logins does a teacher, a custodian, and a front office person each need? Second, do outside vendors need accounts and licenses, or can they act on a work order from a simple emailed link? In URBI, vendors never get a login; they schedule, update, and upload completion photos through a tokenized link. Third, what does training look like and who pays for it? Get the training plan in writing before you sign.
What are the contract terms?
Ask about term length, renewal mechanics, and what happens to your data if you leave. Insist on a full data export in a usable format as a contractual right. Ask what implementation costs extra and how long deployment really takes for a district your size. Ask direct technical questions too: does the vendor offer single sign on, a public API, or live sync with your student information system? URBI is honest here: today it imports data through CSV, has no published public API, and does not yet offer operator single sign on. Any vendor should answer these questions as plainly.
What procurement realities should you plan for?
School procurement runs on its own clock. A typical district cycle moves through needs assessment, RFP development, vendor evaluation and scoring, board approval, contract negotiation, and implementation. End to end, that can run from roughly a year to nearly three years for a large deployment, so start earlier than feels necessary.
Cooperative purchasing can compress the front end dramatically. Vehicles like OMNIA Partners, Sourcewell, and NASPO ValuePoint hold publicly awarded contracts that many districts can buy through without running their own solicitation, cutting months out of the process. Ask every vendor which cooperative contracts they hold.
Know your decision makers. Operations leadership typically owns facilities platforms, finance leadership owns anything touching money, technology leadership evaluates security and integration, the superintendent approves the strategic direction, and the board approves contracts above a district set threshold. Map these people early and give each one the evidence they care about.
What are the red flags?
- The vendor will not demo your workflows, only a scripted tour.
- Nobody can show you the audit log live.
- Rental and fee payments pass through the vendor's own bank account.
- Outside contractors need paid licenses just to close a work order.
- Multilingual communication means "parents can use a translation app."
- Data export on exit is vague, slow, or costs extra.
- Roadmap items are presented as shipped. Ask "is this in production today" about every feature you care about.
- The reference customers look nothing like your school or district.
The evaluation checklist
| Area | What to verify | Pass looks like |
|---|---|---|
| Consolidation | Which current tools it replaces | Honest map of replaced vs kept systems |
| Work orders | Triage, assignment, recurring maintenance, vendor access | Full workflow demoed on your scenarios |
| Rental payments | Where money sits between payment and your account | Funds settle to the school's own account |
| Audit trail | Logs of actions, votes, entries, payments | Shown live, permanent, exportable |
| Campus safety | Visitor passes, denial reasons, contractor clearances, emergency alerts | Every entry logged with reason, alerts confirmed as seen |
| Parent reach | App, no app portal, languages, urgent delivery tracking | Reaches families without downloads, multiple languages |
| Adoption | Logins per role, vendor access, training plan | One login for staff, no vendor licenses, written training plan |
| Contract | Term, renewal, data export, implementation cost | Export rights in writing, clear implementation timeline |
| Procurement | Cooperative contracts, references | Named cooperative vehicles, comparable references |
Score each vendor per row with your full evaluation team. If you also run ticketed school events like plays and fundraisers, add a row for ticketing and waitlists; events software for buildings and schools covers what good looks like there.
Frequently asked questions
Should we buy one platform or best of breed point tools?
If one workflow is broken and everything else works, a point tool can be the right call. If you are managing four or more disconnected systems, consolidation usually wins: fewer logins, fewer contracts, one training program, and data that connects. Weigh depth in your hardest workflow against the ongoing cost of stitching separate tools together with staff time.
How long should a district budget for implementation?
Plan for the full procurement cycle, which commonly runs a year or more from needs assessment to deployment for a district. Cooperative purchasing vehicles like Sourcewell or OMNIA Partners can cut months from solicitation. For implementation itself, insist on a phased plan: start with one campus or one workflow, prove adoption, then expand.
Does URBI replace our student information system?
No. URBI covers operations: work orders, parent communication, visitor check in, facility bookings, events, payments, documents, and board governance. Grades, scheduling, and academic records stay in your student information system. Today URBI brings data in through CSV import rather than a live two way sync, so plan the data flow between the two during scoping.
Evaluating operations software is really a decision about how your schools will run for the next decade. Take the checklist to every demo and make vendors prove their answers live. If you want to see how URBI answers them, write to hello@myurbi.co and we will demo your workflows, not ours.
