Turn Friday budget pressure into calm, campus-level proof.

Best for districts that already feel the handoff pain.

• Roughly 8,000–60,000 students, multiple campuses, and outside vendors touching critical assets.
• Separate CMMS, AP / ERP, and invoice workflows that have to be reconciled during Friday review, month-end close, audit prep, or vendor disputes.
• Teams already exporting data from Brightly / SchoolDude, Incident IQ, FMX, Munis, Frontline, or similar systems.
• Finance + facilities pairs that need proof fast without forcing a rip-and-replace project.

Not built for districts without operational sprawl.

• Single-site organizations that can already trace work to spend in one system.
• Teams that need live transactional write-back before they need weekly proof.
• Districts with no export path and no appetite for reviewer-led exception handling.
• Buyers looking for a full CMMS replacement instead of a reconciliation and controls layer.

1. Import district exports

Start with nightly CSV drops or district-hosted SFTP from CMMS, ERP/AP, helpdesk, and vendor invoice folders.

2. Review matched evidence

DistrictOps links tickets, labor, POs, invoices, assets, and campuses, then scores exceptions for reviewer approval.

3. Export calm proof

Share a weekly Leak Report or vendor evidence pack with audit-ready detail instead of rebuilding the trail in spreadsheets.

Walk into cabinet with proof.

Variance explanations, duplicate-spend review, and campus-level flagged totals land in one weekly leak report instead of spreadsheet archaeology.

Show what keeps breaking and why.

Repeat HVAC, boiler, roofing, and vendor-response loops surface beside the invoices, labor, and SLA drift that finance needs to see.

Keep pilots narrow and defensible.

Export-first setup, least-privilege roles, and vendor-shareable evidence packs make it easier to approve a paid pilot without invasive access.

What the MVP does

• Guided import mapper for CMMS, ERP, invoices, and vendor SLA files
• Confidence-scored matcher with reviewer-in-the-loop
• Per-campus and per-vendor leak dashboards
• Leak Report exports in CSV and PDF evidence-pack format

Why districts can say yes

• Starts with file upload or SFTP, not invasive live integrations
• Least-privilege reviewer roles and narrow evidence sharing
• Designed for AP, facilities, cabinet, audit, and vendor review
• Board-ready outputs in days instead of spreadsheet archaeology

Seeded pilot scenario

• Duplicate spend on a mechanical vendor invoice cluster
• Ghost spend with missing PO / work-order linkage
• Chronic HVAC and boiler repeat failures by campus
• SLA overages on contractor response and close-out times

Leak Report sample

Forward a board-safe snapshot that shows findings, campus totals, and flagged spend without needing district data in the room.

Vendor evidence pack

Show how linked invoices, work orders, overages, and reviewer notes travel together when a contractor dispute starts.

What exports we need

One page for finance, facilities, and procurement: scope, minimum columns, pilot guardrails, and success metrics.