Start with exports you already have.

Brightly / SchoolDude work orders

Work-order export shape for campus, asset, vendor, timing, and labor fields.

FMX requests

Request-based facilities export shape for locations, categories, and assigned vendors.

Incident IQ tickets

Helpdesk / facilities crossover tickets with asset tags and priority fields.

ERP PO + invoice export

Purchasing and AP export shape for PO, invoice, amount, campus, and description matching.

Privacy-by-design import posture

• CSV upload and district-managed SFTP are first-class workflows.
• Least-privilege access keeps facilities, AP, executive, and vendor views narrow by role.
• Source systems remain systems of record; DistrictOps operates as a controls and evidence layer.

Need a district-specific mapping pack?

Email hello@pilotgrant.io with your export headers and we can help map Brightly, FMX, Incident IQ, Munis, Frontline, or custom purchasing exports into a pilot-ready shape.

Proof assets for internal champions

Need something you can forward before a meeting? Start with the read-only dashboard and sample exports below.

Sample exports should be reviewed by authorized district staff before board circulation, vendor sharing, or other external distribution.

Pilot launch in three steps

• Request pilot access and tell us which data lanes matter first.
• Upload a first export set or point DistrictOps to a district-managed SFTP drop.
• Review exceptions with facilities and AP, then export weekly proof for cabinet or vendor follow-up.